I have seen many recommendations to set the network binding order on you Hyper-V hosts to something similar to:
- Management NIC
- Cluster NICs
- iSCSI NICS
However, all of these recommendations are for scenarios where the NICs are all physical NICs in the host.
Using Server 2012 R2, I am building converged networks with logical switches, NIC Teams, and vNICs on the host. So when I go set the network binding order, I now have all these components to deal with as well. For example, on a 4 adapter blade, I might typically have the following items in the binding order drop-down.
- 4 - physical NICs (2- teamed for the 1 virtual switch, the other 2 used for iSCSI)
- 1 - Team interface (Datacenter_Switch)
- 5 - vNICs (Management, Cluster, LiveMigration, iSCSI-1, iSCSI-2)
So, should you only worry about order of the vNICS (placed at the top) and let the other components just fall to the bottom of the list? This seems to be likely to me, since the binding order applies to service access to the resources, and the other components are not being directly accessed by network services?
Or, should the order start out with the physical resources needed to access the vNICs, followed by any intermediate resources (switches or team interfaces, then the vNICS themselves, to ensure that the resources are available to the subcompnents accessing them?
Any help would be appreciated.
Thanks.
-Tim Reid