Veritas Volume Manager 5.0.1 Administrator's Guide, HP-UX 11i v3, First Edition, November 2009

Re-including support for an excluded disk array library
To re-include support for an excluded disk array library
◆
If you have excluded support for all arrays that depend on a particular disk
array library, you can use the includearray keyword to remove the entry
from the exclude list, as shown in the following example:
# vxddladm includearray libname=libvxenc.sl
Listing excluded disk arrays
To list all disk arrays that are currently excluded from use by VxVM
◆
Type the following command:
# vxddladm listexclude
Listing supported disks in the DISKS category
To list disks that are supported in the DISKS (JBOD) category
◆
Type the following command:
# vxddladm listjbod
Adding unsupported disk arrays to the DISKS category
Disk arrays should be added as JBOD devices if no ASL is available for the array.
JBODs are assumed to be Active/Active (A/A) unless otherwise specified. If a
suitable ASL is not available, an A/A-A, A/P or A/PF array must be claimed as an
Active/Passive (A/P) JBOD to prevent path delays and I/O failures. If a JBOD is
ALUA-compliant, it is added as an ALUA array.
See “How DMP works” on page 137.
Warning: The procedure in this section ensures that Dynamic Multipathing (DMP)
is set up correctly on an array that is not supported by Veritas Volume Manager.
If the native multipathing in HP-UX 11i v3 does not recognize such an array as
being multipathed, Veritas Volume Manager treats the independent legacy paths
to the disks as separate devices, which can result in data corruption.
Administering disks
Discovering and configuring newly added disk devices
92