mgibson85
1 Copper

Re: MD3200i / ESXi 4.1 Multipathing problem

Jump to solution

Hi,

Thanks for the quick reply. So my vmware setup looks ok?

On the MDSM, as a test I setup 2x 500gbs in RAID0.
I've assigned these to the host group rather than the server as we will be adding an additional vmware server in.

Here's the host setup - http://i52.tinypic.com/2j1tms5.jpg

Here's the host port identifier - http://i55.tinypic.com/2cnjgk6.jpg

iqn.1998-01.com.vmware:bm-vm-06-4aebf8f7 is the name of the iSCSI initiator on my vmware server. Is this correct?

Kind Regards,

Mark

0 Kudos
Highlighted
dlreid
1 Copper

Re: MD3200i / ESXi 4.1 Multipathing problem

Jump to solution

Hi kwarnimo,

You mention a Dell white paper for setting up the Md3200 with ESXi 4.1    I have looked for it but can't find it.  Could you put the link to it here so I could get a copy?

 

Thanks.


 


Tags (3)
0 Kudos
mrokkam
3 Argentium

Re: MD3200i / ESXi 4.1 Multipathing problem

Jump to solution

www.dell.com/md3200i <--look on the right hand side

direct link: http://www.dell.com/downloads/global/products/pvaul/en/powervault-md32x0i-vmware-solution.pdf

Hope this helps,

-Mohan

 

0 Kudos
Solema
1 Copper

Re: MD3200i / ESXi 4.1 Multipathing problem

Jump to solution

Does the separate subnet requirement apply also to the SAN controller ports themselves, or just to the hosts?  What about for Windows 2008 R2 hosts?  I've spent over a week with Dell support trying to fix our awful SAN read speeds (6MB/s!) and still no solution.

I have two R710's with two iSCSI ports each, connected to an MD3200i with two 4-port controllers, all connected to two 5424 switches.  My config is as follows (Subnet Masks are all 255.255.255.0):

Switch 1:
All 192.168.130.x iSCSI traffic

Switch 2:
All 192.168.131.x iSCSI traffic

SAN
Controller 0:
Port 0: 192.168.130.101 (Switch 1)
Port 1: 192.168.131.101 (Switch 2)
Port 2: 192.168.130.103 (Switch 1)
Port 3: 192.168.131.103 (Switch 2)

Controller 1:
Port 0: 192.168.130.102 (Switch 1)
Port 1: 192.168.131.102 (Switch 2)
Port 2: 192.168.130.104 (Switch 1)
Port 3: 192.168.131.104 (Switch 2)

SERVERS
Server1:
Port 0: 192.168.130.51 (Switch 1)
Port 1: 192.168.131.51 (Switch 2)

Server2:
Port 0: 192.168.130.52 (Switch 1)
Port 1: 192.168.131.52 (Switch 2)

Now what I have found out is that if I DISCONNECT ports 2&3 on each controller, the SAN read speed jumps from 6MB/s to 230MB/s.  Can anyone shed some light on why this is and what I can do to permanently fix the issue?  Does it have anything to do with the fact that ports 2&3 on each controller share the same subnet as 0&1, respectively?

Thanks,
Nick

0 Kudos
Dev Mgr
5 Iridium

Re: MD3200i / ESXi 4.1 Multipathing problem

Jump to solution

You don't want to do this type of setup.

 

Change it to:

Switch 1:
All 192.168.130.x and 192.168.132.x iSCSI traffic

Switch 2:
All 192.168.131.x and 192.168.133.x iSCSI traffic

SAN
Controller 0:
Port 0: 192.168.130.101 (Switch 1)
Port 1: 192.168.131.101 (Switch 2)
Port 2: 192.168.132.101 (Switch 1)
Port 3: 192.168.133.101 (Switch 2)

Controller 1:
Port 0: 192.168.130.102 (Switch 1)
Port 1: 192.168.131.102 (Switch 2)
Port 2: 192.168.132.102 (Switch 1)
Port 3: 192.168.133.102 (Switch 2)

SERVERS
Server1:
Port 0: 192.168.130.51 (Switch 1)
Port 1: 192.168.131.51 (Switch 2)

Server2:
Port 0: 192.168.132.52 (Switch 1)
Port 1: 192.168.133.52 (Switch 2)

 

This way each server connects with each NIC only to one port on each controller (e.g. server 1 port 0 connects to 192.168.130.101 and 192.168.130.102, but not 192.168.130.103 and 192.168.130.104).

This also gives each server full redundancy and it's own iSCSI ports on the SAN to communicate with.

Member since 2003

0 Kudos
tcastantine
1 Copper

Re: MD3200i / ESXi 4.1 Multipathing problem

Jump to solution

Curiously, how does this look if you are adding a 3rd host to the mix?  You are kind of losing that 1-to-1 connection exclusivity.

0 Kudos
Dev Mgr
5 Iridium

Re: MD3200i / ESXi 4.1 Multipathing problem

Jump to solution

You have to double up on one of the two subnet-sets.

So server 3 would use 192.168.130.x and 192.168.132.x.

Member since 2003

0 Kudos
tcastantine
1 Copper

Re: MD3200i / ESXi 4.1 Multipathing problem

Jump to solution

That is what I figured.  So basically as you add hosts, you just have to manually balance the connections, spreading out the load.

Server 1 - SN 1+2

Server 2 - SN 3+4

Server 3 - SN 1+3

Server 4 - SN 2+4

Server 5 - SN 1+4

Server 6 - SN 2+3

And then start the cycle all over again?  Thanks for the quick reply!

0 Kudos
Dev Mgr
5 Iridium

Re: MD3200i / ESXi 4.1 Multipathing problem

Jump to solution

I usually don't bother with that type of rotation. I just keep it simple;

Server 1 - 130 & 132

Server 2 - 131 & 133

Server 3 - 130 & 132

Server 4 - 131 & 133

Where 130 + 131 are on 'iSCSI switch 1' and 132 + 133 are on 'iSCSI switch 2' with no connections between the switches. This way if 1 of the switches experiences a network storm or some other bad issue causing the switch to go down, the other switch is completely unaffected. In your list/example a switch issue could take down 1 or more servers, unless you opt to use 4 different physical switches for iSCSI.

Member since 2003

0 Kudos