Just a quick note to share my experience in NIC teaming algorithm with 2012 R2 hosts and Hyper-V and hopefully dispel some myths..
Many documents/blogs recommend the load balancing algorithm to be Dynamic by default. In my experience this is not the optimal configuration.
For NIC teams that are used for VM Guest networking, the Load Balancing Algorithm should be set to Hyper-V Port by default.
Every Hyper-V environment I have built in the last few years has performed significantly better using Hyper-V Port as the preferred load balancing algorithm.
Had a quirky one recently where by a client was rebuilding a NVGRE gateway (as per this post) failed with the below warning.
Warning (26926)
Unable to set up Remote Access server to support multi-tenancy mode. (Remote Access server and the host are not configured for multi-tenancy.
Fix the issue in Remote Access server and retry the operation.).
Recommended Action
Fix the issue in Remote Access server and retry the operation.
Fast publish… will revisit later
Scenario:
Existing NVGRE gateways manual deployed. Working fine for ages. NAT resources failed to come online HyperV Network Virtualization Gateway role failed
FOCM below
Cluster resource xxxxxxxxxxxxxxxxxx of type ‘Nat’ in clustered role ‘HyperV Network Virtualization Gateway’ failed
The Windows NAT Driver service failed to start due to the following error:
The property set specified does not exist on the object
So, I decided I wanted to rebuild my gateways and reconnect them… but how?