HP Serviceguard Version A.11.19 Release Notes, July 2009

Table Of Contents
Support for Veritas 5.0 on HP-UX 11i v2 and 11i v3
Serviceguard A.11.19 supports versions 4.1 and 5.0 of Veritas VxVM from Symantec,
and version 5.0 (only) of CVM and CFS, on both HP-UX 11i v2 and 11i v3.
IMPORTANT: For the most up-to-date information about supported versions, check
the Serviceguard/SGeRAC/SMS/Serviceguard Manager Plug-in Compatibility and Feature
Matrix, at the address given under “Compatibility Information and Installation
Requirements” (page 49).
Serviceguard with Storage Management Suite version A.02.01 supports a maximum
of sixteen nodes for CVM and CFS.
HP Serviceguard Storage Management Suite Version A.02.00 and later bundles that
include CFS support CFS 5.0 nested mounts, up to a maximum of four levels of nesting.
This feature is enabled by default; to disable it, add the following line to /etc/
cmcluster.conf:
SGCFS_NESTED_MOUNT_SUPPORT=disabled
For more information, see the HP Serviceguard Storage Management Suite A.02.01 Release
Notes at docs.hp.com -> High Availability -> HP Serviceguard Storage
Management Suite.
IMPORTANT: For information about required patches, see the HP Serviceguard Storage
Management Suite Release Notes for your version of the Storage Management Suite.
Serviceguard NFS Toolkit supports CFS 5.0. See the white paper Serviceguard NFS
Toolkit Support for CFS available from docs.hp.com -> High Availability under
Highly Available NFS -> White Papers.
Features First Introduced Before Serviceguard A.11.18
About Device Special Files (DSFs)
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.
Features Introduced Before A.11.19 43