InfoScale™ 9.0 Dynamic Multi-Pathing Administrator's Guide - Solaris
- Understanding DMP
- About Dynamic Multi-Pathing (DMP)
- How DMP works
- Multi-controller ALUA support
- Multiple paths to disk arrays
- Device discovery
- Disk devices
- Disk device naming in DMP
- Setting up DMP to manage native devices
- About setting up DMP to manage native devices
- Displaying the native multi-pathing configuration
- Migrating ZFS pools to DMP
- Migrating to DMP from EMC PowerPath
- Migrating to DMP from Hitachi Data Link Manager (HDLM)
- Migrating to DMP from Solaris Multiplexed I/O (MPxIO)
- Using Dynamic Multi-Pathing (DMP) devices with Oracle Automatic Storage Management (ASM)
- Enabling Dynamic Multi-Pathing (DMP) devices for use with Oracle Automatic Storage Management (ASM)
- Removing Dynamic Multi-Pathing (DMP) devices from the listing of Oracle Automatic Storage Management (ASM) disks
- Migrating Oracle Automatic Storage Management (ASM) disk groups on operating system devices to Dynamic Multi-Pathing (DMP) devices
- Enabling and disabling DMP support for the ZFS root pool
- Adding DMP devices to an existing ZFS pool or creating a new ZFS pool
- Removing DMP support for native devices
- Administering DMP
- About enabling and disabling I/O for controllers and storage processors
- About displaying DMP database information
- Displaying the paths to a disk
- Setting customized names for DMP nodes
- Managing DMP devices for the ZFS root pool
- Administering DMP using the vxdmpadm utility
- Retrieving information about a DMP node
- Displaying consolidated information about the DMP nodes
- Displaying the members of a LUN group
- Displaying paths controlled by a DMP node, controller, enclosure, or array port
- Displaying information about controllers
- Displaying information about enclosures
- Displaying information about array ports
- User-friendly CLI outputs for ALUA arrays
- Displaying information about devices controlled by third-party drivers
- Displaying extended device attributes
- Suppressing or including devices from VxVM control
- Gathering and displaying I/O statistics
- Setting the attributes of the paths to an enclosure
- Displaying the redundancy level of a device or enclosure
- Specifying the minimum number of active paths
- Displaying the I/O policy
- Specifying the I/O policy
- Disabling I/O for paths, controllers, array ports, or DMP nodes
- Enabling I/O for paths, controllers, array ports, or DMP nodes
- Renaming an enclosure
- Configuring the response to I/O failures
- Configuring the I/O throttling mechanism
- Configuring Subpaths Failover Groups (SFG)
- Configuring Low Impact Path Probing (LIPP)
- Displaying recovery option values
- Configuring DMP path restoration policies
- Stopping the DMP path restoration thread
- Displaying the status of the DMP path restoration thread
- Configuring Array Policy Modules
- Configuring latency threshold tunable for metro/geo array
- Administering disks
- About disk management
- Discovering and configuring newly added disk devices
- Partial device discovery
- About discovering disks and dynamically adding disk arrays
- About third-party driver coexistence
- How to administer the Device Discovery Layer
- Listing all the devices including iSCSI
- Listing all the Host Bus Adapters including iSCSI
- Listing the ports configured on a Host Bus Adapter
- Listing the targets configured from a Host Bus Adapter or a port
- Listing the devices configured from a Host Bus Adapter and target
- Getting or setting the iSCSI operational parameters
- Listing all supported disk arrays
- Excluding support for a disk array library
- Re-including support for an excluded disk array library
- Listing excluded disk arrays
- Listing disks claimed in the DISKS category
- Displaying details about an Array Support Library
- Adding unsupported disk arrays to the DISKS category
- Removing disks from the DISKS category
- Foreign devices
- VxVM coexistence with ZFS
- Changing the disk device naming scheme
- Discovering the association between enclosure-based disk names and OS-based disk names
- Dynamic Reconfiguration of devices
- About online Dynamic Reconfiguration
- About the DMPDR utility
- Reconfiguring a LUN online that is under DMP control using the Dynamic Reconfiguration tool
- Manually reconfiguring a LUN online that is under DMP control
- Overview of manually reconfiguring a LUN
- Manually removing LUNs dynamically from an existing target ID
- Manually adding new LUNs dynamically to a new target ID
- About detecting target ID reuse if the operating system device tree is not cleaned up
- Scanning an operating system device tree after adding or removing LUNs
- Manually cleaning up the operating system device tree after removing LUNs
- Manually replacing a host bus adapter on an M5000 server
- Changing the characteristics of a LUN from the array side
- Upgrading the array controller firmware online
- Event monitoring
- About the Dynamic Multi-Pathing (DMP) event source daemon (vxesd)
- Fabric Monitoring and proactive error detection
- Dynamic Multi-Pathing (DMP) automated device discovery
- Dynamic Multi-Pathing (DMP) discovery of iSCSI and SAN Fibre Channel topology
- DMP event logging
- Starting and stopping the Dynamic Multi-Pathing (DMP) event source daemon
- Performance monitoring and tuning
- About tuning Dynamic Multi-Pathing (DMP) with templates
- DMP tuning templates
- Example DMP tuning template
- Tuning a DMP host with a configuration attribute template
- Managing the DMP configuration files
- Resetting the DMP tunable parameters and attributes to the default values
- DMP tunable parameters and attributes that are supported for templates
- DMP tunable parameters
- Appendix A. DMP troubleshooting
- Appendix B. Reference
Examples of using the vxdmpadm iostat command
Dynamic Multi-Pathing (DMP) enables you to gather and display I/O statistics with the vxdmpadm iostat command. This section provides an example session using the vxdmpadm iostat command.
The first command enables the gathering of I/O statistics:
# vxdmpadm iostat start
The next command displays the current statistics including the accumulated total numbers of read and write operations, and the kilobytes read and written, on all paths.
# vxdmpadm -u k iostat show all
cpu usage = 7952us per cpu memory = 8192b
OPERATIONS BYTES AVG TIME(ms)
PATHNAME READS WRITES READS WRITES READS WRITES
c0t0d0 1088 0 557056k 0 0.00 0.00
c2t118d0 87 0 44544k 0 0.00 0.00
c3t118d0 0 0 0 0 0.00 0.00
c2t122d0 87 0 44544k 0 0.00 0.00
c3t122d0 0 0 0 0 0.00 0.00
c2t115d0 87 0 44544k 0 0.00 0.00
c3t115d0 0 0 0 0 0.00 0.00
c2t103d0 87 0 44544k 0 0.00 0.00
c3t103d0 0 0 0 0 0.00 0.00
c2t102d0 87 0 44544k 0 0.00 0.00
c3t102d0 0 0 0 0 0.00 0.00
c2t121d0 87 0 44544k 0 0.00 0.00
c3t121d0 0 0 0 0 0.00 0.00
c2t112d0 87 0 44544k 0 0.00 0.00
c3t112d0 0 0 0 0 0.00 0.00
c2t96d0 87 0 44544k 0 0.00 0.00
c3t96d0 0 0 0 0 0.00 0.00
c2t106d0 87 0 44544k 0 0.00 0.00
c3t106d0 0 0 0 0 0.00 0.00
c2t113d0 87 0 44544k 0 0.00 0.00
c3t113d0 0 0 0 0 0.00 0.00
c2t119d0 87 0 44544k 0 0.00 0.00
c3t119d0 0 0 0 0 0.00 0.00The following command changes the amount of memory that vxdmpadm can use to accumulate the statistics:
# vxdmpadm iostat start memory=4096
The displayed statistics can be filtered by path name, DMP node name, and enclosure name (note that the per-CPU memory has changed following the previous command):
# vxdmpadm -u k iostat show pathname=c3t115d0s2
cpu usage = 8132us per cpu memory = 4096b
OPERATIONS BYTES AVG TIME(ms)
PATHNAME READS WRITES READS WRITES READS WRITES
c3t115d0s2 0 0 0 0 0.00 0.00
# vxdmpadm -u k iostat show dmpnodename=c0t0d0s2
cpu usage = 8501us per cpu memory = 4096b
OPERATIONS BYTES AVG TIME(ms)
PATHNAME READS WRITES READS WRITES READS WRITES
c0t0d0s2 1088 0 557056k 0 0.00 0.00
# vxdmpadm -u k iostat show enclosure=Disk
cpu usage = 8626us per cpu memory = 4096b
OPERATIONS BYTES AVG TIME(ms)
PATHNAME READS WRITES READS WRITES READS WRITES
c0t0d0s2 1088 0 57056k 0 0.00 0.00You can also specify the number of times to display the statistics and the time interval. Here the incremental statistics for a path are displayed twice with a 2-second interval:
# vxdmpadm iostat show dmpnodename=emc_clariion0_342 interval=1 count=2
cpu usage = 164687us per cpu memory = 409600b
OPERATIONS BLOCKS AVG TIME(ms)
PATHNAME READS WRITES READS WRITES READS WRITES
c0t5006016041E03B33d6s2 3 0 33 0 0.02 0.00
c0t5006016141E03B33d6s2 3 0 3 0 0.16 0.00
c0t5006016841E03B33d6s2 0 0 0 0 0.00 0.00
c1t5006016041E03B33d6s2 1 0 16 0 0.02 0.00
c1t5006016141E03B33d6s2 2 0 2 0 0.18 0.00
c1t5006016841E03B33d6s2 0 0 0 0 0.00 0.00
c0t5006016041E03B33d6s2 0 0 0 0 0.00 0.00
c0t5006016141E03B33d6s2 0 0 0 0 0.00 0.00
c0t5006016841E03B33d6s2 0 0 0 0 0.00 0.00
c1t5006016041E03B33d6s2 0 0 0 0 0.00 0.00
c1t5006016141E03B33d6s2 0 0 0 0 0.00 0.00
c1t5006016841E03B33d6s2 0 0 0 0 0.00 0.00