In a Network Load Balancing (NLB) cluster, port rules are configured to control how each port's cluster network traffic is handled. The NLB cluster may fail to converge unless each port rule has a unique host priority (a number between 1 and 32), the port rules are consistent on all cluster hosts, you are using the proper number of port rules, and the virtual IP address is specified in a valid IPv4 or IPv6 address format
Confirm that all NLB hosts have identical port rules
If there is no port rule that contains a specified port, you should confirm that the port rules are identical on all Network Load Balancing (NLB) hosts.
Confirm all NLB hosts have identical port rules
To confirm that all NLB hosts have identical port rules:
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 ClusterProperties.
Click the Port Rules tab, and review the port rules to verify that they are identical with the rules on the other NLB hosts.
If there are port rules that are not identical, you should reconfigure the port rules to make them identical.
Configure 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 ClusterProperties.
Click the Port Rules tab.
In the Defined port rules list, click a rule, and then click Edit. If you need to add a new port rule, click Add. As required, modify the cluster IP address that you want this rule to apply to, the port range, protocols and filtering mode parameters as required, and then click OK.
| Target | Microsoft.Windows.NetworkLoadBalancing.2008.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.2008.GenerateAlert.SuppressByDescription | Default |
| WriteToDB | WriteAction | Microsoft.Windows.NetworkLoadBalancing.2008.CollectEvent | Default |
Home
<Rule ID="Microsoft.Windows.NetworkLoadBalancing.2008.A.port.rule.operation.was.issued.but.there.is.no.port.rule.that.contains.this.port" Enabled="onEssentialMonitoring" Target="Microsoft.Windows.NetworkLoadBalancing.2008.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>25</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.A.port.rule.operation.was.issued.but.there.is.no.port.rule.that.contains.this.port.AlertMessage"]$</AlertMessageId>
<EnableAlert>true</EnableAlert>
</WriteAction>
<WriteAction ID="WriteToDB" TypeID="Microsoft.Windows.NetworkLoadBalancing.2008.CollectEvent">
<CollectEvent>false</CollectEvent>
</WriteAction>
</WriteActions>
</Rule>