Serviceguard Extension for RAC Version A.11.20 Release Notes, April 2011
Table Of Contents
- Serviceguard Extension for RAC Version A.11.20 Release Notes
- Contents
- 1 Serviceguard Extension for RAC Version A.11.20 Release Notes
- Announcements
- What’s in this Version
- Support for Logical Volume Manager Version 2.0 and later
- Support for Multi-Node Online Configuration (MORE)—LVM Version 2.1 Volume Groups Only
- Support for Cluster Interconnect Subnet Monitoring
- Support for Veritas CFS and CVM Versions 5.0, 5.0.1 and 5.1 SP1
- Support for Oracle 10gR2 RAC with SLVM, ASM, CFS, and CVM
- Support for Oracle 11gR1 RAC with SLVM, ASM, CFS, and CVM
- Support for Oracle 11gR2 RAC with SLVM, ASM, and CFS
- Support for Serviceguard A.11.20 Cluster Verification
- Support for the SGeRAC Toolkit
- GMS authorization
- Upgrade Using DRD
- Documentation for this Version
- Support Information
- Compatibility Information and Installation
- Serviceguard Extension for RAC Compatibility with HP-UX and Oracle Releases
- Port Requirements
- Installing Serviceguard Extension for RAC
- Adding Serviceguard Extension for RAC to an Existing Cluster
- Performing a Rolling Upgrade Using DRD
- Performing a Non-Rolling Upgrade Using DRD
- Removing SGeRAC
- Removing Serviceguard Extension for RAC without Removing Serviceguard
- Troubleshooting Tips
- Patches and Fixes in this Version
- Known Problems
- Types of Releases and Patches
- Software Availability in Native Languages

Performing a Rolling Upgrade Using DRD
CAUTION: See the limitations listed in Appendix A of Using Serviceguard Extension for RAC. In
addition, there are special conditions that apply to upgrading a system to Serviceguard A.11.20.
You should read the entire section on “Rolling Software Upgrades” in Appendix A of Using
Serviceguard Extension for RAC, and the HP Serviceguard Version A.11.20 Release Notes.
Limitations of Rolling Upgrades using DRD
CAUTION: Stricter limitations apply to an upgrade to A.11.20. Do not proceed with an upgrade
to A.11.20 until you have read and understood the “Special Considerations for Upgrade to
Serviceguard A.11.20” in Appendix D of the latest version of Managing Serviceguard.
IMPORTANT: Not all paths that are supported for upgrade are supported for an upgrade using
DRD, and there are additional requirements and restrictions for paths that are supported.
Do not proceed until you have read the “Announcements”, “Compatibility”, and “Installing
Serviceguard” sections of the latest version of the Serviceguard release notes and the corresponding
sections of these SGeRAC release notes. Make sure your cluster meets the current requirements,
and take any necessary preparation steps as instructed in the release notes.
You must also make sure you have read and understood the “Restrictions for DRD Upgrades” (page
15).
In addition, all the limitations for rolling upgrades listed in Appendix A of Using Serviceguard
Extension for RAC also apply to rolling upgrades using DRD. You should also read the section on
“Rolling Software Upgrades” in that appendix before you proceed.
Before You Start
IMPORTANT: If you need to upgrade Oracle software, a non-rolling upgrade may be required.
Consult the Oracle documentation.
• Make sure you plan sufficient system capacity to allow moving the packages from node to
node during the process without an unacceptable loss of performance.
• Make sure you have read and understood the “Restrictions for DRD Upgrades” (page 15),
and that your cluster meets the prerequisites.
• Make sure that you have downloaded the latest DRD software and are thoroughly familiar
with the DRD documentation. See “Rolling Upgrade Using DRD” (page 14) for more information.
• There are some restrictions on where the install depot can reside. Make sure you will be
upgrading the clone disk from a supported location. See “Restrictions for DRD Upgrades”
(page 15).
Running the Rolling Upgrade
1. On the node you want to upgrade, edit /etc/rc.config.d/cmcluster to include the
following line:
AUTOSTART_CMCLD = 0
This value will be replicated on the clone root disk and will keep the upgraded node from
automatically rejoining the cluster when it reboots.
2. Create a clone root disk for the node you want to upgrade.
3. Upgrade the clone disk to the new HP-UX release (if necessary), including Serviceguard (using
drd runcmd update-ux), or upgrade Serviceguard alone (using drd runcmd
swinstall).
18 Serviceguard Extension for RAC Version A.11.20 Release Notes