Systems Without Mux Cards

Loopback Configuration File

A loopback configuration file /opt/acc/cfg/loopback.answ is created when the ACC product is installed on the system. The ttgen program is automatically run to create the file /opt/acc/cfg/loopback.tmem. This occurs whether or not there are any ACC interface cards installed in the system. The loopback.tmem file will be adequate to bring up the ACC Subsystem.

The section “Sample ttgen Configuration File” of Appendix A “Files, Utilities, and Daemons” shows a sample ttgen configuration file. The file created when no ACC cards are in the system is similar, but the Interface-Definition, Port-Definition, and Terminal-Definition sections of the file are empty (i.e. there are no Mux, Port, or Term entries in the file).

Bringing Up ZCOM Mux Subsystem

Before any features of the ZCOM Mux Subsystem can be accessed, the subsystem must be started up by running zmasterd with an appropriate .tmem file. The /opt/acc/cfg/loopback.tmem file should be used, followed by performing the loopback verification test:

# zmasterd cold /opt/acc/cfg/loopback.tmem

Messages indicating whether or not the ZCOM Mux subsystem was started successfully are 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. In this example, the /opt/acc/cfg/loopback.answ file was created for a system with no ACC 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, and znode.

If an error is reported during the start up procedure, it may 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 to /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 of zmasterd.

Performing Verification Test

The “ZNODE - Remote Node Daemon” chapter of the ACC Utilities Reference Guide contains an example of how to demonstrate that the znode and remote node processing is functioning correctly.