 |
| |
|
 | 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 E-1 “Running
Cluster Before Rolling Upgrade ”. (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.)
Step
2. |
|
Upgrade node 1 to the next operating system release (“HP-UX (new)”), and
install the next version of Serviceguard (“SG (new)”).
Step
3. |
|
When upgrading is finished, enter the following command on node 1 to restart the cluster on node 1.
At this point, different versions of the Serviceguard daemon
(cmcld) are running on the two nodes, as shown in Figure E-4 “Node
1 Rejoining the Cluster ”.
Step
4. |
|
Repeat the process on node 2. Halt the node, as follows:
This causes both packages to move to node 1. Then upgrade node 2 to the new versions of HP-UX and Serviceguard.
Step
5. |
|
Move pkg2 back to its original node. Use the following commands:
# cmhaltpkg pkg2
# cmrunpkg -n node2 pkg2
# cmmodpkg -e pkg2 |
The cmmodpkg command re-enables switching of the package, which was disabled
by the cmhaltpkg command. The final running cluster is shown in Figure E-6 “Running
Cluster After Upgrades ”.
Printable version
