HP-UX HB v13.00 Ch-15 - Serviceguard
HP-UX Handbook – Rev 13.00 Page 93 (of 108)
Chapter 15 Serviceguard
October 29, 2013
When the command is complete, the prompt appears. Verify the quorum server is running by
checking the qs.log file.
root@QS:/ # cat /var/adm/qs/qs.log
The log should contain entries like the following indicating the quorum server has started:
Oct 04 12:25:06:0:main:Starting Quorum Server
Oct 04 12:25:09:0:main:Server is up and waiting for connections at port 1238
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
increases the vulnerability of the client clusters to TOC if split-brain failure occurs. 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 (/etc/cmcluster/qs_authfile) 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.
4. Start the quorum server as follows:
• Edit the /etc/inittab file to add the quorum server entries.
• Use the init q command to run the quorum server.
Refer to the qs(1) man page for more details.
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:
root@Node1:/ # cmquerycl –q qhost –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: