My Hyper-V SET team experiences periodic port shutdowns without any physical link failure. Ports shut down on their own. How can I adjust switch and team configurations. Host is on Hyper-V infrastructure.

Haziq Salleh 40 Reputation points
2026-09-16T06:54:49.3533333+00:00

A Hyper-V SET (Switch Embedded Teaming) team on the host is experiencing periodic port shutdowns without any physical cable disconnection. Some ports are shutting down after a specific time interval, while some ports have disconnected and reconnected 2-3 times. Multiple port state changes confirmed in Windows Event Viewer and switch logs verify the unexpected shutdowns. The connected switch ports were configured for static LACP aggregation instead of independent switch ports, confirming the issue is a configuration mismatch rather than a hardware level failure.

Windows for business | Windows 365 Enterprise
0 comments
Answer accepted by question author
Xuan Nhu 1,050 Reputation points Independent Advisor
2026-09-16T07:26:59.6866667+00:00

Hello Haziq,

The physical switch configuration is the first thing I would correct. Switch Embedded Teaming (SET) supports only Switch Independent teaming mode; Set-VMSwitchTeam exposes SwitchIndependent as the only supported teaming mode. Therefore, the physical switch ports connected to the SET members should not be configured as a static LAG/LACP port channel.

Configure the upstream switch ports as independent ports, while keeping the required VLAN/trunk configuration consistent on each port. Then verify the SET configuration and physical adapters:

Get-VMSwitchTeam -Name "YourSETvSwitch" | Format-List * Get-NetAdapter | Format-Table Name,Status,LinkSpeed,InterfaceDescription Get-NetAdapterStatistics

You can also verify or explicitly configure the load-balancing algorithm with:

Set-VMSwitchTeam -Name "YourSETvSwitch" -TeamingMode SwitchIndependent ` -LoadBalancingAlgorithm Dynamic

Dynamic and HyperVPort are load-balancing choices, but neither changes the requirement that SET operates in Switch Independent mode.

Since Event Viewer and the switch logs show ports changing state without a physical link loss, remove the static aggregation configuration first and monitor again. If the issue continues afterward, I would then investigate NIC driver/firmware versions, switch logs, VLAN configuration, and the output of Get-VMSwitchTeam rather than treating it as a physical-link failure.
https://learn.microsoft.com/en-us/powershell/module/hyper-v/set-vmswitchteam?view=windowsserver2025-ps

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Oldest
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.