Managing HP Serviceguard A.11.20.10 for Linux, December 2012

4. Start the quorum server as follows:
• Use the init q command to run the quorum server.
Or
• Create a package in another cluster for the Quorum Server, as described in the Release
Notes for your version of Quorum Server. They can be found at http://www.hp.com/
go/hpux-serviceguard-docs (Select (HP Serviceguard Quorum Server Software).
5. All nodes in all clusters that were using the old quorum server will connect to the new quorum
server. Use the cmviewcl -v command from any cluster that is using the quorum server to
verify that the nodes in that cluster have connected to the QS.
6. The quorum server log file on the new quorum server will show a log message like the following
for each cluster that uses the quorum server:
Request for lock /sg/<ClusterName> succeeded. New lock owners: N1, N2
7. To check that the quorum server has been correctly configured and to verify the connectivity
of a node to the quorum server, you can execute the following command from your cluster
nodes as follows:
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.
8.7 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
8.7.1 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
246 Troubleshooting Your Cluster