HP Serviceguard for Linux Enterprise Version 12.00.
© Copyright 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 2 3 4 Overview.............................................................................................................................5 Supported platforms and Linux distributions...............................................................................5 Packaging information............................................................................................................5 Licensing information...................................................................................
1 Overview This document provides information about HP Serviceguard for Linux Enterprise version 12.00.00. 2 Supported platforms and Linux distributions HP Serviceguard for Linux Enterprise 12.00.
than the total amount of active sockets if Serviceguard is used within virtual machine which utilized less than the total number of sockets. For information about the supported server models, see the QuickSpecs available at http://h18000.www1.hp.com/products/quickspecs/11518_na/ 11518_na.pdf. 4.1 Obtaining a permanent license Before your 90 days instant-on license expires, you must obtain and validate the permanent license to continue to use Serviceguard for Linux 12.00.00 beyond the 90 days grace period.
The mySGlicense file contains the license information. 3. Run the cmgetlicense command: cmgetlicense -f line 4. If the license is valid, keep the new license file $SGCONF/AutoPass/LicFile.txt and delete the old license file $SGCONF/AutoPass/LicFile.txt.sav. If the license is invalid, restore the original license: mv $SGCONF/AutoPass/LicFile.txt.sav $SGCONF/AutoPass/LicFile.txt 4.
For more information about YUM and YaST, see the following: • Red Hat Enterprise Linux Deployment Guide at https://access.redhat.com/site/documentation/ en-US/Red_Hat_Enterprise_Linux/. • SUSE Linux Enterprise Server 11 Deployment Guide at http://www.suse.com/documentation/ sles11/. 6 Compatibility and installation requirements 6.1 Hardware requirements For more information about hardware requirements, see the latest version of HP Serviceguard for Linux Certification Matrix at http://www.hp.
6.2.4 Ports needed by Metrocluster with 3PAR Remote Copy • 5783 TCP HP 3PAR Inform OS CLI secure port • 5782 TCP HP 3PAR Inform OS CLI secure port • 2550 TCP HP 3PAR old Inform OS CLI port 6.2.5 Ports needed by Metrocluster with Continuous Access EVA P6000 • 5988/5989 EVA SMI-S default ports 6.2.6 Ports needed by Metrocluster with Continuous Access XP P9000 • Metrocluster for XP requires RAID manager to be configured and a raid manager instance requires a user configured port.
Table 1 RPMs (prerequisites) for installing Serviceguard for Linux A.12.00.
NOTE: • HP recommends you to install all the products that are part of the HP Serviceguard for Linux Enterprise 12.00.00. • Starting Serviceguard 12.00.00, legacy packages are obsolete. If you have configured legacy packages, you need to migrate to modular packages before you move to 12.00.00. For more information about how to migrate to modular packages, see the white paper Migrating packages from legacy to modular style available at http://www.hp.com/go/ linux-serviceguard-docs. 6.4.
see “Software prerequisites for HP Serviceguard for Linux”. If not already installed, you will be prompted to install these packages for the installation to complete successfully. To run the cmeasyinstall tool: 1. 2. 3. Mount the HP Serviceguard for Linux DVD or ISO image. Open a terminal window to the server from the console or an ssh client. Execute the cmeasyinstall command with appropriate qualifiers.
NOTE: You cannot use the cmeasyinstall tool to upgrade HP Serviceguard for Linux and its components. If you have already installed HP Serviceguard for Linux and its components, the cmeasyinstall tool exits with an appropriate error message. NOTE: The cmeasyinstall does not install HP Serviceguard Metrocluster with Continuous Access EVA P6000 for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using —a option. You need to do the following: 1.
On Red Hat Enterprise Linux 6: rpm -ivh serviceguard-A.12.00.00-0.rhel6.x86_64.rpm On SUSE Linux Enterprise Server 11: rpm -ivh serviceguard-A.12.00.00-0.sles11.x86_64.rpm IMPORTANT: After the Serviceguard Manager RPM installation is complete, you need to follow the procedure described later in this section to start sgmgr service and also create a user which can be used as a replicated user for multi-cluster management. Note: Only sgmgr user can perform configuration tasks.
1. Download the patch depending on the package from the HP Support Centre at http:// www.hp.com/go/hpsc. IMPORTANT: Before you install the patch, ensure that HP Serviceguard for Linux Enterprise 12.00.00 is installed on your system. 2. 3. 4. 5. Extract the patch files from the file. Verify the signature of the RPM. For more information about how to verify the signature of the RPM, see https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do? productNumber=HPLinuxCodeSigning.
6.6 Post installation After the installation is complete, you need to configure the cluster. For more information about how to configure the Serviceguard cluster, see chapter 5 of Managing HP Serviceguard A.12.00.00 for Linux available at http://www.hp.com/go/linux-serviceguard-docs. 7 Rolling software upgrade You can upgrade the Linux operating system and the Serviceguard software one node at a time without bringing down your clusters.
NOTE: HP recommends you to use the rolling upgrade process which: • Helps you upgrade to the latest software version. • Preserves the current OS and cluster configuration. • Keeps running your mission-critical applications. Before you upgrade, ensure that you read the “Limitations of rolling upgrades” and complete the entire upgrade process before you can use any Serviceguard commands.
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 ensure that 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.
Table 5 Upgrade paths Rolling upgrade using cmupgrade tool Rolling upgrade the traditional way Offline upgrade To upgrade from A.11.20.X to A.12.00.00 Yes Yes Yes To upgrade from A.11.19.X to A.12.00.00 No Yes Yes To upgrade from A.11.18.X to A.12.00.00 No No Yes Serviceguard version 7.6 Performing rolling upgrades You can perform online or offline rolling upgrade of HP Serviceguard for Linux across major versions starting from A.11.20.
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. For example, #cmhaltnode -f node1 3. You can upgrade node as follows: a. Export the SGMGR_ENV environment variable: SGMGR_ENV= where, is the password that you want to set for Serviceguard Manager user.
For example, #cmhaltnode -f node1 3. You can upgrade node 1 in the same order as described in the “Packaging information”. For example, Serviceguard rpm for Red Hat 5 x86_64 #rpm –Uvh serviceguard-A.12.00.00-0.rhel5.x86_64.rpm NOTE: • • To upgrade toolkits, use rpm –Uvh with appropriate qualifiers. For more information about qualifiers, see the following documents available at http://www.hp.
3. Create a /etc/yum.repos.d/sglxpatch.repo YUM repository configuration file with the following contents: [sglxpatchrepo] name=sglxrpms baseurl=file:///RedHat/ enabled=1 where: is the mount path where ISO image or DVD is mounted for the main release or the extracted patch location for a patch. is the value that can be either Red Hat 5 or Red Hat 6. 4. Run the following command: #yum clean all 5.
is the mount path where ISO image or DVD is mounted for the main release or the extracted patch location for a patch. 4. Run the following command: #/usr/bin/zypper clean 5. If you are upgrading Serviceguard Manager RPM, do the following: #/opt/hp/cmcluster/serviceguardmanager/Serviceguard_manager_setup/-l -o erase 6. Upgrade all the RPMs.
NOTE: • • When you upgrade toolkits, use rpm –Uvh with appropriate qualifiers. For more information about qualifiers, see the following documents available at http:// www.hp.com/go/linux-serviceguard-docs: ◦ HP Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes Version A.12.00.00 ◦ HP Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux Release Notes Version A.12.00.00 ◦ HP Serviceguard Toolkit for Oracle on Linux Release Notes Version A.12.00.
NOTE: • • When you upgrade toolkits, use rpm –Uvh with appropriate qualifiers. For more information about qualifiers, see the following documents available at http:// www.hp.com/go/linux-serviceguard-docs: ◦ HP Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes Version A.12.00.00 ◦ HP Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux Release Notes Version A.12.00.00 ◦ HP Serviceguard Toolkit for Oracle on Linux Release Notes Version A.12.00.
9 Troubleshooting The following table describes how to troubleshoot issues related to Serviceguard Manager installation: Problem Solution The sgmgr user is not created during installation of You must create the sgmgr user manually and the password Serviceguard Manager. must be same as on the other system. To create the sgmgr user manually: a. Add the user: useradd sgmgr b. Enter the password: passwd sgmgr Login failure For Local user: • Check if PAM module is installed in your Linux system.
• Metrocluster with Continuous Access XP P9000 for Linux Version B.12.00.00 Release Notes • Metrocluster with 3PAR Remote Copy for Linux Version B.12.00.00 Release Notes • Continentalclusters for Linux Version B.12.00.00 Release Notes • HP Serviceguard Extended Distance Cluster for Linux A.12.00.00 Deployment Guide • HP Serviceguard Extension for SAP Version A.06.00 Release Notes for Linux 11 Documentation feedback HP is committed to providing documentation that meets your needs.