HP Serviceguard for Linux Advanced Version 12.00.00 Release Notes, May 2014

cluster needs to be taken offline for hardware maintenance or patch installations. Until the process
of upgrade is complete on all nodes, you cannot change the cluster configuration files, and you
will not be able to use any of the features of the new Serviceguard release.
NOTE: Starting Serviceguard 12.00.00, legacy packages are obsolete. If you have configured
legacy packages, you need to migrate to modular packages before you move to 12.00.00. For
more information about how to migrate to modular packages, see the white paper Migrating
packages from legacy to modular style available at http://www.hp.com/go/linux-serviceguard-docs.
7.1 Requirements
CAUTION:
• Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A.12.00.00.
• If you are using an alternate address, then you must upgrade the Quorum Server to version
A.12.00.00 before you proceed. For more information, see HP Serviceguard Quorum Server
Version A.12.00.00 Release Notes available at http://www.hp.com/go/hpux-SG-QS-docs.
To upgrade a Linux Serviceguard node to a newer Serviceguard release, you need to ensure of
the following:
• The node must be running with a supported version of Linux (Red Hat Enterprise Linux 5.x,
Red Hat Enterprise Linux 6.x, and SUSE Linux Enterprise Server 11)
• The node must be running a supported release of Serviceguard.
NOTE: If the target version of Serviceguard does not support the version of the operating system
currently on the node, then you must upgrade the operating system before upgrading Serviceguard.
• The OS upgrade for the node must be from and to the same Linux distribution (For example,
Red Hat Enterprise Linux 4 to Red Hat Enterprise Linux 5, not Red Hat Enterprise Linux 5 to
SUSE Linux Enterprise Server 11).
• All members of the cluster must be upgraded to the same version of OS and the Serviceguard.
• Ensure that all applications that run on the current OS is also supported with the new OS.
• Verify that the new OS supports the current cluster hardware configuration and drivers (network
interfaces, bonding driver, and shared disk storage).
NOTE: If there is no HP bonding driver for the Linux version you are using, use the bonding
driver supplied with the Linux distribution.
• Do a full back up on each node.
NOTE: HP recommends you to use the rolling upgrade process which:
• Helps you upgrade to the latest software version.
• Preserves the current OS and cluster configuration.
• Keeps running your mission-critical applications.
Before you upgrade, ensure that you read the “Limitations of rolling upgrades” and complete the
entire upgrade process before you can use any Serviceguard commands.
CAUTION: If a failure occurs on one node while you are upgrading another, packages — and
the applications they contain — may not be able to fail over to the node being upgraded.
7 Rolling software upgrade 15