Forum Discussion
[server 25314] External SET Team to Internal after Reboot.
I have created SET Teaming on Windows Server 25314 (actually from a previous build) using External and 3 Intel i350-T4 ports, configured for Hyper-V and external access. ...
Hi, I’m currently dealing with the exact same issue, and funnily enough, not only am I completely unable to connect to my servers, but I’m also beyond frustrated.
This has now happened multiple times in my Windows Server 2025 Hyper-V failover cluster, and each time, the only way to fix it has been to recreate the SET switch from scratch. Have you found any workaround or potential fix? This is becoming a serious problem for me, and I haven't come across any useful information so far.
We have not found any solution at all and there is no information on any change of policy.
If the problem is caused by SET, I guess it means that you should use a faster interface, such as 40gbE or 100gbE.
I have nothing but doubts about the Windows Server Team's response.
That's unreal.
I am using QLogic 57xxx 1gb interfaces (x4) on a PowerEdge R610 (I know it's old).
But it's unreal, currently I am stuck at this, I can't do SET, I am limited to use a single interface or live in fear in case power goes out that my SET switch will explode and I have to reconfigure it again.
The worst part is that I've upgraded all VM hardware configuration to Hyper-V 2025, and I can't even rollback.
aaaaaaaa
