HP Serviceguard A.11.20- Managing Serviceguard Twentieth Edition, August 2011

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 41. (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.)
Figure 41 Running Cluster Before Rolling Upgrade
Step 1.
Halt the first node, as follows
# cmhaltnode -f node1
This will cause pkg1 to be halted cleanly and moved to node 2. The Serviceguard daemon on
node 1 is halted, and the result is shown in Figure 42.
Example of a Rolling Upgrade 363