Managing HP Serviceguard A.12.00.00 for Linux, June 2014

Dec 14 14:39:36 star04 CM-pkg4[2127]: cmrunserv Service4 /vg01/MyPing 127.0.0.1
>>/dev/null
Dec 14 14:39:36 star04 cmcld[2098]: Started package pkg4 on node star04.
10.7.3 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.
10.7.4 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.
10.7.5 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.
10.8 Solving Problems
Problems with Serviceguard may be of several types. The following is a list of common categories
of problem:
• Serviceguard Command Hangs.
• Cluster Re-formations.
• System Administration Errors.
• Package Control Script Hangs.
276 Troubleshooting Your Cluster