Managing Serviceguard Nineteenth Edition, Reprinted June 2011

NOTE: While the old Quorum Server is down and the new one is being set up, these things can
happen:
• These three commands will not work:
cmquerycl -q
cmapplyconf -C
cmcheckconf -C
• 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.
NOTE: Make sure that the old Quorum Server system does not rejoin the network with the old
IP address.
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
NOTE: HP recommends you use Serviceguard Manager as a convenient way to observe the
status of a cluster and the properties of cluster objects: from the System Management Homepage
(SMH), select the cluster you need to troubleshoot.
Reviewing Package IP Addresses
The netstat -in command can be used to examine the LAN configuration. The command, if
executed on ftsys9 after ftsys10 has been halted, shows that the package IP addresses are
assigned to lan0 on ftsys9 along with the primary LANIP address.
ftsys9>netstat -in
IPv4:
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
ni0# 0 none none 0 0 0 0 0
ni1* 0 none none 0 0 0 0 0
lo0 4608 127 127.0.0.1 10114 0 10 0 0
lan0 1500 15.13.168 15.13.171.14 959269 0 33069 0 0
lan0:1 1500 15.13.168 15.13.171.23 959269 0 33069 0 0
lan0:2 1500 15.13.168 15.13.171.20 959269 0 33069 0 0
lan1* 1500 none none 418623 0 55822 0 0
IPv6:
Name Mtu Address/Prefix Ipkts Opkts
lan1* 1500 none 0 0
lo0 4136 ::1/128 10690 10690
Reviewing the System Log File
Messages from the Cluster Manager and Package Manager are written to the system log file. The
default location of the log file is /var/adm/syslog/syslog.log. Also, package-related
messages are logged into the package log file. The package log file is located in the package
316 Troubleshooting Your Cluster