Hosts in a Network Load Balancing (NLB) cluster are configured to load balance network traffic. Host configuration is set by using NLB Manager, and if it is not configured properly, the NLB cluster may not function correctly.
Check that the cluster IP address is valid
If the Network Load Balancing (NLB) driver fails to initialize because the cluster IP address is not in a valid format, you should check that the network IP address is specified in a valid IPv4 or IPv6 address format.
To check that the cluster IP address is in a valid IPv4 or IPv6 format:
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.
In IP address, verify that the IPv4 or IPv6 address is correctly formatted. IPv4 addresses use the standard Internet dotted notation (for example, w.x.y.z). IPv6 addresses use 16-byte addresses, typically expressed in colon-hexadecimal notation. Colon-hexadecimal notation uses eight 4-digit hexadecimal numbers, with colons separating the 16-bit blocks (the 4-digit numbers). To manage addresses more easily, IPv6 suppresses leading zeros and compresses a single contiguous all-zero 16-bit block, represent the contiguous block with two colons (::). This is known as double-colon compression. An example of an IPv6 address with leading zeros suppressed is: FEC0:0:0:0:2AA:FF:FE3F:2A1C.\
| Target | Microsoft.Windows.NetworkLoadBalancing.2008.ServerRole |
| Category | Alert |
| Enabled | True |
| Event_ID | 16 |
| Event Source | Microsoft-Windows-NLB |
| Alert Generate | False |
| Remotable | True |
| Event Log | System |
| ID | Module Type | TypeId | RunAs |
|---|---|---|---|
| DS | DataSource | Microsoft.Windows.EventProvider | Default |
| Alert | WriteAction | Microsoft.Windows.NetworkLoadBalancing.2008.GenerateAlert.SuppressByDescription | Default |
| WriteToDB | WriteAction | Microsoft.Windows.NetworkLoadBalancing.2008.CollectEvent | Default |
Home
<Rule ID="Microsoft.Windows.NetworkLoadBalancing.2008.NLB.driver.failed.to.initialize.because.the.cluster.IP.address.is.invalid" Enabled="onEssentialMonitoring" Target="Microsoft.Windows.NetworkLoadBalancing.2008.ServerRole" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>System</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">16</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">Microsoft-Windows-NLB</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="Microsoft.Windows.NetworkLoadBalancing.2008.GenerateAlert.SuppressByDescription">
<Priority>1</Priority>
<Severity>2</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.NetworkLoadBalancing.2008.NLB.driver.failed.to.initialize.because.the.cluster.IP.address.is.invalid.AlertMessage"]$</AlertMessageId>
<EnableAlert>true</EnableAlert>
</WriteAction>
<WriteAction ID="WriteToDB" TypeID="Microsoft.Windows.NetworkLoadBalancing.2008.CollectEvent">
<CollectEvent>false</CollectEvent>
</WriteAction>
</WriteActions>
</Rule>