Windows Server 2008 R2-based NLB nodes remain in a converging state indefinitely

Article translations Article translations
Article ID: 978943 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You configure a Network Load Balancing (NLB) cluster by using some computers that are running Windows Server 2008 R2.
  • A cluster membership change starts the convergence process. For example, assume that a node is added or that a cluster is partitioned, and then the convergence process starts.
In this scenario, some NLB nodes remain in the converging state and cannot accept connections. Additionally, the following event log is added to the System log:

Source: NLB
Logged: <Time>
Event ID: 119
Task Category: None
Level: Warning
Keywords:
User: N/A
Computer: <computer name>
Description: NLB cluster [<IP or host name>]: The NLB driver has detected an inconsistency in the Extended Affinity configuration between cluster host <ID> and cluster host <ID>. A client IP address is on the Extended Affinity exception list on both hosts. You should run the Powershell cmdlet ‘Set-NlbClusterNode-Reload’ followed by ‘Start-NlbClusterNode’.

Note When this issue occurs, the Network Load Balancing Manager window or another monitoring tool reports that the state of the problematic node is in the converging state.

CAUSE

This issue occurs because both of the NLB nodes incorrectly enter into an infinitely converging state.

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain 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 do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, your computer must be running Windows Server 2008 R2. Additionally, the Network Load Balancing (NLB) feature must be installed.

Restart requirement

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

Restart the Windows load balancing service (WLBS) that hosts the Nlb.sys module by running the following sequence of commands:
  1. net stop wlbs
  2. net start wlbs
If you uninstall this hotfix, restart the computer or restart the service.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Nlb.sys6.1.7600.20608339,96804-Jan-201004:48x64
For all supported IA-64-based versions of Windows Server 2008 R2

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Nlb.sys6.1.7600.20608777,72804-Jan-201003:59IA-64

WORKAROUND

To work around this issue, restart the problematic NLB nodes.

STATUS

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

MORE INFORMATION

The following event is logged after you install this hotfix if the NLB diagnostic log is enabled:

Source: NLB
Event ID: 11
Level: Warning
User: N/A
Computer: <computer name>
Description: NLB cluster ghosted client <IP or hostname>. interface=<name>; port=<number>; bucket=<number>; otherhost=<id>.

Note By default, the NLB diagnostic log is disabled.

For more information about how to enable the NLB diagnostic log, visit the following Microsoft Web sites:
How to enable NLB diagnostic log
General information about the Network Load Balancing feature in Windows Server 2008 R2

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_eb981379c5c254f91a9efb950a3a8b77_31bf3856ad364e35_6.1.7600.20608_none_8d618bb9597d98c7.manifestNot Applicable72604-Jan-201022:35Not Applicable
Amd64_microsoft-windows-n..ncing-networkdriver_31bf3856ad364e35_6.1.7600.20608_none_0ae20a564af504dc.manifestNot Applicable2,66904-Jan-201012:30Not Applicable
Update.mumNot Applicable1,68904-Jan-201022:35Not Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ia64_306de8881bc6dd8fb12138a66c1a0253_31bf3856ad364e35_6.1.7600.20608_none_b7f30ee8c19f760e.manifestNot Applicable72404-Jan-201022:35Not Applicable
Ia64_microsoft-windows-n..ncing-networkdriver_31bf3856ad364e35_6.1.7600.20608_none_aec512c892959ca2.manifestNot Applicable2,66704-Jan-201007:57Not Applicable
Update.mumNot Applicable1,46104-Jan-201022:35Not Applicable

Properties

Article ID: 978943 - Last Review: January 26, 2010 - Revision: 1.0
APPLIES TO
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Datacenter without Hyper-V
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Enterprise without Hyper-V
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Standard without Hyper-V
  • Windows Web Server 2008 R2
Keywords: 
kbqfe kbhotfixserver kbsurveynew kbautohotfix kbexpertiseinter kbbug kbfix KB978943

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com