Hello, everyone!
This is a case about how to solve OceanStor 2600 V3 only one path has data traffic.
Problem Description
At a site, the upper-layer RHEL 6.5 system uses the multipathing software built in the system. When the path traffic is queried on the OS, only one path has data traffic. We suspect that the storage system does not support load balancing.
Process
1. Check whether the multipathing configuration is correct.
device {
vendor "HUAWEI"
product "XSG1"
path_grouping_policy multibus
getuid_callout "/lib/udev/scsi_id --whitelisted --device=/dev/%n"
path_checker tur
path_selector "round-robin 0"
failback immediate
}
For details about how to configure the multipathing software, see http://support.huawei.com/enterprise/KnowledgebaseReadAction.action?contentId=KB1000338674.
2. Check the status of the current initiator.
3. If the built-in multipathing software of the system is used and the upper layer wants to implement load balancing among LUNs on each path, disable ALUA.
4. After the ALUA is disabled, the problem is solved.
Root Cause
The initiator mode is incorrectly switched. Correctly change the initiator mode.
Solution
1. If third-party multipathing is used, to implement load balancing for LUNs on each link, refer to the multipathing configuration and disable ALUA for the storage device.
2. To implement load balancing at the controller level, evenly allocate the owning controllers of LUNs to the two controllers.
This is my solution, how about yours? Go ahead and share it with us!
