HP-UX HB v13.00 Ch-15 - Serviceguard
HP-UX Handbook – Rev 13.00 Page 92 (of 108)
Chapter 15 Serviceguard
October 29, 2013
operation. If you use a different subnet, you may experience network delays which may cause
quorum server timeouts. To prevent these timeouts, you can use the
QS_TIMEOUT_EXTENSION parameter in the cluster configuration file to increase the quorum
server timeout interval.
The Quorum Server 3.0 allows cluster nodes to communicate with the QS on an alternate subnet.
For more information please refer to: http://docs.hp.com/en/B8467-90041/B8467-90041.pdf
If the network used to connect to the quorum server is a cluster heartbeat network, ensure that at
least one other network is also a heartbeat network so that both quorum server and heartbeat
communication are not likely to fail at the same time.
Installing the Quorum Server
The quorum server executable file, qs, is installed in the /usr/lbin directory. When the installation
is complete, you need to create an authorization file on the server where the QS will be running
to allow specific host systems to obtain quorum services. The required pathname for this file is
/etc/cmcluster/qs_authfile. Add to the file the names of all cluster nodes that will access cluster
services from this quorum server. Use one line per node, as in the following example:
Node1.localdomain.com
Node2.localdomain.com
To allow access by all nodes, enter the plus character (+) on its own line.
Specifying a Quorum Server
To specify a quorum server instead of a lock disk, use the -q option of the cmquerycl command,
specifying a Quorum Server host server. Example:
root@Node1:/ # cmquerycl -n Node1 -n Node2 -q qshost
Running the Quorum Server
The quorum server must be running during the following cluster operations:
when the cmquerycl command is issued.
when the cmapplyconf command is issued.
when there is a cluster re-formation.
By default, quorum server run-time messages go to stdout and stderr. It is suggested that you
create a directory /var/adm/qs, then redirect stdout and stderr to a file in this directory, for
example, /var/adm/qs/qs.log.
On a single system, configure the quorum server to start up any time the system on which it is
installed restarts or reboots. Do this by creating an entry like the following in the /etc/inittab file:
qs:345:respawn:/usr/lbin/qs >> /var/adm/qs/qs.log 2>&1
Start the quorum server as follows:
root@QS:/ # init q