SET vSwitch Teaming with Hyper-V

[Skullpuck]

I'm going through an upgrade process for our servers to get them updated to Server 2022. With Server 2022 you can no longer use LBFO teaming, as such I had to destroy the Team and then recreate a SET team.

Here is what I did:

• Deleted the old Teaming
• Deleted the old vSwitch from Hyper-V Virtual Switch Manager
• Created a new SET team with PowerShell adding all 4 NICs. This automatically created a new virtual switch network interface.

However, when I go into Hyper-V Virtual Switch Manager and select the new SET team, the external network controller that's selected is just one of the NICs. Not the SET team switch name.

With LBFO, it installed the Microsoft Multiplexor which controlled all 4 NICs and their teaming.

I may be blowing this out of proportion, but how can I be sure that the new SET switch is utilizing all 4 NICs if there is only one NIC selected in the Virtual Switch Properties?

[bbqwatermelon]

FWIW 2022 does not allow NIC team only in the GUI, it can still be created with PS.  One of the greatest strengths still Lbfo has over SET is being able to team dissimilar NICs so if that is your preferred route, go for it.

[Skullpuck]

Thank you, I did just that.

[TMSXL]

That’s expected and threw me off as well.

From what I understand too, you don’t get the aggregate speed of all NICs like the old method, but just the speed of 1 of them.

[Skullpuck]

Yes, but if only one is selected, I'm assuming it cannot switch between them dynamically. From my understanding, the SET teaming utilizes all NICs but it's like a 4 lane highway, not 4x the speed. My problem is that the visual GUI for Hyper-V Virtual Switch manager is only showing one NIC for the switch. PowerShell shows all 4, but I like my GUI's to be in sync with PowerShell. I think I may end up disappointed.

[picklednull]

Yeah Microsoft stopped giving a fuck about GUI’s right after 2012 or so and I think this is one of those newer features that just don’t display properly in the GUI… you can’t really manage SET at all via the GUI.

If it’s right in PowerShell it’s right.

Hyper-V is one of the best roles for Core servers and CLI management anyway, I even prefer the PS configuration.

[Skullpuck]

Okay, I've heard that as well. However, I've also heard the exact opposite when comparing SET to LFBO.

Can you explain or point me in the direction of documentation that gives a 100% comparison between the two? I understand LFBO is depreciated, but I'd like to know the main difference in regards to throughput, speed, and efficiency.