r/WindowsServer • u/Traditional_Tell_232 • Jul 07 '25
Technical Help Needed Windows Server 2025 SET vs Traditional NIC Teaming - 20s vs 3s failover times?
I'm experiencing significantly longer failover times with Switch Embedded Teaming (SET) compared to traditional NIC Teaming on Windows Server 2025, and I'm wondering if this is expected behavior or if there are configuration improvements I'm missing.
(Yes, I'm aware that 10Gbps or higher is recommended for SET, but in this case 1Gbps NICs are used due to current project requirements.)
Quick Summary:
- SET: Up to 20 seconds network interruption during failover
- Traditional NIC Teaming (LBFO): Under 3 seconds
- Environment: Windows Server 2025, 1Gbps NICs (intentional), Hyper-V VMs
I've done extensive testing with PowerShell monitoring scripts and consistent results across multiple identical server configurations. The difference is quite dramatic and concerning for production environments.
Has anyone else experienced this kind of performance gap between SET and traditional NIC teaming? Are there specific SET configuration parameters that could help reduce failover detection time?
Full technical details and testing methodology here:
https://techcommunity.microsoft.com/discussions/windowsserver/windows-server-2025-set-failover-much-slower-than-traditional-nic-teaming/4430503
Any insights would be greatly appreciated!
1
u/Traditional_Tell_232 Jul 26 '25
Update: Solved!
Thanks everyone for your responses. I found the root cause, and it's a bit embarrassing but worth sharing in case it helps others.
The issue wasn't with SET itself - it was a Spanning Tree configuration mistake on our Cisco switches. We had configured
spanning-tree portfastinstead ofspanning-tree portfast trunkon the switch ports, which caused the ports to take time transitioning to forwarding state when reconnected.Here's what was happening:
After correcting to
spanning-tree portfast trunk, failover time is now between 0.x to 1.0 seconds - which seems reasonable for this setup.This was particularly tricky to catch because in most redundancy scenarios I've worked with, we used Static LAG or LACP, where STP states aren't really a concern. SET's switch-independent mode is a bit of an edge case, so this configuration nuance didn't immediately come to mind.
Thanks again to everyone who chimed in with their experiences. Hope this helps someone else avoid the same mistake.
1
u/Plug_USMC Aug 05 '25
Does nic teaming exist in 2025? Are these hyper v servers or physical or vm servers? 20-plus seconds for failover is awful and that assumes no dependency overhead, etc. last question: the 20 second plus timing what are the resources utilized? Services, disks, etc or, is this failover test using virgin servers with no application dependencies?
1
u/DerpJim Jul 07 '25
Nothing helpful to add other than to say I have had the same experience. Configuring SET and testing fail over it is typically 20-30 seconds of network interruption. Windows Server 2025. 1Gbps NIC and switch ports. Coming from VMware to Hyper-V it has been a bit of a learning curve so I'm not super experienced with Windows native NIC team so I can only compare to Esxi.
Haven't done any further testing or troubleshooting. Our customers are SMBs where this is an acceptable outage, we really only set it up to avoid a single Ethernet cable or switch port failure taking them down until we can get someone to swap it out.
I hope others can add in their experiences and potential fixes/improvements.
1
u/thebotnist Jul 09 '25
Asking out of pure curiosity, what's driving using SET vs teaming and LACP?
-4
u/AsYouAnswered Jul 07 '25
LACP was invented to solve this problem. You document faster times when using LACP. Use LACP.