Managing Serviceguard 14th Edition, June 2007

Software Upgrades
Performing a Rolling Upgrade
Appendix E466
Performing a Rolling Upgrade
Limitations of Rolling Upgrades
The following limitations apply to rolling upgrades:
• During a 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 hardware configuration—including the
cluster’s network configuration—during rolling upgrade.
• You cannot modify the cluster or package configuration until the
upgrade is complete.
If you need to modify the configuration (for example, to take
advantage of new features), upgrade all nodes to the new release,
then modify the configuration file and copy it to all the nodes.
NOTE This means that you cannot migrate to the HP-UX 11i v3 agile
addressing scheme for device files during a rolling upgrade if cluster
lock disks are used as a tie-breaker, because that involves changing
the cluster configuration. See “Updating the Cluster Lock
Configuration” on page 348 for instructions in this case. See “About
Device File Names (Device Special Files)” on page 111 for more
information about agile addressing.
• 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.
• No more than two versions of Serviceguard can be running in the
cluster while the rolling upgrade is in progress.