HP Serviceguard Quorum Server for Linux Version A.12.00.
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 1 HP Serviceguard Quorum Server for Linux version A.12.00.00 Release Notes.....4 Announcements........................................................................................................................4 Cluster name restrictions.......................................................................................................4 Using this version.....................................................................................................................
1 HP Serviceguard Quorum Server for Linux version A.12.00.00 Release Notes Announcements This edition of the release notes provides information about Quorum Server for Linux version A.12.00.00 and is supported for Serviceguard cluster on HP-UX and Linux. Supported Platforms HP Serviceguard Quorum Server for Linux version A.12.00.
These characters are deprecated, meaning that you must not use them even if you are not using the Quorum Server, because they will be illegal in a future Serviceguard release. Future releases will require the cluster name to: • Begin and end with an alphanumeric character • Otherwise use only alphanumeric characters, or dot (.
NOTE: The difference between Serviceguard A.11.19 and the earlier versions that support an alternate-subnet connection is that in the earlier versions, the alternate connections are serialized; if the first connection fails, the node will attempt to connect to the Quorum Server on the alternate subnet. In A.11.19 the connections are created in parallel, improving availability: if one connection fails, the other is still active.
Network recommendations • Ideally the Quorum Server and the cluster or clusters it serves must communicate over a subnet that does not handle other traffic. (If you are using a version of Serviceguard that supports 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.
Installing on Linux The install command for Linux uses the complete version name. Refer to the Serviceguard Quorum Server Support Matrix for the Supported Linux versions.. Before installing, you can see the complete version name in the file name; after installing, you can get it by using the command rpm -q qs. 1. Get the version A.12.00.00 from the appropriate directory on the HP Serviceguard for Linux DVD. 2.
Updating the Quorum Server (SUSE) 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 you update Serviceguard. 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.
Using alternate subnets Some versions of Serviceguard (see “Compatibility with Serviceguard versions” (page 7)) support new functionality in the Quorum Server that allows you to configure more than one subnet on which communication between the Quorum Server and the cluster nodes can take place. In this case, you configure a primary subnet (indicated by the QS_HOST parameter in the cluster configuration file) and a second subnet (indicated by QS_ADDR in the cluster configuration file).
The resulting file contains the QS_HOST, QS_POLLING_INTERVAL, and QS_TIMEOUT_EXTENSION parameters, and the QS_ADDR parameter if your version of Serviceguard 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_qs1 QS_ADDR 15.106.73.
1. 2. Make sure that there is at least one IPv4 address on the Quorum Server that can be reached by all the cluster nodes. Generate the cluster configuration file; for example: cmquerycl -q -n -n -C .conf 3. Edit the resulting file: 1. Change the value of the QS_HOST parameter to an IPv6 address, or a hostname that resolves to an IPv6 address. 2. Add the QS_ADDR parameter, and a second IPv6 address or hostname that resolves to an IPv6 address. 3.
Table 1 Package configuration file parameters for qs-pkg 5. Parameter Value PACKAGE_NAME qs-pkg PACKAGE_TYPE FAILOVER 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 2 (page 13).
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, 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.
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 7). • 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.
