Managing HP Serviceguard for Linux Ninth Edition, April 2009

cmquerycl -q <QSHostName> -n <Node1> -n <Node2> ...
The command will output an error message if the specified nodes cannot
communicate with the quorum server.
CAUTION: Make sure that the old system does not rejoin the network with the old
IP address.
NOTE: While the old quorum server is down and the new one is being set up:
The cmquerycl, cmcheckconf and cmapplyconf commands will not work
The cmruncl, cmhaltcl, cmrunnode, and cmhaltnode commands will work
If there is a node or network failure that creates a 50-50 membership split, the
quorum server will not be available as a tie-breaker, and the cluster will fail.
Troubleshooting Approaches
The following sections offer a few suggestions for troubleshooting by reviewing the
state of the running system and by examining cluster status data, log files, and
configuration files. Topics include:
Reviewing Package IP Addresses
Reviewing the System Log File
Reviewing Configuration Files
Reviewing the Package Control Script
Using cmquerycl and cmcheckconf
Using cmviewcl
Reviewing the LAN Configuration
Reviewing Package IP Addresses
The ifconfigcommand can be used to examine the LAN configuration. The command,
if executed on ftsys9 after the halting of node ftsys10, shows that the package IP
addresses are assigned to eth1:1 and eth1:2 along with the heartbeat IP address on eth1.
eth0 Link encap:Ethernet HWaddr 00:01:02:77:82:75
inet addr:15.13.169.106 Bcast:15.13.175.255 Mask:255.255.248.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:70826196 errors:0 dropped:0 overruns:1 frame:0
TX packets:5741486 errors:1 dropped:0 overruns:1 carrier:896
collisions:26706 txqueuelen:100
Interrupt:9 Base address:0xdc00
eth1 Link encap:Ethernet HWaddr 00:50:DA:64:8A:7C
inet addr:192.168.1.106 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2337841 errors:0 dropped:0 overruns:0 frame:0
TX packets:1171966 errors:0 dropped:0 overruns:0 carrier:0
collisions:6 txqueuelen:100
278 Troubleshooting Your Cluster