Details
-
Improvement
-
Resolution: Done
-
Minor
-
7.0, 7.1
-
None
-
XenServer 7.0, HPE MSA2040 via FC
Description
Hello!
Since HPEs documentation is a bit ...sloppy, I needed to open a case and several mails to finally get a correctly functional config-part, which had to be requested from a lab-engineer.
So I'd like to see (and probably not only me), that XenServer would take the following part into the vendor-specific section of multipath.conf:
device{
vendor "HP"
product "MSA 2040 SAN"
path_grouping_policy group_by_prio
uid_attribute "ID_SERIAL"
prio alua
path_checker tur
hardware_handler "0"
failback immediate
path_selector "round-robin 0"
rr_weight uniform
rr_min_io_rq 1
no_path_retry 18
dev_loss_tmo 10
fast_io_fail_tmo 5
}
they also use a global:
polling_interval 10
But it would probably also work, to put that into the device-specific section.
This config is tested by me and multipath-output says it works:
# multipath -ll 3600c0ff00027ec45f66d9e5801000000 dm-8 HP ,MSA 2040 SAN size=15T features='1 queue_if_no_path' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=50 status=active | |- 0:0:3:0 sdc 8:32 active ready running | `- 9:0:1:0 sde 8:64 active ready running `-+- policy='round-robin 0' prio=10 status=enabled |- 0:0:2:0 sdb 8:16 active ready running `- 9:0:0:0 sdd 8:48 active ready running
(These are 2 Dualport FC-HBAs, running alua because only controller 1 has optimized paths)
XenCenter says: 4 of 4 paths active.
Regards
- Christof
