HP Serviceguard for Linux Version A.11.19 Release Notes, October 2009

and finished upgrading the node to the new cluster manager (Cluster Membership
Protocol version 2), and then, once all nodes have been upgraded, you will see
a message indicating that the new cluster has formed. Watch for three messages similar
to the following (for clarity, intervening messages have been replaced with ellipses
[...]):
Nov 14 13:52:46 bbq1 cmcld[20319]: Starting to upgrade this node to Cluster Membership Protocol
version 2
[....]
Nov 14 13:52:46 bbq1 cmcld[20319]: Finished upgrading this node to Cluster Membership Protocol version
2
[....]
Nov 14 13:52:47 bbq1 cmcld[20319]: Membership: membership at 3 is FORMED (coordinator 1) includes:
1 3 2 4 excludes
When you see the Membership: message, and specifically the capitalized word FORMED
in this message, the transition to the new cluster manager is complete and you can use
all the Serviceguard commands.
Limitations
The following limitations apply to rolling upgrades:
• During rolling upgrade, you should 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 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 (cmclconfd) 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.
Rolling Software Upgrades 51