Managing Serviceguard Sixteenth Edition, March 2009

Information about the starting and halting of each package is found in the package’s
control script log. This log provides the history of the operation of the package control
script. By default, it is found at
/etc/cmcluster/<package_name>/control_script.log; but another location
may have been specified in the package configuration file’s script_log_file parameter.
This log documents all package run and halt activities. If you have written a separate
run and halt script for a legacy package, each script will have its own log.
Using the cmcheckconf Command
In addition, cmcheckconf can be used to troubleshoot your cluster just as it was used
to verify the configuration.
The following example shows the commands used to verify the existing cluster
configuration on ftsys9 and ftsys10:
cmquerycl -v -C /etc/cmcluster/verify.ascii -n ftsys9 -n ftsys10
cmcheckconf -v -C /etc/cmcluster/verify.ascii
The cmcheckconf command checks:
• The network addresses and connections.
• The cluster lock disk connectivity.
• The validity of configuration parameters of the cluster and packages for:
— The uniqueness of names.
— The existence and permission of scripts.
It doesn’t check:
• The correct setup of the power circuits.
• The correctness of the package configuration script.
Using the cmviewconf Command
cmviewconf allows you to examine the binary cluster configuration file, even when
the cluster is not running. The command displays the content of this file on the node
where you run the command.
Reviewing the LAN Configuration
The following networking commands can be used to diagnose problems:
• netstat -in can be used to examine the LAN configuration. This command
lists all IP addresses assigned to each LAN interface card.
• lanscan can also be used to examine the LAN configuration. This command lists
the MAC addresses and status of all LAN interface cards on the node.
• arp -a can be used to check the arp tables.
• landiag is useful to display, diagnose, and reset LAN card information.
374 Troubleshooting Your Cluster