Quorum Server Configuration

HP Serviceguard Quorum Server VersionA.04.00 Release Notes

HP Part Number: B8467-90048Published: July 2009

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 SoftwareDocumentation, andTechnicalData forCommercial Items are licensed to theU.S.Governmentunder vendor’s standard commercial license.

The information contained herein is subject to changewithout notice. The onlywarranties forHP products and services are set forth in the expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HPshall not be liable for technical or editorial errors or omissions contained herein.

Intel®, Itanium®, are registered trademarks of Intel Corporation or its subsidiaries in the United States or other countries.

HP Serviceguard® is a registered trademark of Hewlett-Packard Company, and is protected by copyright.

Linux® is a registered trademark of Linus Torvalds.

Red Hat® is a registered trademark of Red Hat Software, Inc.

SUSE® is a registered trademark of SUSE AG, a Novell Business.

Table of Contents

Printing History ..................................................................................................................5

1 HP Serviceguard Quorum Server Version A.04.00 Release Notes..........................7Announcements......................................................................................................................................7

Cluster Name Restrictions.................................................................................................................7Using this Version...................................................................................................................................7

Getting the Software..........................................................................................................................7Documentation for This Version ......................................................................................................8Further Information...........................................................................................................................8

What Is the Quorum Server?..................................................................................................................8How the Quorum Server Works........................................................................................................8

System Requirements and Recommendations.......................................................................................9System Requirements........................................................................................................................9

Operating System and Hardware Requirements.........................................................................9Memory and Disk Requirements.................................................................................................9

Network Recommendations..............................................................................................................9Compatibility with Serviceguard Versions...........................................................................................10Installing the Quorum Server...............................................................................................................10

Installing on HP-UX........................................................................................................................11Installing on Linux...........................................................................................................................11

Updating the Quorum Server...............................................................................................................12Updating the Quorum Server (HP-UX) ..........................................................................................12Updating the Quorum Server (Red Hat Linux)..............................................................................12Updating the Quorum Server (SUSE Linux)...................................................................................12

Configuring Serviceguard to Use the Quorum Server.........................................................................13About the QS Polling Interval and Timeout Extension...................................................................13Using Alternate Subnets..................................................................................................................13

Requirements for Using Alternate Subnets...............................................................................14Setting Quorum Server Parameters in the Cluster Configuration File...........................................14

Setting Quorum Server Parameters for IPv6 Subnets................................................................15Requirements for Using IPv6 Subnets..................................................................................15Configuring IPv6 Addresses without the July 2009 Patch.....................................................15

Configuring and Running the Quorum Server....................................................................................16Creating a Package for the Quorum Server.....................................................................................16Running the Quorum Server on a Single System............................................................................18

Specifying a Log File..................................................................................................................18Running the Quorum Server......................................................................................................18

Creating and Updating the Authorization File...............................................................................18Replacing a Failed Quorum Server System..........................................................................................19Uninstalling the Quorum Server..........................................................................................................20Patches, Fixes, and Known Problems in this Version...........................................................................20

Patches.............................................................................................................................................20Known Problems and Workarounds...............................................................................................20

Software Availability in Native Languages .........................................................................................21

Table of Contents 3

List of Tables1 Printing History...............................................................................................................................51-1 Package Configuration File Parameters for qs-pkg.....................................................................161-2 Package Control Script Parameters for qs-pkg..............................................................................17

4 List of Tables

Printing HistoryTable 1 Printing History

EditionPart NumberPrinting Date

First EditionB8467-90045March 2009

Second EditionB8467-90048July 2009

The last printing date and part number indicate the current edition.

5

6

1 HP Serviceguard Quorum Server Version A.04.00 ReleaseNotes

AnnouncementsThis edition of the release notes provides information about Quorum Server version A.04.00.This version supports Serviceguard versionsA.11.14 and later onHP-UX andLinux, and providesthe 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).

IMPORTANT: This version is required if you intend to use an alternate subnet withServiceguard A.11.19, and must be installed before you upgrade an A.11.18 cluster usingan alternate subnet to A.11.19.

• Allows Serviceguard A.11.19 cluster nodes to communicate with the Quorum Server usingIPv6 subnets.See “Setting Quorum Server Parameters in the Cluster Configuration File” (page 14) forinstructions.

• Supports IPv6–only Quorum Servers.A system configured to use only IPv6 addresses canprovide quorumservice to a Serviceguardcluster that is configured as an IPv6–only ormixed-mode cluster. See “About HostnameAddress Families: IPv4-Only, IPv6-Only, andMixedMode” in Chapter 4 of the latest versionofManaging Serviceguard orManaging Serviceguard for Linux.

IMPORTANT: These alternate-subnet and IPv6 capabilities are available onlywith Serviceguardversions that support them. See “Compatibilitywith ServiceguardVersions” formore informationand restrictions.

The Quorum Server software can run on either an HP-UX or Linux system. See “SystemRequirements and Recommendations”.

Cluster Name RestrictionsThe following characters must not be used in the cluster name if you are using the QuorumServer: at-sign (@), equal-sign (=), or-sign (|), semicolon (;).These characters are deprecated, meaning that you should not use them, even if you are notusing the Quorum Server, because they will be illegal in a future Serviceguard release. Futurereleases will require the cluster name to:• Begin and end with an alphanumeric character• Otherwise use only alphanumeric characters, or dot (.), hyphen (-), or underscore (_)

Using this VersionFor support information see “Compatibility with Serviceguard Versions” (page 10); forinstructions see “Configuring and Running the Quorum Server” (page 16).

Getting the SoftwareYou can obtain Quorum Server free from HP’s software web site:http://software.hp.com -> High Availability -> ServiceGuard QuorumServer

Announcements 7

The version of the software you download is determined by the operating system you specifyon the download page.

Documentation for This VersionThese release notes are shipped with Quorum Server Version A.04.00, and published underQuorum 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 QuorumServer at http://docs.hp.com -> High Availability.

Further InformationThe most recent versions of user’s guides, release notes, and white papers about Serviceguardand related topics are available at http://docs.hp.com -> High Availability.Support information, including current information about patches and known problems, isavailable from the Hewlett-Packard IT Resource Center:http://itrc.hp.com (Americas andAsiaPacific) orhttp://europe.itrc.hp.com (Europe)

What Is the Quorum Server?Serviceguard cluster products are specialized facilities for protectingmission-critical applicationsfrom a wide variety of hardware and software failures. The HP Serviceguard Quorum Serverprovides arbitration services for Serviceguard clusters when a cluster partition is discovered:should equal-sized groups of nodes become separated from each other, the Quorum Serverallows one group to achieve quorumand form the cluster, while the other group is denied quorumand cannot start a cluster.

How the Quorum Server WorksTheQuorumServer runs on anHP-UXor Linux system outside of the cluster for which it is providingquorum services.Within the restrictions specified under “System Requirements” (page 9), a Quorum Serverrunning on either a Linux or an HP-UX system can serve a Serviceguard for Linux cluster, anHP-UX Serviceguard cluster, or a combination of clusters of both types.TheQuorumServer uses TCP/IP, and listens to connection requests from the Serviceguard nodeson port # 1238. The server maintains a special area in memory for each cluster; when a nodeobtains the cluster lock, this area ismarked so that other nodeswill recognize the lock as “taken.”In recent versions of Serviceguard, you can configure more than one connection between theQuorumServer and each cluster node; see “Compatibilitywith ServiceguardVersions” (page 10)and “Using Alternate Subnets” (page 13).

NOTE: The difference between Serviceguard A.11.19 and the earlier versions that support analternate-subnet connection is that in those earlier versions, the alternate connections are serialized:if the first connection fails, the nodewill attempt to connect to theQuorum Server on the alternatesubnet. InA.11.19 the connections are created in parallel, improving availability: if one connectionfails, the other is still active.

You can make the Quorum Server highly available by configuring it as a Serviceguard package,so long as the package runs outside the cluster theQuorumServer serves; see “Creating a Packagefor the Quorum Server” (page 16).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 atdocs.hp.com -> High Availability -> Quorum Server.

8 HP Serviceguard Quorum Server Version A.04.00 Release Notes

If the Quorum Server is not available or reachable, it will not adversely affect any clusters usingit, 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 fromanother quorum method, while the cluster is running.

IMPORTANT: For more information, see “What Happens when You Change the QuorumConfiguration Online” in Chapter 3 ofManaging Serviceguard.

System Requirements and Recommendations

System Requirements

Operating System and Hardware RequirementsThe HP-UX version of Quorum Server version A.04.00 runs on HP 9000 servers, HP Integrityservers, and HP-UX workstations, running HP-UX 11i v2 or 11i v3.The Linux version runs on:• Any hardware specified in theHP Serviceguard for Linux Certification Matrix (which you can

find at: http://www.hp.com/info/sglx) and running one of the following Linuxdistributions in IA32, IA64, or x86_64 versions:— Red Hat 5— SUSE SLES10— SUSE SLES11

• AnyHP PC supported to run any of the operating systems indicated by the previous bullet.A Quorum Server can provide quorum services for multiple HP-UX or Linux clusters, or acombination of both, up 150 clusters but not exceeding 300 nodes in all.

CAUTION: Make sure that each cluster served by a given Quorum Server has a unique clustername. Serviceguard normally enforces this, but under some circumstances (for example if theclusters are on different subnets) Serviceguard will not be able to detect a duplicate name. Seealso “Network Recommendations” (page 9).

Memory and Disk RequirementsMemory: 7.0 MBDisk space: 1 MB

Network Recommendations• Ideally the Quorum Server and the cluster or clusters it serves should communicate over a

subnet that does not handle other traffic. (If you are using a version of Serviceguard thatsupports more than one subnet for communication with the Quorum Server, this should betrue of both subnets.) This helps to ensure that the Quorum Server is available when it isneeded.If this is not practical, or if the communication must cover a long distance (for example, iftheQuorumServer is serving an ExtendedDistance cluster) heavy network traffic or networkdelays could cause Quorum Server timeouts. You can reduce the likelihood of timeouts byincreasing the Quorum Server timeout interval; use the QS_TIMEOUT_EXTENSIONparameter in the cluster configuration file. See “Configuring Serviceguard toUse theQuorum

System Requirements and Recommendations 9

Server” (page 13) and “Setting Quorum Server Parameters in the Cluster ConfigurationFile” (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 andheartbeat communication are not likely to fail at the same time.

Compatibility with Serviceguard VersionsThis version of the Quorum Server supports:• Serviceguard clusters running Serviceguard 11.14 or later on HP-UX 11i v1, 11i v2 or 11i v3.• Serviceguard clusters running Serviceguard 11.14 or later on supported Red Hat or SUSE

Linux distributions.

IMPORTANT:• The alternate-subnet capability is available only for Serviceguard A.11.17 on HP-UX 11i v2

with patch PHSS_35427, and on HP-UX 11i v2, HP-UX 11i v3, and Linux for ServiceguardA.11.18 (withOctober 2007 or later patch) andA.11.19. See “How theQuorumServerWorks”(page 8) for information about the difference in implementation between A.11.19 and theearlier releases.See the latest version of the corresponding Serviceguard A.11.18 Release Notes for requiredpatches for Serviceguard A.11.18.

• Quorum Server version A.04.00 is required if you are using an alternate subnet forcommunication with a Serviceguard A.11.19 cluster, and must be installed before youupgrade the cluster to A.11.19.

• If you are running ServiceguardA.11.19 andwant to use an IPv6 connection, or connections,between the cluster and the Quorum Server, you should apply the July 2009 patch toServiceguard. See the latest Serviceguard release notes for information about this patch.The patch is required for IPv6-only clusters, but it is also possible to configure IPv6connectionswithout the patch; see “Configuring IPv6Addresseswithout the July 2009 Patch”(page 15) for instructions.

• You will need to apply Cluster Object Manger (COM) patch PHSS_35372 in order to usethe older, station-management version of Serviceguard Manager to manage a cluster thatuses more than one subnet for communication with the Quorum Server.

For complete compatibility information, see the Quorum Server Compatibility Matrix posted atdocs.hp.com -> High Availability -> Quorum Server.

Installing the Quorum ServerRead this entire document and any other Release Notes or READMEs you may have before youbegin an installation.The Quorum Server software, which has to be running during cluster configuration, must beinstalled on a system other than the nodes on which your cluster will be running. This could bea single Linux or HP-UX system, or it could be a separate cluster.If you are updating from an older version of Quorum Server, see the instructions below.


IMPORTANT: Order is important if you are updating Quorum Server and also updatingServiceguard. Youmust updateQuorumServer before updating Serviceguard. See the instructionsbelow.

Installing on HP-UXUse the swinstall command to install the Quorum Server, product number B8467BA, on thesystem or systems where it will run. You must install the Quorum Server on a node outside thecluster (or clusters) that it will serve. The only installation required on the clusters that use theQuorum Server lock is Serviceguard itself.If you are updating from an earlier version of Quorum Server, skip to the upgrading instructionsbelow.To install from the web, go to http://software.hp.com. Select High Availability, thenHP Serviceguard Quorum Server for HP-UX.1. Download B8467BA version A.04.00, and store it to disk.2. Run theswinstall command on this depot. SelectB8467BA A.04.00 Quorum Server.The Quorum Server executable file, qs, is installed in the /usr/lbin directory. When theinstallation is complete, you need to create an authorization file on the server where the QuorumServer will be running, to allow specific cluster nodes to obtain quorum services. See “Creatingand Updating the Authorization File” (page 18).Now create a directory for the Quorum Server log file. The recommended pathnames are inTable 1-2 (page 17). (You may need to create the directory.)

Installing on LinuxThe install command for Linux uses the complete version name. The current version is A.04.00.Before installing, you can see the complete version name in the file name; after installing, youcan get it by using the command rpm -q qs.1. Either download B8467BA version A.04.00 and store it to disk, or get it from the appropriate

directory on the HP Serviceguard for Linux CD.2. From the directory that contains the file, use the rpm command to install the version you

need, as in the following examples.Example 1 (for Red Hat i386):rpm -ihv qs-A.04.00.00-0.rhel5.i386.rpm

Example 2 (for SUSE SLES 10 i386):rpm -ihv qs-A.04.00.00-0.sles10.i386.rpm

For SUSE 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.04.00.00-0.sles10.IA64.rpm

NOTE: On SLES 11 i386 and IA64 systems, use the SLES 10 rpm; on an x86_64 SLES 11 system,use the SLES 11 rpm.

The Quorum Server executable file, qs, is installed on Red Hat in the /usr/local/qs/bindirectory, and on SUSE in the/opt/qs/bin directory.

Installing the Quorum Server 11

When the installation is complete, you need to create an authorization file on the server wherethe 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 inTable 1-2 (page 17). (You may need to create thedirectory.)

Updating the Quorum ServerAn update can be done while the cluster the Quorum Server system is running, but the QuorumServer’s tie-breaking serviceswill not be available while the update is in progress (see “Replacinga Failed Quorum Server System” (page 19) for more details).

CAUTION: If you are updating Serviceguard as well, the Quorum Server update must be donebefore you update Serviceguard.

Updating the Quorum Server (HP-UX)1. Comment out theQuorumServer entry in/etc/inittab, and run the following command:

/sbin/init q

2. Uninstall the existing Quorum Server:swremove B8467BA

3. Install Quorum Server A.04.00:swinstall B8467BA

4. Uncomment the Quorum Server entry in the /etc/inittab file.5. Start the Quorum Server:

/sbin/init q

Updating the Quorum Server (Red Hat Linux)1. Comment out theQuorumServer 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 commandmay remove the file /var/log/qs/qs.log. If this is your logfile, 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.rhel5.i386.rpm

4. Uncomment the entry you commented out in /etc/inittab.5. Re-start the Quorum Server:

/sbin/init q

Updating the Quorum Server (SUSE Linux)An update can be done while the cluster is running.If you are updating Serviceguard as well, the Quorum Server update must be done before youupdate Serviceguard.


1. Comment out theQuorumServer 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 commandmay remove the file /var/log/qs/qs.log. If this is your logfile, 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. Uncomment the entry you commented out in /etc/inittab.5. Restart the Quorum Server:

/sbin/init q

Configuring Serviceguard to Use the Quorum Server

About the QS Polling Interval and Timeout ExtensionServiceguard probes theQuorumServer at intervals determined by theQS_POLLING_INTERVALparameter in the cluster configuration file. The default value for QS_POLLING_INTERVAL is 5minutes and the minimum value is 10 seconds.If the quorum server process goes downwhile its node is still up, the Serviceguard cluster nodescan detect the halt in the quorum server process. Serviceguardwill try to reconnect to the quorumserver every 10 seconds until the quorum server is back up and the connection is successful. Ifthe quorum server is needed as a tie-breaker during this downtime, the cluster will halt.However, Serviceguard cannot immediately detect the loss of connection to the process if thequorum server’s node goes down. Serviceguard will continue to poll at the configured interval,and will not discover that the quorum server connection is down until the next polling is done.If a cluster reformation starts before the next polling has occurred, Serviceguard assumes theQuorum Server is down. Because it requires the Quorum Server as a tie-breaker, it will halt thecluster. (Even if the Quorum Server comes back up before or during reformation, Serviceguardwill not know that it has until the next polling.)Theminimumvalue for the polling interval is 10 seconds. Reducing theQS_POLLING_INTERVALmeans Serviceguard will detect Quorum Server failures sooner, but it will also increase the loadon the Quorum Server. If you set a short interval, youmay have to reduce the number of clustersor nodes using theQuorum Server to reduce the load. Test very low settings carefully to fine-tuneall timing parameters, and do the tests in an environment that imitates the actual productionenvironment as closely as possible.You can use the optional QS_TIMEOUT_EXTENSION to increase the time interval (inmicroseconds) after which the current connection (or attempt to connect) to the quorum serveris deemed to have failed; see “Network Recommendations” (page 9) and “Setting QuorumServer Parameters in the Cluster Configuration File” (page 14).

Using Alternate SubnetsSome versions of Serviceguard (see “Compatibility with Serviceguard Versions” (page 10))support new functionality in the Quorum Server that allows you to configure more than onesubnet on which communication between the Quorum Server and the cluster nodes can takeplace.In this case, you configure a primary subnet (indicated by theQS_HOST parameter in the clusterconfiguration file) and a second subnet (indicated byQS_ADDR in the cluster configuration file).

Configuring Serviceguard to Use the Quorum Server 13

Requirements for Using Alternate SubnetsAll of the following must be true in order for you to configure more than one subnet forcommunication 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 “SystemRequirements and Recommendations” (page 9).

• All of the cluster nodesmust be able to communicatewith both of theQuorumServer subnetswhen you configure or reconfigure the cluster.If this is not truewhen you runcmquerycl,cmcheckconf, orcmapplyconf, the commandwill fail.

• Both of the IP addresses specified for the Quorum Server must map to the same QuorumServer.

• The authorization file must specify all the addresses from which the cluster nodes willcommunicatewith the Quorum Server. See “Creating andUpdating the Authorization File”(page 18).

Setting Quorum Server Parameters in the Cluster Configuration File

IMPORTANT: If you will be using an IPv6 subnet or subnets for communication between theQuorum Server and a ServiceguardA.11.19 cluster, and you have not applied the July 2009 patchto Serviceguard A.11.19, follow the instructions under “Configuring IPv6 Addresseswithout theJuly 2009 Patch” (page 15) to generate the cluster configuration file. Read the remainder of thissection first.

You need to set values for Quorum Server parameters in the cluster configuration file. Use acommand such as the following (all on one line) to obtain a cluster configuration file that includesQuorum Server parameters:cmquerycl -q <QS_Host> -n <Node1> -n <Node2> -C <ClusterName>.conf

NOTE: If you are using a version of Serviceguard that supports alternate subnets (see“Compatibility with Serviceguard Versions” (page 10)), you can specify a second hostname orIP address in the -q option (all one line):cmquerycl -q <QS_Host> <QS_Addr> -n <Node1> -n <Node2> -C<ClusterName>.config

QS_Host and QS_Addr can each be either a fully qualified hostname or an IP address.The setting of the HOSTNAME_ADDRESS_FAMILY parameter in the cluster configuration fileconstrains the type of address(es) you can use for the Quorum Server connection:• If HOSTNAME_ADDRESS_FAMILY is set to IPV4, the connection (or both connections if

QS_ADDR is used) must be IPv4.• If HOSTNAME_ADDRESS_FAMILY is set to IPV6, the connection (or both connections if

QS_ADDR is used) must be IPv6.• If HOSTNAME_ADDRESS_FAMILY is set to ANY, each connection can be either IPv4 or

IPv6.

The resulting file contains the QS_HOST, QS_POLLING_INTERVAL, andQS_TIMEOUT_EXTENSION parameters, and the QS_ADDR parameter if your version ofServiceguard supports it. In that case, the Quorum Server section of the file looks like this:# for the quorum server timeout, enter# QS_HOST qs_host# QS_ADDR qs_addr# QS_POLLING_INTERVAL 120000000


# QS_TIMEOUT_EXTENSION 2000000 QS_HOST gf2_qs1QS_ADDR 15.106.73.114QS_POLLING_INTERVAL 300000000

If your version of Serviceguard supports alternate subnets, but you are workingwith an existingcluster configuration file that does not contain the QS_ADDR parameter, you can add thisparameter, and its value, yourself.You can use the optional QS_TIMEOUT_EXTENSION to increase the time interval (inmicroseconds) after which the current connection (or attempt to connect) to the quorum serveris deemed to have failed; see “Network Recommendations” (page 9).

NOTE: Increasing this value will increase the failover time accordingly; that is, if failover timeis currently 30 seconds and you setQS_TIMEOUT_EXTENSION to one second, the failover timewill increase to 31 seconds.

Setting Quorum Server Parameters for IPv6 SubnetsServiceguard A.11.19 clusters support IPv6 addresses for both QS_HOST and QS_ADDR, butyou should apply the July 2009 patch to Serviceguard A.11.19 if you want to supply IPv6addresses, or hostnames that resolve only to IPv6 addresses, to cmquerycl. See the latestServiceguard 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, makesure the following requirements are met:• If theQuorumServer is on a different subnet from the cluster, youmust use an IPv6–capable

router.• All the IPv6 addresses used by the cluster nodes to connect to the Quorum Server must be

listed in the Quorum Server's authorization file. See “Creating and Updating theAuthorization File” (page 18).These IPv6 addresses must also be resolvable on the Quorum Server.

IMPORTANT: In the case of an IPv6–only Quorum Server, this means that the addressesmust be listed in /etc/hosts, as you cannot use DNS or NIS for name resolution in anIPv6–only Serviceguard cluster. Similarly, in an IPv6–only cluster, theQuorumServer's IPv6addresses must be listed in the cluster nodes' /etc/hosts.

See “About Hostname Address Families: IPv4-Only, IPv6-Only, and Mixed Mode” in Chapter4 ofManaging Serviceguard for more information.

Configuring IPv6 Addresses without the July 2009 Patch

If you have not applied the patch, you can still use IPv6 addresses, but you must generate thecluster configuration file using an IPv4 address, then edit it to supply the IPv6 address(es) youwill actually use.Proceed as follows to create two IPv6 connections to the Quorum Server if you have not appliedthe July 2009 Serviceguard patch:1. Make sure that there is at least one IPv4 address on the Quorum Server that can be reached

by all the cluster nodes.2. Generate the cluster configuration file; for example:

cmquerycl -q <QS_Host> -n <Node1> -n <Node2> -C <ClusterName>.conf

3. Edit the resulting file:

Configuring Serviceguard to Use the Quorum Server 15

1. Change the value of the QS_HOST parameter to an IPv6 address, or a hostname thatresolves to an IPv6 address.

2. Add the QS_ADDR parameter, and a second IPv6 address or hostname that resolvesto an IPv6 address.

3. Change the value of HOSTNAME_ADDRESS_FAMILY to ANY.4. Apply the new configuration.

Configuring and Running the Quorum Server• You can configure the Quorum Server as a monitored package in one Serviceguard cluster

to provide quorum service to another Serviceguard cluster or clusters; see “Creating aPackage for the Quorum Server” below.

• You can also configure the Quorum Server to run on a single system; see “Running theQuorum Server on a Single System” (page 18).

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 ServerYou 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. Suchpackages are supported with all currently-supported versions of Serviceguard. For informationon creating amodular package, supported as of Serviceguard A.11.18, see Chapter 6 of the latestversion of Managing Serviceguard at http://docs.hp.com -> High Availability ->Serviceguard.

To configure the Quorum Server into a packagewith Quorum Server as themonitored service,do the following.

NOTE: If you have just installed the quorum server, or if you are adding new cluster nodes,or implementing the alternate-subnet functionality, youmust update the authorization file beforeyou run the package; see “Creating and Updating the Authorization File” (page 18).

1. Install the Quorum Server software on all nodes; see “Installing the Quorum Server”(page 10).

2. In the configuration directory ($SGCONF), create a subdirectory for the Quorum Serverpackage, then change your working directory to it:mkdir qs-pkg

cd qs-pkg

3. Create a package configuration file:cmmakepkg -P qs-pkg.config

4. Edit the parameter values in the file as follows.

Table 1-1 Package Configuration File Parameters for qs-pkg

ValueParameter

qs-pkgPACKAGE_NAME

FAILOVERPACKAGE_TYPE


Table 1-1 Package Configuration File Parameters for qs-pkg (continued)

ValueParameter

CONFIGURED_NODEFAILOVER_POLICY

MANUALFAILBACK_POLICY

*NODE_NAME

YESAUTO_RUN

YESLOCAL_LAN_FAILOVER_ALLOWED

NONODE_FAIL_FAST_ENABLED

$SGCONF/qs-pkg/qs-pkg.ctlRUN_SCRIPT

NO_TIMEOUTRUN_SCRIPT_TIMEOUT

$SGCONF/qs-pkg/qs-pkg.ctlHALT_SCRIPT

NO_TIMEOUTHALT_SCRIPT_TIMEOUT

qsSERVICE_NAME

NOSERVICE_FAIL_FAST_ENABLED

10SERVICE_HALT_TIMEOUT

If the Quorum Server connection is on a single subnet,specify the subnet here.

SUBNET

5. 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 1-2 Package Control Script Parameters for qs-pkg

ValueParameter

IP address(es) to be used when accessing the Quorum Server. If you are using morethan one subnet for communicate between the Quorum Server and the cluster nodes,make sure each address is on a different subnet.

IP[]

Specify your subnet(s) hereSUBNET[]

qsSERVICE_NAME[0]

(>> Redirect file in this example shows recommended log pathnames)HP-UX: /usr/lbin/qs >> /var/adm/qs/qs.log 2>&1Linux:Red Hat: /usr/local/qs/bin/qs >> /var/log/qs/qs.log 2>&1SUSE: /opt/qs/bin/qs >> /var/log/qs/qs.log 2>&1

SERVICE_CMD[0]

“-R”SERVICE_RESTART

7. Update the authorization file if necessary.See “Creating and Updating the Authorization File” (page 18).

8. Run the cluster and start the quorum server package.

Configuring and Running the Quorum Server 17

Running the Quorum Server on a Single System

Specifying a Log FileBy default, Quorum Server runtime messages go to stdout and stderr. HP recommends thatyou create a directory such as /var/adm/qs, then redirect stdout and stderr to a file in thisdirectory (for example, /var/adm/qs/qs.log) when you start the Quorum Server; see thesample/etc/inittab entries in the examples below. Recommendedpathnames are in Table 1-2(page 17).

Running the Quorum Server

NOTE: If you have just installed the quorum server, or if you are adding new cluster nodes,or implementing the alternate-subnet functionality (for a cluster running a version of Serviceguardthat supports it; see “Compatibility with Serviceguard Versions” (page 10)) you must updatethe authorization file; see “Creating and Updating the Authorization File” (page 18).

You must have root capability to run the Quorum Server. On a single system, configure theQuorum Server to start up when the system on which it is installed restarts or reboots. Createan 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 Red Hat Linux (all in one line):qs:345:respawn:/usr/local/qs/bin/qs >> /var/log/qs/qs.log 2>&1

• For SUSE Linux:qs:345:respawn:/opt/qs/bin/qs >> /var/log/qs/qs.log 2>&1

Start the Quorum Server as follows:init q

Verify theQuorumServer is running by checking theqs.log file. (Recommended log pathnamesare in Table 1-2 (page 17).)For HP-UX, enter: cat /var/adm/qs/qs.logFor Linux, enter: cat /var/log/qs/qs.logThe log should contain entries such as the following, indicating that the Quorum Server hasstarted:Oct 04 12:25:06:0:main:Starting Quorum ServerOct 04 12:25:09:0:main:Server is up and waiting for connections at port 1238

Creating and Updating the Authorization FileThe Quorum Server reads the authorization file when it starts up. You need to create the file, onthe system(s) where the Quorum Server software resides, when you first install the QuorumServer, and update it when you add nodes to a cluster the Quorum Server serves, or add orchange the IP addresses or hostnames bywhich the nodes communicatewith theQuorumServer.On an HP-UX system, the authorization file must be /etc/cmcluster/qs_authfile.On a Red Hat Linux system, it must be /usr/local/qs/conf/qs_authfile.On a SUSE Linux system, it must be /opt/qs/conf/qs_authfile.Enter into the file the fully-qualified hostnames, or IP addresses, of all the cluster nodes that willobtain quorum services from this Quorum Server. Use one line per node, for example:ftsys9.localdomain.comftsys10.localdomain.com


NOTE: If you are specifying an alternate subnet (for clusters running a version of Serviceguardthat supports it; see “Compatibility with Serviceguard Versions” (page 10)) you must specifyboth 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 gatewaysin the Quorum Server's authorization file.Formore information about ip_strong_es_model, see “TuningNetwork andKernel Parameters”in Chapter 5 of the latest version of theManaging Serviceguardmanual, and theHP-UX IPSecVersionA.03.00Administrator's Guide, which you can find ondocs.hp.comunderInternetand Security Solutions —> IPSec.

• If the Quorum Server serves amixed-mode or IPv6–only cluster, make sure that all the IPv6addresses from which cluster nodes can reach the Quorum Server are listed in theauthorization file (or use the plus sign to allow access from any system). See also “SettingQuorum 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 SystemUse the following procedure to replace a defective Quorum Server systemwithout changing theconfiguration 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 onmore than one subnet, the newQuorum Servermust be able to communicatewith all clusternodes 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 wereconfigured 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

Refer to the qs(1)man page for more details.5. All nodes in all clusters that were using the old Quorum Server will connect to the new

QuorumServer. Use the cmviewcl -v command from any cluster that is using theQuorumServer to verify that the nodes in that cluster have connected to the Quorum Server.

6. The Quorum Server log file on the newQuorum Server will show a log message such as thefollowing for each cluster that uses the Quorum Server:Request for lock /sg/<ClusterName> succeeded. New lock owners: N1, N2

7. To check that theQuorumServer has been correctly configured and to verify the connectivityof a node to the Quorum Server, you can execute the following command from your clusternodes as follows:cmquerycl -q <QS_Host> -n <Node1> -n <Node2> ...or (if you are using more than one subnet; see “Using Alternate Subnets” (page 13)):cmquerycl -q <QS_Host> <QS_Addr> -n <Node1> -n <Node2> ...The commandwill output an errormessage if the specified nodes cannot communicatewiththe Quorum Server.

While the old Quorum Server is down and the new one is being set up, these things can happen:• These three commands will not work: cmquerycl -q, cmapplyconf -C,and

cmcheckconf -C.• If there is a node or network failure that creates a 50-50 membership split, the Quorum

Server will not be available as a tie-breaker, and the cluster will fail.

CAUTION: Make sure that the old systemdoes not re-join the networkwith its old IP address(es).

Uninstalling the Quorum Server• To uninstall the Quorum server on Linux, use the rpm command:

rpm -e qs

• To uninstall the Quorum server on HP-UX, use the swremove command:swremove B8467BA

Patches, Fixes, and Known Problems in this VersionThis section describes patches that are required, defects that have been fixed in version A.04.00of Quorum Server, and known problems.

PatchesApart from the patchesmentioned under “Compatibilitywith ServiceguardVersions” (page 10),no other patches are needed for version A.04.00 at the time of publication. Contact yourHewlett-Packard support representative for up-to-the-moment information. Patches can becreated, superseded, or withdrawn at any time without notice. An updated list of patches isavailable on the Hewlett-Packard IT Resource Center site: http://itrc.hp.com (Americasand Asia Pacific) or http://europe.itrc.hp.com (Europe).

Known Problems and WorkaroundsThere are no known problems with HP Serviceguard Quorum Server A.04.00 at the time ofpublication. Contact your Hewlett-Packard support representative for up-to-the-momentinformation. Patches can be created, superseded, or withdrawn at any time without notice. Anupdated list of patches is available on the Hewlett-Packard IT Resource Center site:http://itrc.hp.com (Americas and Asia Pacific) or http://europe.itrc.hp.com (Europe)


Software Availability in Native LanguagesHP Serviceguard Quorum Server Version A.04.00 does not provide Native Language Support.But translated versions of some versions of these Release Notes are available on the DistributedComponents CD, in the following languages:• Japanese• Simplified Chinese

Software Availability in Native Languages 21

Documents

Quorum Server Configuration