Xenserver 5.6 SP2 and HA Starwind 5.8

[dreesedatalink]

Here are the results after editing the multipath.conf on both xenservers and also running service open-iscsi restart on both.

Getting further but not there all the way (notes are int he screen shot also)

addLUN-GIF.gif (78.84 KiB) Viewed 11396 times

[Max (staff)]

Yes, that's correct. Every change to the conf file requires service open-iscsi restart command to apply the changes.

[dreesedatalink]

Yes, that's correct. Every change to the conf file requires service open-iscsi restart command to apply the changes.

I have ran the service open-iscsi restart on both then also tried rebooting both xenservers and tried again. i am still having the same results when trying to add the storage with both IP addresses as shown above. it now detects a LUN but it is the wrong LUN. Does it just detect LUN0 by default? in starwind all LUNs have the same LUN id of 0 which is what i think is confusing to xencenter so it just pulls the first LUN 0 it sees.

Dave

[Anatoly (staff)]

Dear dreesedatalink
When using HA you must know that all the LUNs are 0.

[dreesedatalink]

Dear dreesedatalink
When using HA you must know that all the LUNs are 0.

OK. I am just throwing ideas out. As i need to get this rolled out but things are still not adding properly. any ideas on how to fix it.
Thanks,
Dave

[Max (staff)]

Wait a moment, did you try to add the target by adding both IP's to the discovery IP tab (IP1;IP2 AFAIR)
then the only available target and LUN will be the one marked with *. This should result in propper connection.

[dreesedatalink]

Wait a moment, did you try to add the target by adding both IP's to the discovery IP tab (IP1;IP2 AFAIR)
then the only available target and LUN will be the one marked with *. This should result in propper connection.

i no longer get a failed to detect storage error but it is not detecting the proper LUN. it is detecting a 500GB LUN and not the 21GB LUN for the specific target i am trying to connect.
as explained in detail in the picture on the first post of page 2.
Thanks,
Dave

[Max (staff)]

Got it,
Did you connect all the targets through the Xen console before connecting the SRs through the GUI?
They should appear available after you connect all the 4 targets (if that's 2 HA devices)

[dreesedatalink]

Got it,
Did you connect all the targets through the Xen console before connecting the SRs through the GUI?
They should appear available after you connect all the 4 targets (if that's 2 HA devices)

yes. if i run the following commands on both xenservers

iscsiadm -m discovery -t sendtargets -p 10.0.0.115
iscsiadm -m node -T iqn.2008-08.com.starwindsoftware:10.0.0.115-entaa-ha -p 10.0.0.115:3260 -l
iscsiadm -m discovery -t sendtargets -p 10.0.0.116
iscsiadm -m node -T iqn.2008-08.com.starwindsoftware:10.0.0.115-entaa-ha -p 10.0.0.116:3260 -l
iscsiadm -m discovery -t sendtargets -p 10.0.0.117
iscsiadm -m node -T iqn.2008-08.com.starwindsoftware:10.0.0.117-entaa-hapartner -p 10.0.0.117:3260 -l
iscsiadm -m discovery -t sendtargets -p 10.0.0.118
iscsiadm -m node -T iqn.2008-08.com.starwindsoftware:10.0.0.117-entaa-hapartner -p 10.0.0.118:3260 -l

when i get to the section to add storage with either 10.0.0.115, 10.0.0.117 or all 4 10.0.0.115,10.0.0.116,10.0.0.117,10.0.0.118 when it comes time to detect the LUN i either get an error or it sees the wrong lun as previously stated.

if i just try to add via the single ip 10.0.0.115 it connects and i get 4 of 4 in multipath with 2 active sessions. and in starwind i see 2 connections to each san node from each xenserver. but if something reboots it half breaks the multipath. I may be to the point of having your support remote into the box and take a look.

[Max (staff)]

The problem appears because the connection is not configured to re-establish after a path failure.
Could you please drop an email to support@starwindsoftware.com to schedule a remote session.


PS: I'm sure that the problem is on the XenServer side and can be fixed by editing the connection properties files
( etc/iscsi/nodes/SAN#-IQN/SAN# IP/default)

[aabd]

Hi Max,

Could you tell us how you resolved this problem? We're stuck on the same issue when trying to attach the StarWind HA iSCSI luns to the XCP servers.
Do we need to alter the file /etc/iscsi/nodes/SAN#-IQN/SAN# IP/default, and which modifications are necessary?

Many thanks in advance

[Max (staff)]

Hi A.Abd.
I don't have a XenServer installed right now so I don't remember the exact parameter names I've changed to make it work.
It was node.startup = automatic and something like node.conn0.login = auto, but I'm not sure (bad me, I forgot to document it)
If you could send me the default file from the /etc/iscsi/nodes/SAN#-IQN/SAN# IP/ directory
I will find the necessary lines and post them here.
Thanks!