InfoScale™ 9.0 Dynamic Multi-Pathing Administrator's Guide - Solaris
- Understanding DMP
- How DMP works
- Disk device naming in DMP
- Setting up DMP to manage native devices
- Using Dynamic Multi-Pathing (DMP) devices with Oracle Automatic Storage Management (ASM)
- Administering DMP
- Managing DMP devices for the ZFS root pool
- 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
- 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
- Event monitoring
- Performance monitoring and tuning
- Appendix A. DMP troubleshooting
- Appendix B. Reference
Configuring latency threshold tunable for metro/geo array
The Metro/Geo cluster system has visibility for both paths, local and remote. Dynamic Multi-Pathing (DMP) A/A array IO policy distributes IO evenly across both of these paths, local and remote. Also, Metro/Geo support serves IO through the local path if the remote paths have higher latency than latency_threshold_difference.
Tunable lets you manage the parameter values of latency_threshold_difference. The default value of the latency_threshold_difference of the tunable parameter is 200 µs. The latency_threshold_difference tunable is valid only for the METRO type of array.
You can assign a new latency threshold difference value to a specified enclosure. Using tunable option you can increase or decrease the latency_threshold_difference value.
The following is the syntax for the tuning latency_threshold_difference:
# vxdmpadm getattr {enclosure enc-name}
\ latency_threshold_difference
Use the following command vxdmpadm getattr that displays the latency_threshold_difference value that is set for an enclosure emc0:
# vxdmpadm getattr enclosure emc0 latency_threshold_difference ENCLR_NAME default CURRENT ============================================ emc0 200 200
To set new value, you can use the following syntax for the specified enclosure:
# vxdmpadm setattr enclosure <enclr-name>
{name=<value> | \ latency_threshold_difference=<value>}
The following example shows the vxdmpadm setattr command to set the latency_threshold_difference value that is set for an enclosure emc0:
# vxdmpadm setattr enclosure emc0 latency_threshold_difference=300
Note:
The latency_threshold_difference is applicable for enclosure only.
DMP serves IO with local paths only if remote path has higher IO latency, then marks it as STANDBY.
#vxdmpadm getsubpaths dmpnodename=emc0_00d2
Typical output from thevxdmpadm getsubpathscommand is as follows:
NAME STATE[A] PATH-TYPE[M] CLTR-NAME ENCLR-TYPE ENCLR-NAME ATTRS PRIORITY =========================================================================== Sdar ENABLED - c9 EMC emc0 STANDBY - Sdbj ENABLED(A) - c9 EMC emc0 - - Sdh ENABLED(A) - c9 EMC emc0 - - Sdz ENABLED - c9 EMC emc0 STANDBY -
See the vxdmpadm (1M) manual page.