1

I am not a network admin but I am trying to pretend to be one. I have a server with two 1 gig nic cards. I wanted better through put so I teamed the cards together. I am now trying to create a virtual switch that I can use when I set up VMs on this machine (hyper-v). The teamed switch is not listed in the External network drop down, but the Microsoft Network Adapter Multiplexer is. If I try to select that option I get an error message about LBFO team is deprecated.

If I select one of the physical nics then I get an error that a protocol on the network adapter prevented it from binding to the virtual switch.

The nic team works great for the physical server, but I do not seem to be able to use it on the virtual switch. Suggestions?

3 Spice ups
2

LBFO is being deprecated and SET is what replaces it. Give this a read and it will explain it and how it relates to HyperV

Also remember when asking a question like that, you will save time if you give out the basic information of what Server OS you are using. In some cases, the server hardware and nic type is helpful as well. General rule, more info is always better than less.

3 Spice ups
3

LBFO Teaming is depreciated in Server 2022 requiring PowerShell command to create instead of GUI. I understand that the command line option is disabled too in Server 2025.

SET replaces LBFO Teaming but no longer supports LACP – only switch independent mode.

3 Spice ups
4

Wait… I am a bit lost ??

In Hyper-v server (2019 or earlier) and ESXi, we can create vSwitches with 1 or more physical NICs.

Then in VMs (or even physical servers), we can also create NIC teaming such that the OS can have 2 or more NICs using only 1 IP address ?

But if in Server 20xx with Hyper-v role, can we add “teamed NICs” as NICs to vSwitch ?

1 Spice up
5

The OP wants a vSwitch to use a teamed network setup on the host, to do this on Hyper-V you need to use SET, as already covered.

Since this isn’t about ESXi and that works a lot simpler, it’s best not to confuse with how Hyper-V works.

Yes, see the links above.

1 Spice up
6

Hyper-v or Server 20xx with hyper-v role ??

Coz I remember someone here ever told me that Server 20xx with hyper-v role does not need vSwitch for VMs, unlike Hyper-v server or ESXi ?

1 Spice up
7

I’m not sure if you’re misread something, but a vSwitch needs to be there and used, even if it’s for host only traffic.

vSwitches on Hyper-V do not use VLAN tags, those are done at the VM level, but a switch is still required.

1 Spice up
8

I hope I did…

1 Spice up
9

The simple view of teaming in hypervisors is: the main use is for resilience and redundancy. Secondary benefit of additional throughput is only realised with a high number of VMs.

It is better to use faster NICs over more slower nics.

ESXi still supports Link aggregation. Hyper-V does not - but Hyper-V now supports RDMA and other sdn stack features in SET that have greater benefit.

Simply put this is a non-issue in Enterprise as highly converged servicers will typically have multiples of 25gig or higher NICs. Network throughput is not typically a bottleneck, storage and vm production traffic is often separated if throughput could be congested.

I feel the pain as in SMB land a server with multiple 1 gig NICs is still common.

1 Spice up
10

Thanks for all of the information. I was able to resolve my issues by setting up a SET team and using that on the v-switch.

2 Spice ups
11

Awesome, thanks for following up.

1 Spice up
12

Please mark the topic as solved by selecting a best answer to the poster who best helped solve your issue

1 Spice up