NLB Extended Affinity Configuration

Updated: November 25, 2009

Applies To: Windows Server 2008 R2

In a Network Load Balancing (NLB) cluster, port rules are configured to control how each port's cluster network traffic is handled. One of the settings for port rules is whether extended affinity is enabled. The NLB cluster may fail to converge unless the extended affinity setting on each port rule is identical on all cluster hosts.

Events

Event ID Source Message

118

Microsoft-Windows-NLB

NLB cluster [%2]: The NLB driver has detected an inconsistency in the extended affinity configuration on cluster host %5. The host received an invalid entry from another cluster host, which may be caused by an improper configuration. Use Network Load Balancing Manager to configure NLB, and once the configuration is fixed, run the PowerShell cmdlet 'Set-NlbClusterNode -Reload' followed by 'Start-NlbClusterNode'.

119

Microsoft-Windows-NLB

NLB cluster [%2]: The NLB driver has detected an inconsistency in the extended affinity configuration between cluster host %5 and cluster host %6. A client IP address is listed on the extended affinity exception list on both hosts. You should run the PowerShell cmdlet 'Set-NlbClusterNode -Reload' followed by 'Start-NlbClusterNode'.

Related Management Information

NLB Host

NLB Cluster

Community Additions

ADD
Show: