Using Serviceguard Extension for RAC, 4th Edition, February 2007

Serviceguard Configuration for Oracle 9i RAC
Support for HP-UX 11i v3
Chapter 3 117
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.
NOTE Veritas Cluster Volume Manager (CVM) and Cluster File System (CFS)
are not yet supported on HP-UX 11i v3. If you are currently running
CVM or CFS, do not upgrade to Serviceguard Extension for RAC version
A.11.17 on 11i v3 until support for these Veritas products is available.
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 on http://docs.hp.com.
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-11.i 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.