Nov 09 2022 12:28 AM
Starting with Windows Server 1903 and 1909, Hyper-V virtual switches on an LBFO-type network adapter cluster are deprecated (see documentation). The technology remains supported, but it will not evolve. It is recommended to c...an aggregate of type SET.
The SET is a very interesting technology that has some constraints. The interfaces used must have identical characteristics:
Even if these constraints do not seem huge, we are very far from the flexibility of LBFO Teaming. As a reminder, this one has absolutely no constraints.
In practice the SET is recommended with network interfaces of 10Gb or more. Therefore, we are very far from the target of the LBFO (use of all integrated boards with motherboard pro, Home Lab, refurbish).
As of Windows Server 2022, it is not possible to use the Hyper-V Management Console to create a virtual switch with LBFO, as it will prompt an error saying that LBFO have been depreciated. However, it is possible to use PowerShell to create this virtual switch.
First, create the Teaming of your network cards using the Server Manager, in my case the teaming will be with LACP mode and Dynamic load balancing mode.
Then execute the below PowerShell Command to create the virtual switch based on the teaming created in the previous step:
New-VMSwitch -Name "LAN" -NetAdapterName "LINK-AGGREGATION" -AllowNetLbfoTeams $true -AllowManagementOS $true
In detail:
You will see your network teaming up and running on Hyper-V host.
Thats it!
Sep 29 2023 05:36 PM
Sep 30 2023 11:42 PM
@evermall refer again to my blog post to check if you missed any step
Bypass LBFO Teaming deprecation on Hyper-V and Windows Server 2022 | LinkedIn
Oct 01 2023 10:46 PM
I followed every steps. Enable and created a network teaming, Even copied the same network teaming name but i got an error when firing the powershell command
Oct 02 2023 01:28 AM
@evermall lets try to remove the IPv6 from the teaming and open the PowerShell as admin and let the path be Windows/system32.
Mar 08 2024 06:07 AM
@eliekarkafy
Many thanks for the assist, glad there is a way to bypass this.
Am setting up a server where I wanted Hyper-V to have exclusive access to a 10gbps network card but wanted that card to have a backup 1gbps network card setup in teaming.