HP Serviceguard Quorum Server Version A.04.
Legal Notices © Copyright 2006-2009 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Table of Contents Printing History ..................................................................................................................5 1 HP Serviceguard Quorum Server Version A.04.00 Release Notes..........................7 Announcements......................................................................................................................................7 Cluster Name Restrictions..................................................................................................
List of Tables 1 1-1 1-2 4 Printing History...............................................................................................................................5 Package Configuration File Parameters for qs-pkg.....................................................................16 Package Control Script Parameters for qs-pkg..............................................................................
Printing History Table 1 Printing History Printing Date Part Number Edition March 2009 B8467-90045 First Edition July 2009 B8467-90048 Second Edition The last printing date and part number indicate the current edition.
1 HP Serviceguard Quorum Server Version A.04.00 Release Notes Announcements This edition of the release notes provides information about Quorum Server version A.04.00. This version supports Serviceguard versions A.11.14 and later on HP-UX and Linux, and provides the following new capabilities: • Allows Serviceguard A.11.19 cluster nodes to communicate with the Quorum Server on an alternate subnet; see “Using Alternate Subnets” (page 13).
The version of the software you download is determined by the operating system you specify on the download page. Documentation for This Version These release notes are shipped with Quorum Server Version A.04.00, and published under Quorum Server at http://docs.hp.com -> High Availability. Updated versions are published on that site as they become available. See also the white paper Arbitration for Data Integrity in Serviceguard Clusters, under Quorum Server at http://docs.hp.com -> High Availability.
If the Quorum Server is not available or reachable, it will not adversely affect any clusters using it, unless a cluster needs to reform and requires the Quorum Server’s arbitration to do so. As of Serviceguard A.11.19, you can change from one quorum server to another, or to or from another quorum method, while the cluster is running. IMPORTANT: For more information, see “What Happens when You Change the Quorum Configuration Online” in Chapter 3 of Managing Serviceguard.
Server” (page 13) and “Setting Quorum Server Parameters in the Cluster Configuration File” (page 14). • 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: • • Serviceguard clusters running Serviceguard 11.
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. Installing on HP-UX Use the swinstall command to install the Quorum Server, product number B8467BA, on the system or systems where it will run. You must install the Quorum Server on a node outside the cluster (or clusters) that it will serve.
When the installation is complete, you need to create an authorization file on the server where the Quorum Server will be running, to allow specific host systems to obtain quorum services. See “Creating and Updating the Authorization File” (page 18). Now create a directory for the Quorum Server log file. The recommended pathnames are in Table 1-2 (page 17). (You may need to create thedirectory.
1. Comment out the Quorum Server entry in /etc/inittab and run the following command: /sbin/init q 2. Uninstall the existing Quorum Server. For example: rpm -e qs-A.02.04 CAUTION: This command may remove the file /var/log/qs/qs.log. If this is your log file, you may want to save it before running this command. 3. Install the version of Quorum Server A.04.00 appropriate to your distribution and hardware. For example: rpm -ihv qs-A.04.00.00-0.sles10.i386.rpm 4. 5.
Requirements for Using Alternate Subnets All of the following must be true in order for you to configure more than one subnet for communication between the Quorum Server and the cluster nodes: • • You must be running a version of Serviceguard, and of Quorum Server, that support this capability. See “Compatibility with Serviceguard Versions” (page 10), and “System Requirements and Recommendations” (page 9).
# 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.
1. 2. 3. 4. Change the value of the QS_HOST parameter to an IPv6 address, or a hostname that resolves to an IPv6 address. Add the QS_ADDR parameter, and a second IPv6 address or hostname that resolves to an IPv6 address. Change the value of HOSTNAME_ADDRESS_FAMILY to ANY. Apply the new configuration.
Table 1-1 Package Configuration File Parameters for qs-pkg (continued) 5. Parameter Value FAILOVER_POLICY CONFIGURED_NODE FAILBACK_POLICY MANUAL NODE_NAME * AUTO_RUN YES LOCAL_LAN_FAILOVER_ALLOWED YES NODE_FAIL_FAST_ENABLED NO RUN_SCRIPT $SGCONF/qs-pkg/qs-pkg.ctl RUN_SCRIPT_TIMEOUT NO_TIMEOUT HALT_SCRIPT $SGCONF/qs-pkg/qs-pkg.
Running the Quorum Server on a Single System Specifying a Log File By default, Quorum Server runtime messages go to stdout and stderr. HP recommends that you create a directory such as /var/adm/qs, then redirect stdout and stderr to a file in this directory (for example, /var/adm/qs/qs.log) when you start the Quorum Server; see the sample /etc/inittab entries in the examples below. Recommended pathnames are in Table 1-2 (page 17).
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 (+).
5. 6. Refer to the qs(1) man page for more details. All nodes in all clusters that were using the old Quorum Server will connect to the new Quorum Server. Use the cmviewcl -v command from any cluster that is using the Quorum Server to verify that the nodes in that cluster have connected to the Quorum Server. The Quorum Server log file on the new Quorum Server will show a log message such as the following for each cluster that uses the Quorum Server: Request for lock /sg/ succeeded.
Software Availability in Native Languages HP Serviceguard Quorum Server Version A.04.00 does not provide Native Language Support.
