VMware Network Configuration Help

[davemayo]

I am doing my first vSphere deployment, and I am wondering if this is a good strategy to go about doing this configuration. First I will list the current hardware we will be using;

1) Dell R710 4xGB TOE NICS 4xGB NICS (8 Total, 4 TOE, 4 NON-TOE)

2) Dell R710 4xGB TOE NICS 4xGB NICS (8 Total, 4 TOE, 4 NON-TOE)

3) EqualLogic PS4000XV iSCSI SAN

4) PowerConnect 6224 L3 Switch

I plan to use an IP address structure of 10.80.0.1/22. My plan for the networking setup is as follows;

VLAN 101 - iSCSI Traffic 10.80.4.x/22

VLAN 102 - VMotion 10.80.8.x/22

Production Network 10.80.0.x

vSwitch0 - Management Interface 10.80.0.5

- VMNetwork

vSwitch1 - VMKernel - ISCSI Traffic 10.80.4.x/22 (VLAN 101)

vSwitch 2 - VMKernel VMotion - 10.80.8.x/22 (VLAN 102)

I have a couple questions regarding this configuration. I know its recommended to have two switches but as of right now its just not in the budget so I have to work with what I have and use VLANs. Does the VMotion VMKernel port have to be on a seperate network segment because I ran into issues putting iSCSI traffic on the same network segment but under a different VLAN.

Also, if putting the iSCSI traffic and VMotion traffic under a different subnet/segment will I run into any issues? Please let me know anything you see wrong or if I did not go into as much detail as I should have.

[marcelo_soares]

If you will place VMotion and iSCSI traffic on different VLAN's (in this you are totally right) place the VMkernel IP's on different network segments, or you will not be able to VMotion or access your storage (or vice-versa). The ESX do not communicate with simultaneous interfaces when the IP of both are on the same segment.

But all the configuration seems fine.

Marcelo Soares

VMWare Certified Professional 310/410

Technical Support Engineer

Globant Argentina

Consider awarding points for "helpful" and/or "correct" answers.

[davemayo]

Okay, yes I remember your wisdom from last night, haha. Yes that does make sense they do have the be on separate network segments. So continuing with this configuration shouldn't be a problem when I go to use VMotion, could you explain to me how they are able to VMotion when technically the VMKernel VMotion port is on a different segment and VLAN than the SAN?

[AndreTheGiant]

If you use different NIC for iSCSI and other traffic you can minimize the problems.

Remember that hardware TOE is not used by ESX, so you can mix one on-board NIC with one additional NIC.

And also check on Equallogic site the document with the best practice for vmkernel configuration for iSCSI.

Andre

[davemayo]

Hi Andre,

Sorry maybe I wasn't clear enough, I do plan to use a different NIC for ISCSI and a different NIC for VMotion. I plan to NIC team two NICs on the ESXi host for iSCSI. On the switch I plan to create a 4 port LAG for the iSCSI VLAN.

VLAN 101 - iSCSI (4PORT) LAG

ESX Host - 2x1GB NIC (Teamed) iSCSI Only. Seperate vSwitch entirely.

[davemayo]

So, I recieved a document from Dell, with Andre's advice. I found a great document on how to configure VMWare with a Dell EqualLogic system. They are telling me to create up to 6 VMKernel ports on a single vSwitch! I believe they do this for Native VMWare Multipath I/O.

If I look at what they are telling me.

My SAN has two active 1Gbps ports for iSCSI traffic, so why do I need so many ports?

[AndreTheGiant]

Remember to do not use LAG or Etherchannel on iSCSI NIC ports.

Follow the Dell documents and it will works fine.

Andre