Windows 10 NIC loadbalancing - LACP

faxfan · 29 Dec 2015 at 10:15

All,

Has anyone played with Windows 10 NIC load balancing, specifically the powershell "netlbfoteam" command to create new links?

Specifically I'm struggling with LACP to work. I have a LACP capable switch (Cisco 3560 CX, IOS 15.2) and I've configured it work with Windows Server 2012 NIC load balancing with LACP - so I'm pretty confident the switch configuration should *work* with Windows 10.

However when I enable LACP teaming in Windows 10 the switch just reports that "LACP currently not enabled on the remote port".

Anyone got this working at all on Windows 10?

lude1962 · 29 Dec 2015 at 10:53

do you have to configure the switch ports your using (win 10) to use LACP?

-TeamingMode<TeamingModes>
SwitchIndependent option?

Caged · 29 Dec 2015 at 11:08

What makes you think it will work in Windows 10? Everything I can find points to it being a Server-only feature.

https://www.microsoft.com/en-us/download/details.aspx?id=40319

That document is slightly out of date but mentions the PowerShell commands exist in the client OS only for managing teaming on a remote server.

bledd · 29 Dec 2015 at 11:22

This feature is currently broken in w10 and server 2016.

I guess when they fix it for 2016,it will work again for w10.

For now you have to do it on a driver level.

faxfan · 29 Dec 2015 at 12:32

Lots of references to it working on Windows 10 via google and indeed it does work if you the teaming mode is set to Static or Switch Independent. Just want to get LACP functioning.

bledd · 29 Dec 2015 at 12:39

It worked in the RTM version, but it's broken in the latest. I'll find the link I read for you..

faxfan · 29 Dec 2015 at 12:48

bledd. said:
It worked in the RTM version, but it's broken in the latest. I'll find the link I read for you..

It's certainly working in anything but LACP teaming (Windows 10, build 10240)

bledd · 29 Dec 2015 at 13:31

https://social.technet.microsoft.co...ing-on-server-2016-tp4?forum=WinServerPreview

new-netLBFOTeam -name TEAM1 -TeamMembers "Ethernet", "Ethernet 2" -TeamingMode LACP

This command is broken in builds after 10240 and Server 2016 Preview. They will fix it.

faxfan · 29 Dec 2015 at 15:12

Oh, good spot, think I must have seen every other TechNet article but this one. The command actually works but doesn't actually do anything i.e. LACP doesn't work. Anyway I shall stop buggering around trying to get it work then...