HP Serviceguard A.11.20.10 for Linux Release Notes, December 2012

fail, logging a “Permission denied for user” message. This situation can arise when the

Serviceguard remote security file, $SGCONF/cmclnodelist, is not used and remote node security

is resolved by means of .rhosts.

NOTE: /etc/cmcluster.conf contains the mappings that resolve the symbolic references to

$SGCONF, $SGROOT, and so on, used in these Release Notes. See Understanding the Location of

Serviceguard Files in Chapter 5 of the Managing HP Serviceguard for Linux manual for details.

For more information about configuring security for prospective cluster nodes, and for an existing

cluster, see Chapter 5 of Managing HP Serviceguard for Linux.

Rolling software upgrades

You can upgrade the Linux operating system and the Serviceguard software one node at a time

without bringing down your clusters. This process can also be used any time when a node in the

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: For Red Hat Linux, rolling upgrade is allowed from A.11.19 to 11.20.10, but you must

first install the A.11.20.00 version and then install the patch.

For SUSE Linux you can directly perform rolling upgrade from A.11.19 to A.11.20.10.

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 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 33).

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).