Update adds support for the slow timer in LACP in Windows Server 2012 R2

About this update

This article describes a hotfix that adds support for the slow timer in Link Aggregation Control Protocol (LACP) in Windows Server 2012 R2. Before you install this hotfix, check out the Prerequisites section. Additional steps are required to enable this hotfix after the installation.

Note The fast timer is already supported in Windows Server 2012 R2.

Hotfix information

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you have to have before you install this hotfix. For more information, see Add language packs to Windows.


A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that don't qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.

Prerequisites

To apply this hotfix, install update 2919355 on Windows Server 2012 R2. 

Registry information

To enable slow time-out, follow these steps:

Important Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restorationin case problems occur.

  1. In Registry Editor, locate and then select the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MsLbfoProvider\Parameters\NdisAdapters\<GUID>

  2. Press and hold (or right-click) <GUID>, select New, and then select DWORD (32-bit) Value.

  3. Name the new registry entry as LacpTimeout.

  4. Double-click the LacpTimeout registry entry.

  5. In the Edit DWORD Value dialog box, enter 0 in the Value data field, and then select OK.

  6. Exit Registry Editor.

Notes

  • When you set the LacpTimeoutregistry entry to a value of 0, the time-out value will be set to 90 seconds.

  • When you set the LacpTimeoutregistry entry to a value of 1, the time-out value will be set to 3 seconds.

  • After you set the registry key, you have to restart the NIC Teaming (LBFO) service by using the following commands. This causes a brief network disruption.

    sc stop mslbfoprovider
    sc start mslbfoprovider


Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix doesn't replace a previously released hotfix.

Status

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

References

See the terminology that Microsoft uses to describe software updates.

File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you run certain operations on the files.

Notes

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.18 xxx

    Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

    RTM

    GDR

  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

x64 Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Mslbfoprovider.sys

6.3.9600.18121

117,248

06-Nov-2015

22:20

x64


x64 Windows Server 2012 R2

File property

Value

File name

Amd64_d1b569ce33fa37fd43a4ecbfd6798ed0_31bf3856ad364e35_6.3.9600.18121_none_26702beb3df0b6a9.manifest

File version

Not applicable

File size

701

Date (UTC)

07-Nov-2015

Time (UTC)

11:12

Platform

Not applicable

File name

Amd64_microsoft-windows-ndis-lbfo_31bf3856ad364e35_6.3.9600.18121_none_02600dfdea9a21b5.manifest

File version

Not applicable

File size

21,621

Date (UTC)

07-Nov-2015

Time (UTC)

00:38

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,839

Date (UTC)

07-Nov-2015

Time (UTC)

11:12

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×