Using Serviceguard Extension for RAC, 8th Edition, March 2009

Figure A-6 Running Cluster After Upgrades
Limitations of Rolling Upgrades
The following limitations apply to rolling upgrades:
• During a rolling upgrade, you should issue Serviceguard/SGeRAC 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. Also,
you cannot modify the hardware configuration—including the cluster’s network
configuration—during a 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.
• The new features of the Serviceguard/SGeRAC release may not work until all nodes have
been upgraded.
• Binary configuration files may be incompatible between releases of Serviceguard/SGeRAC.
Do not manually copy configuration files between nodes.
• Within a Serviceguard/SGeRAC cluster, no more than two versions of Serviceguard and
SGeRAC 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 and
SGeRAC within the same cluster. SGeRAC requires the compatible version of Serviceguard.
Upgrade all cluster nodes as quickly as possible to the new release level.
For more information on support, compatibility, and features for SGeRAC, refer to the
Serviceguard and Serviceguard Extension for RAC Compatibility and Feature Matrix, located at
http://docs.hp.com -> High Availability -> Serviceguard Extension for RAC
• You cannot delete Serviceguard/SGeRAC software (via swremove) from a node while the
cluster is in the process of a rolling upgrade.
Rolling Software Upgrades 141