Managing Serviceguard 12th Edition, March 2006

Rolling Software Upgrades
Limitations of Rolling Upgrades
Appendix E442
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.
• 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.
• Rolling upgrades are not intended as a means of using mixed
releases of Serviceguard or HP-UX 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 swremove) from a node
while the cluster is in the process of rolling upgrade.