Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Troubleshooting Your Cluster
Replacing a Failed Quorum Server System
Chapter 8 271
Replacing a Failed Quorum Server System
When a quorum server fails or becomes unavailable to the clusters it is
providing quorum services for, this will not cause a failure on any cluster.
However, the loss of the quorum server does increase the vulnerability of
the clusters in case there is an additional failure. Use the following
procedure to replace a defective quorum server system. If you use this
procedure, you do not need to change the configuration of any cluster
nodes.
1. Remove the old quorum server system from the network.
2. Set up the new system and configure it with the old quorum server’s
IP address and hostname.
3. Install and configure the quorum server software on the new system.
Be sure to include in the new QS authorization file (for example,
/usr/local/qs/conf/qs_authfile) on all of the nodes that were
configured for the old quorum server. Refer to the qs(1) man page for
details about configuring the QS authorization file.
NOTE The quorum server reads the authorization file at startup. Whenever
you modify the file qs_authfile, run the following command to force
a re-read of the file. For example on a Red Hat distribution:
# /usr/local/qs/bin/qs -update
On a SuSE distribution:
# /opt/qs/bin/qs -update
4. Start the quorum server as follows:
• Edit the /etc/inittab file to add the quorum server entries, as
shown in “Running the Quorum Server” on page 135 above.
•Use the init q command to run the quorum server.
Or
• Create a package in another cluster for the Quorum Server as
shown in “Creating a Package for the Quorum Server” on
page 136 above.