ACC Installation and Configuration Guide

52 Chapter2
Software Installation and Verification
Systems Without Mux Cards
interface cards installed:
------------------------------------------------------------------
Tue Jun 20 18:14:35 1998: zmlog: message logging resumed
------------------------------------------------------------------
18:14:34 zmast 00101 Launched daemon zmlog, pid 2709.
18:14:34 zmast 00117 Zmasterd daemon start running...
18:14:34 zmast 00101 Launched daemon zmon, pid 2711.
18:14:35 zmon 00002 Resource manager (Rev 1.32) for ZCOM 6.2.0.0
18:14:35 zmon 00003 Cold start with: /opt/acc/cfg/loopback.tmem
18:14:43 zmon 00020 Cold start completed, ZCOM system ready
18:14:43 zmon 00004 Waiting for ZMON requests ...
18:14:43 zmast 00101 Launched daemon znode, pid 2729.
18:14:54 zcom 00165 Node 123 is now UP
Zmasterd starts the daemons that are listed with “start” statements in
the /opt/acc/cfg/zmasterd_list file. For the base ACC product, it starts
the zmlog logging facility, zmon,andznode.
If an error is reported during the start up procedure, it m ay be necessary
to stop the ZCOM subsystem by running:
# zmasterd stop
The error should then be addressed, and then the ZCOM subsystem
should be restarted. Refer to the ACC Error Guide for a description of
messages reported by zmlog.
Note that file /opt/acc/cfg/zmasterd_list refers t o
/opt/acc/cfg/loopback.tmem by default. If another .tmem file will be
used, it is suggested that the /opt/acc/cgf/zmasterd_list file be updated
accordingly. Refer to the ACC Utilities Reference Guide for more
information on the use o f zmasterd.
Performing Verification Test
The“ZNODE-RemoteNodeDaemon”chapteroftheACC Ut ilities
Reference Guide contains an example of how to demonstrate that the
znode and remote node processing is functioning correctly.