Serviceguard Extension for RAC Version A.11.17 Release Notes, February 2007
Serviceguard Extension for RAC Version A.11.17 Release Notes
What’s in this Version
Chapter 1 11
HP-UX 11i v3 Operating System Application Release
The A.11.17.01 version of Serviceguard Extension for RAC is a release
that supports the use of the HP-UX 11i v3 Operating System and
provides the following new functionality, features and restrictions:
• SGeRAC supports HP-UX agile addressing, sometimes also called
persistent LUN binding, for device special files (DSFs)
See “About Device Special Files”
• Veritas CVM and CFS Not Yet Supported
• Multipathing, Veritas DMP and Related Features
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.
CAUTION You cannot migrate to the agile addressing scheme during a rolling
upgrade if you are using cluster lock disks as a tie-breaker, because that
involves changing the cluster configuration. But under certain
conditions, you can migrate the cluster lock device file names to the new