The maximum number of IP addresses with stickiness to this node that could be tracked by NLB is reached

Microsoft.Windows.NetworkLoadBalancing.2008.R2.Client.stickiness.descriptors.exceeded (Rule)

Knowledge Base article:

Summary

The maximum number of active connections that Network Load Balancing (NLB) can track is reached. Although NLB will continue to accept new connections, it will not track the connection state until other connections are closed. This might result in breaking the affinity maintained by the driver during the connection.

Resolutions

To address the connection tracking limits, you can either add more hosts to the NLB cluster, which distributes the number of incoming connections across more cluster hosts, or increase the connection tracking limit.

When you are using NLB Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running NLB Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

Add a host to the NLB cluster

To add a host to the NLB cluster:

Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on your computer.

Increase the connection tracking limit by editing the registry key

To increase the connection tracking limit by editing the registry key:

The GUID is the globally unique identifier of the network adapter that is experiencing the problem. This is the network adapter that is bound to NLB. If NLB is, or has been, bound to multiple network adapters, you can find the correct adapter by looking at the value for the ClusterIPAddress key for each GUID entry in the registry.

You should double the existing value of the registry key. After increasing the value, you must disable and re-enable the appropriate network adapter.

Element properties:

TargetMicrosoft.Windows.NetworkLoadBalancing.2008.R2.ServerRole
CategoryAlert
EnabledTrue
Alert GenerateFalse
RemotableTrue

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.NetworkLoadBalancing.EventProvider Default
WA WriteAction Microsoft.Windows.NetworkLoadBalancing.2008.GenerateAlert.SuppressByDescription Default
WriteToDB WriteAction Microsoft.Windows.NetworkLoadBalancing.2008.CollectEvent Default

Source Code:

<Rule ID="Microsoft.Windows.NetworkLoadBalancing.2008.R2.Client.stickiness.descriptors.exceeded" Enabled="onEssentialMonitoring" Target="Microsoft.Windows.NetworkLoadBalancing.2008.R2.ServerRole" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="NLBLibrary!Microsoft.Windows.NetworkLoadBalancing.EventProvider">
<Criteria>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>117</Value>
</ValueExpression>
</SimpleExpression>
</Criteria>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WA" TypeID="Microsoft.Windows.NetworkLoadBalancing.2008.GenerateAlert.SuppressByDescription">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.NetworkLoadBalancing.2008.R2.Client.stickiness.descriptors.exceeded.AlertMessage"]$</AlertMessageId>
<EnableAlert>true</EnableAlert>
</WriteAction>
<WriteAction ID="WriteToDB" TypeID="Microsoft.Windows.NetworkLoadBalancing.2008.CollectEvent">
<CollectEvent>false</CollectEvent>
</WriteAction>
</WriteActions>
</Rule>