HP Serviceguard A.11.20.20 for Linux Release Notes HP Part Number: 701461-004 Published: February 2014 Edition: 4.
© 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 Overview.............................................................................................................................5 2 Supported platforms and Linux distributions...............................................................................5 3 What is new in this release.....................................................................................................5 3.1 What is new in Serviceguard for Linux...................................................................
6.15 Verifying installation....................................................................................................29 6.16 Rolling upgrade in Serviceguard Manager.....................................................................29 7 Hardware requirements........................................................................................................30 8 Software requirements..........................................................................................................
1 Overview This document provides information about HP Serviceguard A.11.20.20 for Linux. 2 Supported platforms and Linux distributions Serviceguard A.11.20.20 is available on HP ProLiant Servers for the following Linux distributions: • Red Hat Enterprise Linux 5 or Advanced Platform • Red Hat Enterprise Linux 6 or Advanced Platform • SUSE Linux Enterprise Server 11 The HP Serviceguard Extended Distance Cluster (serviceguard-xdc) for Linux A.11.
3.1.1 What is new in Serviceguard Manager There are no new features in this release. Features provided by Serviceguard Manager B.03.31.
• Hardware support X86 (32 bit) • CLX is not supported with Serviceguard A.11.20.xx or later. Metrocluster for Linux products replace CLX functionality. For more information about Metrocluster for Linux products, see http://www.hp.com/info/ sglx. 3.3 About the new features This section explains the major new capabilities introduced in the A.11.20.20 release. For more information about using these capabilities, see Managing HP Serviceguard A.11.20.20 for Linux at http://www.hp.
3.3.4 Support for iSCSI storage device Starting Serviceguard A.11.20.20, iSCSI storage device accessible via Linux distributed iSCSI software initiator is supported as shared storage for application data in a Serviceguard for Linux cluster. For more information about iSCSI storage device, see Managing HP Serviceguard A.11.20.20 for Linux manual. NOTE: An iSCSI storage device does not support configuring a lock LUN. 3.3.5 IP_MONITOR parameter disabled by default Starting Serviceguard A.11.20.
4.
• QXCR1001270152: Easy migration of legacy toolkit packages • QXCR1001271118: cmapplyconf should fail if vg has not been specified in XDC package • QXCR1001271796: Request for XFS filesystem support in Serviceguard • QXCR1001272108: SGLX: Support for ext4 on RHEL 5.
• When nodes are in mixed patch version, WWID for lock LUN device on Node running Serviceguard version A.11.20.00 might mismatch with WWID of lock LUN device on Node-2 running Serviceguard version A.11.20.10 or later even when the device is same. This is due to the way the WWID is read by Serviceguard. Due to this it leads to the failure of cmcheckconf and cmapplyconf of cluster configured with lock LUN as arbitration mechanism in the mixed patch environment.
◦ The following Warning message is displayed during cmquerycl –n Warning: Unable to determine local domain name for ◦ Wbemexec command fails for method getInstance on certain classes such as HP_SGNodeIdentity and HP_SGNode. Work around: ◦ HP recommends that you ignore the warning message. cmquerycl command does not fail because of this warning. ◦ Only node names without domain names must be mentioned in the input XML passed to wbemexec command as applicable.
Serviceguard Manager. If they are present, the component rpms are installed. For more information, see the README_cmeasyinstall.txt that is bundled along with the cmeasyinstall script. 6.1.1 Serviceguard for Linux patches (updates) Patches are available for Serviceguard on Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6, and SUSE Linux Enterprise Server 11. Table 1 provides details about the Serviceguard patches for each platform. You can download the latest Serviceguard patches for Linux A.11.
You can use the chkconfig command to enable xinetd: /sbin/chkconfig --level 35 xinetd on • You may need to install additional software from the distribution, depending on the Serviceguard components that you are installing. The following lists all the software you will need for each distribution, if you install all the Serviceguard components. You may want to install all of this software now, to make sure all dependencies are met. Table 2 RPMs (pre-requisites) for installing Serviceguard for Linux A.11.20.
Java(TM) SE Runtime Environment (build 1.7.0-b147) Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode) b. If the command “which Java” results with no output or, if it is pointing to a wrong version of Java, then follow the below steps to provide the link to the appropriate Java inside JDK: 1) Remove the soft link, if the link is pointing to a wrong version of Java (if it is pointing to wrong location).
c. Untar the tarball: # tar –xvf apache-tomcat-6.0.35.tar d. Remove the soft link, if any earlier incorrect link is provided: # rm /usr/share/sgmgr-tomcat e. Provide the soft link to the untarred directory: # ln –s /opt/myTomcat/apache- tomcat-6.0.35 /usr/share/sgmgr-tomcat f. Verify whether the soft link is pointing to the required tomcat directory: # ll /usr/share/sgmgr-tomcat lrwxrwxrwx 1 root root 23 Aug 15 03:03 /usr/share/sgmgr-tomcat -> /opt/myTomcat/apache-tomcat-6.0.35 6.1.
• hacl-cfg 5302/TCP HA Cluster TCP configuration • hacl-cfg 5302/UDP HA Cluster UDP configuration • hacl-local 5304/TCP HA Cluster Commands If you are using SNMP: • snmp 161/UDP • snmptrap 162/UDP If you are using the WBEM provider (used by Serviceguard Manager): • wbem-http TCP/5988 • wbem-https TCP/5989 If you are using the Quorum Server • hacl-qs 1238/TCP HA Quorum Server If you are using the appserver utility: • hacl-poll 5315/TCP 6.
If you have adjusted the dynamic port range using kernel tunable parameters, alter your firewall rules accordingly.
6.6 Installing the Quorum Server If you choose to use a Quorum Server rather than a lock LUN for tie-breaking, install the Quorum Server software on a system outside the cluster. The Quorum Server software is on the Serviceguard for Linux CD. Updated versions may be available from http://www.hp.com/go/softwaredepot. CAUTION: If you are upgrading both the Quorum Server and Serviceguard for Linux, upgrade the Quorum Server before you upgrade Serviceguard.
6.8.1 Requirements CAUTION: • Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A.11.20.10. • If you are using a Quorum Server, make sure you read the latest version of HP Serviceguard Quorum Server A.04.00.01 Release Notes available at http://www.hp.com/go/ hpux-serviceguard-docs—>HP Serviceguard Quorum Server Software. If you are using an alternate address, then you must upgrade the Quorum Server to version A.04.00 before you proceed.
configuration—during rolling upgrade. This means that you must upgrade all nodes to the new release before you can modify the configuration file and copy it to all nodes. • None of the features of the newer release of Serviceguard are allowed until all nodes have been upgraded. • Binary configuration files may be incompatible between releases of Serviceguard. Do not manually copy configuration files between nodes.
3. Record the storage configuration, such as all LVM information, and if possible, collect a list of hardware disks configured, for example, sfdisk -l. On SUSE Linux Enterprise Server, you may need to run YAST or YAST2. 4. Back up the following files on media that can be easily recovered by the node after its upgrade or a new OS installation: • Host files: /root/.
For example, Serviceguard rpm for Red Hat 5 x86_64: • For a node not configured into a cluster: rpm -i --force RedHat5/Serviceguard/x86_64/serviceguard-A.11.20.00-0.rhel5.x86_64.rpm • For a node already configured into a cluster: rpm -U --replacefiles RedHat5/Serviceguard/x86_64/serviceguard-A.11.20.00-0.rhel5.x86_64.
For SUSE Linux Enterprise Server: /opt/cmcluster/conf/cmcluster.rc e. Repeat this process for each node in the cluster. NOTE: Be sure to plan sufficient system capacity to allow moving the packages from node to node during the process without an unacceptable loss of performance.
Figure 2 Running cluster with packages moved to node 2 6.11.2.2 Step 2. Upgrade first node Upgrade node1 new version of Serviceguard as shown in the figure. Figure 3 Node 1 upgraded to Serviceguard A.11.20.00 6.11.2.3 Step 3. Restart cluster on first node When upgrade is finished and the node has been rebooted and all data restored, enter the following command on node1 to restart the cluster on node1.
Figure 4 Node 1 rejoining the cluster 6.11.2.4 Step 4. Repeat the process on next node Repeat the process on node2. Halt the node as follows: # cmhaltnode -f node2 This causes both packages to move to node1. Then upgrade node2 to new version of Serviceguard A.11.20.00. Figure 5 Running cluster with packages moved to node 1 6.11.2.5 Step 5. Move package back to original node Move pkg2 back to its original node.
Figure 6 Running cluster after upgrades 6.12 Rolling upgrade from A.11.19.X to A.11.20.20 The following procedure describes how to perform the Rolling upgrade from A.11.19.X to A.11.20.20: 1. Enable global switching for packages running on node 1. The cmmodpkg command enables switching of the package. For example, #cmmodpkg -e pkg1 2. Halt first node. Halt the node you want to upgrade. This results in the node's packages to start up on an adoptive node. The Serviceguard daemon on node 1 is halted.
7. 8. Run the sgupdate script, and follow the instructions provided in the install file to install the rpm. Restart Cluster on first node. For example, # cmrunnode -n node1 Check that the node joins the cluster successfully, and if necessary, move packages back to the node. 9. Repeat steps from 2 to 8 for all the nodes. 6.13 Performing offline upgrade from A.11.18.X to A.11.20.20 The following procedure describes how to perform offline rolling upgrade from A.11.18.X to A.11.20.20: 1. Halt the cluster.
On Red Hat Enterprise Linux 5: If Serviceguard A.11.19.xx is installed on the node, first you must upgrade to Serviceguard A.11.20.20. For information about upgrading to Serviceguard A.11.20.20, see “Rolling upgrade from A.11.19.X to A.11.20.20” After Serviceguard is upgraded to the A.11.20.20 version: 1. Verify whether xdc rpm is installed on the node: #rpm -q xdc xdc-A.01.01-0.rhel5.noarch 2. Uninstall the xdc rpm: #rpm -e xdc-A.01.01-0.rhel5.noarch 3. 4. 5.
• SGMgr-Tomcat (serviceguard-manager-tomcat-01.10-0.linux.noarch.rpm) • SGMgrB03.31 (serviceguard-manager-B.03.31.10-0.redhat.noarch.rpm) 7 Hardware requirements For more information about hardware requirements, see the latest version of HP Serviceguard for Linux Certification Matrix at http://www.hp.com/go/linux-serviceguard-docs. 8 Software requirements For more information about software requirements, see “Prerequisites” section in the HP Serviceguard Extended Distance Cluster for Linux A.11.
11 Quorum server upgrade required if you are using an alternate address If you are using an Alternate Quorum Server Subnet, you must upgrade the Quorum Server to version A.04.00 before you upgrade the cluster to Serviceguard A.11.20.00. CAUTION: If you fail to do this, the upgraded cluster will be running without a cluster lock until you have upgraded the Quorum Server.
