Windows Server 2012/2012R2 NIC Teaming Mode

Question

Hi,
Question 1:
In Windows Server 2012 the following teaming mode was recommended for Hyper-V NIC teams:
Teaming mode: Switch Independent
Load balancing mode: Hyper-V Port
All Adapers Active
In a session at TechEd 2014 it was stated that Dynamic is the new recommendation for Windows Server 2012 R2. However, a Microsoft PFE stated a few weeks ago that he would still recommend Hyper-V Port for Windows Server 2012 R2. What is your opinions around
this?
Question 2:
We have a Hyper-V Failover Cluster which isn`t migrated to 2012 R2 yet, it`s running 2012. In this cluster we use Switch Independent/Hyper-V Port for the team. We also use converged networking, having 2 physical adapters bound to the NIC team, as well as
3 virtual adapters in the management OS for management, CSV and Live Migration. Recently one of the team NICs failed, and this incident also caused the cluster membership on the affected node to go offline even though the other team NIC was
connected. Is this expected behaviour? Would the behaviour be different if 2012 R2 with Dynamic mode was being used?

Answer 1

Hello,
As for question number 1:
For Hyper-V workload it's recommended to use Dynamic with
Switch Independent mode. Why?
This configuration will distribute the load based on the TCP Ports address hash as modified by the Dynamic load balancing algorithm. The Dynamic load balancing algorithm will redistribute flows to optimize team member bandwidth utilization so individual
flow transmissions may move from one active team member to another.  The algorithm takes into account the small possibility that redistributing traffic could cause out-of-order delivery of packets so it takes steps to minimize that possibility.
The receive side, however, will look identical to Hyper-V Port distribution.  Each Hyper-V switch port’s traffic, whether bound for a virtual NIC in a VM (vmNIC) or a virtual NIC in the host (vNIC), will see all its inbound traffic arriving on a single
NIC.
This mode is best used for teaming in both native and Hyper-V environments except when:
1) Teaming is being performed in a VM,
2) Switch dependent teaming (e.g., LACP) is required by policy, or
3) Operation of a two-member Active/Standby team is required by policy. 
As for question number 2:
The Switch Independent/Hyper-V Port will send packets using all active team members distributing the load based on the Hyper-V switch port number.  Each Hyper-V port will be bandwidth limited to not more than one team member’s bandwidth because the port
is affinitized to exactly one team member at any point in time. 
In all cases where this configuration was recommended back in Windows Server 2012 the new configuration in 2012 R2, Switch Independent/Dynamic, will provide better performance.
Microsoft recommend for a clustered Hyper-V deployment
in Windows server 2012 to use Switch Independent/Hyper-V Port as you mentioned and to configure
Hyper-V QoS that applies to the virtual switch. (Configure minimum bandwidth in
weight mode instead of in bits per second and Enable and configure QoS
for all virtual network adapters 
Did you apply QoS on the Converged vSwitch after you
created the team?? However Nodes are considered down if they do not respond to 5 heartbeats. The Switch Independent/Hyper-V Port does not cause the cluster to goes down if one NIC failed. The issue is somewhere else and not in the teaming mode
that you choose.
Hope this help.
Regards,
Charbel Nemnom
MCSA, MCSE, MCS, MCITP
Blog: www.charbelnemnom.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if
a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.