Dynamic Multi-Pathing 7.4.1 Administrator's Guide - AIX
- Understanding DMP
- Setting up DMP to manage native devices
- Using Dynamic Multi-Pathing (DMP) devices with Oracle Automatic Storage Management (ASM)
- Dynamic Multi-Pathing for the Virtual I/O Server
- Configuring Dynamic Multi-Pathing (DMP) on Virtual I/O server
- Configuring Dynamic Multi-Pathing (DMP) pseudo devices as virtual SCSI devices
- Extended attributes in VIO client for a virtual SCSI disk
- Administering DMP
- Configuring DMP for SAN booting
- Administering the root volume group (rootvg) under DMP control
- Extending an LVM rootvg that is enabled for DMP
- Using Storage Foundation in the logical partition (LPAR) with virtual SCSI devices
- How DMP handles I/O for vSCSI devices
- Administering DMP using the vxdmpadm utility
- Gathering and displaying I/O statistics
- Specifying the I/O policy
- Administering disks
- Discovering and configuring newly added disk devices
- About discovering disks and dynamically adding disk arrays
- How to administer the Device Discovery Layer
- Changing the disk device naming scheme
- Dynamic Reconfiguration of devices
- Reconfiguring a LUN online that is under DMP control using the Dynamic Reconfiguration tool
- Manually reconfiguring a LUN online that is under DMP control
- Event monitoring
- Performance monitoring and tuning
- Appendix A. DMP troubleshooting
- Appendix B. Reference
Displaying information about devices controlled by third-party drivers
The third-party driver (TPD) coexistence feature allows I/O that is controlled by third-party multi-pathing drivers to bypass Dynamic Multi-Pathing (DMP) while retaining the monitoring capabilities of DMP. The following commands allow you to display the paths that DMP has discovered for a given TPD device, and the TPD device that corresponds to a given TPD-controlled node discovered by DMP:
# vxdmpadm getsubpaths tpdnodename=TPD_node_name # vxdmpadm gettpdnode nodename=TPD_path_name
For example, consider the following disks in an EMC Symmetrix array controlled by PowerPath, which are known to DMP:
# vxdisk list
DEVICE TYPE DISK GROUP STATUS hdiskpower10 auto:cdsdisk disk1 ppdg online hdiskpower11 auto:cdsdisk disk2 ppdg online hdiskpower12 auto:cdsdisk disk3 ppdg online hdiskpower13 auto:cdsdisk disk4 ppdg online hdiskpower14 auto:cdsdisk disk5 ppdg online hdiskpower15 auto:cdsdisk disk6 ppdg online hdiskpower16 auto:cdsdisk disk7 ppdg online hdiskpower17 auto:cdsdisk disk8 ppdg online hdiskpower18 auto:cdsdisk disk9 ppdg online hdiskpower19 auto:cdsdisk disk10 ppdg online
The following command displays the paths that DMP has discovered, and which correspond to the PowerPath-controlled node, emcpower10:
# vxdmpadm getsubpaths tpdnodename=hdiskpower10 NAME TPDNODENAME PATH-TYPE[-]DMP-NODENAME ENCLR-TYPE ENCLR-NAME =================================================================== hdisk10 hdiskpower10s2 - hdiskpower10 EMC EMC0 hdisk20 hdiskpower10s2 - hdiskpower10 EMC EMC0
Conversely, the next command displays information about the PowerPath node that corresponds to the path, hdisk10, discovered by DMP:
# vxdmpadm gettpdnode nodename=hdiskpower10 NAME STATE PATHS ENCLR-TYPE ENCLR-NAME =================================================================== hdiskpower10s2 ENABLED 2 EMC EMC0