Managing Serviceguard Eighteenth Edition, September 2010

AUTOSTART_CMCLD = 1
7. Restart the cluster on the upgraded node, using Serviceguard Manager or
cmrunnode (1m).
8. Move the packages back to the upgraded node.
9. Verify that the applications are functioning properly.
• If the applications do not function properly and this is not the last node to be
upgraded, you can revert to the previous release on this node. This is called
hot recovery, and it will allow you to keep the node up and running in the
cluster while you upgrade the other nodes, though you will still need to
investigate and solve the problems on this node before the cluster upgrade
can complete. If you decide to perform a hot recovery, proceed as follows:
1. Halt the packages and restart them on another node.
2. Halt the node.
3. Reboot the node from the original root disk (which still contains the
pre-upgrade versions of HP-UX and Serviceguard).
4. Restart the cluster on the node, using Serviceguard Manager or
cmrunnode (1m).
• If the applications do not function properly and this is the last node to be
upgraded, you cannot revert to the previous release on just this node. You
must either solve the problems with this release on this node, or revert the
entire cluster to the previous release by halting the cluster (cmhaltcl),
rebooting each node from its original (pre-upgrade) root disk, and restarting
the cluster (cmruncl).
• If the applications are functioning properly, continue with the next step.
10. Repeat the above steps for each node in the cluster.
If the cluster fails before the rolling upgrade is complete (because of a catastrophic
power failure, for example), you can restart the cluster by running cmruncl (1m) on
a node which has been upgraded to the latest version of the software.
Example of a Rolling Upgrade
NOTE: Warning messages may appear during a rolling upgrade while the node is
determining what version of software is running. This is a normal occurrence and not
a cause for concern.
The following example shows a simple rolling upgrade on two nodes running one
package each, as shown in Figure D-1. (This and the following figures show the starting
point of the upgrade as “SG (old)” and “HP-UX (old)”, with a roll to “SG (new)” and
“HP-UX (new)”. Substitute the actual release numbers of your rolling upgrade path.)
Example of a Rolling Upgrade 455