Record and Playback Program
Overview
The Record Program (G1000-Record) allows a
user to spool (record) inbound data from any protocol or port on a Gateway 1000 (G1000) to the
G1000's hard drive. The data can be retrieved for analysis or retransmission (playback) through
the same or different line and protocol at a later time. The data can be spooled to the hard
drive while it is also being sent to the other connection or only spooled for later playback.
The program runs on any Gateway
1000 and provides several benefits, including:
- Enhanced logging
- Data capture for stress testing
- Store and forward
- Off-line testing
- Extended diagnostics
The data is always stored in the same format using JBM Standard
Headers. When the data is played back,
it can be routed to any of the configured ports and protocols on
the G1000. Alternatively, the spooled data can be retrieved through
the FTP.
Features
The Configuration Program provides
complete control over the spooling functions used in this program. The configuration
options are:
| Journal size |
Each sub-address can be defined from
1 MB to 4 GB. A 30 GB hard drive is provided for the spooled files. |
| File Name |
The file name and path can be
specified for easy management. |
| Wrap function |
When the allocated size is reached,
the recording can be set to stop or overwrite the oldest data. |
| Error notification |
Error messages can be incorporated
into the log. |
Operation
The recording of the individual
sub-address can be enabled or disabled through a Telnet command. Once the sub-address
recording is enabled, the data from the inbound line will be sent to the destination
port (if enabled) and also converted to the standard format. This data will be spooled
to the specified file on the G1000's hard drive.
The playback of the spooled file
can be started through a Telnet command. The data is converted from the standard format
and routed to a destination port and protocol. This mechanism allows messages to be
received from one protocol and transmitted to another protocol. An example would be
spooling bisync messages and sending them out TCP or receiving messages in multicast
UDP and sending them out as TCP/IP.
The stored message file will be
maintained in the Gateway until the file is overwritten through the message wrap
function or deleted through manual action or a script file.
| 
