Bringing Up Zcom Mux Subsystem - HP 9000 Installation And Configuration Manual

Software Installation and Verification
Installation Verification
# zmasterd cold /opt/acc/cfg/loopback.tmem
------------------------------------------------------------------
Tue Jun 20 16:45:38 1998: zmlog: message logging resumed
------------------------------------------------------------------
16:45:37 zmast 00101
16:45:37 zmast 00117
16:45:37 zmast 00101
16:45:38 zmon 00002
16:45:38 zmon 00003
16:45:39 zmon 00100
16:45:39 zmon 00100
16:45:46 zmon 00110
16:45:46 zmon 00110
16:45:46 zmon 00020
16:45:46 zmon 00004
16:45:46 zmast 00101
16:45:57 zcom 00165
42

Bringing Up ZCOM Mux Subsystem

Before any of the features of the ZCOM Mux Subsystem can be accessed,
it must be started up by running zmasterd (located in /opt/acc/bin) with
an appropriate .tmem file. The /opt/acc/cfg/loopback.tmem file should
be used, followed by performing the loopback verification test:
Messages indicating whether or not the ZCOM Mux subsystem was
started successfully will be logged to the file
/var/opt/acc/log/XXX.tlog, where XXX represents the day of the week
(i.e. mon.tlog, tue.tlog, etc.).
The following listing is an example of what might be displayed when the
ZCOM Mux subsystem is started successfully. Note that in this example,
the /opt/acc/cfg/loopback.answ file is configured to start up two mux
cards.
Launched daemon zmlog, pid 10663.
Zmasterd daemon start running...
Launched daemon zmon, pid 10665.
Resource manager (Rev 1.32) for ZCOM 6.2.0.0
Cold start with: /opt/acc/cfg/loopback.tmem
Card 0 starting up ...
Card 1 starting up ...
Card 0 startup successful, card READY
Card 1 startup successful, card READY
Cold start completed, ZCOM system ready
Waiting for ZMON requests ...
Launched daemon znode, pid 10674.
Node 123 is now UP
Chapter 2