Managing Serviceguard Eighteenth Edition, September 2010

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.
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
Troubleshooting Approaches 409