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

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; see “Compatibility with Serviceguard Versions” (page 12))
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
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 22).
4. Start the Quorum Server as follows:
Replacing a Failed Quorum Server System 23