MPIO Configuration

[misabel]

Hi,

I'm having difficulty getting the MPIO configuration correctly. I’ve been able to configure MPIO using the following method for the Microsoft iSCSI target in order to leverage the 2 x 1Gbps connections of the server. i.e. I have a session per initiator IP and target IP

Right now, I can only use 1Gbps with the StarWind target.

Here's what I've done:

Starwind Server
- 2 IP, all active in the Network section of the StarWind Configuration section)
- Created a new target, checked Allow multiple concurrent iSCSI connections (clustering)
- I then added a new Hard Disk device (Basic Virtual) using an Image File device and specified the Asynchronous mode for the device and selected Normal for the cache mode
- To grant access to the server that will use the LUN, I’ve created a new rule with the source being the IQN of the initiator of the server and the IQN of the target created above.

Initiator Server (2 IP)
- In the iSCSI initiator of the Windows Server 8
o In the Discovery tab, under Target Portal, I added the 2 IPs of the StarWind server
o In the targets tab, I connect the target I created above
 I check Enable multi-path and click Advanced
 In the Local Adapter drop down, I pick Microsoft iSCSI initiator
 In the initiator IP, I pick one of 2 IPs on my initiator server
 In the Target portal IP drop down, I only have 1 of the IP of the StarWind target
 If I leave the Local Adapter to Default, then I can see the 2 IP of the target


Am I missing something?

Thanks!

Mathieu

[anton (staff)]

Biggest question is - are you really using beta version or you're using 5.8 release?

[misabel]

Another question, would I need to have the MPIO Windows feature installed on the StarWind server side?

[misabel]

Hi Anton,

I'm using version 5.9 Build 20120418. I've had a similar issue with 5.8 that I couldn't resolve. I was hoping that version 5.9 might help.

Mathieu

[anton (staff)]

It's configuration rather then anything else feature. In a couple of hours support staff should come to you case. Stay tuned

[jsmithv]

Was there ever a resolution to this question? I am experiencing the same issue. I only see one of the two IP's I entered into the discovery tab. Using Starwind Free 6.0.4837.

Starwind Server:
IP1: 10.30.0.5
IP2: 10.30.1.5
Device: Asynch Mode - Yes
Target: Allow Multiple - Yes

Initiator:
IP1: 10.30.0.10
IP2: 10.30.1.10

Like the original poster, I try to enable multipath, click advanced, but only get 10.30.0.5 as the IP choice for "target portal ip" when I change the options from all defaults.

Any help would be appreciated,

[Bohdan (staff)]

Uncomment
<!--<iScsiDiscoveryListInterfaces value="1"/>-->
option in the starwind.cfg file
<iScsiDiscoveryListInterfaces value="1"/>
and restart starwind service

[jsmithv]

That did the trick! Thanks so much. Seeing great numbers now over 2x1Gbps mpio between the server and initiator. Thanks,

[Anatoly (staff)]

We are always glad to assist you!

Please do not hesitate to contact usshould you have any additional questions. It would be ourpleasure to further assist you!

[rjkunde]

If I restart the starwind service, does that disconnect the current iSCSI targets or disrupt the production environment?

[anton (staff)]

Obviously YES.

So the only way to have no downtime - configure a HA.

If I restart the starwind service, does that disconnect the current iSCSI targets or disrupt the production environment?

[rjkunde]

I'm configuring an HA environment right now using StarWind 6, but this will still require downtime.... we are using version 5.7 currently, which is why I asked about the StarWind service...

[Anatoly (staff)]

Well, actually this question is well described in our FAQ. Here is the link:
http://www.starwindsoftware.com/starwind-faq#q_20

I hope it helped