HP Serviceguard Quorum Server Version A.04.00 Release Notes, revised August 2009

NOTE: If you are specifying an alternate subnet (for clusters running a version of Serviceguard
that supports it; see “Compatibility with Serviceguard Versions” (page 10)) 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:
• For HP-UX: /usr/lbin/qs -update
• For Linux:
— 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, which you can find on docs.hp.com under Internet
and Security Solutions —> IPSec.
• 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 15).
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 18).
4. Start the Quorum Server as follows:
• Edit the /etc/inittab file to add the Quorum Server entries, as shown in “Installing
the Quorum Server” (page 10).
• Use the init q command to run the Quorum Server.
Replacing a Failed Quorum Server System 19