Virtual Networking for a Microsoft Cluster Server

[sfortuna74]

Hello -

We were having a team discussion about Microsoft Clustering in a VI 3.5 environment a bit earlier and I was stumped on something. When creating a 2 node active\passive Microsoft cluster in VI 3.5, what is the best approach when setting up the virtual network, specifically with regards to the private cluster network? Is the best approach to create a dedicated vswitch for the private cluster heartbeat network, or would a port group on the same vswitch as the other ip's work just as well??

Thanks in advance fo the help -

Steve

[weinstein5]

At a minimum I would set up a vlan for the heartbeat but would prefer having an isolalted network to reduce the risk of network problems causing a failover - check out this document for more information on MSCS set up best practices - http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_mscs.pdf

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful

[AndreTheGiant]

Is the best approach to create a dedicated vswitch for the private cluster heartbeat network, or would a port group on the same vswitch as the other ip's work just as well??

If you use a dedicated vSwitch you will need at least 1 (2 is better) dedicated physical NIC.

For this reason usually it is used a new portgroup (maybe with a different VLAN) on an existing vSwitch.

Remember also to use un MSCS also the public network to do heartbeat (so you have a dual check).

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[kjb007]

Since the clustered nodes can be on different nodes, you need a real vlan for the heartbeat traffic to traverse over. For this, I have in the past piggyback'd on my management or public switch, and used a completely different subnet than what is running on that switch. You can configure a 2nd interface on that same portgroup as public, and give it a 2nd non-routed IP, or configure a portgroup that is on the same segment as your management subnet, and configure an IP address on that 2nd NIC.

For example, I have my public interface on 10.1.1.x, and on that same portgroup, 2nd NIC, I'll configure a 10.2.2.x IP address for heartbeat. It saves having to add an additional NIC just for heartbeat traffic, but I've used that as well. Depends on your requirements for network isolation.

-KjB

VMware vExpert