Run zmasterd with the
desired .tmem file. Note that
zmasterd does not need to be started with the same .tmem file as configured in the zmasterd_list file. It is highly
recommended, however, that the same file be used in both places.
The .tmem file configured in the zmasterd_list will
be used in the case that zmon abnormally
terminates and zmasterd needs to restart it.
Watch the console or /var/opt/acc/log/xxx.tlog (e.g. mon.tlog, tue.tlog).
If it is successful, it will look like this:
--------------------------------------------------------------
Mon June 30 15:55:53 1998: zmlog: message logging resumed
--------------------------------------------------------------
15:48:54 zcom 00000 System bootup
15:55:52 zmast 00101 Launched daemon zmlog, pid 622.
15:55:52 zmast 00117 Zmasterd daemon start running ...
15:55:52 zmast 00101 Launched daemon zmon, pid 624.
15:55:53 zmon 00002 Resource manager (Rev 1.32) for ZCOM 6.2.0.0
15:55:53 zmon 00003 Cold start with: /opt/acc/cfg/loopback.tmem
15:55:54 zmon 00100 Card 0 starting up ...
15:55:55 zmon 00100 Card 1 starting up ...
15:56:11 zmon 00110 Card 0 startup successful, card READY
15:56:11 zmon 00110 Card 1 startup successful, card READY
15:56:11 zmon 00020 Cold start completed, ZCOM system ready
15:56:11 zmon 00004 Waiting for ZMON requests ...
15:56:11 zmast 00101 Launched daemon znode, pid 260.
15:56:11 zmast 00101 Launched daemon zx25d_init, pid 261.
15:56:11 zx25d 00643 X.25 Protocol server started - Rev: 3.10 - 03012000
Logical terminal area X25CNT: 88 Bytes
Once the X.25/ACC subsystem is successfully started up, x25init can be run on the appropriate x25init configuration files to bring
up the Level 2 X.25 connections.
Printable version
