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

7.2 Limitations of rolling upgrades

• 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 of commands on yet to be upgraded nodes in the cluster will result in failure or inconsistent

execution.

• You cannot modify the cluster or package configuration until the upgrade is complete. You

cannot modify the hardware configuration—including the cluster’s network

configuration—during rolling upgrade. This means that you must upgrade all nodes to the

new release before you can modify the configuration file and copy it to all nodes.

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

been upgraded.

• Binary configuration files may be incompatible between releases of Serviceguard. Do not

manually copy configuration files between nodes. The Serviceguard binary configuration file

(cmclconfig) must be in the correct directory or the cluster will not behave properly.

• Within a Serviceguard cluster, no more than two versions of Serviceguard can be running

while the rolling upgrade is in progress.

• All nodes must be running the same releases of Linux and Serviceguard before the upgrade.

• 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 new release level.

• You cannot delete Serviceguard software (via rpm -e) from a node while the cluster is in the

process of rolling upgrade.

• This procedure depends on the upgrade or re-install keeping the same device naming

convention and general system configuration. It is possible for devices to change names or

be changed in the scan order in a way that cannot be corrected. If this happens, the cluster

will need to be re-created rather than to be upgraded.

• Sgmgr does not detect the rolling upgrade status of that cluster, hence you must use sgmgr

after rolling upgrade is complete. Sgmgr assumes that the cluster is not under rolling upgrade.

7.3 Preparation

IMPORTANT: Ensure that there is a supported upgrade path from your current Linux and

Serviceguard versions to the new versions. For more information, see the latest version of HP

Serviceguard for Linux Certification Matrix available at http://www.hp.com/info/sglx..

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

OS (cold install).

CAUTION: No package can be in maintenance mode, whether it is running or not, when you

perform an upgrade from Serviceguard A.11.19 to any later version, including an upgrade from

the initial release of A.11.19 to the July 2009 or later patch.

This means that:

• You must ensure that no packages are in maintenance mode when you start the upgrade.

• You must not put any package in maintenance mode until all the nodes are upgraded.

Breaking this rule will leave the cluster in an inconsistent state. To recover, you must halt the cluster

and then upgrade all the nodes.

For more information, see “Maintaining a Package: Maintenance Mode” section in the Managing

HP Serviceguard for Linux A.12.00.00 manual.