HP Serviceguard A.11.20.20 for Linux Release Notes, May 2013
6.8.1 Requirements
CAUTION:
• Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A.11.20.10.
• If you are using a Quorum Server, make sure you read the latest version of HP Serviceguard
Quorum Server A.04.00.01 Release Notes available at http://www.hp.com/go/
hpux-serviceguard-docs—>HP Serviceguard Quorum Server Software.
If you are using an alternate address, then you must upgrade the Quorum Server to version
A.04.00 before you proceed. For more information about this, see “Quorum server upgrade
required if you are using an alternate address” (page 31).
To upgrade a Linux Serviceguard node to a newer Serviceguard release, you need to make sure
of the following:
• The node must be running with a supported version of Linux (Red Hat Enterprise Linux 5.0,
Red Hat Enterprise Linux 6.0, SUSE Linux Enterprise Server 11 and so on)
• 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.
• Make sure 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 backup on each node.
NOTE: HP recommends you use the rolling upgrade process if possible, because it keeps your
mission-critical applications running; and also that you update the software (rather than do a cold
install) if possible, because updating preserves the current OS and cluster configuration. But make
sure you read the “Limitations of rolling upgrades” (page 20) before you start the upgrade. The
entire upgrade process must be completed successfully 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.
6.9 Limitations of rolling upgrades
• During rolling upgrade, you must issue Serviceguard commands (other than cmrunnode and
cmhaltnode) only on a node containing the latest revision of the software. Performing tasks
on a node containing an earlier revision of the software will not work or will cause inconsistent
results.
• You cannot modify the cluster or package configuration until the upgrade is complete. You
cannot modify the hardware configuration—including the cluster’s network
20