SOLVED XenServer ISCSI multipath wont connect after 9.2.1.8 to 9.3 upgrade

Status
Not open for further replies.

Neil_McCarthy2

Dabbler
Joined
Nov 13, 2014
Messages
13
I have had a look at this since the RELEASE, and apart from the fixed issue with the generation of the ctl.conf file my testing has not encountered the issues that I experienced with the BETA versions.

I have successfully upgraded from 9.2.1.8 to 9.3-RELEASE, and had connection issues as before. I have not tested this on a multipath environment yet.

I followed the Citrix article:

As per: http://support.citrix.com/article/CTX118641

Here Goes from my test machine:


[root@xenserver-test ~]# xe sr-probe type=lvmoiscsi device-config:target=172.16.11.20 device-config:targetIQN=iqn.2011-03.org.example.istgt:lun0
Error code: SR_BACKEND_FAILURE_107
Error parameters: , The SCSIid parameter is missing or incorrect, <?xml version="1.0" ?>
<iscsi-target>
<LUN>
<vendor>
FreeBSD
</vendor>
<serial>
080027b69a59002
</serial>
<LUNid>
2
</LUNid>
<size>
31138512896
</size>
<SCSIid>
3334609fb53540c3c
</SCSIid>
</LUN>
<LUN>
<vendor>
FreeBSD
</vendor>
<serial>
080027b69a59000
</serial>
<LUNid>
0
</LUNid>
<size>
10737418240
</size>
<SCSIid>
33454ad0c7c17f1ff
</SCSIid>
</LUN>
<LUN>
<vendor>
FreeBSD
</vendor>
<serial>
080027b69a59001
</serial>
<LUNid>
1
</LUNid>
<size>
10737418240
</size>
<SCSIid>
3361c711a66706b5f
</SCSIid>
</LUN>
</iscsi-target>


[root@xenserver-test ~]# xe sr-list name-label=ISCSI_LUN1
uuid ( RO) : 4633463c-8157-1e5c-4e74-858895d05443
name-label ( RW): ISCSI_LUN1
name-description ( RW): iSCSI SR [172.16.11.20 (*; LUN 1: 080027b69a59001: 10 GB (FreeBSD))]
host ( RO): xenserver-test
type ( RO): lvmoiscsi
content-type ( RO):


[root@xenserver-test ~]# xe pbd-list sr-uuid=4633463c-8157-1e5c-4e74-858895d05443
uuid ( RO) : 42164e9b-c4e0-b841-a8bd-6a3b891e1306
host-uuid ( RO): 7c04945e-0237-4cbe-8673-1c8a0490588c
sr-uuid ( RO): 4633463c-8157-1e5c-4e74-858895d05443
device-config (MRO): multiSession: 172.16.11.20,3260,iqn.2011-03.org.example.istgt:lun0|; target: 172.16.11.20; multihomelist: 172.16.11.20:3260; targetIQN: *; SCSIid: 3300000001b7a9a51; port: 3260
currently-attached ( RO): false

# As you can see from above the SCSIid is 3300000001b7a9a51, whereas the probe before is showing 3361c711a66706b5f

[root@xenserver-test ~]# xe pbd-destroy uuid=42164e9b-c4e0-b841-a8bd-6a3b891e1306
[root@xenserver-test ~]# xe pbd-create sr-uuid=4633463c-8157-1e5c-4e74-858895d05443 host-uuid=7c04945e-0237-4cbe-8673-1c8a0490588c device-config:target=172.16.11.20 device-config:targetIQN=iqn.2011-03.org.example.istgt:lun0 device-config:SCSIid=3361c711a66706b5f
bbf5db77-a11a-0bd0-a63e-a05a9a8bd7a2

SCSIid is from the probe

[root@xenserver-test ~]#


Then repair in XenCentre.
 

Ste

Dabbler
Joined
Sep 12, 2014
Messages
45
Thanks! I've saved this off for when I upgrade (perhaps this next weekend).
 
Status
Not open for further replies.
Top