HP Serviceguard Storage Management Suite A.03.02 Release Notes (March 2012)

Table 6 Supported SG SMS Bundle Upgrade Paths - HP-UX 11i v2 and HP-UX 11i v3 (continued)
A.03.01or
A.03.02
A.03.00A.02.01 or
A.02.01.01
A.02.00A.02.00A.01.01A.01.00SG SMS
Version
11i v311i v311i v311i v311i v211i v211i v2HP-UX
Version
A.11.20A.11.19A.11.19A.11.18A.11.18A.11.18A.11.17Serviceguard
Version
5.0.15.0.15.05.05.04.14.1Veritas SF
Version
T8687DBR
→
T8687DBO
→
T8687CBR
→
T8687CB
4
HAOE w/
SG SMS
CFS RAC
T8694DBR
→
T8694DBR
→
T8694CBR
→
T8694CB
5
DCOE w/
SG SMS
Oracle
Prem
T8695DBR
→
T8695DBO
→
T8695CBR
→
T8695CB
5
DCOE w/
SG SMS
CFS
T8696DBR
→
T8696DBO
→
T8696CBR
→
T8696CB
5
DCOE w/
SG SMS
CFS Oracle
T8697DBR
→
T8697DBO
→
T8697CBR
→
T8697CB
5
DCOE w/
SG SMS
CFS RAC
1
The T2772xx bundle is no longer available, starting with the SG SMS version A.02.01 release. Use the T2774CB or
T2774DB bundle instead.
2
The T2776xx bundle is no longer available as a "stand-alone" bundle starting with the SG SMS version A.02.01 release,
except when it is included as a component of the T8686xx HAOE bundle, or the T8696xx DCOE bundle. Use the
T2777CB or T2777DB bundle instead.
3
Within a bundle family, you can upgrade any of the MCOE bundle versions to the DCOE bundle for HP-UX 11i v3,
without removing the MCOE bundle.
4
This is the initial release for the HAOE bundles.
5
This is the initial release for the DCOE bundles.
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 45) 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)
Compatibility Information and Installation Requirements 23