Displaying extended attributes after upgrading to DMP 7.0


Displaying extended attributes after upgrading to DMP 7.0
Prev	Appendix A. DMP troubleshooting	Next

You may see the following changes in functionality when you upgrade to DMP 7.0 from the Storage Foundation 5.1 release:

The device names that are listed in the vxdisk list output do not display the Array Volume IDs (AVIDs).
The vxdisk -e list output does not display extended attributes.
An Active/Passive (A/P) or ALUA array is claimed as Active/Active (A/A).

This behavior may be because the LUNs are controlled by the native multi-pathing driver, MPxIO. When a LUN is controlled by TPD drivers like MPxIO, then in DMP those enclosures are claimed as A/A (irrespective of what array mode LUN has at array). This is because multi-pathing is done from the TPD driver and DMP only sees or uses the TPD metanode to route commands. For TPD, DMP also suppresses the value-add extended attributes like AVID, media_type, and so on. If you migrate LUN multi-pathing to DMP, those extended attributes start showing with actual the LUN array mode as per the Array Support Library (ASL).

To check whether LUNs are controlled by the native multi-pathing driver

Check the output of the following command. The LUN is controlled by MPxIO if the controller of the affected LUN has the physical name (PNAME) as /scsi_vhci:
```
# vxdmpadm getctlr all
```

You can migrate the LUNs from the control of the native multi-pathing driver to DMP control.

To migrate to DMP with Veritas Volume Manager, refer to the section on disabling MPxIO in the Storage Foundation Administrator's Guide.
To migrate to DMP with OS native volume support, refer to the section on migrating to DMP from MPxIO in the Dynamic Multi-Pathing Adminstrator's Guide.