Installation Verification

A sample configuration file /opt/acc/cfg/x25_sample.answ file is provided with the ACC Protocols for Application Developers product. This sample file can be used to verify that the X.25 protocol module has been properly installed and is functional. Note that this file will need to be customized to reflect the location of the mux card(s) and to reflect the mux ports to be used. (The x25_sample.answ file is shown at the end of this chapter.)

The steps in the verification process are listed in “Verification Steps”. It is assumed that:

The ACC Protocols for Application Developers product is installed on the system.
The HP-UX kernel has been rebuilt and the system rebooted.
At least one ACC Mux card is installed.
The ACC Mux card has a cable and/or mux panel attached.

At least one loopback cable should be used to connect two of the ports on the mux panel or cabling. For the provided configuration file, it is assumed that the first two ports of the mux card are connected with a loopback cable, and that the end of the cable marked "Internal Clock" (just "INT" for X.21 cable) is connected to port 0.




	NOTE: The loopback cable for the 4-channel E1/T1 multiplexer card has no such requirement. Either end of the cable can be connected to the port.

Verification Steps

The procedure described involves using the zmlog, ttgen, zmntr, and zterm utilities. These utilities are described in the ACC Utilities Reference Guide.

Modify the Mux definition statement in the /opt/acc/cfg/x25_sample.answ to reflect the location of the ACC Mux cards. (Refer to the “Configuration” section in Chapter 3 “ZX25D X.25 Protocol Driver” of this manual for information on how to modify this statement.)
The sample file only configures the first two ports of one mux card. If desired, expand the configuration file to include additional ports.
Note that for the test described here, the ports that will be connected together via the loopback cables must have one port configured as DTE, and the other as DCE. The mux ports must also have one set to internal clocking and the other to external clocking. In the sample configuration file, the even ports are set to internal clocking and the odd ports are set to external clocking. Note that the ports are numbered 0 to 7. Also note that the loopback cable must be connected so that the end marked "Int" is connected to the port configured for internal clocking.

Run ttgen on the modified network configuration (.answ) file.

% ttgen -os x25_sample.answ x25_sample.tmem > x25_sample.tlist
ttgen: END$  0 Disasters, 0 Errors, 0 Warnings
%

Bring up the ZCOM subsystem:

% zmasterd cold /opt/acc/cfg/x25_sample.tmem

It is suggested that the system console (or the appropriate /var/opt/acc/log/*.tlog file, e.g., mon.tlog, tue.tlog, etc.) be monitored to make sure the ZCOM subsystem comes up. The following zmlog messages should be seen:

----------------------------------------------------------------------
Tue Mar  1 09:48:51 2000: zmlog: message logging resumed
----------------------------------------------------------------------
09:48:52 zmon  00002   Resource manager (Rev 1.32) for ZCOM 6.2.0.0
09:48:52 zmon  00003   Cold start with: /opt/acc/cfg/x25_sample.tmem
09:48:52 zmon  00100   Card 0 starting up ...
09:49:00 zmon  00110   Card 0 startup successful, card READY
09:49:00 zmon  00020   Cold start completed, ZCOM system ready
09:49:00 zmon  00004   Waiting for ZMON requests ...
09:49:00 zmast 00101   Launched daemon zx25d_init, pid 862.
09:49:01 zx25d 00643   X25 Protocol server started - Rev: 3.10 - 991201
                       Logical terminal area X25CNT: 88 Bytes            
09:49:19 zcom  00162 3 ZNODE inactive for 20 seconds, all nodes DOWN

Note that the last log message regarding the znode program will be displayed in the case that the znode program is not in use. Refer to the ACC Installation and Configuration Guide for more information on znode.

If zmasterd was configured not to initialize the ACC X.25 subsystem, then run zx25d_init manually to initialize the zx25d driver:

% zx25d_init

The following zmlog messages should be seen on the console or in the zmlog log file:

09:50:10 zx25d 00643     X.25 Protocol server started - Rev: 3.10 - 991201
                         Logical terminal area X25CNT: 88 Bytes
09:50:11 zx25d 00621     Link ZLU 10 HDLC/LAP-B established on enable.
09:50:11 zx25d 00621     Link ZLU 20 HDLC/LAP-B established on enable.
09:50:12 zx25d 00642     Link ZLU 20 X.25 Packet layer (lvl 3) restart complete.
09:50:12 zx25d 00642     Link ZLU 10 X.25 Packet layer (lvl 3) restart complete.

The zmntr utility can be used at this point to show that Level 2 connections have been established:

 % zmntr
 ZMNTR> tt,1,200
 
  ZLU# Mx Pt Terminal Description....Rx.Mes Tx.Mes Error  E.Rate  State.......
  0010 00 0L X25DTE POS  226633004        1      6     0   0.00%  Up,Link Estbd
  0100 00 0V SVCI =n/c   226633011        0      0     0   0.00%  Sd,No Call
  0020 00 1L X25DCE POS  226633004        1      6     0   0.00%  Up,Link Estbd
  0200 00 1V SVCO =n/c   226633011        0      0     0   0.00%  Sd,No Call
  **** ** ** Message totals               2     12     0   0.00%  ************
 
 
 ZMNTR> ex

At this point, the zterm utility can be used to bring up a virtual circuit and transmit data:

% zterm
09:54:36 ZCOM Interactive command utility
09:54:36 Primary ZLU is  803
ZTERM> rc,100,200	 [Set zterm to be receiver for messages to ZLUs 100 to 200.]
ZTERM> cn,100,200,en	 [Issue an "enable" control request to ZLUs 100 to 200.]
ZTERM> cn,100,200,ac	 [Issue an "activate" control request.]
ZTERM> rx
10:33:35 Stat chg (DN) rspns from ZLU#00100(00123) L.C. terminal ENABLED
10:33:35 Stat chg (DN) rspns from ZLU#00200(00123) L.C. terminal ENABLED
10:33:35 Stat chg (UP) rspns from ZLU#00100(00123) L.C. terminal set UP
10:33:35 Stat chg (UP) rspns from ZLU#00200(00123) L.C. terminal set UP
 
 
   <CNTRL-C>
 
10:33:37 Error on ZREAD: Interrupt occurs while waiting
10:33:37 Messages received         4, Messages looped back         0
10:33:37 Elapsed time is      1574 ms
ZTERM> ex

The zmntr utility can be used to show that the Level 3 connections have been established:

% ZMNTR
ZMNTR> tt,1,200
 
 ZLU# Mx Pt Terminal Description....Rx.Mes Tx.Mes Error  E.Rate State.......
 0010 00 0L X25 DTE POS 226633004        2     10     0   0.00% Up,Link Estbd
 0100 00 0V SVCI =0004 226633011         0      0     0   0.00% Up,Call Estbd
 0020 00 1L X25DCE POS 226633004         2     10     0   0.00% Up,Link Estbd
 0200 00 1V SVCO =0004 226633011         0      0     0   0.00% Up,Call Estbd
 **** ** ** Message totals               4     20     0   0.00% ************
 
ZMNTR> ex

Data can now be sent over the established virtual circuit. In this example, messages are sent on ZLU 100. Two messages, 50 bytes in length, are being sent with mode 0. Mode 0 is used to indicate no response is desired.
```
% ZTERM
ZTERM> rc,100,200
ZTERM> tx,100,50,0,2,2
10:06:12 TX test complete!!!
ZTERM> 
```

The sent data can now be received and displayed:

ZTERM> rx,list
10:34:34 Msg from tmnl ZLU#00200(00123) len    50 No error detected
 Lcn .00. .01. .02. .03. .04. .05. .06. .07. .08. .09.  ASCII.....ASCII.....
 000 5A74 3031 3431 3300 206D 6573 7361 6765 206E 6F2E  Zt01413  message no.
 010 2030 3030 3031 206C 656E 6774 6820 2020 2035 3024   00001 length    50$
 020 6F70 7172 7374 7576 7758                           opqrstuvwX
10:34:34 Msg from tmnl ZLU#00200(00123) len    50 No error detected
 Lcn .00. .01. .02. .03. .04. .05. .06. .07. .08. .09.  ASCII.....ASCII.....
 000 5A74 3031 3431 3300 206D 6573 7361 6765 206E 6F2E  Zt01413  message no.
 010 2030 3030 3032 206C 656E 6774 6820 2020 2035 3024   00002 length    50$
 020 6F70 7172 7374 7576 7758                           opqrstuvwX
 
   <CNTRL-C>
 
10:34:42 Error on ZREAD: Interrupt occurs while waiting
10:34:42 Messages received         2, Messages looped back         0
10:34:42 Elapsed time is      7732 ms
ZTERM> ex
%

The ASCII portion of the displayed message can be used to observe the message number. The rx command must be terminated using a <cntrl-C> command.

Installation Verification

Technical documentation

» Table of Contents

Verification Steps