Forum Discussion

brichan's avatar
brichan
Brass Contributor
Mar 09, 2023

[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.

 

 

 

 

 

 

 

 

 

New-VMSwitch -Name SETSwitch -NetAdapterName "i350t4_1","i350t4_2","i350t4_3" -AllowManagementOS $true -EnableEmbeddedTeaming $true -EnableIov $true
Set-VMSwitchTeam -Name SETSwitch -LoadBalancingAlgorithm Dynamic

 

 

 

 

 

 

 

 

 


In that case, the Hyper-V VM and OS can be accessed normally, but when I restart Windows Server, all Adapters disappear from SET Teaming and are changed to the Internal setting, and network access is lost.

The above logs were obtained at WPR with Profile in Network.
Since the file is large, I will post a link to OneDrive.

setTeamingTrouble.etl

https://1drv.ms/u/s!AoGvAA_XXMTH-dJ2gkOa6E5hP4QhLg?e=7hPgLQ

 

In addition, if the EnableIov option is set to $false, a BSOD (KMODE_EXCEPTION_HANDLED) will occur after the Switch is created.
VMSWITCH.SYS

0x0000007e (0xffffffffc0000005, 0xfffff80643a95c61, 0xffffb28989f2a6d8, 0xffffb28989f29ef0)

 

Addition 2:
LBFO Teaming is working properly.

 

I tried to send it through the Feedback Hub and could not get it to work, so I have included it here.

 

Addition 3:
Server 25324 LBFO Teaming with New-VMSwitch failed.

 

management
Networking
  • krasiaa123's avatar
    krasiaa123
    Copper Contributor
    Feb 16, 2025

    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.

    • brichan's avatar
      brichan
      Brass Contributor
      Feb 16, 2025

      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.

      • krasiaa123's avatar
        krasiaa123
        Copper Contributor
        Feb 22, 2025

        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

    • brichan's avatar
      brichan
      Brass Contributor
      Mar 09, 2023

      Thanks for the reply.
      In the meantime, LBFO Teaming can work fine and we usually do it that way.
      However, I get warnings with every Windows Insider update, which is inconvenient to be honest.
      I would like to be able to use SET Teaming normally, as SET Teaming worked in the same environment in a build a while ago (I lost the build number) and the performance was better than LBFO Teaming.

       

      Addition:
      How many years has it been since SET Teaming was implemented?
      How long will you leave it halfway?
      And if you are going to leave it half-assed, isn't there a need to deprecate LBFO?
      I have nothing but questions about the Server Team's policy.

Resources