What is the best practices to configure network connections in Hyper-V and Failover Cluster

What is the best practices to configure network connections in Hyper-V and Failover Cluster

Q: Our Dell R510 server comes with 4 NICs, what is the best practices to configure network connections in Microsoft Windows 2008 Hyper-v?

A: NIC 1: Assigned to parent partition for management; NIC 2: Assigned to parent partition for iSCSI NICs; NIC 3 and 4: Assigned to virtual switches for virtual machine networking.

Q: Our Dell R710 server comes with 12 NICs, what is the best practices to configure network connections in Microsoft Windows 2008 Failover Cluster?

A: It really depends on your environment. Here is the example we configured for one of our clients. 2 NICs as MGMTTeam: Assigned to parent partition for management; 3 NICs: Assigned to parent partition for iSCSI/SAN NICs; 3 NICs as VMTeam: Assigned to virtual switches for virtual machine networking; 1 NIC: assigned to Cluster Shared Volumes (CSV); 1 NIC: assigned Heartbeat; 1 NIC: assigned to LiveMigration. Note: there are 5 VLAN in the network. CSV, Heartbeat and LiveMigration are in the same VLAN, One VLAN is for SAN. Other 3 VLAN are domain network, student network and DMZ.

Post your questions, comments, feedbacks and suggestions

Contact a consultant