Veritas 4.1 Installation Guide (HP-UX 11i v3, February 2007)

appropriate physical path. Unless all the underlying physical paths of the native multipathing
metanode fail, any I/O that DMP performs on a legacy path succeeds.
• The output from the DMP vxdmpadm iostat command does not match the output from
the native HP-UX iostat command.
• Using the vxdmpadm disable and vxdmpadm enable commands on a path or controller
causes Veritas DMP to use another path for I/O, but HP-UX native multipathing still continues
to send I/O to the disabled path or controller.
• Veritas DMP supports device paths only up to 32768.
• A path-specific attribute shown by the Veritas DMP vxdmpadm getsubpaths command
does not match the actual array attribute. This is because Veritas DMP cannot perform
path-specific I/O or ioctl requests unless legacy multipathing is disabled. Instead Veritas
DMP shows the path attributes that are returned by HP-UX native multipathing.
• Veritas DMP supports the A/P arrays that are supported by HP-UX native multipathing.
No additional A/P arrays are supported. If an A/P array is used that is not supported by
HP-UX native multipathing, any I/O or ioctl requests from DMP cause trespass.
• For A/A arrays, the Veritas DMP vxdmpadm getsubpaths command shows all paths in
the ENABLED (A) state until the last path is disabled. For arrays of type A/P, only one path
is shown in the ENABLED (A) state. All path types are shown as PRIMARY until at least one
primary path is enabled. When all the primary paths have become disabled, all the paths
are shown as SECONDARY. Any path attributes are only changed when a device discovery
is performed.
NOTE: After upgrading to HP-UX 11i v3, you should remove the older ASL's for the storage
products supported with HP-UX 11i v2.
70 VxVM 4.1, New Style DSFs and HP-UX Native Multipathing