HP Serviceguard Quorum Server Version A.04.
Legal Notices © Copyright 2006, 2014 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.
Contents Printing History ............................................................................................4 1 HP Serviceguard Quorum Server Version A.04.00 Release Notes.....................5 Announcements........................................................................................................................5 Cluster Name Restrictions......................................................................................................5 Using this Version..........................
Printing History Table 1 Printing History Printing Date Part Number Edition March 2009 B8467-90045 First Edition July 2009 B8467-90048 Second Edition June 2012 702036-001 Third Edition May 2014 TBD Fourth 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 and A.04.00.01. A.04.00 is supported for RHEL versions till 6.0 and A.04.00.01 is supported for RHEL 6.0. This version supports Serviceguard versions A.11.14 and later on HP-UX and Linux, and provides the following new capabilities: • Quorum Server version A.04.00.01 adds support for RHEL 6. • Serviceguard A.11.
Software Depot -> ServiceGuard Quorum Server 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 Quorum Server Version A.04.00.01 for RHEL 6, and published at www.hp.com/go/hpux-serviceguard-docs —> HP Serviceguard Quorum Server Software. See also the white paper Arbitration for Data Integrity in Serviceguard Clusters, under Quorum Server at www.
You can also configure any two Serviceguard clusters to provide quorum services for each other; for more information, see the white paper, Cross-cluster Quorum Server Configurations at www.hp.com/go/hpux-serviceguard-docs -> HP Serviceguard Quorum Server Software. 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.
IMPORTANT: Under certain conditions it is possible for quorum server to deny a lock to a node that should be able to obtain if that node is a member of a cluster that previously shared a duplicate name with another cluster and they both used the same quorum server. This can happen even if the name conflict had been previously resolved by renaming one of the clusters. The quorum server log looks similar to the following: Nov 05 00:55:05:0:Request for lock /sg/CLUSTER_DEV succeeded.
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.
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 or HP-UX system, or it could be a separate cluster. NOTE: Ensure that the latest SGLX_00488 patch is installed on Red Hat Enterprise Linux 6 system before using quorum server.
Example 2 (for Red Hat x86_64): • On an RHEL 5 system: rpm -ihv qs-A.04.00.00-0.rhel5.i386.rpm • On an RHEL 6 system: rpm -ihv qs-A.04.00.01-0.rhel6.x86_64.rpm Example 3 (for SUSE Linux Enterprise Server (SLES) 10 i386): rpm -ihv qs-A.04.00.00-0.sles10.i386.rpm For SUSE Linux Enterprise Server (SLES)11, use one of the following commands: • On an i386 system: rpm -ihv qs-A.04.00.00-0.sles10.i386.rpm • On an x86–64 system: rpm -ihv qs-A.04.00.00-0.sles11.x86_64.rpm • On an IA64 system: rpm -ihv qs-A.
Updating the Quorum Server (For All Red Hat Linux Releases prior to RHEL 6) 1. Comment 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.
Configuring Serviceguard to Use the Quorum Server About the QS Polling Interval and Timeout Extension Serviceguard probes the Quorum Server at intervals determined by the QS_POLLING_INTERVAL parameter in the cluster configuration file. The default value for QS_POLLING_INTERVAL is 5 minutes and the minimum value is 10 seconds. If the quorum server process goes down while its node is still up, the Serviceguard cluster nodes can detect the halt in the quorum server process.
Setting Quorum Server Parameters in the Cluster Configuration File IMPORTANT: If you will be using an IPv6 subnet or subnets for communication between the Quorum Server and a Serviceguard A.11.19 cluster, and you have not applied the July 2009 patch to Serviceguard A.11.19, follow the instructions under “Configuring IPv6 Addresses without the July 2009 Patch” (page 15) to generate the cluster configuration file. Read the remainder of this section first.
or hostnames that resolve only to IPv6 addresses, to cmquerycl. See the latest Serviceguard release notes for information about the patch. Requirements for Using IPv6 Subnets If you are using an IPv6 subnet, or subnets, to connect the Quorum Server to the cluster, make sure the following requirements are met: • If the Quorum Server is on a different subnet from the cluster, you must use an IPv6–capable router.
NOTE: The Quorum Server must be running during the following cluster operations: • when the cmquerycl command is issued • when there is a cluster re-formation • when the cmapplyconf command is issued Creating a Package for the Quorum Server You can run the Quorum Server as a package in another cluster. NOTE: The instructions and examples in this section are for creating a legacy package. Such packages are supported with all currently-supported versions of Serviceguard.
Table 2 Package Configuration File Parameters for qs-pkg (continued) 5. Parameter Value SERVICE_FAIL_FAST_ENABLED NO SERVICE_HALT_TIMEOUT 10 SUBNET If the Quorum Server connection is on a single subnet, specify the subnet here. Create a control script in the same directory: cmmakepkg -s qs-pkg.ctl 6. Edit the file using the parameters in the following table. Table 3 Package Control Script Parameters for qs-pkg Parameter Value IP[] IP address(es) to be used when accessing the Quorum Server.
You must have root capability to run the Quorum Server. On a single system, configure the Quorum Server to start up when the system on where it is installed restarts or reboots. Create an entry such as the following in the /etc/inittab file: • For HP-UX: qs:345:respawn:/usr/lbin/qs >> /var/adm/qs/qs.log 2>&1 • For All Red Hat Linux Releases prior to RHEL 6 (all in one line): qs:345:respawn:/usr/local/qs/bin/qs >> /var/log/qs/qs.
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 (+).
4. Start the Quorum Server as follows: • 5. 6. 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. 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.
updated list of patches is available at Hewlett-Packard Support Centre website: http:// www.hp.
