HP Serviceguard Version A.11.19 Release Notes, March 2009

Support for Veritas 5.0 on HP-UX 11i v2 and 11i v3
Serviceguard A.11.19 supports Veritas VxVM, CVM and CFS 5.0 from Symantec, on
both HP-UX 11i v2 and 11i v3, with the following exception:
• Serviceguard supports a maximum of eight nodes for CVM and CFS per site, up
to a maximum of sixteen nodes across two sites.
Serviceguard sites can be configured (via the SITE_NAME and SITE parameters)
only in a site-aware disaster-tolerant cluster, which requires additional software;
see the documents listed under “About Cross-Subnet Configurations” (page 33)
for more information.
If you are not configuring a site-aware disaster-tolerant cluster, you can configure
a maximum of eight CVM/CFS nodes per Serviceguard cluster.
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.
What’s in this Release 39