Using Serviceguard Extension for RAC, 8th Edition, March 2009

multiple nodes by applications which can manage read/write access contention, such as Oracle
Real Application Cluster (RAC).
NOTE: CVM (and CFS - Cluster File System) are supported on some, but not all, current releases
of HP-UX. See the latest release notes for your version of Serviceguard at
http://www.docs.hp.com -> High Availability - > Serviceguard.
Veritas Storage Management Products
Veritas Volume Manager (VxVM) 3.5 is not supported on HP-UX 11i v3. If you are running
VxVM 3.5 as part of HP-UX (VxVM-Base), version 3.5 will be upgraded to version 4.1 when you
upgrade to HP-UX 11i v3.
About Multipathing
Multipathing is automatically configured in HP-UX 11i v3 (this is often called native
multipathing), or in some cases can be configured with third-party software such as EMC
Powerpath.
NOTE: 4.1 and later versions of Veritas Volume Manager (VxVM) and Dynamic Multipathing
(DMP) from Symantec are supported on HP-UX 11i v3, but do not provide multipathing and load
balancing; DMP acts as a pass-through driver, allowing multipathing and load balancing to be
controlled by the HP-UX I/O subsystem instead.
For more information about multipathing in HP-UX 11i v3, see the white paper HP-UX 11i v3
Native Multipathing for Mass Storage, and the Logical Volume Management volume of the HP-UX
System Administrator’s Guide in the HP-UX 11i v3 Operating Environments collection at
http://docs.hp.com. See also, About Device File Names (Device Special Files)” on page 57.
About Device Special Files
HP-UX releases up to and including 11i v2 use a naming convention for device files that encodes
their hardware path. For example, a device file named /dev/dsk/c3t15d0 would indicate
SCSI controller instance 3, SCSI target 15, and SCSI LUN 0. HP-UX 11i v3 introduces a new
nomenclature for device files, known as agile addressing (sometimes also called persistent LUN
binding). Under the agile addressing convention, the hardware path name is no longer encoded
in a storage device’s name; instead, each device file name reflects a unique instance number, for
example /dev/[r]disk/disk3, that does not need to change when the hardware path does.
Agile addressing is the default on new 11i v3 installations, but the I/O subsystem still recognizes
the pre-11i v3 nomenclature. This means that you are not required to migrate to agile addressing
when you upgrade to 11i v3, though you should seriously consider its advantages. It is possible,
though not a best practice, to have legacy DSFs on some nodes and agile addressing on others;
this allows you to migrate the names on different nodes at different times, if necessary.
Support for the SGeRAC Toolkit
The SGeRAC Toolkit provides documentation and scripts to simplify the integration of SGeRAC
and the Oracle 10g R2/11g R1 RAC stack. It also manages the dependency between Oracle
Clusterware and Oracle RAC instances with a full range of storage management options supported
in the Serviceguard/SGeRAC environment. The framework provided by the SGeRAC toolkit is
unique in the high level of multi-vendor (Oracle, Symantec, HP) and multi-storage platform
(CFS, CVM, SLVM, ASM over SLVM) integration it offers (on HP-UX releases that support Veritas
CFS and CVM; see “About Veritas CFS and CVM from Symantec” (page 18)).
The SGeRAC Toolkit uses multi-node packages and package dependency features to provide a
uniform, intuitive, and easy-to-manage method to co-ordinate between SGeRAC and Oracle
Clusterware.
Veritas Storage Management Products 35