Installation Verification

A sample configuration file /opt/acc/cfg/lapd_4ch_sample.answ file is provided with the ACC Developer Software Suite product. This sample file can be used to verify that the HDLC/LAP-D protocol module has been properly installed and is functional. Note that you need to customize this file, to reflect the location of the mux card(s) and to reflect the mux ports to be used. (The lapd_4ch_sample.answ file is shown in Appendix A “Sample Configuration Files”.)

The steps in the verification process are listed below. It is assumed that the ACC Developer Software Suite product is installed on the system, and that there is at least one ACC Multiplexer card installed with cabling attached.

A loopback cable should be used to connect two of the ports on the multiplexer. For the configuration file provided, it is assumed that the first two ports of the mux card are connected with a loopback cable.

Using the HDLC/LAP-D Protocol Module

The ACC Installation and Configuration Guide contains the general procedure for configuring the network configuration file, and starting up the ACC subsystem with the new protocol and new configuration. Refer to Chapter 4 “Protocol Specific Configuration” for HDLC/LAP-D specific configuration requirements when building the network configuration file.

Verification Procedure

The procedure described involves using the 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/lapd_4ch_sample.answ to reflect the location of the ACC Mux cards if necessary. (Refer to Chapter 4 “Protocol Specific Configuration” 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: For the test described here, the ports that will be logically connected together must have one port configured as DTE, and the other as DCE.
Run ttgen on the .answ file.
```
% ttgen -o lapd_4ch_sample.answ lapd_4ch_sample.tmem
ttgen: END$  0 Disasters, 0 Errors, 0 Warnings
%
```

Bring up the ZCOM subsystem:

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

Monitor the log file:

It is suggested that 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 could be seen:

---------------------------------------------------------------------------
Tue Jun 17 11:28:55 1998: zmlog: message logging resumed
---------------------------------------------------------------------------
 
11:28:54 zmast 00101   Launched daemon zmlog, pid 1704.
11:28:54 zmast 00117   Zmasterd daemon start running ...
11:28:54 zmast 00101   Launched daemon zmon, pid 1705.
11:28:55 zmon  00002   Resource manager (Rev 1.32) for ZCOM 6.1.0.0
11:28:55 zmon  00003   Cold start with: lapd_4ch_sample.tmem
11:28:55 zmon  00100   Card 0 starting up ...
11:28:58 zmon  00110   Card 0 startup successful, card READY
11:28:58 zmon  00020   Cold start completed, ZCOM system ready
11:28:58 zmon  00004   Waiting for ZMON requests ...
11:28:58 zmast 00101   Launched daemon znode, pid 1726.
11:28:59 zcom  00165   Node 123 is now UP

The zmntr utility can be used to display the state of the HDLC/LAP-D link:

% zmntr
ZMNTR> tt 600 601
 ZLU# Mx p:sc Terminal Description....   Rx.Mes Tx.Mes Errors E.Rate State......
 0600 00 0:01  LAP-D DCE                      0      0      0  0.00% Disabled
 0601 00 1:01  LAP-D DTE                      0      0      0  0.00% Disabled
 **** ** ** Message totals                    0      0      0 NaN  % ********
ZMNTR> ex

The link can now be enabled and brought up using the zterm utility:

% zterm
11:34:46 ZCOM Interactive command utility
11:34:46 Primary ZLU is 1001
ZTERM> rc 600 601
ZTERM> cn 600 601 en
ZTERM> cn 600 601 ac
ZTERM> ex
%

The zmntr utility can be used to observe the state of the link:

%  zmntr
ZMNTR> tt 600 601
 ZLU# Mx p:sc Terminal Description...  Rx.Mes Tx.Mes Errors E.Rate State.......
 0600 00 0:01  LAP-D DCE                    0      0      0  0.00% Up
 0601 00 1:01  LAP-D DTE                    0      0      0  0.00% Up
 **** ** ** Message totals                  0      0      0 NaN  % ********
ZMNTR> ex

With the zterm utility set as a receiver, test messages are sent from the ZLUs:
```
% zterm
11:46:56 ZCOM Interactive command utility
11:46:56 Primary ZLU is 1001
ZTERM> rc 600 601
ZTERM> tx 600 50 0 2 2
11:47:14 TX test complete!!!
ZTERM>
```
NOTE: For this example two fifty-byte messages are transmitted from DCE to DTE.

The received data can now be displayed:

ZTERM> rx list
11:49:49 Msg from tmnl ZLU#00601(00123) len    50 No error detected
 Lcn .00. .01. .02. .03. .04. .05. .06. .07. .08. .09.  ASCII.....ASCII.....
 000 5A74 3031 3739 3800 206D 6573 7361 6765 206E 6F2E  Zt01798  message no.
 010 2030 3030 3031 206C 656E 6774 6820 2020 2035 3024   00001 length    50$
 020 6F70 7172 7374 7576 7758                           opqrstuvwX
 
11:49:49 Msg from tmnl ZLU#00601(00123) len    50 No error detected
 Lcn .00. .01. .02. .03. .04. .05. .06. .07. .08. .09.  ASCII.....ASCII.....
 000 5A74 3031 3739 3800 206D 6573 7361 6765 206E 6F2E  Zt01798  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>

11:50:36 Error on ZREAD: Interrupt occurs while waiting
11:50:36 Messages received         2,    Messages sent            0
11:50:36 Elapsed time secs        47,    Messages/sec             0
11:50:36 Data in KBytes            0,    Data rate (KB/s)         0
11:50:36 Sys CPU   0%, User CPU   0%,    Total CPU   0%
11:50:36 Mux   0 utilization      1%
ZTERM>

Installation Verification

Technical documentation

» Table of Contents

» Index

Using the HDLC/LAP-D Protocol Module

Verification Procedure