Managing HP Serviceguard A.11.20.00 for Linux, June 2012

Reviewing Configuration Files
Review the following ASCII configuration files:
• Cluster configuration file.
• Package configuration files.
Ensure that the files are complete and correct according to your configuration planning worksheets.
Reviewing the Package Control Script
For legacy packages, ensure that the package control script is found on all nodes where the
package can run and that the file is identical on all nodes. Ensure that the script is executable on
all nodes. Ensure that the name of the control script appears in the package configuration file, and
ensure that all services named in the package configuration file also appear in the package control
script.
Information about the starting and halting of each package can be found in the package’s control
script log. This log provides the history of the operation of the package, including all package run
and halt activities. The location of the file is determined by the script_log_file parameter
(page 161) in the package configuration file. If you have written a separate run and halt script for
a legacy package, each script will have its own log.
Using the cmquerycl and cmcheckconf Commands
In addition, cmquerycl and cmcheckconf can be used to troubleshoot your cluster just as they
were used to verify its configuration. The following example shows the commands used to verify
the existing cluster configuration on ftsys9 and ftsys10:
cmquerycl -v -C $SGCONF/verify.conf -n ftsys9 -n ftsys10
cmcheckconf -v -C $SGCONF/verify.conf
cmcheckconf checks:
• The network addresses and connections.
• Quorum Server connectivity, if a quorum server is configured.
• Lock LUN connectivity, if a lock LUN is used.
• 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.
Reviewing the LAN Configuration
The following networking commands can be used to diagnose problems:
• ifconfig can be used to examine the LAN configuration. This command lists all IP addresses
assigned to each LAN interface card.
• arp -a can be used to check the arp tables.
• cmscancl can be used to test IP-level connectivity between network interfaces in the cluster.
• cmviewcl -v shows the status of primary LANs.
Use these commands on all nodes.
232 Troubleshooting Your Cluster