The NLB driver has detected an inconsistency in the extended affinity configuration between two cluster hosts
Confirm that the extended affinity configurations for all port rules are identical on all Network Load Balancing (NLB) hosts.
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.
Confirm all NLB hosts have identical extended affinity configurations
To confirm that all NLB hosts have identical extended affinity configurations:
On each NLB host, click Start, click Administrative Tools, and then click Network Load Balancing Manager. You can also open NLB Manager by typing Nlbmgr at a command prompt.
If NLB Manager does not already list the cluster, connect to the cluster.
Right-click the cluster, and then click Cluster Properties.
Click the Port Rules tab, and review the port rules to verify that the settings for extended affinity are identical with the rules on the other NLB hosts. If there are extended affinity port rule settings that are not identical, you should reconfigure the port rules to make them identical.
Configure extended affinity on port rules
To configure port rules:
Click Start, click Administrative Tools, and then click Network Load Balancing Manager. You can also open NLB Manager by typing Nlbmgr at a command prompt.
If NLB Manager does not already list the cluster, connect to the cluster.
Right-click the cluster, and then click Cluster Properties.
Click the Port Rules tab.
In the Defined port rules list, click a rule, and then click Edit. If you need to enable extended affinity for a port rule, click Timeout and provide an appropriate timeout value. When done, click OK.
Target | Microsoft.Windows.NetworkLoadBalancing.6.2.ServerRole |
Category | Alert |
Enabled | True |
Alert Generate | False |
Remotable | True |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.NetworkLoadBalancing.EventProvider | Default |
WA | WriteAction | Microsoft.Windows.NetworkLoadBalancing.6.2.GenerateAlert.SuppressByDescription | Default |
WriteToDB | WriteAction | Microsoft.Windows.NetworkLoadBalancing.6.2.CollectEvent | Default |
<Rule ID="Microsoft.Windows.NetworkLoadBalancing.6.2..Client.stickiness.conflict" Enabled="onEssentialMonitoring" Target="Microsoft.Windows.NetworkLoadBalancing.6.2.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>119</Value>
</ValueExpression>
</SimpleExpression>
</Criteria>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WA" TypeID="Microsoft.Windows.NetworkLoadBalancing.6.2.GenerateAlert.SuppressByDescription">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.NetworkLoadBalancing.6.2..Client.stickiness.conflict.AlertMessage"]$</AlertMessageId>
<EnableAlert>true</EnableAlert>
</WriteAction>
<WriteAction ID="WriteToDB" TypeID="Microsoft.Windows.NetworkLoadBalancing.6.2.CollectEvent">
<CollectEvent>false</CollectEvent>
</WriteAction>
</WriteActions>
</Rule>