Windows Server 2022 Hyper-V VSwitch Teaming issue

Wahyudin Kurniawan 0 Reputation points
2024-06-07T02:57:39.1366667+00:00

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:

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?

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,521 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,613 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
974 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ian Xue (Shanghai Wicresoft Co., Ltd.) 33,301 Reputation points Microsoft Vendor
    2024-06-13T02:34:39.8633333+00:00

    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.

    0 comments