Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Troubleshooting Your Cluster
Replacing a Failed Quorum Server System
Chapter 8 293
• 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://docs.hp.com ->High
Availability ->Quorum Server.
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:
•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.