大网数据广告活动
网络与域名解析

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

· 52CE 我爱测

Describes an issue that misconfigures the LACP Timer when you create a new NIC Team for LBFO in Windows Server 2016. A workaround is provided.

This article describes an issue that Link Aggregation Control Protocol (LACP) Timer is configured incorrectly when you create a new NIC Team for LBFO in Windows Server 2016.

Applies to:   Windows Server 2016
Original KB number:   4014014

Symptoms

In Windows Server 2016, there's a new feature that lets administrators configure the 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.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。