Veritas 5.0.1 Installation Guide, HP-UX 11i v3, First Edition, November 2009

# vxdg upgrade <diskgroup>
After you upgrade from a previous release of VxVM, HP recommends that you upgrade to the
latest disk group version.
For more information on disk groups, see the Veritas Volume Manager Administrator's Guide
available at:
http://www.docs.hp.com
Native Multipathing with Veritas Volume Manager
By default, VxVM uses DMP to manage multiple paths to I/O devices. It is possible to configure
VxVM to use HP-UX native multipathing instead by defining I/O devices as foreign devices,
which are bypassed by DMP. To revert to using DMP, you must remove the I/O devices from
the foreign device list. This section outlines a system-wide procedure to switch between using
DMP and using HP-UX native multipathing using the vxddladm addforeign and vxddladm
rmforeign commands. Using the procedure you can migrate all devices in the /dev/disk and
/dev/rdisk directories. To migrate an individual device or only a subset of devices, see the
vxdiskadm3(1M).
Migrating from DMP to HP-UX native multipathing for systems that do not have VxVM root
disks
CAUTION: Before switching between DMP and HP-UX native multipathing, ensure that no
application is accessing the VxVM volumes and no file system is mounted on the VxVM volumes.
Otherwise, you cannot complete the following procedure. The following procedure cannot be
used on a system that has VxVM root disks.
Prior to migrating from DMP to HP-UX native multipathing, ensure that there are no applications
accessing VxVM volumes and no file system is mounted on VxVM volumes.
To migrate from DMP to HP-UX native multipathing, complete the following steps:
1. Stop all volumes in each disk group on the system:
# vxvol –g diskgroup stopall
2. Initiate the migration:
# vxddladm addforeign blockdir=/dev/disk chardir=/dev/rdisk
# vxconfigd –kr reset
3. Restart the volumes in each group:
# vxvol –g diskgroup startall
The output from the vxdisk list command now displays a list of devices following the agile
naming scheme of the operating system instead of the DMP metanode names
For example:
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
disk155 auto:LVM - - LVM
disk156 auto:LVM - - LVM
disk224 auto:cdsdisk - - online
disk225 auto:cdsdisk - - online
disk226 auto:cdsdisk - - online
disk227 auto:hpdisk - - online
disk228 auto:hpdisk - - online
disk229 auto:hpdisk - - online
This procedure essentially instructs DMP to bypass all auto-configured devices. As a result, no
DMP metanodes are created under /dev/vx/[r]dmp directory. VxVM names these devices
58 Upgrading from Previous Versions of VxVM to VxVM 5.0.1