Modify the interface definition statement
in the /opt/acc/cfg/lapb_sample.answ to reflect the location of the ACC Mux cards if necessary.
(Refer to Chapter 4 “Protocol Specific Configuration” in this manual for information
on how to modify this statement.) Also modify the <card-type> term
for the Interface-Definition statement to "z7200a",
or your card type.
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 connected together via a loopback cable 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.
Also note that for 2-port and 8-port cards 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 -o lapb_sample.answ lapb_sample.tmem
ttgen: END$ 0 Disasters, 0 Errors, 0 Warnings
%
Bring up the ZCOM subsystem:
% zmasterd cold /opt/acc/cfg/lapb_sample.tmem
Monitor the appropriate /var/opt/acc/log/*.tlog file, e.g. mon.tlog, tue.tlog, etc., to make sure the ACC ZCOM subsystem comes up.
The following zmlog messages should be seen:
-------------------------------------------------------------------
MON JUN 16 13:36:25 1998: ZMLOG: MESSAGE LOGGING RESUMED
-------------------------------------------------------------------
13:36:11 ZNODE 00109 zcom SYSTEM DOWN, EXITING
13:36:11 ZMAST 00129 STOPPING ZMLOG DAEMON.
13:36:11 ZMON 00049 END OF zMON REQUEST, PROGRAM TERMINATED
13:36:11 ZMON 00075 zcom SYSTEM STOPPED
13:36:24 ZMAST 00101 LAUNCHED DAEMON ZMLOG, PID 1433.
13:36:24 ZMAST 00117 ZMASTERD DAEMON START RUNNING ...
13:36:24 ZMAST 00101 LAUNCHED DAEMON ZMON, PID 1434.
13:36:25 ZMON 00002 RESOURCE MANAGER (REV 1.32) FOR zcom 6.2.0.0
13:36:25 ZMON 00003 COLD START WITH: LAPB_SAMPLE.TMEM
13:36:25 ZMON 00100 CARD 0 STARTING UP ...
13:36:32 ZMON 00110 CARD 0 STARTUP SUCCESSFUL, CARD READY
13:36:32 ZMON 00020 COLD START COMPLETED, zcom SYSTEM READY
13:36:32 ZMON 00004 WAITING FOR ZMON REQUESTS ...
13:36:32 ZMAST 00101 LAUNCHED DAEMON ZNODE, PID 1455.
13:36:32 ZCOM 00165 NODE 123 IS NOW
The zmntr utility
can be used to display the original state of the HDLC link:
ZMNTR> tt 10 20
ZLU# MX P:SC TERMINAL DESCRIPTION.. RX.MES TX.MES ERRORS E.RATE STATE.......
0010 00 0:00 HDLC LINK 1 0 0 0 0.00% DISABLED
0020 00 1:00 HDLC LINK 2 0 0 0 0.00% DISABLED
**** ** ** MESSAGE TOTALS 0 0 0 NAN% ***********
ZMNTR> ex
#
The link can now be enabled using the zterm utility:
# zterm
13:40:09 ZCOM INTERACTIVE COMMAND UTILITY
13:40:09 PRIMARY ZLU is 801
ZTERM> rc 10 20
ZTERM> cn 10 20 EN
ZTERM> rx
13:40:29 STAT CHG (UP) RSPNS FROM ZLU#00020(00123) NO ERROR DETECTED
13:40:29 STAT CHG (UP) RSPNS FROM ZLU#00010(00123) NO ERROR DETECTED
<CNTRL-C>
13:40:37 ERROR ON ZREAD: INTERRUPT OCCURS WHILE WAITING
13:40:37 MESSAGES RECEIVED 2, MESSAGES SENT 0
13:40:37 ELAPSED TIME SECS 8, MESSAGES/SEC 0
13:40:37 DATA IN KBytes 0, DATA RATE (KB/S) 0
13:40:37 Sys CPU 0%, User CPU 0%, TOTAL CPU 0%
13:40:37 MUX 0 UTILIZATION 1%
ZTERM> EX
The zmntr utility
can be used to observe the state of the link:
ZMNTR> tt 10 20
ZLU# MX P:SC TERMINAL DESCRIPTION.. RX.MES TX.MES ERRORS E.RATE STATE.......
0010 00 0:00 HDLC LINK 1 0 0 0 0.00% DEACTIVATED
0020 00 1:00 HDLC LINK 2 0 0 0 0.00% DEACTIVATED
**** ** ** MESSAGE TOTALS 0 0 0 NAN% ************
ZMNTR> EX
The link can now be brought up using the zterm utility:
# zterm
13:42:40 ZCOM INTERACTIVE COMMAND UTILITY
13:42:40 Primary ZLU is 801
ZTERM> rc 10 20
ZTERM> cn 10 20 ac [Activate the link.]
ZTERM> ex
|
| |
|
| NOTE: Note that no status change will be received for the
activate request. |
|
| |
|
The zmntr utility
can be used to observe the state of the link:
ZMNTR> tt 10 20
ZLU# MX P:SC TERMINAL DESCRIPTION.. RX.MES TX.MES ERRORS E.RATE STATE.......
0010 00 0:00 HDLC LINK 1 0 0 0 0.00% Up
0020 00 1:00 HDLC LINK 1 0 0 0 0.00% Up
**** ** ** Message totals 0 0 0 .00% **
ZMNTR> ex
Data can now be sent over the established link. In this
example, two 50 byte messages are sent on ZLU 10 using
zsend mode 0 (indicating that no response is desired when
messages have been sent).
% zterm
13:44:28 ZCOM INTERACTIVE COMMAND UTILITY
13:44:28 Primary ZLU is 801
ZTERM> rc 10 20
ZTERM> tx 10 50 0 2 2
13:44:45 TX test complete!!!
ZTERM>
The sent data can now be received and displayed:
ZTERM> rx list
13:44:51 Msg from tmnl ZLU#00020(00123) len 50 No error detected
Lcn .00. .01. .02. .03. .04. .05. .06. .07. .08. .09. ASCII.....ASCII.....
000 5A74 3031 3534 3100 206D 6573 7361 6765 206E 6F2E Zt01541 message no.
010 2030 3030 3031 206C 656E 6774 6820 2020 2035 3024 00001 length 50$
020 6F70 7172 7374 7576 7758 opqrstuvwX
13:44:51 Msg from tmnl ZLU#00020(00123) len 50 No error detected
Lcn .00. .01. .02. .03. .04. .05. .06. .07. .08. .09. ASCII.....ASCII.....
000 5A74 3031 3534 3100 206D 6573 7361 6765 206E 6F2E Zt01541 message no.
010 2030 3030 3032 206C 656E 6774 6820 2020 2035 3024 00002 length 50$
020 6F70 7172 7374 7576 7758 opqrstuvwX
<CNTL-C>
13:44:53 Error on ZREAD: Interrupt occurs while waiting
13:44:53 Messages received 2, Messages sent 0
13:44:53 Elapsed time secs 2, Messages/sec 1
13:44:53 Data in KBytes 0, Data rate (KB/s) 0
13:44:54 Sys CPU 0%, User CPU 2%, Total CPU 2%
13:44:54 Mux 0 utilization 1%
ZTERM> ex
The ASCII part of the displayed message can be used
to observe the message number. The rx command
must be terminated using a <cntrl-C> command.
Printable version
