Open kentnz opened 5 years ago
As a proper multipathing requieres configuration info, it's probably mandatory to put the right settings into: /etc/multipath.conf. I had to add proper device infos for our MSA2040 SAN/FC for XenServer 7.1 - I doubt 3PAR had found it's way into it, since then.
I contacted some guys from HP(E) and after a while I got proper infos back and gave feedback to Citrix for upstream purposes.
My setup was working fine with prior versions of XenServer (up to 7.2) and XCP (7.6). It's only post updating to 8.0 that it's failing. Something has changed with the 8.0 update that is breaking enabling Multipathing.
So, either something has been removed - or something in the process of attaching when Multipathing is enabled.
Why does the log show the help for multipathd ?
[15112] MPATH: multipath activate called [15112] mpath cmd: help [15112] mpath output: multipathd> help
Regarding the /etc/multipath.conf file, the only difference I can see is in the 'blacklist'.
XenServer 7.2
blacklist { devnode "^nvme.*" }
XCP 8.0
blacklist { devnode "^nvme." devnode "scini" devnode "^rbd[0-9]" devnode "^nbd[0-9]" }
I've run: multipathd -k"show conf" I can see a whole group of references to "HP" under 'blacklist_exceptions'
The other thing are there are some new 'defaults' in the list (comparing 7.2 versus 8.0, I don't have a 7.6 server any more).
prkeys_file /etc/multipath/prkeys detect_path_checker no skip_kpartx no remove_retries 0 disable_changed_wwids no unpriv_sgio no ghost_delay no
thanks Kent.
I guess it's your job to test other/old settings in config file and/or contact HP. 3PAR is a rather expensive thing and probably noone here has one to test. I know they change the defaults from time to time, but I can't help you with that - as said: I reached an HP support guy and they gave me their settings from the lab. Also one HP guy was watching the XenServer bugtracker and contributing.
Okay - where is the XenServer bugtracker so I can post this issue there and see ?
To me, this appears to be a regression in XenServer/XCP 8.0 with Multipathing enabled - as it was working fine in 7.6 - plus the error in XCP Admin Console is reporting 'Invalid Parameter' - which seems to tie in with the log file dumping the help for 'mpath output: multipathd> help'
Thanks Kent.
Found the XenServer bug tracker (hopefully) and have submitted this issue there as well. https://bugs.xenserver.org/browse/XSO-965
I'll try and find a time when I can bring one of my servers down to experiment with the options and see if one makes a difference.
Kent.
@kentnz you should really change the title to "Citrix Hypervisor 8.0" instead of "XCP 8.0" otherwise don't expect Citrix people to answer :wink:
Thanks Oliver, have done so. Anything else you can suggest to get this resolved ? thanks Kent.
I'd like to help, but I don't have similar hardware nor experience with HBA :disappointed:
However, I would publish on XCP-ng forum, this is where the community here. Maybe someone is able to assist there! :smile:
I posted on the XCP-ng forum originally a couple of days ago - but so far no replies (other than my own progress one). https://xcp-ng.org/forum/topic/2006/hba-sr-not-available-when-multipathing-enabled-in-xcp-8-0
Is it worth installing Citrix Hypervisor 8.0 on one of my severs (not XCP) and verifying that this is an issue with the Citrix release ?
I was planning on updating my 5x data centre servers from XenServer 7.2 (the version before they introduced the 3 server host limit) to XCP 8.0, but need to get this sorted first.
thanks Kent.
Is it worth installing Citrix Hypervisor 8.0 on one of my severs (not XCP) and verifying that this is an issue with the Citrix release ?
This is always useful information to have indeed, so that we know if the problem comes from us or from Citrix. I thought you already had since you reported the bug to Citrix.
Hi @stormi, No - with the help of @olivierlambert and @r1 I was able to work around this issue by copying the settings from our 7.2 server into the multipath.conf file.
I understood (maybe assumed incorrectly) from their feedback that this wasn't an area they had changed and it was their suggestion to post it as a bug to Citrix.
But, I'll make some time in the next few days to install the Citrix version of 8.0 and verify.
Kent.
This isn't an area we have changed indeed, but you never know for sure until it's been tested :)
We are also running 3par within our org and I hit this problem too after upgrading to 8.0
I had to manually add the following to my multipath.conf device list:
device {
vendor "3PARdata"
product "VV"
path_grouping_policy "multibus"
path_checker "directio"
features "0"
hardware_handler "0"
prio "const"
rr_weight "uniform"
}
I added this to all the hosts within the pool and now everything works as expected.
Hopefully this helps.
There have been insightful (or so it seems) comments from Citrix on https://bugs.xenserver.org/browse/XSO-965
Could someone gather all data about this issue and make a summary as a comment here? Then we could probably document all this on the wiki.
Issue: When Multipathing is enabled in XCP 8.0 for a SR connected via 2 channel Fibre to a HP 3PAR SAN storage array, then XCP fails to connect and reports an error 'Invalid Option'
Steps to Reproduce: 1) Install XCP-NG 8.0. 2) Post installation, run 'yum update' to get up to date. 3) In XenCenter i. Add HBA Storage Repository (I'm connected to an HP 3PAR 8 via Fibre, 2 channels) ii. Ensure the Storage Repository is listed and available, etc. 3) Enter Maintenance Mode, Turn on 'Multipathing' and save. RESULT: XCP fails to reconnect to the Storage Repository (SR) and reports an error 'Invalid Option'. Selecting 'Repair' on the SR reports the same error. 4) Enter maintenance Mode again, turn 'OFF' Multipathing and save. RESULT: After selecting 'Repair', the SR is reconnected again.
Repeating steps 3 & 4 produces the same outcome - whenever Multipathing is enabled, XCP fails to connect to our 3PAR SR. Note: No issues connecting to the local SR or the NFS drive I also have mounted (these don't support Multipathing).
Expected Result: Post enabling Multipathing, the SR should reconnect.
Actual Result: The SR fails to reconnect and reports an error: 'Invalid Option'
More Information: This is the output from the /var/logs/SMlog when enabling Multipathing.