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

Changing device naming for TPD-controlled enclosures
The feature to change device naming is available only if the disk-naming scheme
is set to use operating system-based naming, and the TPD-controlled enclosure
does not contain fabric disks.
To change device naming for TPD-controlled enclosures
◆
For disk enclosures that are controlled by third-party drivers (TPD) whose
coexistence is supported by an appropriate ASL, the default behavior is to
assign device names that are based on the TPD-assigned node names. You
can use the vxdmpadm command to switch between these names and the device
names that are known to the operating system:
# vxdmpadm setattr enclosure enclosure tpdmode=native|pseudo
The argument to the tpdmode attribute selects names that are based on those
used by the operating system (native), or TPD-assigned node names (pseudo).
If tpdmode is set to native, the path with the smallest device number is
displayed.
Persistent simple or nopriv disks with enclosure-based naming
If you change from OS-based naming to enclosure-based naming, persistent simple
or nopriv disks may be put in the error state and cause VxVM objects on those
disks to fail.
You can use the vxdarestore command to handle errors in persistent simple and
nopriv disks that arise from changing to the enclosure-based naming scheme.
You do not need to perform either procedure if the devices on which any simple
or nopriv disks are present are not automatically configured by VxVM (for example,
non-standard disk devices such as ramdisks).
The disk access records for simple disks are either persistent or non-persistent.
The disk access record for a persistent simple disk is stored in the disk’s private
region. The disk access record for a non-persistent simple disk is automatically
configured in memory at VxVM startup. A simple disk has a non-persistent disk
access record if autoconfig is included in the flags field that is displayed by the
vxdisk list disk_access_name command. If the autoconfig flag is not present,
the disk access record is persistent. Nopriv disks are always persistent.
103Administering disks
Changing the disk-naming scheme