Setting Up the Network Configuration File

The first step is to configure the analyzer ports into the ttgen configuration file. A sample file is supplied with the product to illustrate how the configuration should be done. This file is called /opt/acc/cfg/x25an_sample.answ, or x25an_4ch_sample.answ for E1/T1 cards. A full listing of these files is given at the end of this appendix. Some parts of these files are used below to illustrate the configuration process.




	NOTE: If the sample file is to be used as a test of the product, ensure that the multiplexer bus and slot numbers are changed in the file so that they correspond to the actual position of the multiplexer card.

Mux Firmware Download File

The Frame capture protocol used by the X.25 Protocol Analyzer is provided in all the downloadable files. The X.25 Protocol Analyzer may be used with any of these files.

The mux firmware download file is specified in the network configuration file in the card-type statement. For example:

z7200a 0 0:4 /opt/acc/z7200a/x25.zabs

Each multiplexer that is to run X.25 connections, or Data Analyzer ports, will need a card-type entry, such as z7200a. The bus and slot numbers must correspond to the physical position of the interface card. Refer to the ACC Installation and Configuration Guide for more information on determining the hardware location.

Port Definitions

Each port on each multiplexer card to be used for the Data Analyzer must be correctly configured to support the Frame capture firmware protocol. In the 8-channel sample shown below, ports 2 to 7 on mux 0 are used for analyzer ports. Note the following configuration requirements:

Select the correct mux and port for each analyzer connection.
Set RS232 mode for both RS-232 and V.35 analyzer ports.
The baud rate is not important but set for an expected nominal rate (57600 chosen here).
The Clocking option must be set to Ext.
The Mode, clock multiplier, and encoding must be set to SDLC, x1, and NRZ. If NRZI encoding is used set this to NRZI instead.

Port 00:00   RS232   57600   Int SDLC x1 NRZ
Port 00:01   RS232   57600   Ext SDLC x1 NRZ
Port 00:02   RS232   57600   Ext SDLC x1 NRZ
Port 00:03   RS232   57600   Ext SDLC x1 NRZ
Port 00:04   RS232   57600   Ext SDLC x1 NRZ
Port 00:05   RS232   57600   Ext SDLC x1 NRZ
Port 00:06   RS232   57600   Ext SDLC x1 NRZ
Port 00:07   RS232   57600   Ext SDLC x1 NRZ

In the example file, mux 0 ports 0 and 1 are used for a sample X.25 connection that is looped back between these ports. Use the loopback cable supplied with the selected ACC interface panel to connect these ports (see Figure B-1 “Connections For 8-Channel Example”). Ensure the end marked Internal is connected to port 0, and the end marked External is connected as described below. Connect the Y-cable as shown. The connector designated “P2” on the Y-cable goes to the connector marked External on the loopback cable. See also Appendix A “Analyzer Cable Assemblies” for more detailed description of the Y-cable.

Figure B-1 Connections For 8-Channel Example

ZLU Definitions

Finally the ZLUs to be used for the Analyzer session must be defined. Take care to define these carefully since errors in these definitions may not be detected by ttgen. If there are such errors they may not be detected until the ports are used.

            Term 0019 0:2 HDLC.FRAME    0  0   90 20 1 0 0 "Protocol Analyzer"
            Term 0020 0:3 HDLC.FRAME    0  0   90 19 2 0 0 "Protocol Analyzer"
            Term 0021 0:4 HDLC.FRAME    0  0   90 22 1 0 0 "Protocol Analyzer"
            Term 0022 0:5 HDLC.FRAME    0  0   90 21 2 0 0 "Protocol Analyzer"
            Term 0023 0:6 HDLC.FRAME    0  0   90 24 1 0 0 "Protocol Analyzer"
            Term 0024 0:7 HDLC.FRAME    0  0   90 23 2 0 0 "Protocol Analyzer"

Follow the steps below to configure the ZLUs, refer to the examples above for clarification. In the example, ZLUs 19 and 20 form an analyzer pair, so do 21 and 22, and 23 and 24.

Choose ZLU numbers for each of the analyzer ports so they are unique within the whole ttgen configuration file.
Note the ZLU numbers for each analyzer pair; there should always be an even number of analyzer ZLUs.
Set the mux:port numbers so they correspond to the ports defined in the “Port Definitions” section.
Select the HDLC.FRAME protocol for each of the analyzer ZLUs, and set the “poll” and “select” configuration parameters to zero (0) .
Set the Application number to 90. If this is not set correctly the pcapture and pdisplay programs will not be able to find the analyzer ZLUs. (Use the pdisplay command show when the software is running, to ensure the ZLUs have been correctly configured.)
Set the parameter after the 90 (application number) to the partner ZLU number. In the example, the partner ZLU for 19 is 20, for 21 is 22, etc.
Set the next parameter to 1 if the port is to be the DTE (TX monitor) port, and 2 if it is to be the DCE (RX monitor port). Note that the DTE/DCE definitions for partner ZLUs must be different.
Set the last two parameters to 0.
The port description (“Protocol Analyzer,” above) may have any string of up to 30 characters. This is a comment field and its value will not affect the analyzer operation. The field is displayed by ZMNTR and may be used for application or operational description, for example, “Backup X.25 link monitor.”

Running TTGEN and Starting the ACC Mux

Once the network configuration is complete, the file must be compiled by ttgen. To run ttgen use the following command:

   $ ttgen -o file.answ file.tmem

Here file.answ is the source file that has just been set up, and file.tmem is the output file to be used by zmon to start the ACC Mux system. For example, to compile the sample file:

   $ ttgen -o /opt/acc/cfg/x25an_sample.answ \
              /opt/acc/cfg/x25an_sample.tmem

Here the -o option allows a previous copy of the output file /opt/acc/cfg/x25an_sample.tmem to be overwritten if it already exists.

If there are inconsistencies in the configuration file, ttgen may report errors or warnings. These should be corrected and ttgen rerun until it runs without error.

Once ttgen has been successfully run, ACC Mux subsystem must be restarted (note this command must be executed as superuser). First stop ACC Mux using:

   $ zmasterd stop

Starting ACC Subsystem and Analyzer

Once the ttgen file is properly configured, the ACC Mux subsystem can be started using the appropriate .tmem file.

$ zmasterd cold /opt/acc/cfg/x25an_sample.tmem

Once ACC Mux is up and running, start the pcapture daemon.

 $ pcapture

The pcapture program can also be started automatically with the ACC Mux Subsystem by adding the statement “start pcapture” to the file /opt/acc/cfg/zmasterd_list. This will cause zmasterd to automatically start this program.

Pcapture runs as a daemon and reports its errors to the ACC Mux message file. If pcapture is not running correctly, look at the end of the daily ACC Mux log file, or on the system console if console logging has been enabled for ACC Mux. The log file name depends on the day of the week (i.e., /var/opt/acc/log/mon.tlog is Monday's file).

To look at the end of this file:

$ tail -20 /var/opt/acc/log/mon.tlog

This will display the last 20 lines of the log file.

When pcapture is started successfully only the revision message should appear; if pcapture is having problems it will display some reasons and then terminate. In the second example more than one copy of pcapture has been started, so the second one fails and terminates.

19:11:38 pcapt 00001   Protocol analyzer capture program Rev B.11.00
 
21:04:55 pcapt 00001   Protocol analyzer capture program Rev B.11.00
21:04:55 pcapt 00004   Program already running - terminating this copy
21:04:55 pcapt 00007   End of pcapture

Running PDISPLAY

Once pcapture has been successfully started, pdisplay may be run. It may be run interactively, or may be run as single commands. For example just specifying pdisplay alone puts it into the interactive mode:

$ pdisplay
  Display>

The prompt Display> indicates pdisplay is ready for interactive commands. Starting pdisplay with a command following the program name causes it to execute the single command and terminate, for example:

  Exit program
  $

This method may be used to save the display output from a capture file to a file, or to pipe the output to more:

$pdisplay display /var/opt/acc/log/sample.eve > printfile
$
 
$pdisplay display  /var/opt/acc/log/sample.eve -e 1 200 | more

Refer to the section on “Detailed Command Descriptions”"Detailed Command Descriptions" for more information on the possible commands and options.