Networking Setup for MSCS

[msemon1]

Looking at best practices for setting up networking with Microsoft Cluster Services. We are running ESX 3.5 U3. Each ESX host has 6 NICS and a dual port HBA. Looking at setting up as follows for each ESX host:

vSwitch0 -

---

> NIC 0

Service Console NIC1

vSwitch1 -

---

> NIC3

VMKernel NIC4

vSwitch2 -

---

> NIC5

Virtual Machine Network NIC6

For setting up the public and private network, would I create a port group on each host for the public and private network with 2 vmnics? What should this look like? Also the cluster documentation says NIC teaming is not supported, however, I believe that is.

Thanks,

Mike

[DPike]

Private networks require no vmnics to be connected. The ESX host will route traffic only inside that switch with no outbound connection...used mainly for cluster heartbeat for MSCS. For this, just create a new vSwitch with a port group called 'Cluster Heartbeat' and bind the virtual nics for private networking from that VM to that vswitch.This is for setting up a Cluster in a Box.

If you are Clustering across boxes, you will need a vmnic connected. For this, just create a new vSwitch with a port group called 'Cluster Heartbeat' and bind the virtual nics for private networking from that VM to that vswitch. Then add vmnics that are connected to the private physical network.

For the public, you create it just like the others. You can use a new vSwitch or an existing, depending on how your network is setup. From there you can attatch multiple vmnics to create redundancy. Make sure these vmnics are connected to the public networks required in the physical network.

As far as NIC teaming, do you mean teaming inside the Windows OS or on the ESX host?

_________________

Dustin Pike

Wintel and ESX Admin

VCP3

[msemon1]

So then would it be unnecessary to create a virtual NIC for the private network (Hearbeat) if the public and private networks are on the same virtual switch? Which port group would be used for the public and private, VMkernel? The NICS are teamed on the ESX host and not within the Windows OS.

[msemon1]

Perhaps it shoud like this:

vSwtich0 NIC0, NIC1

Service Console

vSwitch1 Private (Heartbeat) NIC2 ,NIC3

vSwtich 2 Public NIC4,NIC5

I could reconfigure my vitual swtiches this way since I already have 3 pairs of teamed NICS. Only seems like a waste of NICS on redundancy for Private Network and Service console.

[AndreTheGiant · Accepted solution]

With MSCS NIC redoundacy is not required, but I suggest to use at least for "public" net.

The "private" net could be another portgroup on the same vSwitch of the "public" net, or could be a portgroup on another vSwitch.

If you have VLAN you can isolate it, but is not strictly required (although is a good security practice).

Andre

[msemon1]

Since I have 6 NICS to work with would this be preferrable?

vSwitch1 Service Console

NIC0

vSwtich2 Private Network

NIC1

vSwitch2 Public Network

NIC2

NIC3

NIC4

NIC5

[AndreTheGiant]

I suggest to have 2 NIC for SC.

You do not have VMotion? Or IP storage?

Andre

[msemon1]

We don't have IP Storage since we are using FC. Can you use VMotion with MSCS? I thought VMotion was a limitation with MSCS. Maybe it is just cold migration or SVMotion that is not allowed with MSCS.

[AndreTheGiant]

Can you use VMotion with MSCS?

No... but for other VMs yes

Andre