HP Serviceguard A.11.20.20 for Linux Release Notes HP Part Number: 701461-003 Published: May 2013 Edition: 3.
© Copyright 2006, 2013 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...................................................................
7 Hardware requirements........................................................................................................30 8 Software requirements..........................................................................................................30 9 Related information..............................................................................................................30 10 Legacy packages..................................................................................................
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.
Features provided by Serviceguard Manager B.03.31.10 • Configuration, administration, and monitoring support for a Metrocluster XPCA, 3PAR, and CAEVA packages • Configuration, administration, and monitoring support of SGeSAP toolkit for the following modules: ◦ SAP instance ◦ DB instance ◦ External instance ◦ SAP infrastructure component ◦ MDM instance ◦ Live cache instance ◦ SAP NetWeaver operation resource component (enqor) • Configuration and monitoring support for Sites.
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.com/go/linux-serviceguard-docs. 3.3.1 Support for persistent reservation with Device Mapper multipath Serviceguard for Linux packages use persistent reservations (PR) to control access to LUNs.
3.3.5 IP_MONITOR parameter disabled by default Starting Serviceguard A.11.20.20, when you create a cluster for the first time, the IP_MONITOR parameter is disabled by default. For more information about how to enable or disable the IP_MONITOR parameter, see Managing HP Serviceguard A.11.20.20 for Linux manual. 3.3.6 Utilities to migrate legacy style toolkit packages to modular style packages Starting Serviceguard A.11.20.
• QXCR1001261975: SGLX:Core dump once the cmresourced respawns if generic resource is not set • QXCR1001262028: cmpreparecl should add boot vg to volume_list • QXCR1001263415: Support for iSCSI in Linux • QXCR1001264031: cmpreparecl on linux fails due to cmsshsetup failure if DNS is not configured • QXCR1001264822: Package script fails to unmount devices if logical volume names contain a hyphen • QXCR1001265360: cmapplyconf fails to apply pkg ascii with multi IPs/subnets with multi node_name •
• QXCR1001274453: Error messages during vgdisplay of package vg seen during cmcheckconf • QXCR1001273835: cmcheckconf outputs error but reports no errors found 4.2 Defects fixed in Serviceguard Manager There are no defects fixed in this version of the release. 5 Known problems and limitations This section provides a list of known problems and limitations as known to HP at the time of publication. If workarounds are available, they are included. 5.
• When using Generic Resources feature with Serviceguard A.11.20.10 or earlier versions, killing of cmresourced brings down the node. • No LAD support for MNP packages that are configured to use Persistent Reservation (PR). • Problem : While trying to install sgproviders in SUSE Linux Enterprise Server, it reports insserve warning or missing messages. Workaround: HP recommends that you ignore the warning message.
5.2 Known problems and limitations in Serviceguard Manager • When the package is configured with XFS as file system type in the Property page, the following message is displayed: TODO:createModifyUPCCPackages.fs.xfs • QXCR1001229847: From Serviceguard Manager, disable sg maintenance does not have proper checks for toolkit packages. • QXCR1001246109: Previous button must not have any checks in the Site page. • QXCR1001246279: Node status showing as up in the tooltip, even if the node is halted.
Table 1 Serviceguard patches for Linux Serviceguard version Supported platforms Patches A.11.20.20 Red Hat Enterprise Linux 5 SGLX_00354 Red Hat Enterprise Linux 6 SGLX_00355 SUSE Linux Enterprise Server 11 SGLX_00356 Red Hat Enterprise Linux 5 SGLX_00339 Red Hat Enterprise Linux 6 SGLX_00340 SUSE Linux Enterprise Server 11 Not applicable1 Red Hat Enterprise Linux 5 Not applicable A.11.20.10 A.11.20.
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.
1) Remove the soft link, if the link is pointing to a wrong version of Java (if it is pointing to wrong location). # rm /usr/bin/java 2) Either install the java rpm or, if you are using a tarball, provide a soft link to the Java location. Installing rpm: 1) # rpm –ivh jdk-7-linux-x64.rpm command installs the Java rpm, if it is not installed. 2) If you are using a .bin extension of Java rpm , run the following command cd (change directory) to the directory, where the .bin file is present: # .
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.5 Considerations when upgrading Serviceguard • .rhosts If you relied on .
• 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.3 Ports needed for authentication The ports reserved for authentication are also used by Serviceguard: • auth 113/TCP authentication • auth 113/UDP authentication 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.
