Using Serviceguard Extension for RAC, 6th Edition, April 2008

• “Rolling Software Upgrades”
— “Steps for Rolling Upgrades ”
— “Example of Rolling Upgrade ”
— “Limitations of Rolling Upgrades ”
• “Non-Rolling Software Upgrades”
— “Steps for Non-Rolling Upgrades ”
— “Limitations of Non-Rolling Upgrades ”
• “Migrating a SGeRAC Cluster with Cold Install”
Rolling Software Upgrades
SGeRAC version A.11.15 and later allow you to roll forward to any higher revision
provided all of the following conditions are met:
• The upgrade must be done on systems of the same architecture (HP 9000 or Integrity
Servers).
• All nodes in the cluster must be running on the same version of HP-UX.
• Each node must be running a version of HP-UX that supports the new SGeRAC
version.
• Each node must be running a version of Serviceguard that supports the new
SGeRAC version.
For more information on support, compatibility, and features for SGeRAC, refer to the
Serviceguard Compatibility and Feature Matrix, located at http://docs.hp.com -> High
Availability -> Serviceguard Extension for RAC.
Steps for Rolling Upgrades
Use the following steps when performing a rolling SGeRAC software upgrade:
1. Halt Oracle (RAC, CRS, Clusterware, OPS) software on the local node (if running).
2. Halt Serviceguard/SGeRAC on the local node by issuing the Serviceguard
cmhaltnodecommand.
3. Edit the /etc/rc.config.d/cmcluster file to include the following line:
AUTOSTART_CMCLD = 0
4. Upgrade the node to the new Serviceguard and SGeRAC release. (SGeRAC requires
the compatible version of Serviceguard.)
5. Edit the /etc/rc.config.d/cmcluster file, on the local node, to include the
following line:
AUTOSTART_CMCLD = 1
168 Software Upgrades