Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)
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 141.
Warning: The procedure in this section ensures that Dynamic Multi-Pathing (DMP)
is set up correctly on an array that is not supported by Veritas Volume Manager.
If the native multi-pathing 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.
To add an unsupported disk array to the DISKS category
1
Use the following command to identify the vendor ID and product ID of the
disks in the array:
# /etc/vx/diag.d/vxscsiinq device_name
where device_name is the device name of one of the disks in the array. Note
the values of the vendor ID (VID) and product ID (PID) in the output from this
command. For Fujitsu disks, also note the number of characters in the serial
number that is displayed.
The following example shows the output for the example disk with the device
name /dev/rdsk/c1t20d0
# /etc/vx/diag.d/vxscsiinq /dev/rdsk/c1t20d0
Vendor id (VID) : SEAGATE
Product id (PID) : ST318404LSUN18G
Revision : 8507
Serial Number : 0025T0LA3H
In this example, the vendor ID is SEAGATE and the product ID is
ST318404LSUN18G.
2
Stop all applications, such as databases, from accessing VxVM volumes that
are configured on the array, and unmount all file systems and Storage
Checkpoints that are configured on the array.
3
If the array is of type A/A-A, A/P or A/PF, configure it in autotrespass mode.
Administering disks
Discovering and configuring newly added disk devices
94