HP Serviceguard for Linux Version A.11.16 Release Notes, Third Edition, August 2006

Serviceguard for Linux Version A.11.16 Release Notes
Compatibility Information and Installation Requirements
Chapter 1 43
Limitations of Rolling Upgrades
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.
• You can perform a rolling upgrade only on a configuration that has
not been modified since the last time the cluster was started. 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.
• Finally, 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.