HP Serviceguard Storage Management Suite Version A.02.01 for HP-UX 11iv3 Release Notes, Edition 2 (May 2010)

This cluster offline upgrade procedure considers the upgrade of SG SMS only. You need to take
responsibility for applications that run in the SG SMS cluster you plan to upgrade. Before starting
this procedure, make certain your computing environment and the applications running on top
of SG SMS in the cluster can accommodate being offline temporarily.
Offline Upgrade Procedure:
Divide the cluster nodes into two groups. For purposes of explanation, we will refer to these
groups of nodes as Group A and Group B. In explaining this procedure we assume groups of
equal size will be the most efficient approach. It is not necessary to divide the cluster nodes into
groups of equal size, if some other arrangement will work better in your computing environment.
• If the cluster has an even number of nodes, assign half of the nodes to Group A and the
other half to Group B.
• If the cluster has an odd number of nodes, subtract one node from the total number of nodes,
divide that number in half, then assign the resulting number of nodes to Group A. Assign
the remaining, larger group of nodes to Group B. For example, if the cluster contains 9 nodes,
assign (9 - 1)/2 = 4 nodes to Group A, and assign the remaining 5 nodes to Group B.
We will use a 3 node cluster as an example for explaining this offline upgrade procedure. For a
3 node cluster, Group A will contain Node 1, and Group B will contain Node 2 and Node 3.
NOTE: Steps 1, and 2 in this procedure can be performed on multiple nodes in parallel, or on
one node at a time, before continuing to step 3.
1. Move all application failover packages that can be moved from Group A nodes, to Group
B nodes.
2. Halt the Group A cluster nodes and upgrade them to the new SMS version:
a. Node 1 > cmhaltnode –f node1
b. Perform an offline upgrade of the Group A nodes (Node 1 in this example).
3. Gracefully halt application packages running on Group B nodes, before halting the cluster
on the Group B nodes.
4. Halt the cluster on the Group B nodes:
a. Node 2 or Node 3> cmhaltcl -f
5. Start the cluster on the Group A cluster nodes (these are the nodes where the SG SMS version
has already been upgraded):
a. Node 1 > cmruncl –f –n node1
NOTE: Steps 6, 7, and 8 in this procedure can be performed on multiple nodes in parallel,
or on one node at a time, before continuing to step 9.
6. Perform an offline upgrade of the Group B nodes (Node 2 and Node 3) to SG SMS version
A.03.00 (the same SG SMS version that the Group A nodes were upgraded to).
7. Re-join the Group B nodes to the cluster, one at a time:
a. Node 2 > cmrunnode node2
b. Node 3 > cmrunnode node3
8. Redistribute the application failover packages over ALL of the active cluster nodes (Group
A and Group B nodes).
9. Optional steps must be performed on the CVM master/CFS primary nodes to upgrade to
the new CVM and CFS protocol/layout versions (refer to the VxVM and VxFS Administrators
Guides for details):
• vxdctl upgrade to upgrade CVM protocol version
• vxdg upgrade <diskgroup> to upgrade disk group version
• vxupgrade <mountpoint> to upgrade to new file system layout version
28 HP Serviceguard Storage Management Suite Version A.02.01 for HP-UX 11i v3 Release Notes