Managing Serviceguard Sixteenth Edition, March 2009

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” (page 327) for instructions in this case. See “About
Device File Names (Device Special Files)” (page 107) 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.
• Rolling upgrades are not intended as a means of using mixed releases of
Serviceguard or HP-UX within the cluster. HP strongly recommends 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 a
rolling upgrade is in progress.
Before You Start
Make sure you plan sufficient system capacity to allow moving the packages from node
to node during the process without an unacceptable loss of performance.
CAUTION: Do not proceed with an upgrade to A.11.19 until you have read and
understood the Special Considerations for Upgrade to Serviceguard A.11.19 (page 407).
Running the Rolling Upgrade
1. Halt the node you want to upgrade. You can do this in Serviceguard Manager, or
use the cmhaltnode command. This will cause the node’s packages to start up
on an adoptive node
2. Edit the /etc/rc.conf.d/cmcluster file to include the following line:
AUTOSTART_CMCLD = 0
410 Software Upgrades