HP Serviceguard Quorum Server for Linux Version A.12.00.00 Release Notes, March 2014

The resulting file contains the QS_HOST, QS_POLLING_INTERVAL, and QS_TIMEOUT_EXTENSION
parameters, and the QS_ADDR parameter if your version of Serviceguard supports it. In that case,
the Quorum Server section of the file looks like this:
# for the quorum server timeout, enter
# QS_HOST qs_host
# QS_ADDR qs_addr
# QS_POLLING_INTERVAL 120000000
# QS_TIMEOUT_EXTENSION 2000000
QS_HOST gf2_qs1
QS_ADDR 15.106.73.114
QS_POLLING_INTERVAL 300000000
If your version of Serviceguard supports alternate subnets, but you are working with an existing
cluster configuration file that does not contain the QS_ADDR parameter, you can add this parameter,
and its value, yourself.
You can use the optional QS_TIMEOUT_EXTENSION to increase the time interval (in microseconds)
after which the current connection (or attempt to connect) to the quorum server is deemed to have
failed; see “Network recommendations” (page 7).
NOTE: Increasing this value will increase the failover time accordingly; that is, if failover time is
currently 30 seconds and you set QS_TIMEOUT_EXTENSION to one second, the failover time will
increase to 31 seconds.
Setting Quorum Server parameters for IPv6 subnets
Serviceguard A.11.19 clusters support IPv6 addresses for both QS_HOST and QS_ADDR, but you
must apply the July 2009 patch to Serviceguard A.11.19 if you want to supply IPv6 addresses,
or hostnames that resolve only to IPv6 addresses, to cmquerycl. See the latest Serviceguard
release notes for information about the patch.
Requirements for using IPv6 subnets
If you are using an IPv6 subnet, or subnets, to connect the Quorum Server to the cluster, make sure
the following requirements are met:
• If the Quorum Server is on a different subnet from the cluster, you must use an IPv6–capable
router.
• All the IPv6 addresses used by the cluster nodes to connect to the Quorum Server must be
listed in the Quorum Server's authorization file. See “Creating and updating the authorization
file” (page 14).
These IPv6 addresses must also be resolvable on the Quorum Server.
IMPORTANT: In the case of an IPv6–only Quorum Server, this means that the addresses
must be listed in /etc/hosts, as you cannot use DNS or NIS for name resolution in an
IPv6–only Serviceguard cluster. Similarly, in an IPv6–only cluster, the Quorum Server's IPv6
addresses must be listed in the cluster nodes' /etc/hosts.
See “About Hostname Address Families: IPv4-Only, IPv6-Only, and Mixed Mode” in Chapter 4
of Managing Serviceguard for more information.
Configuring IPv6 addresses without the July 2009 patch
If you have not applied the patch, you can still use IPv6 addresses, but you must generate the
cluster configuration file using an IPv4 address, then edit it to supply the IPv6 address(es) you will
actually use.
Proceed as follows to create two IPv6 connections to the Quorum Server if you have not applied
the July 2009 Serviceguard patch:
Configuring Serviceguard to use the Quorum Server 11