Managing Serviceguard A.11.20, March 2013

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.
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 NIC information.
• linkloop verifies the communication between NICs at MAC address levels. For example,
if you enter
linkloop -i4 0x08000993AB72
you should see displayed the following message:
Link Connectivity to LAN station: 0x08000993AB72 OK
• cmscancl can be used to verify that primary and standby LANs are on the same bridged
net.
• cmviewcl -v shows the status of primary and standby LANs.
Use these commands on all nodes.
Solving Problems
Problems with Serviceguard may be of several types. The following is a list of common categories
of problem:
• Serviceguard command hangs
• Networking and security configuration errors
• Cluster re-formations
• System administration errors
338 Troubleshooting Your Cluster