VERITAS Volume Manager 4.1 Administrator's Guide

Chapter 2 73
This command adds the array library to the database so that the library can once again be
used in device discovery. If vxconfigd is running, you can use the vxdisk scandisks
command to discover the array and add its details to the database.
Listing Excluded Disk Arrays
To list all disk arrays that are currently excluded from use by VxVM, use the following
command:
# vxddladm listexclude
Listing Supported Disks in the DISKS Category
To list supported disks in the DISKS (JBOD) category, use the following command:
# vxddladm listjbod
Adding Unsupported Disk Arrays to the DISKS Category
CAUTION 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.
Otherwise, VERITAS Volume Manager treats the independent paths to the
disks as separate devices, which can result in data corruption.
To add an unsupported disk array:
1. Use the following command to identify the vendor ID and product ID of the disks in the
array:
# /etc/vx/diag.d/vxdmpinq device_name
where device_name is the device name of one of the disks in the array (for example,
/dev/rdsk/c1t20d0). 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.
2. Enter the following command to add a new JBOD category:
# vxddladm addjbod vid=vendorid pid=productid [length=serialno_length]
where vendorid and productid are the VID and PID values that you found from the
previous step. For example, vendorid might be FUJITSU, IBM, or SEAGATE. For Fujitsu
devices, you must also specify the number of characters in the serial number as the
argument to the length argument (for example, 10).
NOTE In VxVM 4.0 and later releases, a SEAGATE disk is added as a JBOD device
by default.
Continuing the previous example, the command to define an array of disks of this type as
a JBOD would be: