Dynamic Multi-Pathing 8.0.2 Administrator's Guide - Linux
- Understanding DMP
- Setting up DMP to manage native devices
- Using Dynamic Multi-Pathing (DMP) devices with Oracle Automatic Storage Management (ASM)
- Administering DMP
- 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
Handling Fabric Performance Impact Notification (FPIN) events
DMP handles switch level Fabric Performance Impact Notification (FPIN) events to avoid degradation in IO performance. In certain cases, IO performance of the storage subsystem is degraded due to a link failure or a congestion event in the fabric. Multipathing solutions that manage a storage subsystem have the capability to avoid using affected paths and choosing an alternate path for performing IO.
To mitigate such performance degradation scenarios, fabric vendors provide a functionality to receive fabric-specific notifications for each path. To get fabric-specific notifications, the host (end device) has to register with the fabric. After registration, the host receives these events through a Fibre Channel Extended Link Service (ELS) function that is known as Fabric Performance Impact Notifications (FPINs). Multipathing solutions can use these events to evaluate error conditions and use an alternate path, if required.
The DMP event source daemon (vxesd
) listens to fabric events through the netlink socket and reacts to the fabric performance notification events. The vxesd
daemon analyses the FPIN events to identify the affected path and avoids using it until the link or the congestion event subsides. The daemon thus prevents IO throughput degradation. Any performance blips caused due to such events are avoided. After the link or the congestion subsides, The affected path is used for the IO again.
The vxesd
daemon monitors the FPIN events and marks a path as a standby path on receiving a link integrity event. When a path is marked as a standby, DMP does not send any new IO to that path unless the standby path is the last path to the device. DMP avoids using the standby path to reduce the performance impact due to the event. After the link condition is resolved, DMP moves the standby paths to an active state and resumes IO on that path.
Note:
The FPIN event monitoring functionality does not work with an SRDF or a VPLEX Metro configuration. Veritas recommends that you disable this feature in such configurations.
The DMP tunable dmp_monitor_fpin_event
tracks the FPIN monitoring functionality status and the tunable is disabled by default.
To display the current status of the FPIN monitoring functionality, use the following command:
# vxdmpadm gettune dmp_monitor_fpin_event
To enable the FPIN monitoring functionality, use the following command:
# vxdmpadm settune dmp_monitor_fpin_event=on
To disable the FPIN monitoring functionality, use the following command:
# vxdmpadm settune dmp_monitor_fpin_event=off
The value of the tunable is persistent across restarts.