im fooling a bit with xenserver, it seems like open-e really dosnt report multiple paths to the target, but there is a little manual workaround
first my device in multipath.conf:
device {
vendor "iSCSI"
product "*"
path_grouping_policy multibus
path_checker tur
features "1 queue_if_no_path"
failback immediate
rr_min_io 1000 # try different values, for me 4 seems to work best
path_selector "round-robin 0"
}
since xen allows only to setup one connection to a specific lun, you have to setup another connection manually, for example:
- iscsi target (open-e) on 192.168.0.1/24 and 192.168.1.1/24
- in xencenter activate multipath
- setup SR to 192.168.0.1
- login to xen via ssh
- iscsi login to the 192.168.1.1:
"iscsiadm --mode discovery --type sendtargets --portal 192.168.1.1
iscsiadm --mode node --targetname iqn.2009-04:dss.target0 --portal 192.168.1.1 --login"
at this moment xencenter should report 2 active paths to the SR.. well there should be a way to make it automatic but didnt see in to it yet, also i would suggest to read dm-multipath manual
I added the following config:
# BARRY ADDED
device {
vendor "iSCSI"
product "*"
path_grouping_policy multibus
path_checker tur
features "1 queue_if_no_path"
failback immediate
rr_min_io 4 # try different values, for me 4 seems to work best
path_selector "round-robin 0"
}
device {
vendor "SCST_FIO"
product "*"
path_grouping_policy multibus
path_checker tur
features "1 queue_if_no_path"
failback immediate
rr_min_io 4 # try different values, for me 4 seems to work best
path_selector "round-robin 0"
}
And also:
multipaths {
multipath {
wwid 200000000d11ba481dm-2
alias multipath2
}