StarWind Software

Hello,
i am doing my preliminary config on a new install and i am running into a slight issue presenting storage to xen. I am using the below link as a reference guide.
http://www.starwindsoftware.com/providi ... -xenserver
I am also using as a reference an older version of this which i was given in MS word format named XenGuide.docx (to large even when zipped to attach) by support back when on 2 installs for starwind 5.6 and xenserver 5.6 FR1. which has been running smooth for some time now on both installs.

The issue i am running into which is also not the way i am presenting storage to my previous installs is when adding the shared storage in xencenter. it states the final attachment wizard using SAN1 and SAN2 IPs in the target host like so. 10.0.0.115,10.0.0.117 and then selecting the (*10.0.0.115,10.0.0.117:3260) as the IQN but no matter how i do this i always get a unable to connect to iscsi service on target error when discovering the LUN.

I am able to attach the storage how i am in the older 5.6 install guides by just pointing to the IP of SAN1 and manually running some iscsiadm commands to be sure things are attached prior to adding to xencenter. adn multipathing still says 2 of 2 paths. which can be a little picky sometimes and revert to 1 of 1 after a xenserver reboot in the pool.

any assistance would be appreciated,
Dave

So just to clarify - you are getting error when trying to connect to the HA, correect?
Can you please provide us with the screenshot of the error?

when clicking the discover LUNs i get the following. i just tried the secondary method in the PDF via command line and it completes with no errors. but this is what i see as far as actual connections. i cant add the 4th screen shot but it is of the target on san2 showing no sessions.

here is the other screen shot.

I just ran through the process i use to connect HA storage using multipathing on previous installs which is.

create ha target
run following commands on each CPU node

iscsiadm -m discovery -t sendtargets -p 10.0.0.115
iscsiadm -m node -T iqn.2008-08.com.starwindsoftware:10.0.0.115-entaa-dc -p 10.0.0.115: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-dcpartner -p 10.0.0.117:3260 -l

then add storage in xencenter pointing to the SAN1 IP 10.0.0.115

and it attached. but out of the gate this is what i see for its multipathing settings. which technically should work. but with the number of nics and such on this system i think the proper number for multipathing is 4 of 4 with 2 active sessions.


nic config details are:
CPU nodes - 4 NICs
node 1
nic0 + nic1 bonded (lan access) 172.20.1.110
nic2 10.0.0.110
nic3 10.0.0.112

node 2
nic0 + nic1 bonded (lan access) 172.20.1.111
nic2 10.0.0.111
nic3 10.0.0.113

SAN nodes - 10 NICs each
SAN1
nic1 + nic2 bonded (lan access, disabled in starwind) 172.20.1.115
nic3 + nic4 bonded (san access, enabled in starwind) 10.0.0.115
nic5 + nic6 bonded (san access, enabled in starwind) 10.0.0.116
nic7-nic10 NOT bonded (sync channels) 192.168.168.110,112,114,116

SAN2
nic1 + nic2 bonded (lan access, disabled in starwind) 172.20.1.117
nic3 + nic4 bonded (san access, enabled in starwind) 10.0.0.117
nic5 + nic6 bonded (san access, enabled in starwind) 10.0.0.118
nic7-nic10 NOT bonded (sync channels) 192.168.168.111,113,115,117

Idea is to segment some LUNs between SAN bonds on SAN nodes. SAN bonds are LAG/LACP 802.3ad which is configured on the HP 2910AL switching.

OK, I will definitely ask you to provide us with the network diagram with all hte IPs and iSCSI session that you created because number 20 that we see in SW console looks too big for me.

Since the last post this is how things are configured right now.
Also this is a full screen shot of a LUN created and presented to XEN. next post will have more screen shots...

And here is the commands used on xenserver console prior to adding iscsi in xencenter and the end result in xencenter.
here are the device details for when the target and device was created.

Can you tell us which multipathing option you've selected in the multipath.conf (path_grouping_policy)
Group_by_prio/multibus/left defaults?

Max (staff) wrote:Can you tell us which multipathing option you've selected in the multipath.conf (path_grouping_policy)
Group_by_prio/multibus/left defaults?

sorry for the delay i have been out of town. here is the multipatch.conf defaults section

defaults {
user_friendly_names no
}

under this there is a bunch of devices { that have different settings for path_group_policy

Thanks,
Dave

and here is an updated visio with all addressing and bonding.
Thanks,
dave

Did you have a chance to make that multipath.conf change I mentioned eralier?
You'll need to add the additional parameters right after the default line (user friendly names no)

dreesedatalink wrote:

Max (staff) wrote:Can you tell us which multipathing option you've selected in the multipath.conf (path_grouping_policy)
Group_by_prio/multibus/left defaults?

sorry for the delay i have been out of town. here is the multipatch.conf defaults section

defaults {
user_friendly_names no
}

under this there is a bunch of devices { that have different settings for path_group_policy

Thanks,
Dave

Max,
user_friendly_names no is already in the multipath.conf under default. but below that is a bunch of model specific items that look to be there by default like

device {
vendor "DELL"
product "MD3000i"


which i did not add they look to be there by default.

you need to add right after the "user_friendly_names no" line in the config

Max (staff) wrote:you need to add

Code: Select all

polling_interval 10 
path_grouping_policy multibus

right after the "user_friendly_names no" line in the config

Max,
I have updated the multipath.conf as specified. i am guessing i will at least need to restart openiscsid for it to apply correct? either way i will give it a test from here and let you know how things look after.
Thanks,
Dave