Hello,
I'm having this difficulty to create multiple external vSwitches using NIC teaming. SwitchIndependent
is the only option I can utilize since I just have one Layer 2 switch. With LoadBalancingAlgorithm i'm leaving it to PowerShell (-WhatIf usually report it will use 'TransportPort' if no algorithm specified to determine that
for me, since the objective is to be able to carve multiple external switches (for management, VMs traffic,
clustering etc) using NIC teaming based on only two physical NICs in server.
Hyper-V Server 2012 R2 has identical 2x GBoE NICs installed. Say NICs are named GBNIC1/GBNIC2. They both are connected to same switch. First I create a NIC teaming using following:
1. Create NIC team using GBNIC2/GBNIC2
new-NetLbfoTeam -Name TestTeam -TeamMembers GBNIC1,GBNIC2
Above command results in a team; having a teamed NIC with name "TestTeam". Now this team is ready to host external switches.
2. Create external switch based on teamed NIC "TestTeam"
Next I would like to create an external switch. 1st external switch is created using following command:
new-VMSwtich -Name e-vSwitch1 -NetAdapterName TestTeam -AllowManagementOS 0
Above command results in an external switch created fine.
3. Create additional external switch based on same teamed NIC "TestTeam"
After 1st external switch "e-vSwitch1" is created, repeaing same command in step2 with a different value for -Name (for example "e-vSwitch2") it complains stating the "TestTeam" interface is already bound to another exetrnal
swtich.
Question: Can we not create more than 1 external switch using NIC teaming ? was this not the purpose of NIC teaming; to be bale to carve out multiple external networks and breaking free from one external swtich--to--one physical NIC in host?
Please advise where/what is wrong?
Regards,
Shahzad.