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

Network recommendations
• Ideally the Quorum Server and the cluster or clusters it serves must communicate over a subnet
that does not handle other traffic. (If you are using a version of Serviceguard that supports
more than one subnet for communication with the Quorum Server, this must be true for all
subnets.) This helps to ensure that the Quorum Server is available when it is needed.
If this is not practical, or if the communication must cover a long distance (for example, if the
Quorum Server is serving an Extended Distance cluster) heavy network traffic or network
delays could cause Quorum Server timeouts. You can reduce the likelihood of timeouts by
increasing the Quorum Server timeout interval; use the QS_TIMEOUT_EXTENSION parameter
in the cluster configuration file. See “Configuring Serviceguard to use the Quorum Server”
(page 9) and “Setting Quorum Server parameters in the cluster configuration file” (page 10).
• If a subnet that connects the Quorum Server to a cluster is also used for the cluster heartbeat,
configure the heartbeat on at least one other network, so that both Quorum Server and
heartbeat communication are not likely to fail at the same time.
Compatibility with Serviceguard versions
This version of the Quorum Server supports:
Linux distributions.
• Serviceguard clusters running Serviceguard A.11.19 or later on HP-UX 11i v2 or 11iv3.
• Serviceguard clusters running Serviceguard A.11.18 or later on supported Red Hat or SUSE
Linux distributions.
IMPORTANT:
• Quorum Server version A.12.00.00 supports alternate subnet for communication with a
Serviceguard A.11.19 or later cluster.
• If you are running Serviceguard A.11.19 or later, and want to use an IPv6 connection between
the cluster and the Quorum Server, you must apply the July 2009 patch to Serviceguard. See
the latest Serviceguard release notes for information about this patch.
The patch is required for IPv6-only clusters, but it is also possible to configure IPv6 connections
without the patch; see “Configuring IPv6 addresses without the July 2009 patch” (page 11)
for instructions.
• You will need to apply Cluster Object Manger (COM) patch PHSS_35372 in order to use
the older, station-management version of Serviceguard Manager to manage a cluster that uses
more than one subnet for communication with the Quorum Server.
For complete compatibility information, see the latest version of HP Serviceguard Quorum Server
Compatibility Matrix available at http://www.hp.com/go/linux-serviceguard-docs.
Installing the Quorum Server
Read this entire document and any other Release Notes you may have before you begin an
installation.
The Quorum Server software, which must be running during cluster configuration, must be installed
on a system other than the nodes on which your cluster will be running. This could be a single
Linux system, or it could be a separate cluster.
If you are updating from an older version of Quorum Server, see the instructions below.
IMPORTANT: Order is important if you are updating Quorum Server and also updating
Serviceguard. You must update Quorum Server before updating Serviceguard. See the instructions
below.
Compatibility with Serviceguard versions 7