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

Enter into the file the fully-qualified hostnames, or IP addresses, of all the cluster nodes that will
obtain quorum services from this Quorum Server. Use one line per node, for example:
ftsys9.localdomain.com
ftsys10.localdomain.com
NOTE: If you are specifying an alternate subnet (for clusters running a version of Serviceguard
that supports it, you must specify both IP addresses by which each node can be reached, for
example:
ftsys9.localdomain.com
10.10.10.20 #alternate IP address on ftsys9
ftsys10.localdomain.com
10.10.10.21 #alternate IP address on ftsys10
To allow access by any system, enter a plus sign (+).
After modifying this file, you must force the Quorum Server to re-read it:
• Red Hat:
/usr/local/qs/bin/qs -update
• SUSE:
/opt/qs/bin/qs -update
IMPORTANT:
• If you enable the ip_strong_es_model parameter on HP-UX cluster nodes, make sure that
you list all relocatable IP addresses that are associated with the per-interface default gateways
in the Quorum Server's authorization file.
For more information about ip_strong_es_model, see “Tuning Network and Kernel
Parameters” in Chapter 5 of the latest version of the Managing Serviceguard manual, and
the HP-UX IPSec Version A.03.00 Administrator's Guide, available at www.hp.com/go/
hpux-security-docs under HP-UX IPSec Software .
• If the Quorum Server serves a mixed-mode or IPv6–only cluster, make sure that all the IPv6
addresses from which cluster nodes can reach the Quorum Server are listed in the authorization
file (or use the plus sign to allow access from any system). See also “Setting Quorum Server
parameters for IPv6 subnets” (page 11).
For more information about the authorization file, see the qs(1) man page.
Replacing a failed Quorum Server system
Use the following procedure to replace a defective Quorum Server system without changing 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(es) and
hostname(s).
NOTE: If you have configured the cluster to communicate with the Quorum Server on more
than one subnet, the new Quorum Server must be able to communicate with all cluster nodes
on both subnets, using the same IP addresses as the old.
3. Install and configure the Quorum Server software on the new system.
Be sure to include in the new Quorum Server authorization file all of the nodes that were
configured for the old Quorum Server; see “Creating and updating the authorization file”
(page 14).
Replacing a failed Quorum Server system 15