HP Serviceguard A.11.20.10 for Linux Release Notes HP Part Number: 701461-002 Published: December 2012 Edition: 2.
© Copyright 2001–2012 Hewlett-Packard Development Company. All rights reserved. Reproduction, adaptation, or translation of this document without prior written permission is prohibited, except as allowed under copyright laws. © Copyright 1979, 1980, 1983, 1985-96 Regents of the University of California. This software is based in part on the Fourth Berkeley Software Distribution under license from the regents of the University of California. © Copyright 1986-1997 Sun Microsystems, Inc.
Contents Overview................................................................................................................................5 Supported platforms and Linux distributions..................................................................................5 Serviceguard bundled components - product structure...............................................................5 What is new in this release...............................................................................................
Hardware requirements...........................................................................................................32 Software requirements.............................................................................................................32 Related information.................................................................................................................32 Legacy packages..................................................................................................
Overview This document provides information about HP Serviceguard A.11.20.10 for Linux. Supported platforms and Linux distributions Serviceguard A.11.20.10 is available on HP ProLiant Servers for the following Linux distributions: • Red Hat Enterprise Linux (RHEL) 5 server or Advanced Platform • Red Hat Enterprise Linux (RHEL) 6 server or Advanced Platform • SUSE Linux Enterprise Server (SLES) 11 The HP Serviceguard Extended Distance Cluster (Serviceguard-xdc) for Linux A.11.20.
Table 1 Softwares and product numbers (continued) Software Product number HP Serviceguard for Linux Trade in license for 2 Socket HP ProLiant servers BB070ACN HP Serviceguard for Linux Trade in license for 4 to 8 Socket HP ProLiant servers BB071ACN HP Serviceguard Toolkit for Oracle Database for Linux A.05.01.01.00 NOTE: • Simplifies integration of an Oracle database (non-RAC) into a Serviceguard for Linux cluster. • Requires HP Serviceguard for Linux.
Table 1 Softwares and product numbers (continued) Software Product number NOTE: • Automatic, bi-directional failover for applications across data centers while ensuring data currency through integration with Continuous Access replication software for HP P9000/XP storage arrays. • Requires HP Serviceguard for Linux.
Table 1 Softwares and product numbers (continued) Software Product number NOTE: This part number can be used to purchase one license certificate delivering multiple per core licenses.
http://h18000.www1.hp.com/products/quickspecs/11518_div/11518_div.html What is new in this release This section describes the new and changed features for HP Serviceguard A.11.20.10 for Linux.
Features not supported in this version • Red Hat Enterprise Linux GFS and reiserfs file systems on SUSE Linux Enterprise Server • Xen • 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. About the new features The subsections that follow discuss the major new capabilities introduced in the A.11.20.10 release.
Servicegurad-xdc supports LAD for modular failover packages. For more information, see HP Serviceguard Extended Distance Cluster for Linux A.11.20.10 Deployment Guide NOTE: Serviceguard-xdc is supported with physical nodes. It is not supported on Virtual Machines. For more information about XDC module attributes, see HP Serviceguard Extended Distance Cluster for Linux A.11.20.10 Deployment Guide.
Defects fixed in Serviceguard 12 • QXCR1001244388: XDC/LAD: Need to sync CDB to 0 from 3 since an applyconf slipped in. • QXCR1001248973: cmcheckconf is failing for MCEVApackage configuration with sg/pr_cntl module. • QXCR1001249682: SG Package does not handle the FS configuration related errors properly. • QXCR1001248027: sg_check_and_mount can not handle asymmetric FS options. • QXCR1001246924: Deadman driver for Serviceguard may be out of compliance for it's GPL licence.
• QXCR1001243281: Observing assertion and core in ST on SLES 11 SP2. • QXCR1001183544: cmcld core in ST in pkg/pkg_commands.c 1061. • QXCR1001241439: cmcld Aborting: pkg/pkg_commands.c 1059 (Unexpected package state). • QXCR1001239675: Remove references of unsupported filesystems in package configuration file. • QXCR1001240468: cmmigratepkg with -o option failed while path specified doesn't exists. • QXCR1001227617: /etc/init.
• QXCR1001248606: While editing cluster configuration from Serviceguard Manager, if the number of nodes in the Nodes tab is changed, the corresponding network information is not updated in the summary page. • QXCR1001244974: While editing a multinode package from Serviceguard Manager, using the Add Toolkit or Update Toolkit option, displays toolkits which are incompatible with a multinode package. • QXCR1001250641: While configuring an Oracle ASM Toolkit package, if the Serviceguard Manager version B.
returned is not the FQDN of the host. Therefore the following effects are observed on Serviceguard: ◦ 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.
Installing HP Serviceguard for Linux HP provides an automated installation script that takes you through the process of installing and configuring Serviceguard for Linux, including Serviceguard Manager and ancillary software. For information and installation instructions, see the latest version of HP Serviceguard for Linux Deployment Guide, at http://www.hp.com/go/linux-serviceguard-docs.
Table 2 RPMs (pre-requisites) for installing Serviceguard for Linux A.11.20.10 (continued) Red Hat Enterprise Linux SUSE Linux Enterprise Server e2fsprogs-libs (RHEL 5) libstdc++43 (SP1) libblkid (RHEL 6) libgcc46 (SP2) libstdc++ libstdc++46 (SP2) libXp sblim-sfcb libgomp sblim-sfcc authd sblim-cmpi-base tog-pegasus net-snmp lm_sensors gcc net-snmp glibc gcc glibc-devel glibc sg3_utils glibc-devel xinetd sg3_utils xinetd java >= 1.6 - Output of "which java" must point to JDK .
1) 2) # rpm –ivh jdk-7-linux-x64.rpm command installs the Java rpm, if it is not installed. 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: # ./ jdk-7-linux-x64.rpm.bin command installs the java rpm If the rpm is already installed: 1) Find the java and provide the soft link to the desired location.
Considerations when upgrading Serviceguard • .rhosts If you relied on .rhosts for access in the previous version of the cluster, you must now configure Access Control Policies for the cluster users. For instructions on how to proceed, see the subsection “Allowing Root Access to an Unconfigured Node” under “Configuring Root-Level Access” in Chapter 5 of the Managing HP Serviceguard for Linux manual.
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 Ports needed for authentication The ports reserved for authentication are also used by Serviceguard: • auth 113/TCP authentication • auth 113/UDP authentication Ports required by Serviceguard Manager If you are using Serviceguard Manager via HP SMH, make sure the following ports are open in addition to the ports listed above: • compaq-https 2381/tcp • compaq-https 23
There are additional firewall requirements to enable execution of Serviceguard commands from nodes outside the cluster, such as those listed in cmclnodelist.
fail, logging a “Permission denied for user” message. This situation can arise when the Serviceguard remote security file, $SGCONF/cmclnodelist, is not used and remote node security is resolved by means of .rhosts. NOTE: /etc/cmcluster.conf contains the mappings that resolve the symbolic references to $SGCONF, $SGROOT, and so on, used in these Release Notes. See Understanding the Location of Serviceguard Files in Chapter 5 of the Managing HP Serviceguard for Linux manual for details.
NOTE: If there is no HP bonding driver for the Linux version you are using, use the bonding driver supplied with the Linux distribution. • Do a full backup on each node. NOTE: HP recommends you use the rolling upgrade process if possible, because it keeps your mission-critical applications running; and also that you update the software (rather than do a cold install) if possible, because updating preserves the current OS and cluster configuration.
CAUTION: No package can be in maintenance mode, whether it is running or not, when you perform an upgrade from Serviceguard A.11.19 to any later version, including an upgrade from the initial release of A.11.19 to the July 2009 or later patch. This means that: • You must make sure no packages are in maintenance mode when you start the upgrade. • You must not put any package in maintenance mode until all the nodes are upgraded. Breaking this rule will leave the cluster in an inconsistent state.
sysconfig/network/ifcfg*(or /etc/sysconfig/ network-scripts/ifcfg*) and bonding files. Verify that the network configurations are the same prior to the upgrade or the new installation. Check the current interface eth0 has the same corresponding Mac address before and after. 4. Verify that all disks and their filesystems are the same prior to this OS upgrade or new installation. Check and compare with the disk layout collected before the upgrade.
a. b. c. d. Run the # lsmod | grep deadman command and verify whether deadman is already loaded. If deadman is already loaded, you must remove it. Run # rmmod deadman command to remove the deadman. To build and install deadman module, run the following commands in the $SGROOT/ drivers directory: 1) To make the module run the # make modules command. 2) To install the module run the # make modules_install command. 3) To insert the module run the # insmod deadman.ko command.
Example The following example shows a simple rolling upgrade on two nodes running one package each. NOTE: This and the following figures are from a use case in which the starting point of the upgrade was Serviceguard A.11.19 and Red Hat Enterprise Linux 5.7, and the rolling upgrade was to Serviceguard A.11.20.00. Figure 1 Running cluster before rolling upgrade Step 1. Halt first node Halt the first node, as follows # cmhaltnode -f node1 This will cause Pkg1 to be halted cleanly and moved to node 2.
Figure 3 Node 1 upgraded to Serviceguard A.11.20.00 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. # cmrunnode -n node1 At this point, different versions of the Serviceguard daemon (cmcld) are running on the two nodes, as shown in Figure 4. Figure 4 Node 1 rejoining the cluster Step 4. Repeat the process on next node Repeat the process on node2.
Figure 5 Running cluster with packages moved to node 1 Step 5. Move package back to original node Move pkg2 back to its original node. Use the following commands: # cmhaltpkg pkg2 # cmrunpkg -n node2 pkg2 # cmmodpkg -e pkg2 The cmmodpkg command re-enables switching of the package, which is disabled by the cmhaltpkg command. The final running cluster is shown in Figure 1-6. Figure 6 Running cluster after upgrades Rolling upgrade from A.11.19.X to A.11.20.
3. Uninstall sg_pidentd rpm. CAUTION: Serviceguard commands will not work unless step 5 is complete. You cannot change the cluster configuration files until the process of upgrade is complete on all nodes. For example, #rpm -e --nodeps sg_pidentd-3.0.19-2 4. Install authd rpm from the Linux Distribution DVD or Repository For example, #rpm -i 5. Upgrade node1. The following examples show only the Serviceguard rpm.
Rolling software upgrade for Serviceguard XDC environment If you have already deployed XDC A.01.01 or later with HP Serviceguard for Linux A.11.19.xx, you can upgrade HP Serviceguard and XDC software one node at a time without bringing down your clusters. You can complete this process at a time when one system needs to be taken offline for hardware maintenance or patch installations. On Red Hat Enterprise Linux 5: If Serviceguard A.11.19.
1. 2. 3. Ensure to complete the steps mentioned under “Pre-installation checklist for Serviceguard Manager” (page 17) Rolling upgrade to Serviceguard Manager B.03.31.10 is not supported and users need to uninstall the existing version of the following products: • Serviceguard Manager • sgmgr-tomcat Reinstall the following products from Serviceguard Linux A.11.20.10 bundle: NOTE: You must remove and install HPSMH before reinstalling the below mentioned rpms if the HPSMH version is older than 7.1.0-16.
Legacy packages In A.11.20, you can create new packages using the legacy method (the method used before Serviceguard A.11.18; see Chapter 7: Configuring a Legacy Package of Managing HP Serviceguard for Linux). In some cases new capabilities provided in modular packages (those created by the method introduced in A.11.18) have been added to legacy packages as well. Use the modular method to create new packages whenever possible. See Chapter 6 of Managing HP Serviceguard for Linux for more information. .
