HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ......

48
HPE Serviceguard for Linux Enterprise edition 12.10.00 Release Notes Part Number: 766797-008 Published: June 2017

Transcript of HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ......

Page 1: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

HPE Serviceguard for Linux Enterpriseedition 121000 Release Notes

Part Number 766797-008Published June 2017

Contents

Overview6

Supported platforms and Linux distributions7

Packaging information 8

Licensing information 9Obtaining a permanent license9Renewing the permanent license 9Validating the permanent license10

Compatibility and installation requirements12Hardware requirements12Port requirements12

Ports needed for Serviceguard12Ports needed for authentication12Ports needed by Serviceguard Manager 12System firewalls13

Supported browsers15

Software prerequisites for Serviceguard for Linux 16

Installing Serviceguard for Linux19Installing Serviceguard for Linux using cmeasyinstall 19Installing Serviceguard for Linux the traditional way 21Installing Serviceguard for Linux Patch 22Post installation 24

Rolling software upgrade25Requirements 25Limitations of rolling upgrades26Preparation26Rolling upgrade on OS 27Supported rolling upgrade paths 28Performing rolling upgrades 29

Rolling upgrade from 1120X to 121000 29Upgrading Serviceguard for Linux using cmupgrade tool29Upgrading Serviceguard for Linux the traditional way 31Upgrading Serviceguard for Linux using YUM or Zypper 32

Rolling upgrade from 1119X to 121000 34

2 Contents

Performing offline rolling upgrade from 1118X to 121000 35Rolling upgrade from 1200X to 1210X36

Upgrading Serviceguard for Linux using cmupgrade tool36Upgrading Serviceguard for Linux the traditional way 37Upgrading Serviceguard for Linux using YUM or Zypper 38

Rolling upgrade from A1119X to A1210X 40Offline rolling upgrade from A1118X to A1210X 40

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for Linux 42

Troubleshooting43

Related information 47

Documentation feedback 48

Contents 3

NoticesThe information contained herein is subject to change without notice The only warranties for Hewlett PackardEnterprise products and services are set forth in the express warranty statements accompanying suchproducts and services Nothing herein should be construed as constituting an additional warranty HewlettPackard Enterprise shall not be liable for technical or editorial errors or omissions contained herein

Confidential computer software Valid license from Hewlett Packard Enterprise required for possession useor copying Consistent with FAR 12211 and 12212 Commercial Computer Software Computer SoftwareDocumentation and Technical Data for Commercial Items are licensed to the US Government undervendors standard commercial license

Links to third-party websites take you outside the Hewlett Packard Enterprise website Hewlett PackardEnterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprisewebsite

4 Notices

AcknowledgmentsIntelreg Itaniumreg Pentiumreg Intel Insidereg and the Intel Inside logo are trademarks of Intel Corporation in theUnited States and other countries

Microsoftreg and Windowsreg are either registered trademarks or trademarks of Microsoft Corporation in theUnited States andor other countries

Adobereg and Acrobatreg are trademarks of Adobe Systems Incorporated

Javareg and Oraclereg are registered trademarks of Oracle andor its affiliates

UNIXreg is a registered trademark of The Open Group

Linuxreg is the registered trademark of Linus Torvalds in the US and other countries

Red Hatreg is a registered trademark of Red Hat Inc in the United States and other countries

SUSEreg is a registered trademark of SUSE AG a Novell Business

Acknowledgments 5

OverviewThis document provides information about HPE Serviceguard for Linux Enterprise edition 121000

6 Overview

Supported platforms and Linux distributionsServiceguard for Linux Enterprise edition 121000 is available on the following Linux distributions

bull Red Hat Enterprise Linux 6 or Advanced platformbull Red Hat Enterprise Linux 7bull SUSE Linux Enterprise Server 11bull SUSE Linux Enterprise Server 12

NOTE

For more information about supported updates supported hardware storage and other informationsee the latest version of HPE Serviceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Supported platforms and Linux distributions 7

Packaging informationServiceguard for Linux 121000 is available on all three editions namely Serviceguard for Linux BaseServiceguard for Linux Advanced and Serviceguard for Linux Enterprise Serviceguard for Linux Enterpriseedition 121000 June 2017 contains rpms for the following components

bull Serviceguard Licensebull Serviceguard for Linuxbull Serviceguard for Linux snmpbull Serviceguard for Linux WBEM providersbull Serviceguard for Linux analyticsbull Serviceguard Quorum Serverbull Serviceguard Managerbull Serviceguard Toolkit for Enterprise DB PPAS for Linuxbull HPE Serviceguard Toolkit for Oracle Database for Linuxbull HPE Serviceguard Toolkit for SAP Sybase ASE and Sybase Replication Server for Linuxbull Serviceguard Extension for SAPbull Serviceguard XDC for Linuxbull Metrocluster with Continuous Access XP P9000 for Linuxbull Metrocluster with 3PAR Remote Copy fo Linuxbull Metrocluster with Continuous Access EVA P6000 for Linuxbull Serviceguard Toolkit for KVM on Linuxbull Metrocluster with EMC SRDFbull HPE Serviceguard Toolkit for Oracle Data Guard on Linux

8 Packaging information

Licensing informationStarting Serviceguard for Linux 120000 requires licenses on per-socket basis When you installServiceguard for Linux Enterprise edition an instant-on license valid for 90 days is installed With this instant-on license you can use the product even if you do not have a permanent license You must get a permanentlicense before the grace period expires

When ordering the licenses determine the number of active sockets on the server and order one license foreach active socket irrespective of number of cores A virtualized server may select less than the total amountof active sockets if Serviceguard is used within virtual machine which utilized less than the total number ofsockets For information about the license terms and supported server models see the QuickSpecs availableat httpwwwhpecominfoquickspecs

IMPORTANT

If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 youcan use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

Obtaining a permanent licenseBefore your 90 days instant-on license expires you must obtain and validate the permanent license tocontinue to use applicable Serviceguard versions beyond the grace period

To obtain a permanent license

1 Go to httpsmyenterpriselicensehpecom2 Log into HPE Passport If you do not have an account you can create one3 Enter Entitlement Order Number and click Go

bull Here are the licenses listed that have been activated and license that have not yet been activated4 Check the box that belongs to products you want to activate and click Next5 Select ldquoif you are activating for yourselfrdquo or ldquoif you are activating on behalf of another customerrdquo If ldquoon

behalf of another customerrdquo is selected you will enter the final user email address6 Activation Completes Save the files One includes the license key and the other includes additional

product information7 You will receive a license certificate in your email box You must retain the email message because this is

the valid proof of purchase documentation you may need for future reference or support requests

IMPORTANT

Ensure that you save the file and make a note of its path (See the example in Validating thepermanent license on page 10)

Renewing the permanent licenseAfter you have obtained the permanent license follow these steps to renew the license

NOTE

You must renew or apply the license on each node

Procedure

1 Ensure that $SGCONFAutoPassLicFiletxt exists

Licensing information 9

NOTE

Hewlett Packard Enterprise recommends that you back up the $SGCONFAutoPassLicFiletxtbefore renewing the license

2 Place the permanent license key in a file on the system

NOTE

Ensure the file that contains the license key must not have the commented line

3 Renew the license

cmsetlicense -i ltabsolute path of the license filegtOn successful license renewal it displays the following message

License is successfully installedFor more information see cmsetlicense(1m) manpage

Example

To verify if the license is valid

a Copy the license file

cp $SGCONFAutoPassLicFiletxt $SGCONFAutoPassLicFiletxtsavb Run the cmsetlicense command

cmsetlicense -i testmySGlicenseThe mySGlicense file contains the license information

c Run the cmgetlicense command

cmgetlicense -f lined If the license is valid keep the new license file $SGCONFAutoPassLicFiletxt and delete the old

license file $SGCONFAutoPassLicFiletxtsav

If the license is invalid restore the original license

mv $SGCONFAutoPassLicFiletxtsav $SGCONFAutoPassLicFiletxt

Validating the permanent licenseIMPORTANT

Ensure that you validate the permanent license before the 90ndashday grace period of instant-on licenseexpires

To validate the permanent license

1 Run the following command

cmgetlicense -f line2 On successful renewal the command displays the following output

cmgetlicense -f line

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

10 Validating the permanent license

NOTE

bull If you install higher license than the one already installed on the system the license on the nodeis upgraded automatically

For example if you have Serviceguard for Advanced and install Serviceguard for Enterprise thelicense on the node is upgraded to Enterprise and the cmgetlicense -f line commanddisplays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

bull If you have multiple licenses of the same type installed on the system the cmgetlicense -fline command displays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=3 nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

Licensing information 11

Compatibility and installation requirements

Hardware requirementsFor more information about hardware requirements see the latest version of HPE Serviceguard for LinuxCertification Matrix at httpwwwhpecominfolinux-serviceguard-docs

Port requirements

Ports needed for ServiceguardBefore installing ensure that no other program uses these ports

On Red Hat Enterprise Linux and SUSE Linux Enterprise Server

bull icmp 8icmpbull hacl-hb 5300TCP High Availability (HA) Cluster heartbeatbull hacl-hb 5300UDP High Availability (HA) Cluster heartbeatbull hacl-cfg 5302TCP HA Cluster TCP configurationbull hacl-cfg 5302UDP HA Cluster UDP configurationbull hacl-local 5304TCP HA Cluster Commands

If you are using SNMP

bull snmp 161UDPbull snmptrap 162UDP

If you are using the WBEM provider

bull wbem-http TCP5988bull wbem-https TCP5989

If you are using the Quorum Server

bull hacl-qs 1238TCP HA Quorum Server

If you are using the appserver utility

bull hacl-poll 5315TCP

If you are using VMware VMFS volumes

bull https 443TCP

Ports needed for authenticationThe ports reserved for authentication are also used by Serviceguard

bull auth 113TCP authenticationbull auth 113UDP authentication

Ports needed by Serviceguard Managerbull 5511 (http) and 5522 (https) 5301 (multicast port) are used by Serviceguard Managerbull Serviceguard Manager needs a multicast IP address and a TCPIP port for auto-discovery of the nodes in

the subnet Serviceguard uses default multicast IP 235111 and 5301 port which are configured in thesetting page

12 Compatibility and installation requirements

NOTE

Only IP address can be modified by the user The default port 5301 cannot be modified

System firewallsSystem firewalls When using a system firewall with Serviceguard for Linux you must leave open the portslisted above For more information see the latest version of Configuring firewall rules for HP Serviceguard onSUSE Linux Enterprise Server and Red Hat White Paper at httpwwwhpecominfolinux-serviceguard-docs mdashgt Whitepapers

Serviceguard also uses some dynamic ports for some cluster services These must be open in the firewallThey are typically in the range 32768-61000 for Red Hat To determine the range on a given system checkthe contents of the file procsysnetipv4ip_local_port_range

If you have adjusted the dynamic port range using kernel tunable parameters alter your firewall rulesaccordingly

bull To enable intra-cluster communications each HEARTBEAT_IP network on every node in the cluster mustallow the following communications in both directions with all other nodes in the cluster

TCP on port numbers 5300 and 5302 ndash and allow only packets with the SYN flag UDP on port numbers 5300 and 5302 TCP and UDP on dynamic ports

bull If you use a quorum server all nodes in the cluster must allow the following communication to the quorumserver IP address

TCP on port 1238 mdash and allow only packets with the SYN flag

Any node providing quorum service for another cluster must allow the following communication fromthat clusterrsquos nodes

TCP on port 1238 mdash and allow only packets with the SYN flagbull Running the cmscancl command requires the ssh port be open

There are additional firewall requirements to enable execution of Serviceguard commands from nodesoutside the cluster such as those listed in cmclnodelist To allow execution of Serviceguard commandsfollow these guidelines

All nodes in the cluster must allow the following communicationsbull from the remote nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

bull to the remote nodes

TCP and UDP on dynamic ports

The remote nodes must allow the following communicationsbull from the cluster nodes

TCP and UDP on dynamic portsbull to the cluster nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

Authentication communication must allow the following ports

System firewalls 13

bull from the cluster nodes

TCP and UDP on port 113bull to the cluster nodes

TCP and UDP on port 113

NOTE

If you suspect that the firewall is blocking communications you can add -j LOG before the last line inyour iptables file (for example etcsysconfigiptables) to log any blocked ports Consult your Linuxdistributionrsquos documentation on firewalls for information on iptables

14 Compatibility and installation requirements

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 2: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Contents

Overview6

Supported platforms and Linux distributions7

Packaging information 8

Licensing information 9Obtaining a permanent license9Renewing the permanent license 9Validating the permanent license10

Compatibility and installation requirements12Hardware requirements12Port requirements12

Ports needed for Serviceguard12Ports needed for authentication12Ports needed by Serviceguard Manager 12System firewalls13

Supported browsers15

Software prerequisites for Serviceguard for Linux 16

Installing Serviceguard for Linux19Installing Serviceguard for Linux using cmeasyinstall 19Installing Serviceguard for Linux the traditional way 21Installing Serviceguard for Linux Patch 22Post installation 24

Rolling software upgrade25Requirements 25Limitations of rolling upgrades26Preparation26Rolling upgrade on OS 27Supported rolling upgrade paths 28Performing rolling upgrades 29

Rolling upgrade from 1120X to 121000 29Upgrading Serviceguard for Linux using cmupgrade tool29Upgrading Serviceguard for Linux the traditional way 31Upgrading Serviceguard for Linux using YUM or Zypper 32

Rolling upgrade from 1119X to 121000 34

2 Contents

Performing offline rolling upgrade from 1118X to 121000 35Rolling upgrade from 1200X to 1210X36

Upgrading Serviceguard for Linux using cmupgrade tool36Upgrading Serviceguard for Linux the traditional way 37Upgrading Serviceguard for Linux using YUM or Zypper 38

Rolling upgrade from A1119X to A1210X 40Offline rolling upgrade from A1118X to A1210X 40

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for Linux 42

Troubleshooting43

Related information 47

Documentation feedback 48

Contents 3

NoticesThe information contained herein is subject to change without notice The only warranties for Hewlett PackardEnterprise products and services are set forth in the express warranty statements accompanying suchproducts and services Nothing herein should be construed as constituting an additional warranty HewlettPackard Enterprise shall not be liable for technical or editorial errors or omissions contained herein

Confidential computer software Valid license from Hewlett Packard Enterprise required for possession useor copying Consistent with FAR 12211 and 12212 Commercial Computer Software Computer SoftwareDocumentation and Technical Data for Commercial Items are licensed to the US Government undervendors standard commercial license

Links to third-party websites take you outside the Hewlett Packard Enterprise website Hewlett PackardEnterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprisewebsite

4 Notices

AcknowledgmentsIntelreg Itaniumreg Pentiumreg Intel Insidereg and the Intel Inside logo are trademarks of Intel Corporation in theUnited States and other countries

Microsoftreg and Windowsreg are either registered trademarks or trademarks of Microsoft Corporation in theUnited States andor other countries

Adobereg and Acrobatreg are trademarks of Adobe Systems Incorporated

Javareg and Oraclereg are registered trademarks of Oracle andor its affiliates

UNIXreg is a registered trademark of The Open Group

Linuxreg is the registered trademark of Linus Torvalds in the US and other countries

Red Hatreg is a registered trademark of Red Hat Inc in the United States and other countries

SUSEreg is a registered trademark of SUSE AG a Novell Business

Acknowledgments 5

OverviewThis document provides information about HPE Serviceguard for Linux Enterprise edition 121000

6 Overview

Supported platforms and Linux distributionsServiceguard for Linux Enterprise edition 121000 is available on the following Linux distributions

bull Red Hat Enterprise Linux 6 or Advanced platformbull Red Hat Enterprise Linux 7bull SUSE Linux Enterprise Server 11bull SUSE Linux Enterprise Server 12

NOTE

For more information about supported updates supported hardware storage and other informationsee the latest version of HPE Serviceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Supported platforms and Linux distributions 7

Packaging informationServiceguard for Linux 121000 is available on all three editions namely Serviceguard for Linux BaseServiceguard for Linux Advanced and Serviceguard for Linux Enterprise Serviceguard for Linux Enterpriseedition 121000 June 2017 contains rpms for the following components

bull Serviceguard Licensebull Serviceguard for Linuxbull Serviceguard for Linux snmpbull Serviceguard for Linux WBEM providersbull Serviceguard for Linux analyticsbull Serviceguard Quorum Serverbull Serviceguard Managerbull Serviceguard Toolkit for Enterprise DB PPAS for Linuxbull HPE Serviceguard Toolkit for Oracle Database for Linuxbull HPE Serviceguard Toolkit for SAP Sybase ASE and Sybase Replication Server for Linuxbull Serviceguard Extension for SAPbull Serviceguard XDC for Linuxbull Metrocluster with Continuous Access XP P9000 for Linuxbull Metrocluster with 3PAR Remote Copy fo Linuxbull Metrocluster with Continuous Access EVA P6000 for Linuxbull Serviceguard Toolkit for KVM on Linuxbull Metrocluster with EMC SRDFbull HPE Serviceguard Toolkit for Oracle Data Guard on Linux

8 Packaging information

Licensing informationStarting Serviceguard for Linux 120000 requires licenses on per-socket basis When you installServiceguard for Linux Enterprise edition an instant-on license valid for 90 days is installed With this instant-on license you can use the product even if you do not have a permanent license You must get a permanentlicense before the grace period expires

When ordering the licenses determine the number of active sockets on the server and order one license foreach active socket irrespective of number of cores A virtualized server may select less than the total amountof active sockets if Serviceguard is used within virtual machine which utilized less than the total number ofsockets For information about the license terms and supported server models see the QuickSpecs availableat httpwwwhpecominfoquickspecs

IMPORTANT

If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 youcan use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

Obtaining a permanent licenseBefore your 90 days instant-on license expires you must obtain and validate the permanent license tocontinue to use applicable Serviceguard versions beyond the grace period

To obtain a permanent license

1 Go to httpsmyenterpriselicensehpecom2 Log into HPE Passport If you do not have an account you can create one3 Enter Entitlement Order Number and click Go

bull Here are the licenses listed that have been activated and license that have not yet been activated4 Check the box that belongs to products you want to activate and click Next5 Select ldquoif you are activating for yourselfrdquo or ldquoif you are activating on behalf of another customerrdquo If ldquoon

behalf of another customerrdquo is selected you will enter the final user email address6 Activation Completes Save the files One includes the license key and the other includes additional

product information7 You will receive a license certificate in your email box You must retain the email message because this is

the valid proof of purchase documentation you may need for future reference or support requests

IMPORTANT

Ensure that you save the file and make a note of its path (See the example in Validating thepermanent license on page 10)

Renewing the permanent licenseAfter you have obtained the permanent license follow these steps to renew the license

NOTE

You must renew or apply the license on each node

Procedure

1 Ensure that $SGCONFAutoPassLicFiletxt exists

Licensing information 9

NOTE

Hewlett Packard Enterprise recommends that you back up the $SGCONFAutoPassLicFiletxtbefore renewing the license

2 Place the permanent license key in a file on the system

NOTE

Ensure the file that contains the license key must not have the commented line

3 Renew the license

cmsetlicense -i ltabsolute path of the license filegtOn successful license renewal it displays the following message

License is successfully installedFor more information see cmsetlicense(1m) manpage

Example

To verify if the license is valid

a Copy the license file

cp $SGCONFAutoPassLicFiletxt $SGCONFAutoPassLicFiletxtsavb Run the cmsetlicense command

cmsetlicense -i testmySGlicenseThe mySGlicense file contains the license information

c Run the cmgetlicense command

cmgetlicense -f lined If the license is valid keep the new license file $SGCONFAutoPassLicFiletxt and delete the old

license file $SGCONFAutoPassLicFiletxtsav

If the license is invalid restore the original license

mv $SGCONFAutoPassLicFiletxtsav $SGCONFAutoPassLicFiletxt

Validating the permanent licenseIMPORTANT

Ensure that you validate the permanent license before the 90ndashday grace period of instant-on licenseexpires

To validate the permanent license

1 Run the following command

cmgetlicense -f line2 On successful renewal the command displays the following output

cmgetlicense -f line

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

10 Validating the permanent license

NOTE

bull If you install higher license than the one already installed on the system the license on the nodeis upgraded automatically

For example if you have Serviceguard for Advanced and install Serviceguard for Enterprise thelicense on the node is upgraded to Enterprise and the cmgetlicense -f line commanddisplays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

bull If you have multiple licenses of the same type installed on the system the cmgetlicense -fline command displays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=3 nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

Licensing information 11

Compatibility and installation requirements

Hardware requirementsFor more information about hardware requirements see the latest version of HPE Serviceguard for LinuxCertification Matrix at httpwwwhpecominfolinux-serviceguard-docs

Port requirements

Ports needed for ServiceguardBefore installing ensure that no other program uses these ports

On Red Hat Enterprise Linux and SUSE Linux Enterprise Server

bull icmp 8icmpbull hacl-hb 5300TCP High Availability (HA) Cluster heartbeatbull hacl-hb 5300UDP High Availability (HA) Cluster heartbeatbull hacl-cfg 5302TCP HA Cluster TCP configurationbull hacl-cfg 5302UDP HA Cluster UDP configurationbull hacl-local 5304TCP HA Cluster Commands

If you are using SNMP

bull snmp 161UDPbull snmptrap 162UDP

If you are using the WBEM provider

bull wbem-http TCP5988bull wbem-https TCP5989

If you are using the Quorum Server

bull hacl-qs 1238TCP HA Quorum Server

If you are using the appserver utility

bull hacl-poll 5315TCP

If you are using VMware VMFS volumes

bull https 443TCP

Ports needed for authenticationThe ports reserved for authentication are also used by Serviceguard

bull auth 113TCP authenticationbull auth 113UDP authentication

Ports needed by Serviceguard Managerbull 5511 (http) and 5522 (https) 5301 (multicast port) are used by Serviceguard Managerbull Serviceguard Manager needs a multicast IP address and a TCPIP port for auto-discovery of the nodes in

the subnet Serviceguard uses default multicast IP 235111 and 5301 port which are configured in thesetting page

12 Compatibility and installation requirements

NOTE

Only IP address can be modified by the user The default port 5301 cannot be modified

System firewallsSystem firewalls When using a system firewall with Serviceguard for Linux you must leave open the portslisted above For more information see the latest version of Configuring firewall rules for HP Serviceguard onSUSE Linux Enterprise Server and Red Hat White Paper at httpwwwhpecominfolinux-serviceguard-docs mdashgt Whitepapers

Serviceguard also uses some dynamic ports for some cluster services These must be open in the firewallThey are typically in the range 32768-61000 for Red Hat To determine the range on a given system checkthe contents of the file procsysnetipv4ip_local_port_range

If you have adjusted the dynamic port range using kernel tunable parameters alter your firewall rulesaccordingly

bull To enable intra-cluster communications each HEARTBEAT_IP network on every node in the cluster mustallow the following communications in both directions with all other nodes in the cluster

TCP on port numbers 5300 and 5302 ndash and allow only packets with the SYN flag UDP on port numbers 5300 and 5302 TCP and UDP on dynamic ports

bull If you use a quorum server all nodes in the cluster must allow the following communication to the quorumserver IP address

TCP on port 1238 mdash and allow only packets with the SYN flag

Any node providing quorum service for another cluster must allow the following communication fromthat clusterrsquos nodes

TCP on port 1238 mdash and allow only packets with the SYN flagbull Running the cmscancl command requires the ssh port be open

There are additional firewall requirements to enable execution of Serviceguard commands from nodesoutside the cluster such as those listed in cmclnodelist To allow execution of Serviceguard commandsfollow these guidelines

All nodes in the cluster must allow the following communicationsbull from the remote nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

bull to the remote nodes

TCP and UDP on dynamic ports

The remote nodes must allow the following communicationsbull from the cluster nodes

TCP and UDP on dynamic portsbull to the cluster nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

Authentication communication must allow the following ports

System firewalls 13

bull from the cluster nodes

TCP and UDP on port 113bull to the cluster nodes

TCP and UDP on port 113

NOTE

If you suspect that the firewall is blocking communications you can add -j LOG before the last line inyour iptables file (for example etcsysconfigiptables) to log any blocked ports Consult your Linuxdistributionrsquos documentation on firewalls for information on iptables

14 Compatibility and installation requirements

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 3: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Performing offline rolling upgrade from 1118X to 121000 35Rolling upgrade from 1200X to 1210X36

Upgrading Serviceguard for Linux using cmupgrade tool36Upgrading Serviceguard for Linux the traditional way 37Upgrading Serviceguard for Linux using YUM or Zypper 38

Rolling upgrade from A1119X to A1210X 40Offline rolling upgrade from A1118X to A1210X 40

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for Linux 42

Troubleshooting43

Related information 47

Documentation feedback 48

Contents 3

NoticesThe information contained herein is subject to change without notice The only warranties for Hewlett PackardEnterprise products and services are set forth in the express warranty statements accompanying suchproducts and services Nothing herein should be construed as constituting an additional warranty HewlettPackard Enterprise shall not be liable for technical or editorial errors or omissions contained herein

Confidential computer software Valid license from Hewlett Packard Enterprise required for possession useor copying Consistent with FAR 12211 and 12212 Commercial Computer Software Computer SoftwareDocumentation and Technical Data for Commercial Items are licensed to the US Government undervendors standard commercial license

Links to third-party websites take you outside the Hewlett Packard Enterprise website Hewlett PackardEnterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprisewebsite

4 Notices

AcknowledgmentsIntelreg Itaniumreg Pentiumreg Intel Insidereg and the Intel Inside logo are trademarks of Intel Corporation in theUnited States and other countries

Microsoftreg and Windowsreg are either registered trademarks or trademarks of Microsoft Corporation in theUnited States andor other countries

Adobereg and Acrobatreg are trademarks of Adobe Systems Incorporated

Javareg and Oraclereg are registered trademarks of Oracle andor its affiliates

UNIXreg is a registered trademark of The Open Group

Linuxreg is the registered trademark of Linus Torvalds in the US and other countries

Red Hatreg is a registered trademark of Red Hat Inc in the United States and other countries

SUSEreg is a registered trademark of SUSE AG a Novell Business

Acknowledgments 5

OverviewThis document provides information about HPE Serviceguard for Linux Enterprise edition 121000

6 Overview

Supported platforms and Linux distributionsServiceguard for Linux Enterprise edition 121000 is available on the following Linux distributions

bull Red Hat Enterprise Linux 6 or Advanced platformbull Red Hat Enterprise Linux 7bull SUSE Linux Enterprise Server 11bull SUSE Linux Enterprise Server 12

NOTE

For more information about supported updates supported hardware storage and other informationsee the latest version of HPE Serviceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Supported platforms and Linux distributions 7

Packaging informationServiceguard for Linux 121000 is available on all three editions namely Serviceguard for Linux BaseServiceguard for Linux Advanced and Serviceguard for Linux Enterprise Serviceguard for Linux Enterpriseedition 121000 June 2017 contains rpms for the following components

bull Serviceguard Licensebull Serviceguard for Linuxbull Serviceguard for Linux snmpbull Serviceguard for Linux WBEM providersbull Serviceguard for Linux analyticsbull Serviceguard Quorum Serverbull Serviceguard Managerbull Serviceguard Toolkit for Enterprise DB PPAS for Linuxbull HPE Serviceguard Toolkit for Oracle Database for Linuxbull HPE Serviceguard Toolkit for SAP Sybase ASE and Sybase Replication Server for Linuxbull Serviceguard Extension for SAPbull Serviceguard XDC for Linuxbull Metrocluster with Continuous Access XP P9000 for Linuxbull Metrocluster with 3PAR Remote Copy fo Linuxbull Metrocluster with Continuous Access EVA P6000 for Linuxbull Serviceguard Toolkit for KVM on Linuxbull Metrocluster with EMC SRDFbull HPE Serviceguard Toolkit for Oracle Data Guard on Linux

8 Packaging information

Licensing informationStarting Serviceguard for Linux 120000 requires licenses on per-socket basis When you installServiceguard for Linux Enterprise edition an instant-on license valid for 90 days is installed With this instant-on license you can use the product even if you do not have a permanent license You must get a permanentlicense before the grace period expires

When ordering the licenses determine the number of active sockets on the server and order one license foreach active socket irrespective of number of cores A virtualized server may select less than the total amountof active sockets if Serviceguard is used within virtual machine which utilized less than the total number ofsockets For information about the license terms and supported server models see the QuickSpecs availableat httpwwwhpecominfoquickspecs

IMPORTANT

If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 youcan use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

Obtaining a permanent licenseBefore your 90 days instant-on license expires you must obtain and validate the permanent license tocontinue to use applicable Serviceguard versions beyond the grace period

To obtain a permanent license

1 Go to httpsmyenterpriselicensehpecom2 Log into HPE Passport If you do not have an account you can create one3 Enter Entitlement Order Number and click Go

bull Here are the licenses listed that have been activated and license that have not yet been activated4 Check the box that belongs to products you want to activate and click Next5 Select ldquoif you are activating for yourselfrdquo or ldquoif you are activating on behalf of another customerrdquo If ldquoon

behalf of another customerrdquo is selected you will enter the final user email address6 Activation Completes Save the files One includes the license key and the other includes additional

product information7 You will receive a license certificate in your email box You must retain the email message because this is

the valid proof of purchase documentation you may need for future reference or support requests

IMPORTANT

Ensure that you save the file and make a note of its path (See the example in Validating thepermanent license on page 10)

Renewing the permanent licenseAfter you have obtained the permanent license follow these steps to renew the license

NOTE

You must renew or apply the license on each node

Procedure

1 Ensure that $SGCONFAutoPassLicFiletxt exists

Licensing information 9

NOTE

Hewlett Packard Enterprise recommends that you back up the $SGCONFAutoPassLicFiletxtbefore renewing the license

2 Place the permanent license key in a file on the system

NOTE

Ensure the file that contains the license key must not have the commented line

3 Renew the license

cmsetlicense -i ltabsolute path of the license filegtOn successful license renewal it displays the following message

License is successfully installedFor more information see cmsetlicense(1m) manpage

Example

To verify if the license is valid

a Copy the license file

cp $SGCONFAutoPassLicFiletxt $SGCONFAutoPassLicFiletxtsavb Run the cmsetlicense command

cmsetlicense -i testmySGlicenseThe mySGlicense file contains the license information

c Run the cmgetlicense command

cmgetlicense -f lined If the license is valid keep the new license file $SGCONFAutoPassLicFiletxt and delete the old

license file $SGCONFAutoPassLicFiletxtsav

If the license is invalid restore the original license

mv $SGCONFAutoPassLicFiletxtsav $SGCONFAutoPassLicFiletxt

Validating the permanent licenseIMPORTANT

Ensure that you validate the permanent license before the 90ndashday grace period of instant-on licenseexpires

To validate the permanent license

1 Run the following command

cmgetlicense -f line2 On successful renewal the command displays the following output

cmgetlicense -f line

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

10 Validating the permanent license

NOTE

bull If you install higher license than the one already installed on the system the license on the nodeis upgraded automatically

For example if you have Serviceguard for Advanced and install Serviceguard for Enterprise thelicense on the node is upgraded to Enterprise and the cmgetlicense -f line commanddisplays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

bull If you have multiple licenses of the same type installed on the system the cmgetlicense -fline command displays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=3 nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

Licensing information 11

Compatibility and installation requirements

Hardware requirementsFor more information about hardware requirements see the latest version of HPE Serviceguard for LinuxCertification Matrix at httpwwwhpecominfolinux-serviceguard-docs

Port requirements

Ports needed for ServiceguardBefore installing ensure that no other program uses these ports

On Red Hat Enterprise Linux and SUSE Linux Enterprise Server

bull icmp 8icmpbull hacl-hb 5300TCP High Availability (HA) Cluster heartbeatbull hacl-hb 5300UDP High Availability (HA) Cluster heartbeatbull hacl-cfg 5302TCP HA Cluster TCP configurationbull hacl-cfg 5302UDP HA Cluster UDP configurationbull hacl-local 5304TCP HA Cluster Commands

If you are using SNMP

bull snmp 161UDPbull snmptrap 162UDP

If you are using the WBEM provider

bull wbem-http TCP5988bull wbem-https TCP5989

If you are using the Quorum Server

bull hacl-qs 1238TCP HA Quorum Server

If you are using the appserver utility

bull hacl-poll 5315TCP

If you are using VMware VMFS volumes

bull https 443TCP

Ports needed for authenticationThe ports reserved for authentication are also used by Serviceguard

bull auth 113TCP authenticationbull auth 113UDP authentication

Ports needed by Serviceguard Managerbull 5511 (http) and 5522 (https) 5301 (multicast port) are used by Serviceguard Managerbull Serviceguard Manager needs a multicast IP address and a TCPIP port for auto-discovery of the nodes in

the subnet Serviceguard uses default multicast IP 235111 and 5301 port which are configured in thesetting page

12 Compatibility and installation requirements

NOTE

Only IP address can be modified by the user The default port 5301 cannot be modified

System firewallsSystem firewalls When using a system firewall with Serviceguard for Linux you must leave open the portslisted above For more information see the latest version of Configuring firewall rules for HP Serviceguard onSUSE Linux Enterprise Server and Red Hat White Paper at httpwwwhpecominfolinux-serviceguard-docs mdashgt Whitepapers

Serviceguard also uses some dynamic ports for some cluster services These must be open in the firewallThey are typically in the range 32768-61000 for Red Hat To determine the range on a given system checkthe contents of the file procsysnetipv4ip_local_port_range

If you have adjusted the dynamic port range using kernel tunable parameters alter your firewall rulesaccordingly

bull To enable intra-cluster communications each HEARTBEAT_IP network on every node in the cluster mustallow the following communications in both directions with all other nodes in the cluster

TCP on port numbers 5300 and 5302 ndash and allow only packets with the SYN flag UDP on port numbers 5300 and 5302 TCP and UDP on dynamic ports

bull If you use a quorum server all nodes in the cluster must allow the following communication to the quorumserver IP address

TCP on port 1238 mdash and allow only packets with the SYN flag

Any node providing quorum service for another cluster must allow the following communication fromthat clusterrsquos nodes

TCP on port 1238 mdash and allow only packets with the SYN flagbull Running the cmscancl command requires the ssh port be open

There are additional firewall requirements to enable execution of Serviceguard commands from nodesoutside the cluster such as those listed in cmclnodelist To allow execution of Serviceguard commandsfollow these guidelines

All nodes in the cluster must allow the following communicationsbull from the remote nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

bull to the remote nodes

TCP and UDP on dynamic ports

The remote nodes must allow the following communicationsbull from the cluster nodes

TCP and UDP on dynamic portsbull to the cluster nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

Authentication communication must allow the following ports

System firewalls 13

bull from the cluster nodes

TCP and UDP on port 113bull to the cluster nodes

TCP and UDP on port 113

NOTE

If you suspect that the firewall is blocking communications you can add -j LOG before the last line inyour iptables file (for example etcsysconfigiptables) to log any blocked ports Consult your Linuxdistributionrsquos documentation on firewalls for information on iptables

14 Compatibility and installation requirements

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 4: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

NoticesThe information contained herein is subject to change without notice The only warranties for Hewlett PackardEnterprise products and services are set forth in the express warranty statements accompanying suchproducts and services Nothing herein should be construed as constituting an additional warranty HewlettPackard Enterprise shall not be liable for technical or editorial errors or omissions contained herein

Confidential computer software Valid license from Hewlett Packard Enterprise required for possession useor copying Consistent with FAR 12211 and 12212 Commercial Computer Software Computer SoftwareDocumentation and Technical Data for Commercial Items are licensed to the US Government undervendors standard commercial license

Links to third-party websites take you outside the Hewlett Packard Enterprise website Hewlett PackardEnterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprisewebsite

4 Notices

AcknowledgmentsIntelreg Itaniumreg Pentiumreg Intel Insidereg and the Intel Inside logo are trademarks of Intel Corporation in theUnited States and other countries

Microsoftreg and Windowsreg are either registered trademarks or trademarks of Microsoft Corporation in theUnited States andor other countries

Adobereg and Acrobatreg are trademarks of Adobe Systems Incorporated

Javareg and Oraclereg are registered trademarks of Oracle andor its affiliates

UNIXreg is a registered trademark of The Open Group

Linuxreg is the registered trademark of Linus Torvalds in the US and other countries

Red Hatreg is a registered trademark of Red Hat Inc in the United States and other countries

SUSEreg is a registered trademark of SUSE AG a Novell Business

Acknowledgments 5

OverviewThis document provides information about HPE Serviceguard for Linux Enterprise edition 121000

6 Overview

Supported platforms and Linux distributionsServiceguard for Linux Enterprise edition 121000 is available on the following Linux distributions

bull Red Hat Enterprise Linux 6 or Advanced platformbull Red Hat Enterprise Linux 7bull SUSE Linux Enterprise Server 11bull SUSE Linux Enterprise Server 12

NOTE

For more information about supported updates supported hardware storage and other informationsee the latest version of HPE Serviceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Supported platforms and Linux distributions 7

Packaging informationServiceguard for Linux 121000 is available on all three editions namely Serviceguard for Linux BaseServiceguard for Linux Advanced and Serviceguard for Linux Enterprise Serviceguard for Linux Enterpriseedition 121000 June 2017 contains rpms for the following components

bull Serviceguard Licensebull Serviceguard for Linuxbull Serviceguard for Linux snmpbull Serviceguard for Linux WBEM providersbull Serviceguard for Linux analyticsbull Serviceguard Quorum Serverbull Serviceguard Managerbull Serviceguard Toolkit for Enterprise DB PPAS for Linuxbull HPE Serviceguard Toolkit for Oracle Database for Linuxbull HPE Serviceguard Toolkit for SAP Sybase ASE and Sybase Replication Server for Linuxbull Serviceguard Extension for SAPbull Serviceguard XDC for Linuxbull Metrocluster with Continuous Access XP P9000 for Linuxbull Metrocluster with 3PAR Remote Copy fo Linuxbull Metrocluster with Continuous Access EVA P6000 for Linuxbull Serviceguard Toolkit for KVM on Linuxbull Metrocluster with EMC SRDFbull HPE Serviceguard Toolkit for Oracle Data Guard on Linux

8 Packaging information

Licensing informationStarting Serviceguard for Linux 120000 requires licenses on per-socket basis When you installServiceguard for Linux Enterprise edition an instant-on license valid for 90 days is installed With this instant-on license you can use the product even if you do not have a permanent license You must get a permanentlicense before the grace period expires

When ordering the licenses determine the number of active sockets on the server and order one license foreach active socket irrespective of number of cores A virtualized server may select less than the total amountof active sockets if Serviceguard is used within virtual machine which utilized less than the total number ofsockets For information about the license terms and supported server models see the QuickSpecs availableat httpwwwhpecominfoquickspecs

IMPORTANT

If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 youcan use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

Obtaining a permanent licenseBefore your 90 days instant-on license expires you must obtain and validate the permanent license tocontinue to use applicable Serviceguard versions beyond the grace period

To obtain a permanent license

1 Go to httpsmyenterpriselicensehpecom2 Log into HPE Passport If you do not have an account you can create one3 Enter Entitlement Order Number and click Go

bull Here are the licenses listed that have been activated and license that have not yet been activated4 Check the box that belongs to products you want to activate and click Next5 Select ldquoif you are activating for yourselfrdquo or ldquoif you are activating on behalf of another customerrdquo If ldquoon

behalf of another customerrdquo is selected you will enter the final user email address6 Activation Completes Save the files One includes the license key and the other includes additional

product information7 You will receive a license certificate in your email box You must retain the email message because this is

the valid proof of purchase documentation you may need for future reference or support requests

IMPORTANT

Ensure that you save the file and make a note of its path (See the example in Validating thepermanent license on page 10)

Renewing the permanent licenseAfter you have obtained the permanent license follow these steps to renew the license

NOTE

You must renew or apply the license on each node

Procedure

1 Ensure that $SGCONFAutoPassLicFiletxt exists

Licensing information 9

NOTE

Hewlett Packard Enterprise recommends that you back up the $SGCONFAutoPassLicFiletxtbefore renewing the license

2 Place the permanent license key in a file on the system

NOTE

Ensure the file that contains the license key must not have the commented line

3 Renew the license

cmsetlicense -i ltabsolute path of the license filegtOn successful license renewal it displays the following message

License is successfully installedFor more information see cmsetlicense(1m) manpage

Example

To verify if the license is valid

a Copy the license file

cp $SGCONFAutoPassLicFiletxt $SGCONFAutoPassLicFiletxtsavb Run the cmsetlicense command

cmsetlicense -i testmySGlicenseThe mySGlicense file contains the license information

c Run the cmgetlicense command

cmgetlicense -f lined If the license is valid keep the new license file $SGCONFAutoPassLicFiletxt and delete the old

license file $SGCONFAutoPassLicFiletxtsav

If the license is invalid restore the original license

mv $SGCONFAutoPassLicFiletxtsav $SGCONFAutoPassLicFiletxt

Validating the permanent licenseIMPORTANT

Ensure that you validate the permanent license before the 90ndashday grace period of instant-on licenseexpires

To validate the permanent license

1 Run the following command

cmgetlicense -f line2 On successful renewal the command displays the following output

cmgetlicense -f line

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

10 Validating the permanent license

NOTE

bull If you install higher license than the one already installed on the system the license on the nodeis upgraded automatically

For example if you have Serviceguard for Advanced and install Serviceguard for Enterprise thelicense on the node is upgraded to Enterprise and the cmgetlicense -f line commanddisplays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

bull If you have multiple licenses of the same type installed on the system the cmgetlicense -fline command displays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=3 nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

Licensing information 11

Compatibility and installation requirements

Hardware requirementsFor more information about hardware requirements see the latest version of HPE Serviceguard for LinuxCertification Matrix at httpwwwhpecominfolinux-serviceguard-docs

Port requirements

Ports needed for ServiceguardBefore installing ensure that no other program uses these ports

On Red Hat Enterprise Linux and SUSE Linux Enterprise Server

bull icmp 8icmpbull hacl-hb 5300TCP High Availability (HA) Cluster heartbeatbull hacl-hb 5300UDP High Availability (HA) Cluster heartbeatbull hacl-cfg 5302TCP HA Cluster TCP configurationbull hacl-cfg 5302UDP HA Cluster UDP configurationbull hacl-local 5304TCP HA Cluster Commands

If you are using SNMP

bull snmp 161UDPbull snmptrap 162UDP

If you are using the WBEM provider

bull wbem-http TCP5988bull wbem-https TCP5989

If you are using the Quorum Server

bull hacl-qs 1238TCP HA Quorum Server

If you are using the appserver utility

bull hacl-poll 5315TCP

If you are using VMware VMFS volumes

bull https 443TCP

Ports needed for authenticationThe ports reserved for authentication are also used by Serviceguard

bull auth 113TCP authenticationbull auth 113UDP authentication

Ports needed by Serviceguard Managerbull 5511 (http) and 5522 (https) 5301 (multicast port) are used by Serviceguard Managerbull Serviceguard Manager needs a multicast IP address and a TCPIP port for auto-discovery of the nodes in

the subnet Serviceguard uses default multicast IP 235111 and 5301 port which are configured in thesetting page

12 Compatibility and installation requirements

NOTE

Only IP address can be modified by the user The default port 5301 cannot be modified

System firewallsSystem firewalls When using a system firewall with Serviceguard for Linux you must leave open the portslisted above For more information see the latest version of Configuring firewall rules for HP Serviceguard onSUSE Linux Enterprise Server and Red Hat White Paper at httpwwwhpecominfolinux-serviceguard-docs mdashgt Whitepapers

Serviceguard also uses some dynamic ports for some cluster services These must be open in the firewallThey are typically in the range 32768-61000 for Red Hat To determine the range on a given system checkthe contents of the file procsysnetipv4ip_local_port_range

If you have adjusted the dynamic port range using kernel tunable parameters alter your firewall rulesaccordingly

bull To enable intra-cluster communications each HEARTBEAT_IP network on every node in the cluster mustallow the following communications in both directions with all other nodes in the cluster

TCP on port numbers 5300 and 5302 ndash and allow only packets with the SYN flag UDP on port numbers 5300 and 5302 TCP and UDP on dynamic ports

bull If you use a quorum server all nodes in the cluster must allow the following communication to the quorumserver IP address

TCP on port 1238 mdash and allow only packets with the SYN flag

Any node providing quorum service for another cluster must allow the following communication fromthat clusterrsquos nodes

TCP on port 1238 mdash and allow only packets with the SYN flagbull Running the cmscancl command requires the ssh port be open

There are additional firewall requirements to enable execution of Serviceguard commands from nodesoutside the cluster such as those listed in cmclnodelist To allow execution of Serviceguard commandsfollow these guidelines

All nodes in the cluster must allow the following communicationsbull from the remote nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

bull to the remote nodes

TCP and UDP on dynamic ports

The remote nodes must allow the following communicationsbull from the cluster nodes

TCP and UDP on dynamic portsbull to the cluster nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

Authentication communication must allow the following ports

System firewalls 13

bull from the cluster nodes

TCP and UDP on port 113bull to the cluster nodes

TCP and UDP on port 113

NOTE

If you suspect that the firewall is blocking communications you can add -j LOG before the last line inyour iptables file (for example etcsysconfigiptables) to log any blocked ports Consult your Linuxdistributionrsquos documentation on firewalls for information on iptables

14 Compatibility and installation requirements

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 5: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

AcknowledgmentsIntelreg Itaniumreg Pentiumreg Intel Insidereg and the Intel Inside logo are trademarks of Intel Corporation in theUnited States and other countries

Microsoftreg and Windowsreg are either registered trademarks or trademarks of Microsoft Corporation in theUnited States andor other countries

Adobereg and Acrobatreg are trademarks of Adobe Systems Incorporated

Javareg and Oraclereg are registered trademarks of Oracle andor its affiliates

UNIXreg is a registered trademark of The Open Group

Linuxreg is the registered trademark of Linus Torvalds in the US and other countries

Red Hatreg is a registered trademark of Red Hat Inc in the United States and other countries

SUSEreg is a registered trademark of SUSE AG a Novell Business

Acknowledgments 5

OverviewThis document provides information about HPE Serviceguard for Linux Enterprise edition 121000

6 Overview

Supported platforms and Linux distributionsServiceguard for Linux Enterprise edition 121000 is available on the following Linux distributions

bull Red Hat Enterprise Linux 6 or Advanced platformbull Red Hat Enterprise Linux 7bull SUSE Linux Enterprise Server 11bull SUSE Linux Enterprise Server 12

NOTE

For more information about supported updates supported hardware storage and other informationsee the latest version of HPE Serviceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Supported platforms and Linux distributions 7

Packaging informationServiceguard for Linux 121000 is available on all three editions namely Serviceguard for Linux BaseServiceguard for Linux Advanced and Serviceguard for Linux Enterprise Serviceguard for Linux Enterpriseedition 121000 June 2017 contains rpms for the following components

bull Serviceguard Licensebull Serviceguard for Linuxbull Serviceguard for Linux snmpbull Serviceguard for Linux WBEM providersbull Serviceguard for Linux analyticsbull Serviceguard Quorum Serverbull Serviceguard Managerbull Serviceguard Toolkit for Enterprise DB PPAS for Linuxbull HPE Serviceguard Toolkit for Oracle Database for Linuxbull HPE Serviceguard Toolkit for SAP Sybase ASE and Sybase Replication Server for Linuxbull Serviceguard Extension for SAPbull Serviceguard XDC for Linuxbull Metrocluster with Continuous Access XP P9000 for Linuxbull Metrocluster with 3PAR Remote Copy fo Linuxbull Metrocluster with Continuous Access EVA P6000 for Linuxbull Serviceguard Toolkit for KVM on Linuxbull Metrocluster with EMC SRDFbull HPE Serviceguard Toolkit for Oracle Data Guard on Linux

8 Packaging information

Licensing informationStarting Serviceguard for Linux 120000 requires licenses on per-socket basis When you installServiceguard for Linux Enterprise edition an instant-on license valid for 90 days is installed With this instant-on license you can use the product even if you do not have a permanent license You must get a permanentlicense before the grace period expires

When ordering the licenses determine the number of active sockets on the server and order one license foreach active socket irrespective of number of cores A virtualized server may select less than the total amountof active sockets if Serviceguard is used within virtual machine which utilized less than the total number ofsockets For information about the license terms and supported server models see the QuickSpecs availableat httpwwwhpecominfoquickspecs

IMPORTANT

If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 youcan use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

Obtaining a permanent licenseBefore your 90 days instant-on license expires you must obtain and validate the permanent license tocontinue to use applicable Serviceguard versions beyond the grace period

To obtain a permanent license

1 Go to httpsmyenterpriselicensehpecom2 Log into HPE Passport If you do not have an account you can create one3 Enter Entitlement Order Number and click Go

bull Here are the licenses listed that have been activated and license that have not yet been activated4 Check the box that belongs to products you want to activate and click Next5 Select ldquoif you are activating for yourselfrdquo or ldquoif you are activating on behalf of another customerrdquo If ldquoon

behalf of another customerrdquo is selected you will enter the final user email address6 Activation Completes Save the files One includes the license key and the other includes additional

product information7 You will receive a license certificate in your email box You must retain the email message because this is

the valid proof of purchase documentation you may need for future reference or support requests

IMPORTANT

Ensure that you save the file and make a note of its path (See the example in Validating thepermanent license on page 10)

Renewing the permanent licenseAfter you have obtained the permanent license follow these steps to renew the license

NOTE

You must renew or apply the license on each node

Procedure

1 Ensure that $SGCONFAutoPassLicFiletxt exists

Licensing information 9

NOTE

Hewlett Packard Enterprise recommends that you back up the $SGCONFAutoPassLicFiletxtbefore renewing the license

2 Place the permanent license key in a file on the system

NOTE

Ensure the file that contains the license key must not have the commented line

3 Renew the license

cmsetlicense -i ltabsolute path of the license filegtOn successful license renewal it displays the following message

License is successfully installedFor more information see cmsetlicense(1m) manpage

Example

To verify if the license is valid

a Copy the license file

cp $SGCONFAutoPassLicFiletxt $SGCONFAutoPassLicFiletxtsavb Run the cmsetlicense command

cmsetlicense -i testmySGlicenseThe mySGlicense file contains the license information

c Run the cmgetlicense command

cmgetlicense -f lined If the license is valid keep the new license file $SGCONFAutoPassLicFiletxt and delete the old

license file $SGCONFAutoPassLicFiletxtsav

If the license is invalid restore the original license

mv $SGCONFAutoPassLicFiletxtsav $SGCONFAutoPassLicFiletxt

Validating the permanent licenseIMPORTANT

Ensure that you validate the permanent license before the 90ndashday grace period of instant-on licenseexpires

To validate the permanent license

1 Run the following command

cmgetlicense -f line2 On successful renewal the command displays the following output

cmgetlicense -f line

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

10 Validating the permanent license

NOTE

bull If you install higher license than the one already installed on the system the license on the nodeis upgraded automatically

For example if you have Serviceguard for Advanced and install Serviceguard for Enterprise thelicense on the node is upgraded to Enterprise and the cmgetlicense -f line commanddisplays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

bull If you have multiple licenses of the same type installed on the system the cmgetlicense -fline command displays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=3 nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

Licensing information 11

Compatibility and installation requirements

Hardware requirementsFor more information about hardware requirements see the latest version of HPE Serviceguard for LinuxCertification Matrix at httpwwwhpecominfolinux-serviceguard-docs

Port requirements

Ports needed for ServiceguardBefore installing ensure that no other program uses these ports

On Red Hat Enterprise Linux and SUSE Linux Enterprise Server

bull icmp 8icmpbull hacl-hb 5300TCP High Availability (HA) Cluster heartbeatbull hacl-hb 5300UDP High Availability (HA) Cluster heartbeatbull hacl-cfg 5302TCP HA Cluster TCP configurationbull hacl-cfg 5302UDP HA Cluster UDP configurationbull hacl-local 5304TCP HA Cluster Commands

If you are using SNMP

bull snmp 161UDPbull snmptrap 162UDP

If you are using the WBEM provider

bull wbem-http TCP5988bull wbem-https TCP5989

If you are using the Quorum Server

bull hacl-qs 1238TCP HA Quorum Server

If you are using the appserver utility

bull hacl-poll 5315TCP

If you are using VMware VMFS volumes

bull https 443TCP

Ports needed for authenticationThe ports reserved for authentication are also used by Serviceguard

bull auth 113TCP authenticationbull auth 113UDP authentication

Ports needed by Serviceguard Managerbull 5511 (http) and 5522 (https) 5301 (multicast port) are used by Serviceguard Managerbull Serviceguard Manager needs a multicast IP address and a TCPIP port for auto-discovery of the nodes in

the subnet Serviceguard uses default multicast IP 235111 and 5301 port which are configured in thesetting page

12 Compatibility and installation requirements

NOTE

Only IP address can be modified by the user The default port 5301 cannot be modified

System firewallsSystem firewalls When using a system firewall with Serviceguard for Linux you must leave open the portslisted above For more information see the latest version of Configuring firewall rules for HP Serviceguard onSUSE Linux Enterprise Server and Red Hat White Paper at httpwwwhpecominfolinux-serviceguard-docs mdashgt Whitepapers

Serviceguard also uses some dynamic ports for some cluster services These must be open in the firewallThey are typically in the range 32768-61000 for Red Hat To determine the range on a given system checkthe contents of the file procsysnetipv4ip_local_port_range

If you have adjusted the dynamic port range using kernel tunable parameters alter your firewall rulesaccordingly

bull To enable intra-cluster communications each HEARTBEAT_IP network on every node in the cluster mustallow the following communications in both directions with all other nodes in the cluster

TCP on port numbers 5300 and 5302 ndash and allow only packets with the SYN flag UDP on port numbers 5300 and 5302 TCP and UDP on dynamic ports

bull If you use a quorum server all nodes in the cluster must allow the following communication to the quorumserver IP address

TCP on port 1238 mdash and allow only packets with the SYN flag

Any node providing quorum service for another cluster must allow the following communication fromthat clusterrsquos nodes

TCP on port 1238 mdash and allow only packets with the SYN flagbull Running the cmscancl command requires the ssh port be open

There are additional firewall requirements to enable execution of Serviceguard commands from nodesoutside the cluster such as those listed in cmclnodelist To allow execution of Serviceguard commandsfollow these guidelines

All nodes in the cluster must allow the following communicationsbull from the remote nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

bull to the remote nodes

TCP and UDP on dynamic ports

The remote nodes must allow the following communicationsbull from the cluster nodes

TCP and UDP on dynamic portsbull to the cluster nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

Authentication communication must allow the following ports

System firewalls 13

bull from the cluster nodes

TCP and UDP on port 113bull to the cluster nodes

TCP and UDP on port 113

NOTE

If you suspect that the firewall is blocking communications you can add -j LOG before the last line inyour iptables file (for example etcsysconfigiptables) to log any blocked ports Consult your Linuxdistributionrsquos documentation on firewalls for information on iptables

14 Compatibility and installation requirements

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 6: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

OverviewThis document provides information about HPE Serviceguard for Linux Enterprise edition 121000

6 Overview

Supported platforms and Linux distributionsServiceguard for Linux Enterprise edition 121000 is available on the following Linux distributions

bull Red Hat Enterprise Linux 6 or Advanced platformbull Red Hat Enterprise Linux 7bull SUSE Linux Enterprise Server 11bull SUSE Linux Enterprise Server 12

NOTE

For more information about supported updates supported hardware storage and other informationsee the latest version of HPE Serviceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Supported platforms and Linux distributions 7

Packaging informationServiceguard for Linux 121000 is available on all three editions namely Serviceguard for Linux BaseServiceguard for Linux Advanced and Serviceguard for Linux Enterprise Serviceguard for Linux Enterpriseedition 121000 June 2017 contains rpms for the following components

bull Serviceguard Licensebull Serviceguard for Linuxbull Serviceguard for Linux snmpbull Serviceguard for Linux WBEM providersbull Serviceguard for Linux analyticsbull Serviceguard Quorum Serverbull Serviceguard Managerbull Serviceguard Toolkit for Enterprise DB PPAS for Linuxbull HPE Serviceguard Toolkit for Oracle Database for Linuxbull HPE Serviceguard Toolkit for SAP Sybase ASE and Sybase Replication Server for Linuxbull Serviceguard Extension for SAPbull Serviceguard XDC for Linuxbull Metrocluster with Continuous Access XP P9000 for Linuxbull Metrocluster with 3PAR Remote Copy fo Linuxbull Metrocluster with Continuous Access EVA P6000 for Linuxbull Serviceguard Toolkit for KVM on Linuxbull Metrocluster with EMC SRDFbull HPE Serviceguard Toolkit for Oracle Data Guard on Linux

8 Packaging information

Licensing informationStarting Serviceguard for Linux 120000 requires licenses on per-socket basis When you installServiceguard for Linux Enterprise edition an instant-on license valid for 90 days is installed With this instant-on license you can use the product even if you do not have a permanent license You must get a permanentlicense before the grace period expires

When ordering the licenses determine the number of active sockets on the server and order one license foreach active socket irrespective of number of cores A virtualized server may select less than the total amountof active sockets if Serviceguard is used within virtual machine which utilized less than the total number ofsockets For information about the license terms and supported server models see the QuickSpecs availableat httpwwwhpecominfoquickspecs

IMPORTANT

If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 youcan use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

Obtaining a permanent licenseBefore your 90 days instant-on license expires you must obtain and validate the permanent license tocontinue to use applicable Serviceguard versions beyond the grace period

To obtain a permanent license

1 Go to httpsmyenterpriselicensehpecom2 Log into HPE Passport If you do not have an account you can create one3 Enter Entitlement Order Number and click Go

bull Here are the licenses listed that have been activated and license that have not yet been activated4 Check the box that belongs to products you want to activate and click Next5 Select ldquoif you are activating for yourselfrdquo or ldquoif you are activating on behalf of another customerrdquo If ldquoon

behalf of another customerrdquo is selected you will enter the final user email address6 Activation Completes Save the files One includes the license key and the other includes additional

product information7 You will receive a license certificate in your email box You must retain the email message because this is

the valid proof of purchase documentation you may need for future reference or support requests

IMPORTANT

Ensure that you save the file and make a note of its path (See the example in Validating thepermanent license on page 10)

Renewing the permanent licenseAfter you have obtained the permanent license follow these steps to renew the license

NOTE

You must renew or apply the license on each node

Procedure

1 Ensure that $SGCONFAutoPassLicFiletxt exists

Licensing information 9

NOTE

Hewlett Packard Enterprise recommends that you back up the $SGCONFAutoPassLicFiletxtbefore renewing the license

2 Place the permanent license key in a file on the system

NOTE

Ensure the file that contains the license key must not have the commented line

3 Renew the license

cmsetlicense -i ltabsolute path of the license filegtOn successful license renewal it displays the following message

License is successfully installedFor more information see cmsetlicense(1m) manpage

Example

To verify if the license is valid

a Copy the license file

cp $SGCONFAutoPassLicFiletxt $SGCONFAutoPassLicFiletxtsavb Run the cmsetlicense command

cmsetlicense -i testmySGlicenseThe mySGlicense file contains the license information

c Run the cmgetlicense command

cmgetlicense -f lined If the license is valid keep the new license file $SGCONFAutoPassLicFiletxt and delete the old

license file $SGCONFAutoPassLicFiletxtsav

If the license is invalid restore the original license

mv $SGCONFAutoPassLicFiletxtsav $SGCONFAutoPassLicFiletxt

Validating the permanent licenseIMPORTANT

Ensure that you validate the permanent license before the 90ndashday grace period of instant-on licenseexpires

To validate the permanent license

1 Run the following command

cmgetlicense -f line2 On successful renewal the command displays the following output

cmgetlicense -f line

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

10 Validating the permanent license

NOTE

bull If you install higher license than the one already installed on the system the license on the nodeis upgraded automatically

For example if you have Serviceguard for Advanced and install Serviceguard for Enterprise thelicense on the node is upgraded to Enterprise and the cmgetlicense -f line commanddisplays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

bull If you have multiple licenses of the same type installed on the system the cmgetlicense -fline command displays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=3 nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

Licensing information 11

Compatibility and installation requirements

Hardware requirementsFor more information about hardware requirements see the latest version of HPE Serviceguard for LinuxCertification Matrix at httpwwwhpecominfolinux-serviceguard-docs

Port requirements

Ports needed for ServiceguardBefore installing ensure that no other program uses these ports

On Red Hat Enterprise Linux and SUSE Linux Enterprise Server

bull icmp 8icmpbull hacl-hb 5300TCP High Availability (HA) Cluster heartbeatbull hacl-hb 5300UDP High Availability (HA) Cluster heartbeatbull hacl-cfg 5302TCP HA Cluster TCP configurationbull hacl-cfg 5302UDP HA Cluster UDP configurationbull hacl-local 5304TCP HA Cluster Commands

If you are using SNMP

bull snmp 161UDPbull snmptrap 162UDP

If you are using the WBEM provider

bull wbem-http TCP5988bull wbem-https TCP5989

If you are using the Quorum Server

bull hacl-qs 1238TCP HA Quorum Server

If you are using the appserver utility

bull hacl-poll 5315TCP

If you are using VMware VMFS volumes

bull https 443TCP

Ports needed for authenticationThe ports reserved for authentication are also used by Serviceguard

bull auth 113TCP authenticationbull auth 113UDP authentication

Ports needed by Serviceguard Managerbull 5511 (http) and 5522 (https) 5301 (multicast port) are used by Serviceguard Managerbull Serviceguard Manager needs a multicast IP address and a TCPIP port for auto-discovery of the nodes in

the subnet Serviceguard uses default multicast IP 235111 and 5301 port which are configured in thesetting page

12 Compatibility and installation requirements

NOTE

Only IP address can be modified by the user The default port 5301 cannot be modified

System firewallsSystem firewalls When using a system firewall with Serviceguard for Linux you must leave open the portslisted above For more information see the latest version of Configuring firewall rules for HP Serviceguard onSUSE Linux Enterprise Server and Red Hat White Paper at httpwwwhpecominfolinux-serviceguard-docs mdashgt Whitepapers

Serviceguard also uses some dynamic ports for some cluster services These must be open in the firewallThey are typically in the range 32768-61000 for Red Hat To determine the range on a given system checkthe contents of the file procsysnetipv4ip_local_port_range

If you have adjusted the dynamic port range using kernel tunable parameters alter your firewall rulesaccordingly

bull To enable intra-cluster communications each HEARTBEAT_IP network on every node in the cluster mustallow the following communications in both directions with all other nodes in the cluster

TCP on port numbers 5300 and 5302 ndash and allow only packets with the SYN flag UDP on port numbers 5300 and 5302 TCP and UDP on dynamic ports

bull If you use a quorum server all nodes in the cluster must allow the following communication to the quorumserver IP address

TCP on port 1238 mdash and allow only packets with the SYN flag

Any node providing quorum service for another cluster must allow the following communication fromthat clusterrsquos nodes

TCP on port 1238 mdash and allow only packets with the SYN flagbull Running the cmscancl command requires the ssh port be open

There are additional firewall requirements to enable execution of Serviceguard commands from nodesoutside the cluster such as those listed in cmclnodelist To allow execution of Serviceguard commandsfollow these guidelines

All nodes in the cluster must allow the following communicationsbull from the remote nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

bull to the remote nodes

TCP and UDP on dynamic ports

The remote nodes must allow the following communicationsbull from the cluster nodes

TCP and UDP on dynamic portsbull to the cluster nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

Authentication communication must allow the following ports

System firewalls 13

bull from the cluster nodes

TCP and UDP on port 113bull to the cluster nodes

TCP and UDP on port 113

NOTE

If you suspect that the firewall is blocking communications you can add -j LOG before the last line inyour iptables file (for example etcsysconfigiptables) to log any blocked ports Consult your Linuxdistributionrsquos documentation on firewalls for information on iptables

14 Compatibility and installation requirements

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 7: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Supported platforms and Linux distributionsServiceguard for Linux Enterprise edition 121000 is available on the following Linux distributions

bull Red Hat Enterprise Linux 6 or Advanced platformbull Red Hat Enterprise Linux 7bull SUSE Linux Enterprise Server 11bull SUSE Linux Enterprise Server 12

NOTE

For more information about supported updates supported hardware storage and other informationsee the latest version of HPE Serviceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Supported platforms and Linux distributions 7

Packaging informationServiceguard for Linux 121000 is available on all three editions namely Serviceguard for Linux BaseServiceguard for Linux Advanced and Serviceguard for Linux Enterprise Serviceguard for Linux Enterpriseedition 121000 June 2017 contains rpms for the following components

bull Serviceguard Licensebull Serviceguard for Linuxbull Serviceguard for Linux snmpbull Serviceguard for Linux WBEM providersbull Serviceguard for Linux analyticsbull Serviceguard Quorum Serverbull Serviceguard Managerbull Serviceguard Toolkit for Enterprise DB PPAS for Linuxbull HPE Serviceguard Toolkit for Oracle Database for Linuxbull HPE Serviceguard Toolkit for SAP Sybase ASE and Sybase Replication Server for Linuxbull Serviceguard Extension for SAPbull Serviceguard XDC for Linuxbull Metrocluster with Continuous Access XP P9000 for Linuxbull Metrocluster with 3PAR Remote Copy fo Linuxbull Metrocluster with Continuous Access EVA P6000 for Linuxbull Serviceguard Toolkit for KVM on Linuxbull Metrocluster with EMC SRDFbull HPE Serviceguard Toolkit for Oracle Data Guard on Linux

8 Packaging information

Licensing informationStarting Serviceguard for Linux 120000 requires licenses on per-socket basis When you installServiceguard for Linux Enterprise edition an instant-on license valid for 90 days is installed With this instant-on license you can use the product even if you do not have a permanent license You must get a permanentlicense before the grace period expires

When ordering the licenses determine the number of active sockets on the server and order one license foreach active socket irrespective of number of cores A virtualized server may select less than the total amountof active sockets if Serviceguard is used within virtual machine which utilized less than the total number ofsockets For information about the license terms and supported server models see the QuickSpecs availableat httpwwwhpecominfoquickspecs

IMPORTANT

If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 youcan use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

Obtaining a permanent licenseBefore your 90 days instant-on license expires you must obtain and validate the permanent license tocontinue to use applicable Serviceguard versions beyond the grace period

To obtain a permanent license

1 Go to httpsmyenterpriselicensehpecom2 Log into HPE Passport If you do not have an account you can create one3 Enter Entitlement Order Number and click Go

bull Here are the licenses listed that have been activated and license that have not yet been activated4 Check the box that belongs to products you want to activate and click Next5 Select ldquoif you are activating for yourselfrdquo or ldquoif you are activating on behalf of another customerrdquo If ldquoon

behalf of another customerrdquo is selected you will enter the final user email address6 Activation Completes Save the files One includes the license key and the other includes additional

product information7 You will receive a license certificate in your email box You must retain the email message because this is

the valid proof of purchase documentation you may need for future reference or support requests

IMPORTANT

Ensure that you save the file and make a note of its path (See the example in Validating thepermanent license on page 10)

Renewing the permanent licenseAfter you have obtained the permanent license follow these steps to renew the license

NOTE

You must renew or apply the license on each node

Procedure

1 Ensure that $SGCONFAutoPassLicFiletxt exists

Licensing information 9

NOTE

Hewlett Packard Enterprise recommends that you back up the $SGCONFAutoPassLicFiletxtbefore renewing the license

2 Place the permanent license key in a file on the system

NOTE

Ensure the file that contains the license key must not have the commented line

3 Renew the license

cmsetlicense -i ltabsolute path of the license filegtOn successful license renewal it displays the following message

License is successfully installedFor more information see cmsetlicense(1m) manpage

Example

To verify if the license is valid

a Copy the license file

cp $SGCONFAutoPassLicFiletxt $SGCONFAutoPassLicFiletxtsavb Run the cmsetlicense command

cmsetlicense -i testmySGlicenseThe mySGlicense file contains the license information

c Run the cmgetlicense command

cmgetlicense -f lined If the license is valid keep the new license file $SGCONFAutoPassLicFiletxt and delete the old

license file $SGCONFAutoPassLicFiletxtsav

If the license is invalid restore the original license

mv $SGCONFAutoPassLicFiletxtsav $SGCONFAutoPassLicFiletxt

Validating the permanent licenseIMPORTANT

Ensure that you validate the permanent license before the 90ndashday grace period of instant-on licenseexpires

To validate the permanent license

1 Run the following command

cmgetlicense -f line2 On successful renewal the command displays the following output

cmgetlicense -f line

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

10 Validating the permanent license

NOTE

bull If you install higher license than the one already installed on the system the license on the nodeis upgraded automatically

For example if you have Serviceguard for Advanced and install Serviceguard for Enterprise thelicense on the node is upgraded to Enterprise and the cmgetlicense -f line commanddisplays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

bull If you have multiple licenses of the same type installed on the system the cmgetlicense -fline command displays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=3 nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

Licensing information 11

Compatibility and installation requirements

Hardware requirementsFor more information about hardware requirements see the latest version of HPE Serviceguard for LinuxCertification Matrix at httpwwwhpecominfolinux-serviceguard-docs

Port requirements

Ports needed for ServiceguardBefore installing ensure that no other program uses these ports

On Red Hat Enterprise Linux and SUSE Linux Enterprise Server

bull icmp 8icmpbull hacl-hb 5300TCP High Availability (HA) Cluster heartbeatbull hacl-hb 5300UDP High Availability (HA) Cluster heartbeatbull hacl-cfg 5302TCP HA Cluster TCP configurationbull hacl-cfg 5302UDP HA Cluster UDP configurationbull hacl-local 5304TCP HA Cluster Commands

If you are using SNMP

bull snmp 161UDPbull snmptrap 162UDP

If you are using the WBEM provider

bull wbem-http TCP5988bull wbem-https TCP5989

If you are using the Quorum Server

bull hacl-qs 1238TCP HA Quorum Server

If you are using the appserver utility

bull hacl-poll 5315TCP

If you are using VMware VMFS volumes

bull https 443TCP

Ports needed for authenticationThe ports reserved for authentication are also used by Serviceguard

bull auth 113TCP authenticationbull auth 113UDP authentication

Ports needed by Serviceguard Managerbull 5511 (http) and 5522 (https) 5301 (multicast port) are used by Serviceguard Managerbull Serviceguard Manager needs a multicast IP address and a TCPIP port for auto-discovery of the nodes in

the subnet Serviceguard uses default multicast IP 235111 and 5301 port which are configured in thesetting page

12 Compatibility and installation requirements

NOTE

Only IP address can be modified by the user The default port 5301 cannot be modified

System firewallsSystem firewalls When using a system firewall with Serviceguard for Linux you must leave open the portslisted above For more information see the latest version of Configuring firewall rules for HP Serviceguard onSUSE Linux Enterprise Server and Red Hat White Paper at httpwwwhpecominfolinux-serviceguard-docs mdashgt Whitepapers

Serviceguard also uses some dynamic ports for some cluster services These must be open in the firewallThey are typically in the range 32768-61000 for Red Hat To determine the range on a given system checkthe contents of the file procsysnetipv4ip_local_port_range

If you have adjusted the dynamic port range using kernel tunable parameters alter your firewall rulesaccordingly

bull To enable intra-cluster communications each HEARTBEAT_IP network on every node in the cluster mustallow the following communications in both directions with all other nodes in the cluster

TCP on port numbers 5300 and 5302 ndash and allow only packets with the SYN flag UDP on port numbers 5300 and 5302 TCP and UDP on dynamic ports

bull If you use a quorum server all nodes in the cluster must allow the following communication to the quorumserver IP address

TCP on port 1238 mdash and allow only packets with the SYN flag

Any node providing quorum service for another cluster must allow the following communication fromthat clusterrsquos nodes

TCP on port 1238 mdash and allow only packets with the SYN flagbull Running the cmscancl command requires the ssh port be open

There are additional firewall requirements to enable execution of Serviceguard commands from nodesoutside the cluster such as those listed in cmclnodelist To allow execution of Serviceguard commandsfollow these guidelines

All nodes in the cluster must allow the following communicationsbull from the remote nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

bull to the remote nodes

TCP and UDP on dynamic ports

The remote nodes must allow the following communicationsbull from the cluster nodes

TCP and UDP on dynamic portsbull to the cluster nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

Authentication communication must allow the following ports

System firewalls 13

bull from the cluster nodes

TCP and UDP on port 113bull to the cluster nodes

TCP and UDP on port 113

NOTE

If you suspect that the firewall is blocking communications you can add -j LOG before the last line inyour iptables file (for example etcsysconfigiptables) to log any blocked ports Consult your Linuxdistributionrsquos documentation on firewalls for information on iptables

14 Compatibility and installation requirements

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 8: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Packaging informationServiceguard for Linux 121000 is available on all three editions namely Serviceguard for Linux BaseServiceguard for Linux Advanced and Serviceguard for Linux Enterprise Serviceguard for Linux Enterpriseedition 121000 June 2017 contains rpms for the following components

bull Serviceguard Licensebull Serviceguard for Linuxbull Serviceguard for Linux snmpbull Serviceguard for Linux WBEM providersbull Serviceguard for Linux analyticsbull Serviceguard Quorum Serverbull Serviceguard Managerbull Serviceguard Toolkit for Enterprise DB PPAS for Linuxbull HPE Serviceguard Toolkit for Oracle Database for Linuxbull HPE Serviceguard Toolkit for SAP Sybase ASE and Sybase Replication Server for Linuxbull Serviceguard Extension for SAPbull Serviceguard XDC for Linuxbull Metrocluster with Continuous Access XP P9000 for Linuxbull Metrocluster with 3PAR Remote Copy fo Linuxbull Metrocluster with Continuous Access EVA P6000 for Linuxbull Serviceguard Toolkit for KVM on Linuxbull Metrocluster with EMC SRDFbull HPE Serviceguard Toolkit for Oracle Data Guard on Linux

8 Packaging information

Licensing informationStarting Serviceguard for Linux 120000 requires licenses on per-socket basis When you installServiceguard for Linux Enterprise edition an instant-on license valid for 90 days is installed With this instant-on license you can use the product even if you do not have a permanent license You must get a permanentlicense before the grace period expires

When ordering the licenses determine the number of active sockets on the server and order one license foreach active socket irrespective of number of cores A virtualized server may select less than the total amountof active sockets if Serviceguard is used within virtual machine which utilized less than the total number ofsockets For information about the license terms and supported server models see the QuickSpecs availableat httpwwwhpecominfoquickspecs

IMPORTANT

If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 youcan use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

Obtaining a permanent licenseBefore your 90 days instant-on license expires you must obtain and validate the permanent license tocontinue to use applicable Serviceguard versions beyond the grace period

To obtain a permanent license

1 Go to httpsmyenterpriselicensehpecom2 Log into HPE Passport If you do not have an account you can create one3 Enter Entitlement Order Number and click Go

bull Here are the licenses listed that have been activated and license that have not yet been activated4 Check the box that belongs to products you want to activate and click Next5 Select ldquoif you are activating for yourselfrdquo or ldquoif you are activating on behalf of another customerrdquo If ldquoon

behalf of another customerrdquo is selected you will enter the final user email address6 Activation Completes Save the files One includes the license key and the other includes additional

product information7 You will receive a license certificate in your email box You must retain the email message because this is

the valid proof of purchase documentation you may need for future reference or support requests

IMPORTANT

Ensure that you save the file and make a note of its path (See the example in Validating thepermanent license on page 10)

Renewing the permanent licenseAfter you have obtained the permanent license follow these steps to renew the license

NOTE

You must renew or apply the license on each node

Procedure

1 Ensure that $SGCONFAutoPassLicFiletxt exists

Licensing information 9

NOTE

Hewlett Packard Enterprise recommends that you back up the $SGCONFAutoPassLicFiletxtbefore renewing the license

2 Place the permanent license key in a file on the system

NOTE

Ensure the file that contains the license key must not have the commented line

3 Renew the license

cmsetlicense -i ltabsolute path of the license filegtOn successful license renewal it displays the following message

License is successfully installedFor more information see cmsetlicense(1m) manpage

Example

To verify if the license is valid

a Copy the license file

cp $SGCONFAutoPassLicFiletxt $SGCONFAutoPassLicFiletxtsavb Run the cmsetlicense command

cmsetlicense -i testmySGlicenseThe mySGlicense file contains the license information

c Run the cmgetlicense command

cmgetlicense -f lined If the license is valid keep the new license file $SGCONFAutoPassLicFiletxt and delete the old

license file $SGCONFAutoPassLicFiletxtsav

If the license is invalid restore the original license

mv $SGCONFAutoPassLicFiletxtsav $SGCONFAutoPassLicFiletxt

Validating the permanent licenseIMPORTANT

Ensure that you validate the permanent license before the 90ndashday grace period of instant-on licenseexpires

To validate the permanent license

1 Run the following command

cmgetlicense -f line2 On successful renewal the command displays the following output

cmgetlicense -f line

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

10 Validating the permanent license

NOTE

bull If you install higher license than the one already installed on the system the license on the nodeis upgraded automatically

For example if you have Serviceguard for Advanced and install Serviceguard for Enterprise thelicense on the node is upgraded to Enterprise and the cmgetlicense -f line commanddisplays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

bull If you have multiple licenses of the same type installed on the system the cmgetlicense -fline command displays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=3 nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

Licensing information 11

Compatibility and installation requirements

Hardware requirementsFor more information about hardware requirements see the latest version of HPE Serviceguard for LinuxCertification Matrix at httpwwwhpecominfolinux-serviceguard-docs

Port requirements

Ports needed for ServiceguardBefore installing ensure that no other program uses these ports

On Red Hat Enterprise Linux and SUSE Linux Enterprise Server

bull icmp 8icmpbull hacl-hb 5300TCP High Availability (HA) Cluster heartbeatbull hacl-hb 5300UDP High Availability (HA) Cluster heartbeatbull hacl-cfg 5302TCP HA Cluster TCP configurationbull hacl-cfg 5302UDP HA Cluster UDP configurationbull hacl-local 5304TCP HA Cluster Commands

If you are using SNMP

bull snmp 161UDPbull snmptrap 162UDP

If you are using the WBEM provider

bull wbem-http TCP5988bull wbem-https TCP5989

If you are using the Quorum Server

bull hacl-qs 1238TCP HA Quorum Server

If you are using the appserver utility

bull hacl-poll 5315TCP

If you are using VMware VMFS volumes

bull https 443TCP

Ports needed for authenticationThe ports reserved for authentication are also used by Serviceguard

bull auth 113TCP authenticationbull auth 113UDP authentication

Ports needed by Serviceguard Managerbull 5511 (http) and 5522 (https) 5301 (multicast port) are used by Serviceguard Managerbull Serviceguard Manager needs a multicast IP address and a TCPIP port for auto-discovery of the nodes in

the subnet Serviceguard uses default multicast IP 235111 and 5301 port which are configured in thesetting page

12 Compatibility and installation requirements

NOTE

Only IP address can be modified by the user The default port 5301 cannot be modified

System firewallsSystem firewalls When using a system firewall with Serviceguard for Linux you must leave open the portslisted above For more information see the latest version of Configuring firewall rules for HP Serviceguard onSUSE Linux Enterprise Server and Red Hat White Paper at httpwwwhpecominfolinux-serviceguard-docs mdashgt Whitepapers

Serviceguard also uses some dynamic ports for some cluster services These must be open in the firewallThey are typically in the range 32768-61000 for Red Hat To determine the range on a given system checkthe contents of the file procsysnetipv4ip_local_port_range

If you have adjusted the dynamic port range using kernel tunable parameters alter your firewall rulesaccordingly

bull To enable intra-cluster communications each HEARTBEAT_IP network on every node in the cluster mustallow the following communications in both directions with all other nodes in the cluster

TCP on port numbers 5300 and 5302 ndash and allow only packets with the SYN flag UDP on port numbers 5300 and 5302 TCP and UDP on dynamic ports

bull If you use a quorum server all nodes in the cluster must allow the following communication to the quorumserver IP address

TCP on port 1238 mdash and allow only packets with the SYN flag

Any node providing quorum service for another cluster must allow the following communication fromthat clusterrsquos nodes

TCP on port 1238 mdash and allow only packets with the SYN flagbull Running the cmscancl command requires the ssh port be open

There are additional firewall requirements to enable execution of Serviceguard commands from nodesoutside the cluster such as those listed in cmclnodelist To allow execution of Serviceguard commandsfollow these guidelines

All nodes in the cluster must allow the following communicationsbull from the remote nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

bull to the remote nodes

TCP and UDP on dynamic ports

The remote nodes must allow the following communicationsbull from the cluster nodes

TCP and UDP on dynamic portsbull to the cluster nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

Authentication communication must allow the following ports

System firewalls 13

bull from the cluster nodes

TCP and UDP on port 113bull to the cluster nodes

TCP and UDP on port 113

NOTE

If you suspect that the firewall is blocking communications you can add -j LOG before the last line inyour iptables file (for example etcsysconfigiptables) to log any blocked ports Consult your Linuxdistributionrsquos documentation on firewalls for information on iptables

14 Compatibility and installation requirements

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 9: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Licensing informationStarting Serviceguard for Linux 120000 requires licenses on per-socket basis When you installServiceguard for Linux Enterprise edition an instant-on license valid for 90 days is installed With this instant-on license you can use the product even if you do not have a permanent license You must get a permanentlicense before the grace period expires

When ordering the licenses determine the number of active sockets on the server and order one license foreach active socket irrespective of number of cores A virtualized server may select less than the total amountof active sockets if Serviceguard is used within virtual machine which utilized less than the total number ofsockets For information about the license terms and supported server models see the QuickSpecs availableat httpwwwhpecominfoquickspecs

IMPORTANT

If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 youcan use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

Obtaining a permanent licenseBefore your 90 days instant-on license expires you must obtain and validate the permanent license tocontinue to use applicable Serviceguard versions beyond the grace period

To obtain a permanent license

1 Go to httpsmyenterpriselicensehpecom2 Log into HPE Passport If you do not have an account you can create one3 Enter Entitlement Order Number and click Go

bull Here are the licenses listed that have been activated and license that have not yet been activated4 Check the box that belongs to products you want to activate and click Next5 Select ldquoif you are activating for yourselfrdquo or ldquoif you are activating on behalf of another customerrdquo If ldquoon

behalf of another customerrdquo is selected you will enter the final user email address6 Activation Completes Save the files One includes the license key and the other includes additional

product information7 You will receive a license certificate in your email box You must retain the email message because this is

the valid proof of purchase documentation you may need for future reference or support requests

IMPORTANT

Ensure that you save the file and make a note of its path (See the example in Validating thepermanent license on page 10)

Renewing the permanent licenseAfter you have obtained the permanent license follow these steps to renew the license

NOTE

You must renew or apply the license on each node

Procedure

1 Ensure that $SGCONFAutoPassLicFiletxt exists

Licensing information 9

NOTE

Hewlett Packard Enterprise recommends that you back up the $SGCONFAutoPassLicFiletxtbefore renewing the license

2 Place the permanent license key in a file on the system

NOTE

Ensure the file that contains the license key must not have the commented line

3 Renew the license

cmsetlicense -i ltabsolute path of the license filegtOn successful license renewal it displays the following message

License is successfully installedFor more information see cmsetlicense(1m) manpage

Example

To verify if the license is valid

a Copy the license file

cp $SGCONFAutoPassLicFiletxt $SGCONFAutoPassLicFiletxtsavb Run the cmsetlicense command

cmsetlicense -i testmySGlicenseThe mySGlicense file contains the license information

c Run the cmgetlicense command

cmgetlicense -f lined If the license is valid keep the new license file $SGCONFAutoPassLicFiletxt and delete the old

license file $SGCONFAutoPassLicFiletxtsav

If the license is invalid restore the original license

mv $SGCONFAutoPassLicFiletxtsav $SGCONFAutoPassLicFiletxt

Validating the permanent licenseIMPORTANT

Ensure that you validate the permanent license before the 90ndashday grace period of instant-on licenseexpires

To validate the permanent license

1 Run the following command

cmgetlicense -f line2 On successful renewal the command displays the following output

cmgetlicense -f line

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

10 Validating the permanent license

NOTE

bull If you install higher license than the one already installed on the system the license on the nodeis upgraded automatically

For example if you have Serviceguard for Advanced and install Serviceguard for Enterprise thelicense on the node is upgraded to Enterprise and the cmgetlicense -f line commanddisplays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

bull If you have multiple licenses of the same type installed on the system the cmgetlicense -fline command displays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=3 nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

Licensing information 11

Compatibility and installation requirements

Hardware requirementsFor more information about hardware requirements see the latest version of HPE Serviceguard for LinuxCertification Matrix at httpwwwhpecominfolinux-serviceguard-docs

Port requirements

Ports needed for ServiceguardBefore installing ensure that no other program uses these ports

On Red Hat Enterprise Linux and SUSE Linux Enterprise Server

bull icmp 8icmpbull hacl-hb 5300TCP High Availability (HA) Cluster heartbeatbull hacl-hb 5300UDP High Availability (HA) Cluster heartbeatbull hacl-cfg 5302TCP HA Cluster TCP configurationbull hacl-cfg 5302UDP HA Cluster UDP configurationbull hacl-local 5304TCP HA Cluster Commands

If you are using SNMP

bull snmp 161UDPbull snmptrap 162UDP

If you are using the WBEM provider

bull wbem-http TCP5988bull wbem-https TCP5989

If you are using the Quorum Server

bull hacl-qs 1238TCP HA Quorum Server

If you are using the appserver utility

bull hacl-poll 5315TCP

If you are using VMware VMFS volumes

bull https 443TCP

Ports needed for authenticationThe ports reserved for authentication are also used by Serviceguard

bull auth 113TCP authenticationbull auth 113UDP authentication

Ports needed by Serviceguard Managerbull 5511 (http) and 5522 (https) 5301 (multicast port) are used by Serviceguard Managerbull Serviceguard Manager needs a multicast IP address and a TCPIP port for auto-discovery of the nodes in

the subnet Serviceguard uses default multicast IP 235111 and 5301 port which are configured in thesetting page

12 Compatibility and installation requirements

NOTE

Only IP address can be modified by the user The default port 5301 cannot be modified

System firewallsSystem firewalls When using a system firewall with Serviceguard for Linux you must leave open the portslisted above For more information see the latest version of Configuring firewall rules for HP Serviceguard onSUSE Linux Enterprise Server and Red Hat White Paper at httpwwwhpecominfolinux-serviceguard-docs mdashgt Whitepapers

Serviceguard also uses some dynamic ports for some cluster services These must be open in the firewallThey are typically in the range 32768-61000 for Red Hat To determine the range on a given system checkthe contents of the file procsysnetipv4ip_local_port_range

If you have adjusted the dynamic port range using kernel tunable parameters alter your firewall rulesaccordingly

bull To enable intra-cluster communications each HEARTBEAT_IP network on every node in the cluster mustallow the following communications in both directions with all other nodes in the cluster

TCP on port numbers 5300 and 5302 ndash and allow only packets with the SYN flag UDP on port numbers 5300 and 5302 TCP and UDP on dynamic ports

bull If you use a quorum server all nodes in the cluster must allow the following communication to the quorumserver IP address

TCP on port 1238 mdash and allow only packets with the SYN flag

Any node providing quorum service for another cluster must allow the following communication fromthat clusterrsquos nodes

TCP on port 1238 mdash and allow only packets with the SYN flagbull Running the cmscancl command requires the ssh port be open

There are additional firewall requirements to enable execution of Serviceguard commands from nodesoutside the cluster such as those listed in cmclnodelist To allow execution of Serviceguard commandsfollow these guidelines

All nodes in the cluster must allow the following communicationsbull from the remote nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

bull to the remote nodes

TCP and UDP on dynamic ports

The remote nodes must allow the following communicationsbull from the cluster nodes

TCP and UDP on dynamic portsbull to the cluster nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

Authentication communication must allow the following ports

System firewalls 13

bull from the cluster nodes

TCP and UDP on port 113bull to the cluster nodes

TCP and UDP on port 113

NOTE

If you suspect that the firewall is blocking communications you can add -j LOG before the last line inyour iptables file (for example etcsysconfigiptables) to log any blocked ports Consult your Linuxdistributionrsquos documentation on firewalls for information on iptables

14 Compatibility and installation requirements

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 10: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

NOTE

Hewlett Packard Enterprise recommends that you back up the $SGCONFAutoPassLicFiletxtbefore renewing the license

2 Place the permanent license key in a file on the system

NOTE

Ensure the file that contains the license key must not have the commented line

3 Renew the license

cmsetlicense -i ltabsolute path of the license filegtOn successful license renewal it displays the following message

License is successfully installedFor more information see cmsetlicense(1m) manpage

Example

To verify if the license is valid

a Copy the license file

cp $SGCONFAutoPassLicFiletxt $SGCONFAutoPassLicFiletxtsavb Run the cmsetlicense command

cmsetlicense -i testmySGlicenseThe mySGlicense file contains the license information

c Run the cmgetlicense command

cmgetlicense -f lined If the license is valid keep the new license file $SGCONFAutoPassLicFiletxt and delete the old

license file $SGCONFAutoPassLicFiletxtsav

If the license is invalid restore the original license

mv $SGCONFAutoPassLicFiletxtsav $SGCONFAutoPassLicFiletxt

Validating the permanent licenseIMPORTANT

Ensure that you validate the permanent license before the 90ndashday grace period of instant-on licenseexpires

To validate the permanent license

1 Run the following command

cmgetlicense -f line2 On successful renewal the command displays the following output

cmgetlicense -f line

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

10 Validating the permanent license

NOTE

bull If you install higher license than the one already installed on the system the license on the nodeis upgraded automatically

For example if you have Serviceguard for Advanced and install Serviceguard for Enterprise thelicense on the node is upgraded to Enterprise and the cmgetlicense -f line commanddisplays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

bull If you have multiple licenses of the same type installed on the system the cmgetlicense -fline command displays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=3 nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

Licensing information 11

Compatibility and installation requirements

Hardware requirementsFor more information about hardware requirements see the latest version of HPE Serviceguard for LinuxCertification Matrix at httpwwwhpecominfolinux-serviceguard-docs

Port requirements

Ports needed for ServiceguardBefore installing ensure that no other program uses these ports

On Red Hat Enterprise Linux and SUSE Linux Enterprise Server

bull icmp 8icmpbull hacl-hb 5300TCP High Availability (HA) Cluster heartbeatbull hacl-hb 5300UDP High Availability (HA) Cluster heartbeatbull hacl-cfg 5302TCP HA Cluster TCP configurationbull hacl-cfg 5302UDP HA Cluster UDP configurationbull hacl-local 5304TCP HA Cluster Commands

If you are using SNMP

bull snmp 161UDPbull snmptrap 162UDP

If you are using the WBEM provider

bull wbem-http TCP5988bull wbem-https TCP5989

If you are using the Quorum Server

bull hacl-qs 1238TCP HA Quorum Server

If you are using the appserver utility

bull hacl-poll 5315TCP

If you are using VMware VMFS volumes

bull https 443TCP

Ports needed for authenticationThe ports reserved for authentication are also used by Serviceguard

bull auth 113TCP authenticationbull auth 113UDP authentication

Ports needed by Serviceguard Managerbull 5511 (http) and 5522 (https) 5301 (multicast port) are used by Serviceguard Managerbull Serviceguard Manager needs a multicast IP address and a TCPIP port for auto-discovery of the nodes in

the subnet Serviceguard uses default multicast IP 235111 and 5301 port which are configured in thesetting page

12 Compatibility and installation requirements

NOTE

Only IP address can be modified by the user The default port 5301 cannot be modified

System firewallsSystem firewalls When using a system firewall with Serviceguard for Linux you must leave open the portslisted above For more information see the latest version of Configuring firewall rules for HP Serviceguard onSUSE Linux Enterprise Server and Red Hat White Paper at httpwwwhpecominfolinux-serviceguard-docs mdashgt Whitepapers

Serviceguard also uses some dynamic ports for some cluster services These must be open in the firewallThey are typically in the range 32768-61000 for Red Hat To determine the range on a given system checkthe contents of the file procsysnetipv4ip_local_port_range

If you have adjusted the dynamic port range using kernel tunable parameters alter your firewall rulesaccordingly

bull To enable intra-cluster communications each HEARTBEAT_IP network on every node in the cluster mustallow the following communications in both directions with all other nodes in the cluster

TCP on port numbers 5300 and 5302 ndash and allow only packets with the SYN flag UDP on port numbers 5300 and 5302 TCP and UDP on dynamic ports

bull If you use a quorum server all nodes in the cluster must allow the following communication to the quorumserver IP address

TCP on port 1238 mdash and allow only packets with the SYN flag

Any node providing quorum service for another cluster must allow the following communication fromthat clusterrsquos nodes

TCP on port 1238 mdash and allow only packets with the SYN flagbull Running the cmscancl command requires the ssh port be open

There are additional firewall requirements to enable execution of Serviceguard commands from nodesoutside the cluster such as those listed in cmclnodelist To allow execution of Serviceguard commandsfollow these guidelines

All nodes in the cluster must allow the following communicationsbull from the remote nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

bull to the remote nodes

TCP and UDP on dynamic ports

The remote nodes must allow the following communicationsbull from the cluster nodes

TCP and UDP on dynamic portsbull to the cluster nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

Authentication communication must allow the following ports

System firewalls 13

bull from the cluster nodes

TCP and UDP on port 113bull to the cluster nodes

TCP and UDP on port 113

NOTE

If you suspect that the firewall is blocking communications you can add -j LOG before the last line inyour iptables file (for example etcsysconfigiptables) to log any blocked ports Consult your Linuxdistributionrsquos documentation on firewalls for information on iptables

14 Compatibility and installation requirements

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 11: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

NOTE

bull If you install higher license than the one already installed on the system the license on the nodeis upgraded automatically

For example if you have Serviceguard for Advanced and install Serviceguard for Enterprise thelicense on the node is upgraded to Enterprise and the cmgetlicense -f line commanddisplays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=1nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

bull If you have multiple licenses of the same type installed on the system the cmgetlicense -fline command displays the following output

nodenode1|license_type=Enterprise|license_type=Enterprisenodenode1|license_type=Enterprise|license_count=3 nodenode1|license_type=Enterprise|license_valid_for_days=Indefinite

Licensing information 11

Compatibility and installation requirements

Hardware requirementsFor more information about hardware requirements see the latest version of HPE Serviceguard for LinuxCertification Matrix at httpwwwhpecominfolinux-serviceguard-docs

Port requirements

Ports needed for ServiceguardBefore installing ensure that no other program uses these ports

On Red Hat Enterprise Linux and SUSE Linux Enterprise Server

bull icmp 8icmpbull hacl-hb 5300TCP High Availability (HA) Cluster heartbeatbull hacl-hb 5300UDP High Availability (HA) Cluster heartbeatbull hacl-cfg 5302TCP HA Cluster TCP configurationbull hacl-cfg 5302UDP HA Cluster UDP configurationbull hacl-local 5304TCP HA Cluster Commands

If you are using SNMP

bull snmp 161UDPbull snmptrap 162UDP

If you are using the WBEM provider

bull wbem-http TCP5988bull wbem-https TCP5989

If you are using the Quorum Server

bull hacl-qs 1238TCP HA Quorum Server

If you are using the appserver utility

bull hacl-poll 5315TCP

If you are using VMware VMFS volumes

bull https 443TCP

Ports needed for authenticationThe ports reserved for authentication are also used by Serviceguard

bull auth 113TCP authenticationbull auth 113UDP authentication

Ports needed by Serviceguard Managerbull 5511 (http) and 5522 (https) 5301 (multicast port) are used by Serviceguard Managerbull Serviceguard Manager needs a multicast IP address and a TCPIP port for auto-discovery of the nodes in

the subnet Serviceguard uses default multicast IP 235111 and 5301 port which are configured in thesetting page

12 Compatibility and installation requirements

NOTE

Only IP address can be modified by the user The default port 5301 cannot be modified

System firewallsSystem firewalls When using a system firewall with Serviceguard for Linux you must leave open the portslisted above For more information see the latest version of Configuring firewall rules for HP Serviceguard onSUSE Linux Enterprise Server and Red Hat White Paper at httpwwwhpecominfolinux-serviceguard-docs mdashgt Whitepapers

Serviceguard also uses some dynamic ports for some cluster services These must be open in the firewallThey are typically in the range 32768-61000 for Red Hat To determine the range on a given system checkthe contents of the file procsysnetipv4ip_local_port_range

If you have adjusted the dynamic port range using kernel tunable parameters alter your firewall rulesaccordingly

bull To enable intra-cluster communications each HEARTBEAT_IP network on every node in the cluster mustallow the following communications in both directions with all other nodes in the cluster

TCP on port numbers 5300 and 5302 ndash and allow only packets with the SYN flag UDP on port numbers 5300 and 5302 TCP and UDP on dynamic ports

bull If you use a quorum server all nodes in the cluster must allow the following communication to the quorumserver IP address

TCP on port 1238 mdash and allow only packets with the SYN flag

Any node providing quorum service for another cluster must allow the following communication fromthat clusterrsquos nodes

TCP on port 1238 mdash and allow only packets with the SYN flagbull Running the cmscancl command requires the ssh port be open

There are additional firewall requirements to enable execution of Serviceguard commands from nodesoutside the cluster such as those listed in cmclnodelist To allow execution of Serviceguard commandsfollow these guidelines

All nodes in the cluster must allow the following communicationsbull from the remote nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

bull to the remote nodes

TCP and UDP on dynamic ports

The remote nodes must allow the following communicationsbull from the cluster nodes

TCP and UDP on dynamic portsbull to the cluster nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

Authentication communication must allow the following ports

System firewalls 13

bull from the cluster nodes

TCP and UDP on port 113bull to the cluster nodes

TCP and UDP on port 113

NOTE

If you suspect that the firewall is blocking communications you can add -j LOG before the last line inyour iptables file (for example etcsysconfigiptables) to log any blocked ports Consult your Linuxdistributionrsquos documentation on firewalls for information on iptables

14 Compatibility and installation requirements

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 12: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Compatibility and installation requirements

Hardware requirementsFor more information about hardware requirements see the latest version of HPE Serviceguard for LinuxCertification Matrix at httpwwwhpecominfolinux-serviceguard-docs

Port requirements

Ports needed for ServiceguardBefore installing ensure that no other program uses these ports

On Red Hat Enterprise Linux and SUSE Linux Enterprise Server

bull icmp 8icmpbull hacl-hb 5300TCP High Availability (HA) Cluster heartbeatbull hacl-hb 5300UDP High Availability (HA) Cluster heartbeatbull hacl-cfg 5302TCP HA Cluster TCP configurationbull hacl-cfg 5302UDP HA Cluster UDP configurationbull hacl-local 5304TCP HA Cluster Commands

If you are using SNMP

bull snmp 161UDPbull snmptrap 162UDP

If you are using the WBEM provider

bull wbem-http TCP5988bull wbem-https TCP5989

If you are using the Quorum Server

bull hacl-qs 1238TCP HA Quorum Server

If you are using the appserver utility

bull hacl-poll 5315TCP

If you are using VMware VMFS volumes

bull https 443TCP

Ports needed for authenticationThe ports reserved for authentication are also used by Serviceguard

bull auth 113TCP authenticationbull auth 113UDP authentication

Ports needed by Serviceguard Managerbull 5511 (http) and 5522 (https) 5301 (multicast port) are used by Serviceguard Managerbull Serviceguard Manager needs a multicast IP address and a TCPIP port for auto-discovery of the nodes in

the subnet Serviceguard uses default multicast IP 235111 and 5301 port which are configured in thesetting page

12 Compatibility and installation requirements

NOTE

Only IP address can be modified by the user The default port 5301 cannot be modified

System firewallsSystem firewalls When using a system firewall with Serviceguard for Linux you must leave open the portslisted above For more information see the latest version of Configuring firewall rules for HP Serviceguard onSUSE Linux Enterprise Server and Red Hat White Paper at httpwwwhpecominfolinux-serviceguard-docs mdashgt Whitepapers

Serviceguard also uses some dynamic ports for some cluster services These must be open in the firewallThey are typically in the range 32768-61000 for Red Hat To determine the range on a given system checkthe contents of the file procsysnetipv4ip_local_port_range

If you have adjusted the dynamic port range using kernel tunable parameters alter your firewall rulesaccordingly

bull To enable intra-cluster communications each HEARTBEAT_IP network on every node in the cluster mustallow the following communications in both directions with all other nodes in the cluster

TCP on port numbers 5300 and 5302 ndash and allow only packets with the SYN flag UDP on port numbers 5300 and 5302 TCP and UDP on dynamic ports

bull If you use a quorum server all nodes in the cluster must allow the following communication to the quorumserver IP address

TCP on port 1238 mdash and allow only packets with the SYN flag

Any node providing quorum service for another cluster must allow the following communication fromthat clusterrsquos nodes

TCP on port 1238 mdash and allow only packets with the SYN flagbull Running the cmscancl command requires the ssh port be open

There are additional firewall requirements to enable execution of Serviceguard commands from nodesoutside the cluster such as those listed in cmclnodelist To allow execution of Serviceguard commandsfollow these guidelines

All nodes in the cluster must allow the following communicationsbull from the remote nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

bull to the remote nodes

TCP and UDP on dynamic ports

The remote nodes must allow the following communicationsbull from the cluster nodes

TCP and UDP on dynamic portsbull to the cluster nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

Authentication communication must allow the following ports

System firewalls 13

bull from the cluster nodes

TCP and UDP on port 113bull to the cluster nodes

TCP and UDP on port 113

NOTE

If you suspect that the firewall is blocking communications you can add -j LOG before the last line inyour iptables file (for example etcsysconfigiptables) to log any blocked ports Consult your Linuxdistributionrsquos documentation on firewalls for information on iptables

14 Compatibility and installation requirements

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 13: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

NOTE

Only IP address can be modified by the user The default port 5301 cannot be modified

System firewallsSystem firewalls When using a system firewall with Serviceguard for Linux you must leave open the portslisted above For more information see the latest version of Configuring firewall rules for HP Serviceguard onSUSE Linux Enterprise Server and Red Hat White Paper at httpwwwhpecominfolinux-serviceguard-docs mdashgt Whitepapers

Serviceguard also uses some dynamic ports for some cluster services These must be open in the firewallThey are typically in the range 32768-61000 for Red Hat To determine the range on a given system checkthe contents of the file procsysnetipv4ip_local_port_range

If you have adjusted the dynamic port range using kernel tunable parameters alter your firewall rulesaccordingly

bull To enable intra-cluster communications each HEARTBEAT_IP network on every node in the cluster mustallow the following communications in both directions with all other nodes in the cluster

TCP on port numbers 5300 and 5302 ndash and allow only packets with the SYN flag UDP on port numbers 5300 and 5302 TCP and UDP on dynamic ports

bull If you use a quorum server all nodes in the cluster must allow the following communication to the quorumserver IP address

TCP on port 1238 mdash and allow only packets with the SYN flag

Any node providing quorum service for another cluster must allow the following communication fromthat clusterrsquos nodes

TCP on port 1238 mdash and allow only packets with the SYN flagbull Running the cmscancl command requires the ssh port be open

There are additional firewall requirements to enable execution of Serviceguard commands from nodesoutside the cluster such as those listed in cmclnodelist To allow execution of Serviceguard commandsfollow these guidelines

All nodes in the cluster must allow the following communicationsbull from the remote nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

bull to the remote nodes

TCP and UDP on dynamic ports

The remote nodes must allow the following communicationsbull from the cluster nodes

TCP and UDP on dynamic portsbull to the cluster nodes

TCP on ports 5302 mdash and allow only packets with the SYN flag UDP on port 5302

Authentication communication must allow the following ports

System firewalls 13

bull from the cluster nodes

TCP and UDP on port 113bull to the cluster nodes

TCP and UDP on port 113

NOTE

If you suspect that the firewall is blocking communications you can add -j LOG before the last line inyour iptables file (for example etcsysconfigiptables) to log any blocked ports Consult your Linuxdistributionrsquos documentation on firewalls for information on iptables

14 Compatibility and installation requirements

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 14: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

bull from the cluster nodes

TCP and UDP on port 113bull to the cluster nodes

TCP and UDP on port 113

NOTE

If you suspect that the firewall is blocking communications you can add -j LOG before the last line inyour iptables file (for example etcsysconfigiptables) to log any blocked ports Consult your Linuxdistributionrsquos documentation on firewalls for information on iptables

14 Compatibility and installation requirements

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 15: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Supported browsersServiceguard Manager supports the following web browsers

bull Microsoft Internet Explorerbull Mozilla Firefoxbull Google Chrome

For latest information about web browser support see the latest version of HPEServiceguard for LinuxCertification Matrix available at httpwwwhpecominfosglx

NOTE

The recommended screen resolution for Serviceguard Manager is 1280 x 1024 or greater HoweverServiceguard Manager also supports a minimum screen resolution of 1024 x 768

Supported browsers 15

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 16: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Software prerequisites for Serviceguard for LinuxBefore installing Serviceguard for Linux ensure that all the following software prerequisites are installed

bull Hewlett Packard Enterprise recommends that you must upgrade all components of the cluster to the latestfirmware versions before you install Serviceguard

bull Serviceguard for Linux depends on the xinetd service Ensure that the xinetd rpm is installed from thedistribution source (for example your Linux installation DVD) and is enabled

To check if the xinetd service is running

ps -ef | grep xinetdTo enable the xinetd service

sbinchkconfig --level 35 xinetd onTo enable the xinetd service on Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12

systemctl enable xinetdservice

NOTE

On SUSE Linux Enterprise Server xinetd service does not run if no services are configured This canlead to patch installation failure To address this perform the following

bull You can configure xinetd with -stayalive option to ensure that it is running even when noservices are configured

bull Alternatively you can configure any other service before installing the patch to ensure that xinetdalways restarts successfully

For example you can configure echo under xinetd using

sbinchkconfig echo on

The table lists all the software that you need for each distribution before installing Serviceguard for LinuxEnterprise edition

16 Software prerequisites for Serviceguard for Linux

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 17: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Table 1 RPMs (prerequisites) for installing Serviceguard A121000 for Linux

Red Hat Enterprise Linux SUSE Linux Enterprise Server

lm_sensors

tog-pegasus

authd

krb5-libs

zlib

libblkid(rhel6)

net-snmp

sg3_utils

sg3_utils-libs

xinetd

libnl (rhel 6)

libnl1 (rhel 7)

mdadm

udev (rhel 6)

lsscsi

net-tools

systemd (rhel 7)

policycoreutil (for KVM toolkit on rhel6 when SELinuxis enforced)1

checkpolicy (for KVM toolkit on rhel6 when SELinuxis enforced )1

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode

open-vm-tools (VMware only rhel7 and theirrespective later releases)2

bash

pidentd

libblkid1

sblim-indication_helper

sblim-sfcb

sblim-sfcc

sblim-cmpi-base

net-snmp

sg3_utils

xinetd

libnl

mdadm

udev

lsscsi

net-tools

systemd (SLES 12)

tog-pegasus (For HPE Metrocluster with ContinuousAccess EVA P6000)

sqlite

dmidecode (SLES 12)

pmtools (SLES 11)

open-vm-tools

open-vm-tools (VMware only SLES11 SP4 SLES12and their respective later releases)2

1 The cmeasyinstall -a will not automatically install these packages You have to manually install thesepackages on an RHEL6 system if the SELinux is enforced2 On SLES11 SP4 SLES12 RHEL7 and their respective later releases open-vm-tools are bundled along withdistributions For installation of VMware tools you may refer Installing and Configuring VMware Toolsdocument at httpswwwvmwarecompdfvmware-tools-installation-configurationpdf

For latest information about Java on each Linux OS see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Other software prerequisites

For latest information about Java and Jetty support on each Linux OS see the latest version of HPEServiceguard for Linux Certification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Software prerequisites for Serviceguard for Linux 17

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 18: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

You can install all these software prerequisites manually or automatically by using cmeasyinstall -acommand except for Java

18 Software prerequisites for Serviceguard for Linux

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 19: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Installing Serviceguard for LinuxIf you are installing Serviceguard for Linux for the first time you can do in the following ways

bull Installing Serviceguard for Linux using cmeasyinstall on page 19bull Installing Serviceguard for Linux the traditional way on page 21

If Serviceguard version earlier than A120000 is installed follow the instructions described in the Performing rolling upgrades on page 29 section to upgrade to latest version

NOTE

bull Hewlett Packard Enterprise recommends installing all the components that are part of theServiceguard for Linux Enterprise edition 121000 (Red Hat Enterprise Linux 6 7 and SUSE LinuxEnterprise Server 11 12)

bull Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacypackages you must migrate to modular packages before you move to 120000 For moreinformation about how to migrate to modular packages see the white paper Migrating packages fromlegacy to modular style available at httpwwwhpecominfolinux-serviceguard-docs

Installing Serviceguard for Linux using cmeasyinstallThe cmeasyinstall tool helps you to install Serviceguard for Linux and its components such asServiceguard Manager Toolkits Extended Distance Cluster Metrocluster and SGeSAP You can alsoexecute the cmeasyinstall tool from one of the nodes in the specified list and also the tool has capabilityto do a fresh installation on the remote nodes that are specified It also provides an option to install thesoftware prerequisites along with Serviceguard for Linux and its components

Prerequisites

Before you begin to use cmeasyinstall tool ensure that the following prerequisites are met

bull You must be a root userbull You must have lsquoexecutersquo permission on the node specifiedbull All nodes must be reachable using FQDN (Fully Qualified Domain Name) or PQDN (Partially Qualified

Domain Name)bull Ensure that all the nodes specified with cmeasyinstall are at same major version of the operating

systembull Ensure that PERL is installed on all the systems where you intend to install Serviceguard using the

cmeasyinstall toolbull Ensure that YUM (Yellowdog Updater Modified) update service on Red Hat Enterprise Linux Server or

Zypper on SUSE Linux Enterprise Server is configured if you intend to use the -a option

NOTE

The cmeasyinstall tool does not install the Quorum Server

The cmeasyinstall tool has the following advantages

bull Checks for dependencies and prompts you to install the required software or packages if not alreadyinstalled

bull Streamlines the installation of several rpm packages that are included on the DVD or ISO imagebull Reduces the installation from many commands to one command to invoke the toolbull Takes the list of nodes that are expected to be a part of the cluster and installs the software on all the

nodes

Installing Serviceguard for Linux 19

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 20: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

The cmeasyinstall tool prompts for the directory path where the Serviceguard for Linux DVD or ISO imageis mounted It checks for Linux packages that are required as prerequisites for Serviceguard for Linux and itscomponents For more information about software prerequisites see Software prerequisites forServiceguard for Linux If not already installed you will be prompted to install these packages for theinstallation to complete successfully

To run the cmeasyinstall tool

1 Mount Serviceguard for Linux DVD or ISO image2 Open a terminal window to the server from the console or an ssh client3 Execute the cmeasyinstall command with appropriate qualifiers For more information about the

command usage and qualifiers see the Read Me available at ltDVD_mount_dirgtREADME_cmeasyinstalltxt

The cmeasyinstall tool installs the RPMs

TIP

In case of SUSE Linux Enterprise Server 11 while installing serviceguard-snmp the following errormessage might be displayed if the xinetd service is not started

Starting cmsnmpdFailed due to no cmclconfderror posttrans(serviceguard-snmp-A120000-0sles11x86_64) scriptlet failed exit status 1After installation is complete if you see the following error message

node1~ cmviewclunable to receive reply from local cmclconfdConnection timed out Unable to initialize `HOSTNAME_ADDRESS_FAMILY`Then there is a problem with xinetd service To enable xinetd service see Software prerequisitesfor Serviceguard for Linux

On successful completion of the script the following message is displayed

Installation script execution completed successfully ltdategt

NOTE

If Serviceguard is already installed use cmupgrade tool to upgrade Serviceguard for Linux and itscomponents You cannot use the cmeasyinstall tool to upgrade Serviceguard for Linux and itscomponents If you have already installed Serviceguard for Linux and its components thecmeasyinstall tool exits with an appropriate error message

NOTE

The cmeasyinstall does not install Serviceguard Metrocluster with Continuous Access EVA P6000for Linux Enterprise on SUSE Linux Enterprise Server version 11 when you are using mdasha option Youneed to do the following

1 Install tog-pegasus rpm

rpm -ivh --nodeps tog-pegasus-280-35x86_64rpm

For more information about tog-pegasus rpm version see HPE Serviceguard for Linux Version120050 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

2 Install Serviceguard Metrocluster with Continuous Access EVA P6000

rpm -ivhserviceguard-metrocluster-caevap6000-B120000-0sles11x86_64rpm

20 Installing Serviceguard for Linux

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 21: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Installing Serviceguard for Linux the traditional wayIf you do not wish to install using the cmeasyinstall tool you must install the Serviceguard for Linux andits components manually in the same order as described in Packaging information on page 8 section andthe location of rpms are described in the DVD directory structure section

DVD directory structure

The following table describes the operating system and the DVD directory structure for Serviceguard for LinuxEnterprise edition

Table 2 DVD directory structure for Serviceguard for Linux Enterprise edition

Operating system DVD directory structure

Red Hat Enterprise Linux 6 ltDVD-mount-pathgtRedHatRedHat6Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat6ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat6Metroclusterx86_64ltrpmgt

Red Hat Enterprise Linux 7 ltDVD-mount-pathgtRedHatRedHat7Serviceguardx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGManagerx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7SGeSAPx86_64ltrpmgtltDVD-mount-pathgtRedHatRedHat7ToolkitnoarchltrpmgtltDVD-mount-pathgtRedHatRedHat7Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 11

ltDVD-mount-pathgtSLESSLES11Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES11ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES11Metroclusterx86_64ltrpmgt

SUSE Linux EnterpriseServer 12

ltDVD-mount-pathgtSLESSLES12Serviceguardx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGManagerx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12SGeSAPx86_64ltrpmgtltDVD-mount-pathgtSLESSLES12ToolkitnoarchltrpmgtltDVD-mount-pathgtSLESSLES12Metroclusterx86_64ltrpmgt

To install Serviceguard for Linux and it components use rpm -ivh ltproductgt command For example

On Red Hat Enterprise Linux 6

rpm -ivh serviceguard-A121000-0rhel6x86_64rpmOn Red Hat Enterprise Linux 7

Installing Serviceguard for Linux the traditional way 21

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 22: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

rpm -ivh serviceguard-A121000-0rhel7x86_64rpmOn SUSE Linux Enterprise Server 11

rpm -ivh serviceguard-A121000-0sles11x86_64rpmOn SUSE Linux Enterprise Server 12

rpm -ivh serviceguard-A121000-0sles12x86_64rpmServiceguard manager 121000 RPM installation requires replicated user sgmgr for performing multi-clustermanagement

Before installing the RPM ensure that the user sgmgr exists in the system If not the installation fails If thesgmgr does not exist in the system complete the steps to create the sgmgr as part of installation ofServiceguard Manager RPM

1 Export the SGMGR_ENV environment and run the RPM command

export SGMGR_ENV=ltpasswordgtrpm -ivh ltserviceguard-managergtrpm

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 and SUSELinux Enterprise Server 12) or Serviceguard Manager for Linux B121000 (Red Hat EnterpriseLinux 6 and SUSE Linux Enterprise Server 11) automatically creates a user called sgmgr andpassword for this user is taken from the SGMGR_ENV environment variable

Installing Serviceguard for Linux PatchStarting Serviceguard for Linux 120000 the patches are available on three different packages namelyServiceguard for Linux Base edition Serviceguard for Linux Advanced edition and Serviceguard for LinuxEnterprise edition For information about the components available in each package see Packaginginformation on page 8

You can download the latest Serviceguard patches for Linux 1200X from Hewlett Packard EnterpriseSupport Center at httpwwwhpecominfohpesc

Table 3 Serviceguard patches for Linux

ServiceguardVersion

Packages Patches

121000 Serviceguard for Linux Enterpriseedition

SGLX_00539tar

120051 Serviceguard for Linux Enterpriseedition

SGLX_00536tar

120050 Serviceguard for Linux Enterpriseedition

SGLX_00531tar

120040 Serviceguard for Linux Enterpriseedition

SGLX_00526tar

120030 Serviceguard for Linux Enterpriseedition

SGLX_00520tar

Table Continued

22 Installing Serviceguard for Linux Patch

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 23: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

ServiceguardVersion

Packages Patches

120020 Serviceguard for Linux Enterpriseedition

SGLX_00496tar

120010 Serviceguard for Linux Enterpriseedition

SGLX_00491tar

120001 Serviceguard for Linux Enterpriseedition

SGLX_00484tar

For latest information on supported OS for patches see the latest version of HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

To install the patch

Procedure

1 Download the patch depending on the package from the Hewlett Packard Enterprise Support Center at httpwwwhpecominfohpesc

IMPORTANT

Use cmeasyinstall if you are installing Serviceguard for the first time on the machine Usecmupgrade if you are upgrading Serviceguard to the next version

2 Extract the patch files from the ltfilenametargt file3 Verify the signature of the RPM For more information about how to verify the signature of the RPM see

httpwwwhpecominfoswdepotLinuxCodeSigning4 Upgrade Serviceguard for Linux in one of the following way

a Upgrading Serviceguard for Linux using cmupgrade toolb Upgrading Serviceguard for Linux the traditional wayc Upgrading Serviceguard for Linux using YUM or Zypper

5 Repeat steps from 2 to 4 on all the nodes in a cluster

Example

To install the patch using cmupgrade tool

1 Download SGLX_00531tar patch file for Serviceguard for Linux Enterprise edition2 Extract the patch file

tar mdashxvf SGLX_00531tarThe contents of the tar file are

cmeasyinstallcmupgradeinstallSGLX_00531textpublic_keyHP-RPM-GPG-2048-KEY-1pub CommonSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpm

ltdistgtltdistro_versiongtrepodatafilelistsxmlgzltdistgtltdistro_versiongtrepodataprimaryxmlgzltdistgtltdistro_versiongtrepodataotherxmlgz

Installing Serviceguard for Linux 23

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 24: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

ltdistgtltdistro_versiongtrepodatarepomdxmlltdistgtltdistro_versiongtServiceguardx86_64serviceguard-analytics-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtServiceguardx86_64serviceguard-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtSGManagerx86_64serviceguard-manager-B120050-0linuxnoarchrpmltdistgtltdistro_versiongtQuorumServerx86_64serviceguard-qs-A120050-0ltos_versiongtx86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-sybase-toolkit-A120040-00redhatnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-oracle-toolkit-A120050-00redhatnoarchrpmltdistgtltdistro_versiongtSGeSAPx86_64serviceguard-extension-for-sap-B060080-0sles12x86_64rpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-kvm-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtToolkitnoarchserviceguard-dataguard-toolkit-A120050-00slesnoarchrpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-3parrc-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caevap6000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-caxpp9000-B120050-0sles12x86_64rpmltdistgtltdistro_versiongtMetroclusternoarchserviceguard-metrocluster-emcsrdf-B120050-0sles12x86_64rpmwhere

ltdistgt is the value that can be either RedHat or SLES based on the operating system

ltdistro_versiongt is the value that can be either RedHat6 RedHat7 SLES11 or SLES12based on the operating system

ltos_versiongt is the value that can be either rhel6 rhel7 sles11 or sles12 based on theoperating system

3 Verify the signature of the RPMs For more information about how to verify the signature of the RPM see httpwwwhpecominfoswdepotLinuxCodeSigning

NOTE

Each RPM contains corresponding signature file with an extension sig

4 Upgrade Serviceguard for Linux Enterprise edition

Post installationAfter the installation is complete you need to configure the cluster For more information about how toconfigure the Serviceguard cluster see chapter 5 of Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

24 Post installation

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 25: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Rolling software upgradeYou can upgrade the Linux operating system and the Serviceguard software on a node at a time withoutbringing down your clusters This process can also be used any time when a node in the cluster must betaken offline for hardware maintenance or patch installations Until the process of upgrade is complete onall nodes you cannot change the cluster configuration files and you will not be able to use any of thefeatures of the new Serviceguard release

NOTE

Starting Serviceguard 120000 legacy packages are obsolete If you have configured legacy packagesyou need to migrate to modular packages before you move to 120000 For more information abouthow to migrate to modular packages see the white paper Migrating packages from legacy to modularstyle available at httpwwwhpecominfolinux-serviceguard-docs

RequirementsCAUTION

bull Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A120000 or laterbull If you are using an alternate address then you must upgrade the Quorum Server to version A

120000 before you proceed For more information see HPE Serviceguard Quorum Server VersionA120000 Release Notes available at httpwwwhpecominfolinux-serviceguard-docs

To upgrade a Linux Serviceguard node to a newer Serviceguard release you must ensure the following

bull The node must be running with a supported version of Linux (Red Hat Enterprise Linux 6x Red HatEnterprise Linux 7x SUSE Linux Enterprise Server 11 or SUSE Linux Enterprise Server 12)

bull The node must be running a supported release of Serviceguard

NOTE

If the target version of Serviceguard does not support the version of operating system on the nodecurrently then you must upgrade the operating system before upgrading Serviceguard

bull All members of the cluster must be upgraded to the same version of OS and the Serviceguardbull Ensure that all applications that run on the current OS are also supported with the new OSbull Verify that the new OS supports the current cluster hardware configuration and drivers (network interfaces

bonding driver and shared disk storage)bull Do a full backup on each node

NOTE

Hewlett Packard Enterprise recommends you to use the rolling upgrade process which

bull Helps you upgrade to the latest software versionbull Preserves the current OS and cluster configurationbull Keeps running your mission-critical applications

Before you upgrade ensure that you read the Limitations of rolling upgrades on page 26 andcomplete the entire upgrade process before you can use any Serviceguard commands

Rolling software upgrade 25

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 26: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

CAUTION

If a failure occurs on one node while you are upgrading another packages and the applications theycontain may not be able to fail over to the node being upgraded

Limitations of rolling upgradesbull During rolling upgrade you must issue Serviceguard commands (other than cmrunnode and

cmhaltnode) on nodes that have been upgraded to latest revision of Serviceguard software Issue ofcommands on yet to be upgraded nodes in the cluster will result in failure or inconsistent execution

bull You cannot modify the cluster or package configuration until the upgrade is complete You cannot modifythe hardware configuration including the clusterrsquos network configuration during rolling upgrade This meansthat you must upgrade all nodes to the new release before you can modify the configuration file and copy itto all nodes This restriction is applicable when you are upgrading Serviceguard from version 11xx to12xxyy

bull None of the features of the newer release of Serviceguard are allowed until all nodes have beenupgraded

bull Binary configuration files may be incompatible between releases of Serviceguard Do not manually copyconfiguration files between nodes The Serviceguard binary configuration file (cmclconfig) must be inthe correct directory or the cluster will not behave properly

bull Within a Serviceguard cluster no more than two versions of Serviceguard can be running while the rollingupgrade is in progress

bull All nodes must be running the same releases of Linux and Serviceguard before the upgradebull Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or Linux within the

cluster It is highly recommended that you upgrade all cluster nodes as quickly as possible to the newrelease level

bull You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the process ofrolling upgrade

bull This procedure depends on the upgrade or re-install keeping the same device naming convention andgeneral system configuration It is possible for devices to change names or be changed in the scan orderin a way that cannot be corrected If this happens the cluster must be recreated rather than to beupgraded

bull SGMgr does not detect the rolling upgrade status of that cluster hence you must use sgmgr after rollingupgrade is complete Sgmgr assumes that the cluster is not under rolling upgrade

PreparationIMPORTANT

Ensure that there is a supported upgrade path from your current Linux and Serviceguard versions to thenew versions For more information see the latest version of HPE Serviceguard for Linux CertificationMatrix available at httpwwwhpecominfolinux-serviceguard-docs

There is no upgrade path between some Linux OS releases In such cases you must install a new OS(cold install)

26 Limitations of rolling upgrades

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 27: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

CAUTION

No package can be in maintenance mode whether it is running or not when you perform an upgradefrom Serviceguard A1119 to any later version including an upgrade from the initial release of A1119to the July 2009 or later patch

This means

bull You must ensure that no packages are in maintenance mode when you start the upgradebull 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 To recover you must halt the cluster andthen upgrade all the nodes

For more information see ldquoMaintaining a Package Maintenance Moderdquo section in the Managing HPEServiceguard for Linux manual

Before you start doing the following

1 Record the hostname and its entire network interface IP addresses Record each MAC address of eachinterface and its network assignment (for example eth1 HWaddr 000BCD69F468)

2 Record all network information such as network mask gateway address DNS server address itsbroadcast address and so on This information can be useful if you are installing a new OS

NOTE

Ensure that all your network and storage interfaces are supported by the new OS

3 Record the storage configuration such as all LVM information and if possible collect a list of hardwaredisks configured for example sfdisk -l

On SUSE Linux Enterprise Server you may need to run YAST or YAST24 Back up the following files on media that can be easily recovered by the node after its upgrade or a new

OS installation

bull Host files rootrhosts etchosts etcprofile and the network information (includingthe bonding configurations)

Red Hat Enterprise Linux etcsysconfignetwork-scriptsifcfg SUSE Linux Enterprise Server etcsysconfignetworkifcfg

5 Ensure you have the latest versions of the software listed in the Software prerequisites forServiceguard for Linux section

bull SG files $SGCONF all current package control and configuration files including their log files

Rolling upgrade on OS1 Halt the node you want to upgrade (cmhaltnode -f) This will cause the nodes packages to start up on

an adoptive node2 Install the new Serviceguard from the DVD in the same order as described in the Packaging information

on page 83 Upgrade the node to latest patch

NOTE

bull Before you upgrade from SUSE Linux Enterprise Server 11 SP3 to SP4 ensure that you haveinstalled Serviceguard for Linux 120030

bull Before you upgrade from Redhat Enterprise Linux 68 to 69 ensure that you have installedServiceguard for Linux 121000

Rolling upgrade on OS 27

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 28: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

4 After completing the OS upgrade for the node restore all its previously saved Host files rootrhosts etchosts etcprofile etcprofile etcsysconfignetworkifcfg(or etcsysconfig network-scriptsifcfg) and bonding files

Verify that the network configurations are the same prior to the upgrade or the new installation Check thecurrent interface eth0 has the same corresponding Mac address before and after

5 Verify that all disks and their file systems are the same prior to this OS upgrade or new installation

Check and compare with the disk layout collected before the upgrade Use command vgscan to ensurethe node with new OS sees all its previously configured LVM disks

6 Follow the instructions in the README file in the directory of each driver If you have installed a new OSversion you must run a convert program This will convert the binary file (cmclconfig) to its newrelease format To run the program on the upgraded node enter$SGGSBINconverta Reboot the nodeb After the node is rebooted verify the cluster status using cmviewcl and also verify all file systems with

fsckc Restart Serviceguard on this node using cmrunnode Check that the node joins the cluster

successfully and if necessary move the packages back onto the noded Edit the following file to include the lineAUTOSTART_CMCLD = 1

For Red Hat Enterprise Linux usrlocalcmclusterconfcmclusterrcFor SUSE Linux Enterprise Server optcmclusterconfcmclusterrc

e Check if sgmgr service is running on the node

For all SLES run service jetty-sgmgr statusFor SLES12 or higher run systemctl status jetty-sgmgr

f 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 duringthe process without an unacceptable loss of performance If the cluster fails before the rollingupgrade is complete (because of a catastrophic power failure for example) you can restart it byentering the cmruncl command from a node which has been upgraded to the latest revision ofthe software

NOTE

bull Serviceguard does not support major OS upgrades For example Red Hat Enterprise Linux 6 to RedHat Enterprise Linux 7 or SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 12 OnRed Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 You must perform a freshinstallation of Serviceguard

bull If you plan to upgrade to new OS version you can use the same license that you are currently usingFor example if you are upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7you can use the same license of Red Hat Enterprise Linux 6 on Red Hat Enterprise Linux 7

bull Warning messages might appear during rolling upgrade while a node is determining the softwareversion that is running This is a normal occurrence and not a cause for concern

bull If you change kernel parameters as a part of doing a rolling upgrade ensure to make the samechanges on all nodes that can run the same packages

Supported rolling upgrade pathsThe following table describes the supported upgrade paths for Serviceguard for Linux

28 Supported rolling upgrade paths

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 29: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Table 4 Upgrade paths

Serviceguard version Rolling upgrade usingcmupgrade tool

Rolling upgradethe traditionalway

Offlineupgrade

To upgrade from A1200X to A1210Ysee Rolling upgrade from 1200X to1210X on page 36

Yes Yes Yes

To upgrade from A1119X to A121000see Rolling upgrade from 1119X to121000 on page 34

No Yes Yes

To upgrade from A1118X to A121000see Performing offline rolling upgradefrom 1118X to 121000 on page 35

No No Yes

To upgrade from A1120X to A121000or from A1120X to A1210Y see Rolling upgrade from 1120X to121000 on page 29

Yes Yes Yes

Performing rolling upgradesYou can perform online or offline rolling upgrade of Serviceguard for Linux across major versions starting A1120X and later in the following ways

bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from 1120X to 121000 on page 29bull Rolling upgrade from 1119X to 121000 on page 34bull Performing offline rolling upgrade from 1118X to 121000 on page 35bull Rolling upgrade from 1200X to 1210X on page 36bull Rolling upgrade from A1119X to A1210X on page 40bull Offline rolling upgrade from A1118X to A1210X on page 40

Rolling upgrade from 1120X to 121000You can perform rolling upgrade of Serviceguard for Linux either from 1120x to 121000 in the followingways

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 29bull Upgrading Serviceguard for Linux the traditional way on page 31bull Upgrading Serviceguard for Linux using YUM or Zypper on page 32

Upgrading Serviceguard for Linux using cmupgrade toolThe cmupgrade is the new tool introduced in Serviceguard for Linux A120000 which helps you inupgrading Serviceguard and its components such as Serviceguard Manager Toolkits Extended DistanceCluster and Metrocluster except for SGeSAP

The cmupgrade tool can be used to perform the previously mentioned upgrades on all Linux distrossupported by Serviceguard For information about supported versions see HPE Serviceguard for LinuxCertification Matrix available at httpwwwhpecominfolinux-serviceguard-docs

Before you begin to use the cmupgrade tool ensure that the following prerequisites are met

Performing rolling upgrades 29

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 30: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

bull You must be a root user to run the cmupgrade toolbull You must have execute permission to run the cmupgrade toolbull Ensure that PERL is installed on the system to run the cmupgrade toolbull Ensure that you run the cmupgrade tool on all the nodes that are part of the clusterbull Ensure that the Java is installed on the nodes before you run the cmupgrade tool Also ensure that java

-version command displays the version greater than or equal to 170 in the output

To perform the rolling upgrade from 1120x to 121000 using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node as follows

a Export the SGMGR_ENV environment variable

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation of Serviceguard Manager for Linux B121000 (Red Hat Enterprise Linux 7 SUSELinux Enterprise Server 12) or A121000 (Red Hat Enterprise Linux 6 or SUSE Linux EnterpriseServer 12) automatically creates a user called sgmgr and password for this user is taken from theSGMGR_ENV environment variable

b Upgrade node 1 cmupgrade [-a ltautomatic-installation-of-pre-requisitesgt] -dltmount-path-where-DVD-is-mountedgtFor more information see cmupgrade (1m) manpage

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

c If you plan to upgrade node 1 to A1210Y then follow the steps listed below If not you can skip thisstep and proceed to step 4

I Upgrade node 1 to A1210Y cmupgrade -d extracted_patch_location

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

30 Rolling software upgrade

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 31: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

5 Repeat steps from 2 to 4 for all the nodes6 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y the traditionalway

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt4 If you plan to upgrade node 1 to A1210Y then follow the steps outlined below If not you can skip this

step and proceed to step 5

a Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A1210Y-0rhel6x86_64rpm

NOTE

To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

bull HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes

IMPORTANT

Serviceguard manager requires a replicated user sgmgr created on the node Before installing orupgrading Serviceguard Manager RPM ensure that sgmgr user is created on all the nodes You canalso create the sgmgr user during the installation process by specifying environment variableSGMGR_ENV= followed by rpm -Uvh command

5 Restart the cluster on first node

For example cmrunnode -n node1

Upgrading Serviceguard for Linux the traditional way 31

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 32: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Check that the node joins the cluster successfully and if necessary move packages back to the node6 Repeat steps from 2 to 5 for all the nodes7 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all5 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 6 on page 33

a Create a etcyumreposdsglxpatchrepo YUM repository configuration file with the followingcontents

[sglxpatchrepo] name=sglxpatchrpms baseurl=fileltdir_locationgtRedHatltdistro_patch_vergt enabled=1where

ltdir_locationgt is the extracted patch location for a patch

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 7b Run the following command

yum clean allc Export SGMGR_ENV creating replicated user for Serviceguard-manager RPM Upgrade all rpms using

yum upgrade serviceguard- commandd Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using YUM

32 Upgrading Serviceguard for Linux using YUM or Zypper

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 33: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

yum upgrade serviceguard-manager6 Restart the cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

a To upgrade serviceguard-manager rpm

export SGMGR_ENV=ltpasswordgt yum upgrade serviceguard-manager7 Repeat steps from 2 to 8 for all the nodes8 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

On SUSE Linux Enterprise Server

To perform the rolling upgrade from A1120X to A121000 or from A1120X to A1210Y using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release4 Run the following command

usrbinzypper clean5 To upgrade Serviceguard-manager RPM using zypper you must first export SGMGR_ENV variable This

variable when initialized is used by RPM to create an user if it does not exist

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager6 If you plan to upgrade to A1210Y then follow the steps listed below If not you can skip this step and

proceed to step 8

a Create a etczyppreposdsglxpatchrepo Zypper repository configuration file with thefollowing contents

[sglxpatchrepo]name=sglxpatchrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patchb Run the following command

Rolling software upgrade 33

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 34: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

usrbinzypper cleanc Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

export SGMGR_ENV=ltpasswordgtzypper upgrade serviceguard-manager7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 If you plan to configure Serviceguard analytics for Linux see Managing HPE Serviceguard for Linux

available at httpwwwhpecominfolinux-serviceguard-docs

Rolling upgrade from 1119X to 121000To perform the rolling upgrade from A1119X to A121000

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node13 Uninstall sg_pidentd rpm

CAUTION

Serviceguard commands will not work unless step 5 is complete You cannot change the clusterconfiguration files until the process of upgrade is complete on all nodes

For example rpm -e --nodeps sg_pidentd-3019-2Note This step is applicable only on Red Hat Enterprise Linux

4 Install authd rpm from the Linux Distribution DVD or Repository

For example rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

5 Upgrade serviceguard-license before you upgrade to Serviceguard For example

rpm -Uvh serviceguard-license-A121000-0rhel6x86_64rpm6 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

34 Rolling upgrade from 1119X to 121000

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 35: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For more

information about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

7 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 7 for all the nodes

Performing offline rolling upgrade from 1118X to 121000To perform offline rolling upgrade from A1118X to A121000

1 Halt the cluster

For example cmhaltcl -f2 Select a node you want to upgrade and uninstall pidentd rpm

rpm -e --nodeps pidentd-3019-0Note This step is applicable only on Red Hat Enterprise Linux

3 Install authd rpm from distro

rpm -i ltauthd rpmgtNote This step is applicable only on Red Hat Enterprise Linux

4 Install serviceguard-license before you upgrade to Serviceguard For example

rpm -ivh serviceguard-license-A121000-0rhel6x86_64rpm5 Upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 6 x86_64

rpm ndashUvh serviceguard-A121000-0rhel6x86_64rpm

NOTE

bull When you upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more informationabout qualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notes HPE Serviceguard Toolkit for SAP Sybase ASE and SAP Sybase Replication Server for Linux

Release Notes HPE Serviceguard Toolkit for Oracle on Linux Release Notes

bull You can use YUM or Zypper to perform rolling upgrade from A1119X to A121000 For moreinformation about how to upgrade using YUM or Zypper see Upgrading Serviceguard for Linuxusing YUM or Zypper on page 32

6 Repeat steps from 2 to 5 on each node of the cluster7 After all nodes are upgraded restart the cluster

Performing offline rolling upgrade from 1118X to 121000 35

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 36: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

cmruncl

Rolling upgrade from 1200X to 1210XYou can perform rolling upgrade of Serviceguard for Linux from A1200X to A1210Y in the following waysfor example X is A120000 and Y is A121000 and Y is always greater than X

bull Upgrading Serviceguard for Linux using cmupgrade tool on page 36bull Upgrading Serviceguard for Linux the traditional way on page 37bull Upgrading Serviceguard for Linux using YUM or Zypper

NOTE

To perform configuration changes to the cluster or package during a rolling upgrade ensure that youinitiate the configuration commands from a node running Serviceguard version 12xxyy

Upgrading Serviceguard for Linux using cmupgrade toolTo perform the rolling upgrade from A1200X to A1210XX using cmupgrade tool

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade the node as follows

a If you have configured Serviceguard Manager and you are required to change the sgmgr userpassword then export the SGMGR_ENV

SGMGR_ENV=ltreplicated user passwordgtwhere ltreplicated user passwordgt is the password that you want to set for ServiceguardManager user

For more information about how to create a replicated user see Installing Serviceguard for Linux thetraditional way on page 21

NOTE

Installation or upgrade of Serviceguard Manager on Linux B121000 (Red Hat Enterprise Linux 6and 7 and SUSE Linux Enterprise Server 11 and 12) requires a replicated user sgmgr During theinstallation or upgrade process a user sgmgr is automatically created if the SGMGR_ENVenvironment is set

b Upgrade node 1 to A121000 if step a is required then

export SGMGR_ENV=ltpasswordgtcmupgrade -d extracted_patch_locatonc Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configure

36 Rolling upgrade from 1200X to 1210X

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 37: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

NFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

d If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

NOTE

The cmupgrade tool does not install or upgrade Quorum Server

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A1210XX and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux the traditional wayTo perform the rolling upgrade from A1200X to A12XXYY the traditional way

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 You can upgrade node 1 in the same order as described in the Packaging information on page 8

For example Serviceguard rpm for Red Hat 7 x86_64

rpm ndashUvh serviceguard-A121000Y-0rhel7x86_64rpm

NOTE

bull To upgrade toolkits use rpm ndashUvh with appropriate qualifiers For more information aboutqualifiers see the following documents available at httpwwwhpecominfolinux-serviceguard-docs

HPE Serviceguard Toolkit for Enterprise DB PPAS for Linux Release Notesbull To upgrade servicgurad-xdc prior to version A112020 rpm ndashUvh ndash-nopreun ltxdc-

rpm-namegt

IMPORTANT

After the Serviceguard Manager RPM installation is complete you must follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser see Installing Serviceguard for Linux the traditional way on page 21

Upgrading Serviceguard for Linux the traditional way 37

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 38: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

a Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you touse NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

b If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguardfor Linux available at httpwwwhpecominfolinux-serviceguard-docs

4 Rejoin the node to the cluster which was halted in step 2

For example cmrunnode -n node1

Check that the node joins the cluster successfully and if necessary move packages back to the node5 Repeat steps from 2 to 4 for all the nodes6 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin start

Upgrading Serviceguard for Linux using YUM or ZypperIf you have configured YUM update service on Red Hat Enterprise Linux Server or Zypper on SUSE LinuxEnterprise Server you can upgrade Serviceguard for Linux Enterprise edition using YUM or Zypper You mustupgrade in the same order as described in the Packaging information on page 8 section

NOTE

Ensure that major version of Serviceguard is installed before you upgrade to patch

On Red Hat Enterprise Linux

To perform the rolling upgrade from A1200X to A12XXYY using YUM

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etcyumreposdsglxrelrepo YUM repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtRedHatltdistro_major_vergtenabled=1where

ltdir_locationgt is the mount path where ISO image or DVD is mounted for the main release

ltdistro_major_vergt is the value that can be either Red Hat 6 or Red Hat 74 Run the following command

yum clean all

38 Upgrading Serviceguard for Linux using YUM or Zypper

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 39: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

5 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

6 You can upgrade node 1 in the same order as described in the Packaging information For example toupgrade Serviceguard Manager RPM using YUM yum upgrade serviceguardbull Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to

use NFS shared storage to create cluster analytics database For information about how to configureNFS as shared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you must follow the procedure describedlater in this section to start sgmgr service and also create a user which can be used as a replicateduser for multi-cluster management For more information about how to create a replicated user see Installing Serviceguard for Linux the traditional way on page 21

7 Rejoin the node to the cluster which was halted in setp 2

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

8 Repeat steps from 2 to 8 for all the nodes9 Once all the nodes are upgraded to A12XXYY and if you have already configured cluster analytics then

start analytics daemon

For example cmcaadmin startOn SUSE Linux Enterprise Server

To perform the rolling upgrade from A1200X to A12XXYY using Zypper

1 Enable global switching for packages running on node 1

The cmmodpkg command enables switching of the package

For example cmmodpkg -e pkg12 Halt first node

Halt the node you want to upgrade This results in the nodes packages to start up on an adoptive nodeThe Serviceguard daemon on node 1 is halted

For example cmhaltnode -f node1a If you have configured cluster analytics stop cluster analytics daemon For example cmcaadmin

stop3 Create a etczyppreposdsglxrelrepo Zypper repository configuration file with the following

contents

[sglxrelrepo]name=sglxrelrpmsbaseurl=fileltdir_locationgtSLESSLES11enabled=1where

ltdir_locationgt is the extracted patch location for a patch4 Run the following command

usrbinzypper clean

Rolling software upgrade 39

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 40: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

5 Starting Serviceguard analytics for Linux A120020 Hewlett Packard Enterprise recommends you to useNFS shared storage to create cluster analytics database For information about how to configure NFS asshared storage see Managing HPE Serviceguard for Linux available at httpwwwhpecominfolinux-serviceguard-docs

6 If you have already configured cluster analytics and plan to use the existing analytics database seesection ldquoCluster Analytics Database Migration to Shared Storagerdquo in the Managing HPE Serviceguard forLinux available at httpwwwhpecominfolinux-serviceguard-docs

7 Upgrade all the RPMs For example to upgrade Serviceguard Manager RPM using Zypper

zypper -n upgrade serviceguard-manager

IMPORTANT

After the Serviceguard Manager RPM upgrade is complete you need to follow the proceduredescribed later in this section to start sgmgr service and also create a user which can be used as areplicated user for multi-cluster management For more information about how to create a replicateduser Installing Serviceguard for Linux the traditional way on page 21

8 Restart cluster on first node

For example cmrunnode -n node1Check that the node joins the cluster successfully and if necessary move packages back to the node

9 Repeat steps from 2 to 9 for all the nodes

Rolling upgrade from A1119X to A1210XTo perform the rolling upgrade from A1119X to A1210X

1 Upgrade node 1 to A121000 For more information on how to upgrade to A121000 see Rollingupgrade from 1119X to 121000 on page 34

Offline rolling upgrade from A1118X to A1210XTo perform offline rolling upgrade from A1118X to A1200X

1 First upgrade node 1 to A120000 For more information on how to upgrade to A120000 see Performing offline rolling upgrade from 1118X to 121000 on page 35

2 Then upgrade node 1 to A1200Y For more information on how to upgrade to A1200Y see Rollingupgrade from 1200X to 1210X on page 36

40 Rolling upgrade from A1119X to A1210X

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 41: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Upgrading Serviceguard for Linux packagesYou can use the cmupgrade tool to upgrade the packages from Serviceguard for Linux Advanced MR toServiceguard for Linux Enterprise MR in which case the additional components are installed

Upgrading Serviceguard for Linux packages 41

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 42: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Removing Serviceguard for LinuxTo remove Serviceguard for Linux and its components do one of the following

bull Use cmeasyinstall tool to remove the Serviceguard and its components

cmeasyinstall [-e ltuninstall serviceguardgt] -n ltnodes including execution nodegt [-l ltdo not add sgmgr user as ldap is configured on all the nodesgt]

bull Use traditional way to remove the Serviceguard for Linux and its components

rpm mdashe ltrpmgt

42 Removing Serviceguard for Linux

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 43: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

TroubleshootingCause

The following are list of issues with respective solutions related to Serviceguard Manager installation

1 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

You must create the sgmgr user manually and the password must be same as on the other system Tocreate the sgmgr user manually

a Add the user

useradd sgmgrb Enter the password

passwd sgmgr2 Problem

The sgmgr user is not created during installation of Serviceguard Manager

Solution

For Local user

bull Check if PAM module and x64 bit JRE is installed in your Linux systembull If you do not find the required node in Serviceguard Manager try logging into that node through CLI

using login credentials this will confirm if the login credentials are valid for that node

LDAP user

Check if the user credentials are valid on the nodes where LDAP is configured then ensure that thelogged in credentials are working with LDAP

3 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

a Check the Jetty status

service jetty-sgmgr statusb If not restart the Jetty server

service jetty-sgmgr restart4 Problem

If nodes are not getting detected by Serviceguard Manager or Serviceguard Manager is unable to launchensure that the product is installed and configured completely on those nodes

Solution

Jetty 9

To configure Jetty 9 with custom certificates

a Perform the following tasks

I Generating Key Pairs and CertificateII Requesting a Trusted Certificate

Troubleshooting 43

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 44: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

III Loading Keys and CertificatesIV Configure Serviceguard Manager for Jetty 9

To configure Serviceguard Manager for Jetty 9 follow step bb Edit sslContextFactory object attributes in ltjetty locationgtetcjetty-ssl-sgmgrxml

file

ltNew id=sslContextFactorySgmgrclass=orgeclipsejettyutilsslSslContextFactorygtltSet name=KeyStorePathgtltProperty name=jettybase default= gtltProperty name=jettykeystoredefault=etckeystoregtltSetgtltSet name=KeyStorePasswordgtltProperty name=jettykeystorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgtltSet name=KeyManagerPasswordgtltProperty name=jettykeymanagerpassworddefault=OBF1u2u1wml1z7s1z7a1wnl1u2ggtltSetgtltSet name=TrustStorePathgtltProperty name=jettybase default= gtltProperty name=jettytruststoredefault=etckeystoregtltSetgtltSet name=TrustStorePasswordgtltProperty name=jettytruststorepassworddefault=OBF1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4gtltSetgt

Edit the following attributes of Jetty to make use of the newly generated KeyStore

a KeyStore (Jetty 8) KeyStorePath (Jetty 9)b KeyStorePasswordc KeyManagerPasswordd TrustStore (Jetty 8) TrustStorePath (Jetty 9)e TrustStorePassword

NOTE

The KeyStorePassword can be in plain text obfuscated checksummed or encrypted to increasesecurity To generate password in these formats see httpeclipseorgjettydocumentationcurrentconfiguring-security-secure-passwordshtml

5 Problem

Serviceguard Manager is not accessible on Internet Explorer or if you see an error message on InternetExplorer browser

44 Troubleshooting

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 45: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Figure 1 Error while accessing Serviceguard Manager

Solution

You can either change Internet Explorer settings or configure Jetty with custom certificates

bull If you select to change Internet Explorer settings then follow the procedure outlined in step bbull If you want to configure Jetty with custom certificates see problem 4

NOTE

Before you make any changes ensure that you verify the Jetty server is running To do so see stepa

a Verify whether the Jetty server is running using service jetty-sgmgr status and check if theJetty running pid message is displayed

bull If Jetty running pid message is not displayed start Jetty using service jetty-sgmgrstart and access Serviceguard Manager on Internet Explorer

bull If Jetty running pid message is displayed follow step bb Verify the Internet Exploreramp settings

I Go to the Tools menu click on Internet OptionsII Go to Advanced tabIII Under Secutiry section locate Use TLS optionsIV Check whether these options Use TLS 10 Use TLS 11 and Use TLS 12 are selectedV If the options are not selected then select themVI Click Apply

NOTE

Before you access the Serviceguard Manager on Internet Explorer ensure that at least one ofthese Use TLS 10 and Use TLS 11 is selected

6 Problem

When Serviceguard Manager is launched analytics graph is missing on Node Cluster or Package pageor if you see an error message

Troubleshooting 45

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 46: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Figure 2 Analytics error

Solution

Verify if the current system time on client (where Serviceguard Manager is launched) is in sync with theserver time

When Serviceguard Manager is launched on a client system from dashboard when you go to Cluster orPackage or Node page Analytics graph is not displayed because it takes the current client system time bydefault in To field to create and display the graph If the client system time (selected in To field) is aheadof the server time then the graph is not displayed and an error message is displayed In this case youmust specify a different time range in To field to see the graph

7 Problem

If you get a warning message with cmupgrade as follows

WARNING

Failed to update multicast port to 5301 on ltnode NamegtThe multicast port must be changed to5301 on ltnode Namegt before proceeding with any further operations Log in to $node usingServiceguard Manager GUI to do the same

Solution

Verify the multicast port configured in setting page of the node by logging in Serviceguard Manager GUI assgmgr user edit settings and update the multicast port to 5301

NOTE

You must update the multicast port to 5301 on all the nodes which are required to be managed bythe Serviceguard Manager

You must also ensure that the multicast port must be 5301 on all the nodes and is not used by anyother applications

46 Troubleshooting

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 47: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Related informationThe latest documentation for HPE XP Storage Plug-in for VMware vCenter is available at Hewlett PackardEnterprise Information Library

Available documents include the HPE XP Storage Plug-in for VMware vCenter User Guide

Related information 47

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback
Page 48: HPE Serviceguard for Linux Enterprise edition 12.10.00 ... · Linux ® is the registered ... Cluster heartbeat • hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat • hacl-cfg

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs To help usimprove the documentation send any errors suggestions or comments to Documentation Feedback(docsfeedbackhpecom) When submitting your feedback include the document title part number editionand publication date located on the front cover of the document For online help content include the productname product version help edition and publication date located on the legal notices page

48 Documentation feedback

  • HPE Serviceguard for Linux Enterprise edition 121000 Release Notes
  • Contents
  • Overview
  • Supported platforms and Linux distributions
  • Packaging information
  • Licensing information
    • Obtaining a permanent license
    • Renewing the permanent license
    • Validating the permanent license
      • Compatibility and installation requirements
        • Hardware requirements
        • Port requirements
          • Ports needed for Serviceguard
          • Ports needed for authentication
          • Ports needed by Serviceguard Manager
          • System firewalls
              • Supported browsers
              • Software prerequisites for Serviceguard for Linux
              • Installing Serviceguard for Linux
                • Installing Serviceguard for Linux using cmeasyinstall
                • Installing Serviceguard for Linux the traditional way
                • Installing Serviceguard for Linux Patch
                • Post installation
                  • Rolling software upgrade
                    • Requirements
                    • Limitations of rolling upgrades
                    • Preparation
                    • Rolling upgrade on OS
                    • Supported rolling upgrade paths
                    • Performing rolling upgrades
                      • Rolling upgrade from 1120X to 121000
                        • Upgrading Serviceguard for Linux using cmupgrade tool
                        • Upgrading Serviceguard for Linux the traditional way
                        • Upgrading Serviceguard for Linux using YUM or Zypper
                          • Rolling upgrade from 1119X to 121000
                          • Performing offline rolling upgrade from 1118X to 121000
                          • Rolling upgrade from 1200X to 1210X
                            • Upgrading Serviceguard for Linux using cmupgrade tool
                            • Upgrading Serviceguard for Linux the traditional way
                            • Upgrading Serviceguard for Linux using YUM or Zypper
                              • Rolling upgrade from A1119X to A1210X
                              • Offline rolling upgrade from A1118X to A1210X
                                  • Upgrading Serviceguard for Linux packages
                                  • Removing Serviceguard for Linux
                                  • Troubleshooting
                                  • Related information
                                  • Documentation feedback