LACP Timer is configured incorrectly when you create a new NIC Team for LBFO in Windows Server 2016

Applies to: Windows Server 2016Windows Server 2016 StandardWindows Server 2016 Datacenter More

Symptoms


In Windows Server 2016, there's a new feature that lets administrators configure the Link Aggregation Control Protocol (LACP) timer in either a "Fast" or "Slow" mode, depending on the device. 

When you create a NIC Team for Load Balancing and Failover (LBFO) on Windows Server 2016 by using the New-NetLbfoTeam cmdlet, and you define the LACP Timer as Fast, the LBFO team that's created is configured with a Slow LACP Timer instead.

Workaround


To work around this issue, use the Set-NetLbfoTeam cmdlet to make the LBFO team use the correct LACP timer.

For example:
Set-NetLbfoTeam -LacpTimer Slow

Reference


For more information about how to use New-NetLbfoTeam cmdlet, see New-NetLbfoTeam.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.