Managing HP Serviceguard for Linux Ninth Edition, April 2009
Specifying a Quorum Server
IMPORTANT: The following are standard instructions. For special instructions that
may apply to your version of Serviceguard and the Quorum Server see “Configuring
Serviceguard to Use the Quorum Server” in the latest version HP Serviceguard Quorum
Server Version A.04.00 Release Notes, at http://www.docs.hp.com -> High
Availability -> Quorum Server.
A cluster lock LUN or quorum server, is required for two-node clusters. To obtain a
cluster configuration file that includes Quorum Server parameters, use the -q option
of the cmquerycl command, specifying a Quorum Server hostname or IP address, for
example (all on one line):
cmquerycl -q <QS_Host> -n ftsys9 -n ftsys10 -C <ClusterName>.conf
To specify an alternate hostname or IP address by which the Quorum Server can be
reached, use a command such as (all on one line):
cmquerycl -q <QS_Host> <QS_Addr> -n ftsys9 -n ftsys10 -C
<ClusterName>.conf
Enter the QS_HOST (IPv4 or IPv6 on SLES 10; IPv4 only on Red Hat 5), optional
QS_ADDR (IPv4 or IPv6 on SLES 10; IPv4 only on Red Hat 5), QS_POLLING_INTERVAL,
and optionally a QS_TIMEOUT_EXTENSION; and also check the
HOSTNAME_ADDRESS_FAMILY setting, which defaults to IPv4. See the parameter
descriptions under Cluster Configuration Parameters (page 100).
Obtaining Cross-Subnet Information
As of Serviceguard A.11.18 it is possible to configure multiple IPv4 subnets, joined by
a router, both for the cluster heartbeat and for data, with some nodes using one subnet
and some another. See “Cross-Subnet Configurations” (page 32) for rules and
definitions.
You must use the -w full option to cmquerycl to discover the available subnets.
For example, assume that you are planning to configure four nodes, NodeA, NodeB,
NodeC, and NodeD, into a cluster that uses the subnets 15.13.164.0, 15.13.172.0,
15.13.165.0, 15.13.182.0, 15.244.65.0, and 15.244.56.0.
The following command
cmquerycl –w full –n nodeA –n nodeB –n nodeB –n nodeC –n nodeD
will produce the output such as the following:
Node Names: nodeA
nodeB
nodeC
nodeD
Bridged networks (full probing performed):
Configuring the Cluster 173