Windows Server 2022 Hyper-V VSwitch Teaming issue

Question

Hyper-V in Windows Server 2022 environment, we have more than one teaming but only 1 teaming NIC server as a Virtual Switch (VSwitch). Upon network disconnection and reconnection other teaming is normal, but teaming with VSwitch is issue with Fault LACP:

We have to do remove and add again NIC Team member to resolve the Fault LACP error.
Other Server with Windows Server 2016 and 2012 R2 is normal also, is there a bug in Windows Server 2022? Anyone experience this?

Answer 1

Hi Wahyudin,

Hope you're doing well.

If you specifically want LACP, follow these additional steps:

(1) First, create NIC teaming using Server Manager with LACP mode and dynamic load balancing.

(2) Execute the following PowerShell command to create the virtual switch based on the teaming:

New-VMSwitch -Name "VMSWITCH-1" -NetAdapterName "SR-LAG-1" -AllowNetLbfoTeams $true -AllowManagementOS $true

(3) Ensure that all your network cards are connected to the network and have valid IP addresses.

(4) Open Server Manager, select "Local Server," and under NIC Teaming, click "Disabled." Then click "Tasks" and choose "New Team" to configure NIC teaming.

(5) If you encounter issues with NIC teaming applying a private connection, try disabling one of the NICs and then re-enabling it.

I hope this helps resolve the issue!

Best Regards,

Ian Xue

---

If the Answer is helpful, please click "Accept Answer" and upvote it.