Microsoft-Windows-NLB

99 events across 2 channels

Event IDTitleChannel
5NLB cluster [.System
6NLB cluster [.System
9NLB cluster [.System
10NLB cluster [.System
14NLB cluster [.System
15NLB cluster [.System
16NLB cluster [.System
17NLB cluster [.System
18NLB cluster [.System
19NLB cluster [.System
20NLB cluster [.System
21NLB cluster [.System
22NLB cluster [.System
23NLB cluster [.System
24NLB cluster [.System
25NLB cluster [.System
26NLB cluster [.System
28NLB cluster [.System
29NLB cluster [.System
30NLB cluster [.System
31NLB cluster [.System
32NLB cluster [.System
34NLB cluster [.System
35NLB cluster [.System
36NLB cluster [.System
37NLB cluster [.System
39NLB cluster [.System
41NLB cluster [.System
42NLB cluster [.System
43NLB cluster [.System
44NLB cluster [.System
45NLB cluster [.System
47NLB cluster [.System
48NLB cluster [.System
50NLB cluster [.System
52NLB cluster [.System
53NLB cluster [.System
55NLB cluster [.System
56NLB cluster [.System
57NLB cluster [.System
58NLB cluster [.System
59NLB cluster [.System
60NLB cluster [.System
61NLB cluster [.System
62NLB cluster [.System
63NLB cluster [.System
64NLB cluster [.System
65NLB cluster [.System
66NLB cluster [.System
67NLB cluster [.System
68NLB cluster [.System
69NLB cluster [.System
73NLB cluster [.System
74NLB cluster [.System
75NLB cluster [.System
76NLB cluster [.System
77NLB cluster [.System
78NLB cluster [.System
79NLB cluster [.System
81NLB cluster [.System
83NLB cluster [.System
85NLB cluster [.System
86NLB cluster [.System
87NLB cluster [.System
88NLB cluster [.System
89NLB cluster [.System
90NLB cluster [.System
91NLB cluster [.System
92NLB cluster [.System
93NLB cluster [.System
94NLB cluster [.System
95NLB cluster [.System
96NLB cluster [.System
97NLB cluster [.System
98NLB cluster [.System
99NLB cluster [.System
100NLB cluster [.System
101NLB cluster [.System
102NLB cluster [.System
103NLB cluster [.System
104NLB cluster [.System
105NLB cluster [.System
106NLB cluster [.System
107NLB cluster [.System
108NLB cluster [.System
109NLB cluster [.System
110NLB cluster [.System
111NLB cluster [.System
112NLB cluster [.System
113NLB cluster [.System
114NLB cluster [.System
115NLB cluster [.System
116NLB cluster [.System
117NLB cluster [.System
118NLB cluster [.System
119NLB cluster [.System
1074212864Configuration update {param2} started by {param1} on adapter {param3}.Operational
1074212865Configuration update {param2} completed with status {param1} on adapter …Operational
2147946496Configuration completed.Operational

Event ID 5 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host is an active member of the NLB cluster. The host priority (unique host identifier) is {param5}. It will start load balancing traffic as soon as it converges with the rest of the cluster hosts.

Fields

NameDescription
param2
param5

Event ID 6 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host is no longer an active member of the NLB cluster.

Fields

NameDescription
param2

Event ID 9 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to bind to the adapter because the medium type is unsupported. Please confirm that you are trying to bind NLB to an Ethernet network adapter.

Fields

NameDescription
param2

Event ID 10 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver could not allocate enough memory resources to perform driver operations. Close all programs on this cluster host that might be consuming memory and rebind NLB to the adapters. If this problem persists; you might need to add additional memory (RAM) to this host.

Fields

NameDescription
param2

Event ID 14 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to initialize because the cluster network address {param3} is invalid. Please check that the network address property of the NLB cluster is specified in a valid MAC address format.

Fields

NameDescription
param2
param3

Event ID 15 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The dedicated IP (DIP) address {param3} is invalid. The cluster will converge and operate normally without this DIP. However; if this DIP is required for remote cluster management; make sure that the DIP is specified in a valid IPv4 or IPv6 address format.

Fields

NameDescription
param2
param3

Event ID 16 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to initialize because the cluster IP address {param3} is invalid. Please check that the network IP address is specified in a valid IPv4 or IPv6 address format.

Fields

NameDescription
param2
param3

Event ID 17 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB detected a duplicate host priority {param5} that is shared between cluster hosts. Each host in the NLB cluster must have a unique host priority. Please check the NLB configuration of all hosts and make sure that each has a unique host priority (a number between 1 and 32).

Fields

NameDescription
param2
param5

Event ID 18 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB detected duplicate cluster subnets. This may be due to network partitioning; which prevents NLB heartbeats of one or more hosts from reaching the other cluster hosts. Although NLB operations have resumed properly; please investigate the cause of the network partitioning.

Fields

NameDescription
param2

Event ID 19 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The maximum number of actively serviced connections that could be tracked by NLB is reached. Although NLB will still 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. To resolve this issue; add more hosts to the cluster and/or increase the {param3} value under the HKLM\SYSTEM\CurrentControlSet\Services\WLBS\Parameters\Interface\{GUID} key in the registry.

Fields

NameDescription
param2
param3
GUID

Event ID 20 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB failed to converge due to port rules with a duplicate single host priority {param5} in the cluster. Each single host port rule in the NLB cluster must have a unique priority. Please check the NLB configuration of all port rules and make sure that each has a unique host priority (a number between 1 and 32).

Fields

NameDescription
param2
param5

Event ID 21 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB failed to converge due to inconsistencies in the port rules between this host and cluster host {param5}. This will occur if the number of port rules or the type of port rules are different between hosts. Please make sure that the port rules are consistent on all cluster hosts.

Fields

NameDescription
param2
param5

Event ID 22 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to initialize because the number of port rules must be between 0 and {param5}. It is currently specified as {param6} in the registry. Please check the NLB configuration to ensure that you are using the proper number of rules.

Fields

NameDescription
param2
param5
param6

Event ID 23 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host will start handling new load balanced traffic for rule containing port {param3}.

Fields

NameDescription
param2
param3

Event ID 24 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host will stop handling new load balanced traffic for rule containing port {param3}.

Fields

NameDescription
param2
param3

Event ID 25 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: A port rule operation on port {param3} was issued but there is no port rule that contains this port. Please confirm that the intended port number is correct; or configure a port rule for this port number.

Fields

NameDescription
param2
param3

Event ID 26 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: A port rule operation was issued while the host was in the stopped state. Such operations can only be performed on a running cluster host. Please ensure that the cluster host is an active member before issuing port rule operations.

Fields

NameDescription
param2

Event ID 28 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: Host {param5} converged with host(s){param3}. It is now an active member of the NLB cluster and will start load balancing traffic.

Fields

NameDescription
param2
param5
param3

Event ID 29 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: Host {param5} converged with host(s){param3}. It is now an active member of the NLB cluster and will start load balancing traffic as the default host. The default host is the host with the lowest host priority. It handles all traffic that isn't covered by any of the defined port rules.

Fields

NameDescription
param2
param5
param3

Event ID 30 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The dedicated network mask {param3} is invalid. The cluster will converge and operate normally without this dedicated IP (DIP) address. However; if this DIP is required for remote cluster management; make sure that the dedicated network mask for the DIP is specified in a valid format.

Fields

NameDescription
param2
param3

Event ID 31 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to initialize because the cluster network mask {param3} is invalid. Please check that the network mask is specified in a valid format.

Fields

NameDescription
param2
param3

Event ID 32 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB detected an unequal number of dedicated IP (DIP) addresses and network masks. For all DIP's listed for use; an equal number of network masks must be specified. The NLB cluster will continue to operate; but the DIP that has no corresponding network mask will be ignored. To use this DIP; make sure that the number of addresses and network masks are the same.

Fields

NameDescription
param2

Event ID 34 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB failed to query parameters from the registry key HKLM\SYSTEM\CurrentControlSet\Services\WLBS\Parameters\Interface\{param3}. This might be due to an improper configuration. Please use Network Load Balancing Manager to configure NLB. Once the configuration is fixed; you should run the PowerShell cmdlet 'Set-NlbClusterNode -Reload' followed by 'Start-NlbClusterNode'.

Fields

NameDescription
param2
param3

Event ID 35 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB failed to verify its parameters. This might be due to an improper configuration. Please use Network Load Balancing Manager to configure NLB. Once the configuration is fixed; you should run the PowerShell cmdlet 'Set-NlbClusterNode -Reload' followed by 'Start-NlbClusterNode'.

Fields

NameDescription
param2

Event ID 36 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: Registry parameters successfully reloaded.

Fields

NameDescription
param2

Event ID 37 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: Version mismatch between the driver and control programs. Please make sure that you are running the same version of all NLB components.

Fields

NameDescription
param2

Event ID 39 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host has drained all connections for port rule containing port {param3}. It will not handle any new load balanced traffic for this port rule.

Fields

NameDescription
param2
param3

Event ID 41 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host has drained all connections for all port rules. It will not handle any new load balanced traffic for all ports rules.

Fields

NameDescription
param2

Event ID 42 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host will start handling new load balanced traffic for all port rules.

Fields

NameDescription
param2

Event ID 43 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host will stop handling new load balanced traffic for all port rules.

Fields

NameDescription
param2

Event ID 44 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host has started draining all connections for all port rules. It will not handle any new load balanced traffic for all ports rules.

Fields

NameDescription
param2

Event ID 45 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host has stopped draining all connections. This may be due to a stop/suspend operation on the host.

Fields

NameDescription
param2

Event ID 47 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host has resumed cluster operations. Once it is started; this host will be an active member of the cluster.

Fields

NameDescription
param2

Event ID 48 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host has suspended cluster operations. Until it is resumed; this host will not be an active member of the cluster.

Fields

NameDescription
param2

Event ID 50 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB failed to add a multicast MAC address to the network adapter it is bound to. This happened because the maximum number of multicast MAC addresses that can be assigned to this network adapter has been exhausted. Use a network adapter that supports more multicast MAC addresses or operate NLB in unicast mode.

Fields

NameDescription
param2

Event ID 52 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: Registry parameters successfully reloaded without resetting the driver.

Fields

NameDescription
param2

Event ID 53 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB will not attach to adapter '{param3}' because it does not support dynamic changing of its MAC address. Replace the network adapter with one which supports that capability.

Fields

NameDescription
param2
param3

Event ID 55 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: An inconsistent teaming configuration was detected for bi-directional affinity (BDA) on host {param5}. BDA configuration must be identical on all cluster hosts. The team in which this cluster participates will be marked inactive and this cluster will remain in the converging state until consistent teaming configuration is detected.

Fields

NameDescription
param2
param5

Event ID 56 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: Invalid bi-directional affinity (BDA) team ID detected. Team IDs must be a GUID of the form {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}. To add this cluster to a team; correct the team ID and run the PowerShell cmdlet 'Set-NlbClusterNode -Reload' followed by 'Start-NlbClusterNode'.

Fields

NameDescription
param2

Event ID 57 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: Invalid bi-directional affinity (BDA) teaming port rules detected. Each member of a BDA team may have no more than one port rule; and its affinity must be single or class C if multiple host filtering is specified. To add this cluster to a team; correct the port rules and run the PowerShell cmdlet 'Set-NlbClusterNode -Reload' followed by 'Start-NlbClusterNode'.

Fields

NameDescription
param2

Event ID 58 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: Consistent bi-directional affinity (BDA) teaming configuration detected again. The team in which this cluster participates has been re-activated.

Fields

NameDescription
param2

Event ID 59 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The bi-directional affinity (BDA) team which this cluster has attempted to join already has a designated master. This cluster will not join the team and will remain in the stopped state until the parameter errors are corrected and the cluster is restarted by running the PowerShell cmdlet 'Set-NlbClusterNode -Reload' followed by 'Start-NlbClusterNode'. {param3} {param4}

Fields

NameDescription
param2
param3
param4

Event ID 60 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The bi-directional affinity (BDA) team in which this cluster participates has no designated master. The team is inactive and will remain inactive until a master for the team is designated and consistent BDA teaming configuration is detected.

Fields

NameDescription
param2

Event ID 61 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This cluster has joined a bi-directional affinity (BDA) team as the designated master. If the rest of the team has been consistently configured; the team will be activated.

Fields

NameDescription
param2

Event ID 62 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This cluster has left a bi-directional affinity (BDA) team in which it was the designated master. If other adapters are still participating in the team; the team will be marked inactive and will remain inactive until a master for the team is designated and consistent BDA teaming configuration is detected.

Fields

NameDescription
param2

Event ID 63 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB is initiating convergence on host {param5} because host {param6} is joining the cluster.

Fields

NameDescription
param2
param5
param6

Event ID 64 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB is initiating convergence on host {param5} because host {param6} has a configuration that conflicts with other hosts.

Fields

NameDescription
param2
param5
param6

Event ID 65 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB is initiating convergence on host {param5} because host {param6} is converging for an unknown reason.

Fields

NameDescription
param2
param5
param6

Event ID 66 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB is initiating convergence on host {param5} because host {param6} is configured with the same host priority.

Fields

NameDescription
param2
param5
param6

Event ID 67 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB is initiating convergence on host {param5} because host {param6} is configured with a conflicting number of port rules.

Fields

NameDescription
param2
param5
param6

Event ID 68 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB is initiating convergence on host {param5} because host {param6} has changed its port rule configuration.

Fields

NameDescription
param2
param5
param6

Event ID 69 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB is initiating convergence on host {param5} because host {param6} is leaving the cluster.

Fields

NameDescription
param2
param5
param6

Event ID 73 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB cluster IGMP multicast IP address {param3} is invalid. Please check the NLB configuration and make sure that the cluster IGMP multicast IP address is in a valid format.

Fields

NameDescription
param2
param3

Event ID 74 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB failed to update the NLB host state in the registry. This will affect the ability of NLB to persist the current state after the system restarts; if NLB has been configured to do so. To predict the state of NLB at the next restart; please delete the HKLM\SYSTEM\CurrentControlSet\Services\WLBS\Parameters\Interface\{GUID}\{param3} registry value; which will cause the state at the next system restart to revert to the user-specified preferred initial host state.

Fields

NameDescription
param2
GUID
param3

Event ID 75 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB host state was successfully updated in the registry. Current state will persist after the system restarts; if NLB has been configured to do so.

Fields

NameDescription
param2

Event ID 76 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: Last known NLB host state was not found in the registry. The state of this host will revert to the user-specified preferred initial host state.

Fields

NameDescription
param2

Event ID 77 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host is configured to persist 'Started' after the system restarts. Because the last known state of this host was started; the host will be restarted regardless of the user-specified preferred initial host state. To stop the host; use NLB Manager or use the PowerShell cmdlet 'Stop-NlbClusterNode' or 'Suspend-NlbClusterNode'.

Fields

NameDescription
param2

Event ID 78 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host is configured to persist 'Stopped' after the system restarts. Because the last known state of this host was stopped; the host will remain stopped regardless of the user-specified preferred initial host state. To start the host; use NLB Manager or use the PowerShell cmdlet 'Start-NlbClusterNode'.

Fields

NameDescription
param2

Event ID 79 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: This host is configured to persist 'Suspended' after the system restarts. Because the last known state of this host was suspended; the host will remain suspended regardless of the user-specified preferred initial host state. To start the host; use NLB Manager or use the PowerShell cmdlet 'Resume-NlbClusterNode' followed by 'Start-NlbClusterNode'.

Fields

NameDescription
param2

Event ID 81 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB can't track TCP connections because it was unable to open the TCP connection callback object. Although NLB will still accept new connections; it will not track the connection state until this is resolved. This might result in breaking the affinity maintained by the driver during the connection. To resolve this issue; try to unbind then rebind NLB to the adapters.

Fields

NameDescription
param2

Event ID 83 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: Duplicate dedicated IP (DIP) address {param3} was detected on the network. Please check that each of the cluster hosts is configured with a unique DIP.

Fields

NameDescription
param2
param3

Event ID 85 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to register with the Network Driver Interface Specification (NDIS) with error code {param5}. As a result; this host will not be an active member of the cluster. Using Control Panel or Device Manager; disable and re-enable the network adapter before attempting to bind NLB to the adapter.

Fields

NameDescription
param2
param5

Event ID 86 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: Host {param5} converged with legacy host(s){param3}. This is expected during rolling upgrades. Until all hosts are upgraded to the latest version; newer NLB features will not be available for use. Please upgrade all hosts to the latest OS version.

Fields

NameDescription
param2
param5
param3

Event ID 87 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: A load distribution error was detected during convergence. This might result in client traffic not being handled; general traffic errors; or connections being reset. To fix the error; restart the cluster by running the PowerShell cmdlet 'Set-NlbClusterNode -Reload' followed by 'Start-NlbClusterNode'.

Fields

NameDescription
param2

Event ID 88 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to register the device object. The cluster will converge and operate normally but controlling the cluster might not work properly. To fix this; disable all network adapters with NLB bound on this host and then re-enable the adapters.

Fields

NameDescription
param2

Event ID 89 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to attach a network adapter due to error {param5}. As a result; this host will not be an active member of the cluster. Using Control Panel or Device Manager; disable and re-enable the network adapter before attempting to bind NLB to the adapter.

Fields

NameDescription
param2
param5

Event ID 90 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to bind to the adapter because the maximum transfer unit (MTU) reported by the adapter is too small to contain an NLB heartbeat message. Ensure that the MTU of all hosts in the cluster is set to the default value.

Fields

NameDescription
param2

Event ID 91 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB received a heartbeat from a host with an invalid ID {param5}. Please check the NLB configuration of all hosts and make sure that each has a unique host priority (a number between 1 and 32).

Fields

NameDescription
param2
param5

Event ID 92 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: A SYN attack has been detected. During the attack; some connections might fail. If this attack recurs frequently; analyze the threat and take appropriate measures. An informational event log entry will be logged when the attack has subsided.

Fields

NameDescription
param2

Event ID 93 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: A SYN attack has subsided.

Fields

NameDescription
param2

Event ID 94 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB failed to update the adapter multicast list. The cluster will converge and operate normally but some client traffic might not be handled. To attempt to update the adapter multicast list again; run the PowerShell cmdlet 'Set-NlbClusterNode -Reload' followed by 'Start-NlbClusterNode'.

Fields

NameDescription
param2

Event ID 95 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver has detected one or more {param3} sessions corresponding to a port rule that is improperly configured. To handle VPN traffic properly; the port rule must be configured with single or network affinity and the port range must include TCP port 1723 for PPTP/GRE and UDP ports 500/4500 for IPSec/L2TP.

Fields

NameDescription
param2
param3

Event ID 96 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to register/unregister the hook interface. The cluster will converge and operate normally but no hook decisions will be left for the registering application. Please check with the application using NLB and make sure it is registering the hooks properly.

Fields

NameDescription
param2

Event ID 97 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: An unsupported legacy host {param3} was discovered on the network. The OS version on this host is no longer supported in a mixed cluster configuration. The cluster will remain in the converging state until all deprecated legacy hosts are removed. Please remove the desprecated hosts from the cluster.

Fields

NameDescription
param2
param3

Event ID 98 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to attach to adapter '{param3}' due to error {param5}. As a result; this host will not be an active member of the cluster. Using Control Panel or Device Manager; disable and re-enable the network adapter before attempting to bind NLB to the adapter.

Fields

NameDescription
param2
param3
param5

Event ID 99 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to open the SYN attack callback object. A SYN attack is a type of denial of service attack which happens when a malicious user sends many open many TCP connections to the server exhausting system resources. Although NLB will still accept new connections; it may not perform optimally in the event of a SYN attack.

Fields

NameDescription
param2

Event ID 100 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver successfully attached (bound) to adapter '{param3}'.

Fields

NameDescription
param2
param3

Event ID 101 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver successfully detached (unbound) from adapter '{param3}'.

Fields

NameDescription
param2
param3

Event ID 102 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to register for notifications with the IPv4 NSI provider. NLB will continue to operate but may not handle auto-configured IPv4 addresses correctly. Please make sure that IPv4 is installed and working on this machine.

Fields

NameDescription
param2

Event ID 103 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to register for notifications with the IPv6 NSI provider. NLB will continue to operate but may not handle auto-configured IPv6 addresses correctly. Please make sure that IPv6 is installed and working on this machine.

Fields

NameDescription
param2

Event ID 104 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to open the timer starvation callback object. Although it will continue to operate; NLB may not perform optimally in the event of timer starvation (usually caused by denial of service attacks).

Fields

NameDescription
param2

Event ID 105 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: Timer starvation has been detected. This might be due to a denial of service attack or a very high server load. During this period; some connections might fail. If this problem recurs frequently; analyze the threat and take appropriate measures and/or add more servers to the cluster. An informational event log entry will be logged when the attack has subsided.

Fields

NameDescription
param2

Event ID 106 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: Timer starvation has subsided.

Fields

NameDescription
param2

Event ID 107 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB failed to add all the dedicated IP (DIP) addresses to this host. This happened because the maximum number ({param5}) of DIP's that can be added to this network adapter has been exhausted. The NLB cluster will continue to operate but all additional DIP's will be ignored.

Fields

NameDescription
param2
param5

Event ID 108 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The virtual IP (VIP) address {param3} is invalid. The cluster will converge and operate normally without this VIP. Make sure that the VIP is specified in a valid IPv4 or IPv6 address format.

Fields

NameDescription
param2
param3

Event ID 109 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The virtual network mask {param3} is invalid. The cluster will converge and operate normally without this virtual IP (VIP) address. Make sure that the virtual network mask for the VIP is specified in a valid format.

Fields

NameDescription
param2
param3

Event ID 110 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB detected an unequal number of virtual IP (VIP) addresses and network masks. For all VIP's listed for use; an equal number of network masks must be specified. The NLB cluster will continue to operate but the VIP with no corresponding network mask will be ignored. To use this VIP; make sure that the number of addresses and network masks are the same.

Fields

NameDescription
param2

Event ID 111 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The virtual IP (VIP) address in a port rule is invalid. The cluster will converge and operate normally but this port rule will be ignored. Make sure that the VIP is specified in a valid IPv4 or IPv6 address format.

Fields

NameDescription
param2

Event ID 112 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver failed to register for notifications with the IPv4 NSI provider. NLB will continue to operate but may not handle IPv4 addresses that are moved between nodes correctly. Please make sure that IPv4 is installed and working on this machine.

Fields

NameDescription
param2

Event ID 113 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB is initiating convergence on host {param5} because host {param6} is an unsupported legacy host.

Fields

NameDescription
param2
param5
param6

Event ID 114 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB failed to initialize bi-directional affinity (BDA) teaming on adapter '{param3}'. The BDA team in which this cluster participates will be marked inactive and this cluster will remain in the converging state until this is resolved. Using Control Panel or Device Manager; disable and re-enable the network adapter before attempting to bind NLB to the adapter.

Fields

NameDescription
param2
param3

Event ID 115 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB failed to register as a WMI provider. As a result; it will not be able to notify applications that are listening for WMI events of any changes in the NLB driver. Using Control Panel or Device Manager; disable and re-enable the network adapter before attempting to bind NLB to the adapter.

Fields

NameDescription
param2

Event ID 116 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: NLB is initiating convergence on host {param5} to synchronize the Extended Affinity configuration between all cluster hosts after the initial attempt failed with error code {param6}.

Fields

NameDescription
param2
param5
param6

Event ID 117 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The maximum number of actively serviced Extended Affinity connections that could be tracked by NLB is reached. Although NLB will still 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. To resolve this issue; add more hosts to the cluster and/or increase the {param3} value under the HKLM\SYSTEM\CurrentControlSet\Services\WLBS\Parameters\Interface\{GUID} key in the registry.

Fields

NameDescription
param2
param3
GUID

Event ID 118 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver has detected an inconsistency in the Extended Affinity configuration on cluster host {param5}. The host received an invalid entry from another cluster host. This might be due to an improper configuration. Please use Network Load Balancing Manager to configure NLB. Once the configuration is fixed; you should run the PowerShell cmdlet 'Set-NlbClusterNode -Reload' followed by 'Start-NlbClusterNode'.

Fields

NameDescription
param2
param5

Event ID 119 — NLB cluster [.

Provider
Microsoft-Windows-NLB
Channel
System

Message

NLB cluster [{param2}]: The NLB driver has detected an inconsistency in the Extended Affinity configuration between cluster host {param5} and cluster host {param6}. A client IP address is on the Extended Affinity exception list on both hosts. You should run the PowerShell cmdlet 'Set-NlbClusterNode -Reload' followed by 'Start-NlbClusterNode'.

Fields

NameDescription
param2
param5
param6

Event ID 1074212864 — Configuration update {param2} started by {param1} on adapter {param3}.

Provider
Microsoft-Windows-NLB
Channel
Operational

Message

Configuration update {param2} started by {param1} on adapter {param3}

Fields

NameDescription
param2
param1
param3

Event ID 1074212865 — Configuration update {param2} completed with status {param1} on adapter {param3}.

Provider
Microsoft-Windows-NLB
Channel
Operational

Message

Configuration update {param2} completed with status {param1} on adapter {param3}. Information log contains:{param4}

Fields

NameDescription
param2
param1
param3
param4

Event ID 2147946496 — Configuration completed.

Provider
Microsoft-Windows-NLB
Channel
Operational

Message

Configuration completed. Microsoft Cluster Service is also installed on this machine; and this may prevent the proper operation of both.