Serviceguard Extension for RAC Version A.11.20 Release Notes, April 2011

RAC Toolkit with Oracle RAC 10g Release 2 or later, at the address given above, and the SGeRAC
Toolkit README. The contents of the README has been moved to the Using Serviceguard Extension
for RAC user guide (published March 2011 or later). Go to www.hp.com/go/
hpux-serviceguard-docs, and then click HP Serviceguard Extension for RAC.
NOTE: This feature is distinct from Serviceguard's package maintenance mode, described in the
latest version of the Managing Serviceguard manual that is available at www.hp.com/go/
hpux-serviceguard-docs —> HP Serviceguard —> User guide.
Support for ASM DG Packages
If you are using ASM over SLVM in a Metrocluster environment or in a non-Metrocluster environment,
this feature allows you to decouple the ASM disk groups from your OC package and provides
flexibility to maintain your ASM disk groups independently.
For more information on how to configure and use the ASM DG package, see the README file
included with the SGeRAC Toolkit. The contents of the README has been moved to the Using
Serviceguard Extension for RAC user guide (published March 2011 or later). Go to www.hp.com/
go/hpux-serviceguard-docs, and then click HP Serviceguard Extension for RAC.
GMS authorization
GMS prevents unauthorized users from accessing cluster information and registering or de-registering
group memberships. GMS authorization is disabled by default—use the GMS_USER[] parameter
in /etc/opt/nmapi/nmutils.conf to configure it.
Upgrade Using DRD
DRD stands for Dynamic Root Disk. Using a Dynamic Root Disk on HP-UX 11i v3 allows you to
perform the update on a clone of the root disk, then halt the node and reboot it from the updated
clone root disk.
You can obtain the DRD software free from software.hp.com—search for DynRootDisk. For
more information, go to www.hp.com/go/drd.
IMPORTANT: Use the clone disk only on the system on which it was created. At present,
Serviceguard does not support booting from a clone disk made on another system (sometimes
referred to as DRD re-hosting).
Rolling Upgrade Using DRD
A rolling upgrade using DRD is like a rolling upgrade, but it is even less disruptive because each
node is down for a shorter time. It is also very safe—if something goes wrong, you can roll back
to the original (pre-upgrade) state by rebooting from the original disk.
This method is the least disruptive, but you need to make sure your cluster is eligible, see “Restrictions
for DRD Upgrades” in the HP Serviceguard Version A.11.20 Release Notes at www.hp.com/go/
hpux-serviceguard-docs —> HP Serviceguard —> Getting started.
If, after reading and understanding the restrictions, you decide to perform a rolling upgrade using
DRD, follow the instructions under “Performing a Rolling Upgrade Using DRD” (page 18).
Non-Rolling Upgrade Using DRD
In a non-rolling upgrade with DRD, you clone each node's root disk and apply the upgrade to the
clone, halt the cluster, and then reboot each node from its updated clone root disk.
This method involves much less cluster down time than a conventional non-rolling upgrade, and is
particularly safe because the nodes can be quickly rolled back to their original (pre-upgrade) root
disks. But you must make sure your cluster is eligible. See “Restrictions for DRD Upgrades” (page
15).
14 Serviceguard Extension for RAC Version A.11.20 Release Notes