 |
» |
|
|
|
|  | |
A sample configuration file /opt/acc/cfg/hdlcnrm_sample.answ file
is provided with the ACC Protocols for Application Developers product. This
sample file can be used to verify that the HDLC-NRM (SDLC) 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 hdlcnrm_sample.answ file is shown
in Appendix A of this manual.) The steps in the verification process are listed below. It
is assumed that the ACC Protocols for Application Developers product
is installed on the system, and that the ACC base product has already
been installed and the system has been regenerated and rebooted.
It is also assumed that there is at least one ACC Mux card installed,
and that it has a cable and mux panel attached. At least one loopback cable should be used to connect two
of the ports on the mux panel. For the configuration file provided,
it is assumed that the first two ports of the mux card are connected
with an RS-232 loopback cable, and that the end of the cable marked "Int" is
connected to port 0. Using the HDLC-NRM (SDLC) Protocol Module | |
The ACC Installation and Configuration Guide contains
the general procedure for configuring the ttgen configuration file,
creating customized downloadable firmware files, and starting up
the ACC subsystem with the new protocol and new configuration. To
add HDLC-NRM (SDLC) to a firmware file, see “Download Linkage” in Appendix A “Sample Configuration Files”. Refer to Chapter 4 “Protocol Specific Configuration” of this manual for HDLC-NRM
(SDLC) specific configuration requirements when building the network
configuration file. Verification Procedure | |
The procedure described involves using the zmlog, ttgen, zmntr, and zterm utilities.
These utilities are described in the ACC Utilities Reference
Guide. Modify the Bus:Slot[slot] terms
in the Interface-Definition statement in the /opt/acc/cfg/hdlcnrm_sample.answ file
if necessary, to reflect the actual location of the ACC Mux cards.
Also modify the <card-type> term to
reflect your specific card type (replace <card-type> with
z7400a, for example.) Refer to Chapter 4 “Protocol Specific Configuration” of this manual
for information on how to modify these statements. 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
with primary stations, and the other with secondary stations. 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 .answ file. % ttgen -o hdlcnrm_sample.answ hdlcnrm_sample.tmem
ttgen: END$ 0 Disasters, 0 Errors, 0 Warnings
%
Bring up the ZCOM subsystem: % zmasterd cold /opt/acc/cfg/hdlcnrm_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 14 13:10:22 2000: zmlog: message logging resumed
-------------------------------------------------------------------
13:10:22 znode 00109 ZCOM system down, exiting
13:10:22 zmast 00129 Stopping zmlog daemon.
13:10:22 zmon 00049 End of ZMON request, program terminated
13:10:22 zmon 00075 ZCOM system stopped
13:12:06 zmast 00101 Launched daemon zmlog, pid 1350.
13:12:06 zmast 00117 Zmasterd daemon start running ...
13:12:06 zmast 00101 Launched daemon zmon, pid 1351.
13:12:07 zmon 00002 Resource manager (Rev 1.32) for ZCOM 6.2.0.0
13:12:07 zmon 00003 Cold start with: hdlcnrm_sample.tmem
13:12:07 zmon 00100 Card 0 starting up ...
13:12:15 zmon 00110 Card 0 startup successful, card READY
13:12:15 zmon 00020 Cold start completed, ZCOM system ready
13:12:15 zmon 00004 Waiting for ZMON requests ...
13:12:15 zmast 00101 Launched daemon znode, pid 1372.
13:12:15 zcom 00165 Node 123 is now UP
Use the zmntr utility
to display the original state of the HDLC-NRM (SDLC) terminals: % zmntr
ZMNTR> tt 1 20
ZLU# Mx p:sc Terminal Description..... Rx.Mes Tx.Mes Error E.Rate State.
0001 00 0:00 HDLC/NRM Primary A 0 0 0 0.00% Disabled
0002 00 0:00 HDLC/NRM Primary B 0 0 0 0.00% Disabled
0011 00 1:00 HDLC/NRM Secondary A 0 0 0 0.00% Disabled
0012 00 1:00 HDLC/NRM Secondary B 0 0 0 0.00% Disabled
**** ** ** Message totals 0 0 0 0.00% *******
ZMNTR> ex
Use the zterm utility
to enable and activate the HDLC-NRM (SDLC) terminals: % zterm
13:13:43 ZCOM Interactive command utility
13:13:43 Primary ZLU is 801
ZTERM> rc 1 20
ZTERM> cn 1 20 en
ZTERM> cn 1 20 ac
ZTERM> rx
13:14:03 Stat chg (UP) rspns from ZLU#00011(00123) No error detected
13:14:03 Stat chg (UP) rspns from ZLU#00001(00123) No error detected
13:14:03 Stat chg (UP) rspns from ZLU#00012(00123) No error detected
13:14:03 Stat chg (UP) rspns from ZLU#00002(00123) No error detected
<CNTRL-C>
13:14:06 Error on ZREAD: Interrupt occurs while waiting
13:14:06 Messages received 4, Messages sent 0
13:14:06 Elapsed time secs 3, Messages/sec 1
13:14:06 Data in KBytes 0, Data rate (KB/s) 0
13:14:06 Sys CPU 0%, User CPU 1%, Total CPU 1%
13:14:06 Mux 0 utilization 5%
ZTERM> ex
You can now use the zmntr utility
to observe the state of the link: % zmntr
ZMNTR> tt 1 20
ZLU# Mx p:sc Terminal Description.... Rx.Mes Tx.Mes Error E.Rate State.
0001 00 0:00 HDLC/NRM Primary A 0 0 0 0.00% Up
0002 00 0:00 HDLC/NRM Primary B 0 0 0 0.00% Up
0011 00 1:00 HDLC/NRM Secondary A 0 0 0 0.00% Up
0012 00 1:00 HDLC/NRM Secondary B 0 0 0 0.00% Up
**** ** ** Message totals 0 0 0 0.00% *******
ZMNTR> ex
Data can now be sent over the established links between
primary and secondary terminals. In this example, one 40 byte message
is sent to one of the two primary terminals and another to one of
the two secondary terminals: % zterm
13:49:07 ZCOM Interactive command utility
13:49:07 Primary ZLU is 801
ZTERM> rc 1 20
ZTERM> tx 1 40 0 1
13:49:55 TX test complete!!!
ZTERM> tx 12 40 0 1
13:50:04 TX test complete!!!
The data sent can now be received and displayed. Note
that the message sent to ZLU 1 is received from ZLU 11, and similarly
the message sent to ZLU 12 is received from ZLU 2, because of the
loopback configuration. ZTERM> rx li
13:50:12 Msg from tmnl ZLU#00011(00123) len 40 No error detected
Lcn .00. .01. .02. .03. .04. .05. .06. .07. .08. .09. ASCII.....ASCII.....
000 5A74 3031 3532 3500 206D 6573 7361 6765 206E 6F2E Zt01525 message no.
010 2030 3030 3031 206C 656E 6774 6820 2020 2034 3024 00001 length 40$
13:50:12 Msg from tmnl ZLU#00002(00123) len 40 No error detected
Lcn .00. .01. .02. .03. .04. .05. .06. .07. .08. .09. ASCII.....ASCII.....
000 5A74 3031 3532 3500 206D 6573 7361 6765 206E 6F2E Zt01525 message no.
010 2030 3030 3031 206C 656E 6774 6820 2020 2034 3024 00001 length 40$
<CNTRL-C>
13:51:13 Error on ZREAD: Interrupt occurs while waiting
13:51:13 Messages received 2, Messages sent 0
13:51:13 Elapsed time secs 61, Messages/sec 0
13:51:13 Data in KBytes 0, Data rate (KB/s) 0
13:51:13 Sys CPU 0%, User CPU 0%, Total CPU 0%
13:51:13 Mux 0 utilization 7%
ZTERM> ex
| | | | | NOTE: The zterm rx command
must be terminated by using a <cntrl-c> command. | | | | |
|
Printable version
