Software Installation and Verification
Installation Verification
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
Step 3. Bring up the ZCOM subsystem:
% zmasterd cold /opt/acc/cfg/lapd_4ch_sample.tmem
Step 4. 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 11:28:54 zmast 00117 11:28:54 zmast 00101 11:28:55 zmon 00002 11:28:55 zmon 00003 11:28:55 zmon 00100 11:28:58 zmon 00110 11:28:58 zmon 00020 11:28:58 zmon 00004 11:28:58 zmast 00101 11:28:59 zcom 00165
Launched daemon zmlog, pid 1704. Zmasterd daemon start running ...
Launched daemon zmon, pid 1705.
Resource manager (Rev 1.32) for ZCOM 6.1.0.0 Cold start with: lapd_4ch_sample.tmem
Card 0 starting up ...
Card 0 startup successful, card READY Cold start completed, ZCOM system ready Waiting for ZMON requests ...
Launched daemon znode, pid 1726. Node 123 is now UP
Step 5. The zmntr utility can be used to display the state of the
% zmntr |
|
|
|
|
|
|
|
ZMNTR> tt 600 | 601 |
|
|
|
|
| |
ZLU# Mx p:sc | Terminal Description.... | Rx.Mes Tx.Mes Errors E.Rate State | |||||
0600 00 | 0:01 | 0 | 0 | 0 | 0.00% | Disabled | |
0601 00 | 1:01 | 0 | 0 | 0 | 0.00% | Disabled | |
**** ** ** Message totals | 0 | 0 | 0 | NaN % ******** | |||
ZMNTR> ex |
|
|
|
|
|
| |
Chapter 2 | 21 |
