Question: Two NIC teams or one?
Specifics:
I am considering two scenarios. The first because I want to control everything through software/logical means and the second because I think the first scenario is not Microsoft best practice.
1) Create one eight member NIC team using LACP/Dynamic hashing. Create multiple team NICs (tNICs), each on their own VLAN as required, binding the default tNIC (default VLAN) to a v-switch to be managed by Hyper-V. I would then use the other tNICs for the various management, storage, etc. VLANs that the host uses.
or...
2) Create two NIC teams, one for host traffic and one to be bound to Hyper-V. I do not like this as much because it does not allow bandwidth be be as dynamically used as the first scenario (in theory) since I have to provision the amount of physical NICs ahead of time. More chance to over/under subscribe either of the teams.
I know the second scenario is supported based on documentation, blogs etc. but I have not read anything about the first possibility.
Thoughts?
Specifics:
I am considering two scenarios. The first because I want to control everything through software/logical means and the second because I think the first scenario is not Microsoft best practice.
1) Create one eight member NIC team using LACP/Dynamic hashing. Create multiple team NICs (tNICs), each on their own VLAN as required, binding the default tNIC (default VLAN) to a v-switch to be managed by Hyper-V. I would then use the other tNICs for the various management, storage, etc. VLANs that the host uses.
or...
2) Create two NIC teams, one for host traffic and one to be bound to Hyper-V. I do not like this as much because it does not allow bandwidth be be as dynamically used as the first scenario (in theory) since I have to provision the amount of physical NICs ahead of time. More chance to over/under subscribe either of the teams.
I know the second scenario is supported based on documentation, blogs etc. but I have not read anything about the first possibility.
Thoughts?