Veritas Volume Manager 5.1 SP1 Release Notes HP-UX 11i v3 (5900-1518, August 2011)

# vxdmpadm gettune dmp_path_age
• VxVM 5.1 SP1 does not support boot disks of capacity greater than 1 TB.
Known Problems And Workarounds
Following are the known problems of VxVM 5.1 SP1 on HP-UX 11i v3:
NOTE: For information on the Known Problems and Workarounds in VxVM 5.0.1 in the HP-UX
11i v3 operating system, see Veritas Volume Manager 5.0.1 Release Notes, HP-UX 11i v3, First
Edition, November 2009. To locate this document, go to the HP-UX Core docs page at:
www.hp.com/go/hpux-core-docs. On this page, select HP-UX 11i v3.
• Problem
The HP-UX native multipath plugin (NMP) driver does not recognize the hardware path that
DMP has selected and selects the standby path for internal I/Os. This causes delays with
VxVM device discovery and other VxVM commands.
Also, VxVM does not support SAN booting with these arrays on HP-UX 11i v3.
The issue occurs when an ALUA array that supports standby Asymmetric Access State (AAS),
such as an LSI ALUA array, is connected to a HP-UX 11i v3 IA-64 (Itanium) machine and disks
are labelled in Extensible Firmware Interface (EFI) format.
Workaround
Set the active path as the preferred path using the scsimgr utility.
• Problem
If a disk was initialized by a previous VxVM version or defined with a smaller private region
than the default of 32 MB, the public region data will be overridden when the disk is initialized
using VxVM 5.1 SP1. For example, using the dgcfgrestore command to restore the VxVM
disk group configuration on a disk which was initialized using a VxVM version prior to VxVM
5.1 SP1.
Workaround
Specify explicitly the length of privoffset, puboffset, publen, and privlen while
initializing the disk.
• Problem
If a path loses connectivity to the array, the path is marked with the NODE_SUSPECT flag.
After the connectivity is restored, the restore daemon detects that the path is restored when
the it probes the paths. The restore daemon clears the NODE_SUSPECT flag and makes the
path available for I/O. The restore daemon probes the paths at the interval set with the tunable
parameter dmp_restore_interval. If you set the dmp_restore_interval parameter
to a high value, the paths are not available for I/O until the next interval.
Workaround
There is no workaround for this issue.
• Problem
VxVM 5.1 SP1 includes several array names that differ from the array names in earlier releases.
Therefore, if you upgrade from an earlier release to VxVM 5.1 SP1, changes in the enclosure
attributes may not remain persistent. Any enclosure attribute set for these arrays may be reset
to the default value after an upgrade to VxVM 5.1 SP1.
Table 6 (page 13) shows the Hitachi arrays that have new array names.
12 Veritas Volume Manager 5.1 SP1 Release Notes