HP Serviceguard Storage Management Suite A.03.01 Release Notes

NOTE: If a newly installed bundle includes the same version of a product that was previously
installed and patched, the patches may need to be installed again.
NOTE: If there is a cluster configured on a node, the swremove command will not let you remove
SG SMS from that node. You must halt the node, remove the node from the cluster, and then use
swremove to remove SG SMS.
NOTE: The procedure for rolling or offline upgrades of SG SMS HAOE or DCOE bundles requires
additional steps. See “HP-UX Operating Environment Upgrade Limitations” (page 44) for more
information.
Disabling Cluster Auto-Start on Reboot
Before attempting a SG SMS bundle installation or upgrade, you must disable AUTOSTART_CMCLD.
To disable AUTOSTART_CMCLD on all cluster nodes, access the/etc/rc.cofig.d/cmcluster
file and set AUTOSTART_CMCLD to 0, (AUTOSTART_CMCLD=0).
To re-enable Automatic startup (AUTOSTART_CMCLD) after completing your SG SMS bundle
installation or upgrade, set the flag AUTOSTART_CMCLD to 1 in the /etc/rc.config.d/
cmcluster file (AUTOSTART_CMCLD=1)
For more information on AUTOSTART_CMCLD, see the Setting up Autostart Features and Performing
a Rolling Upgrade sections in Managing Serviceguard, Eighteenth Edition, available at
www.hp.com/go/hpux-serviceguard-docs → HP Serviceguard
Cluster Offline Upgrade Option for SG SMS Bundles Containing CVM/CFS
To upgrade a SG SMS CFS bundle (T2775xx, T2776xx, or T2777xx) where the supported upgrade
path in Table 6 (page 21) indicates an offline upgrade is required, there is a procedure that may
work with your configuration to minimize the time that the entire cluster is offline. This is
accomplished by performing an offline upgrade on half of the cluster nodes while the other half
of the cluster nodes remain online.
NOTE: This cluster offline upgrade option is supported for uprades to SG SMS version A.03.01
only from SG SMS versions containing Serviceguard 11.19 (SG SMS versions A.02.01, A.02.01.01
and A.03.00).
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. You might benefit from using
Dynamic Root Disk (DRD) utilities to perform your uprade, if your upgrade is supported with DRD.
See “Using Dynamic Root Disk Utilities (DRD) to upgrade to SG SMS A.03.01” (page 24) for more
information.
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.
Compatibility Information and Installation Requirements 23