Microsoft-Windows-NLB

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 #

Description

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

Message #

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

Fields #

Description

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.

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

Description

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

Message #

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

Fields #

Description

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

Message #

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

Fields #

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 #

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 #

Description

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.

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 #

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 #

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 #

Description

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.

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 #

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 #

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 #

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 #

Description

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

Message #

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

Fields #

Description

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.

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 #

Description

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.

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 #

Description

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.

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 #

Description

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

Message #

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

Fields #

Description

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

Message #

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

Fields #

Description

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.

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 #

Description

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

Message #

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

Fields #

Description

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

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 #

Description

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

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 #

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 #

Description

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

Message #

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

Fields #

Description

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.

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 #

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 #

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 #

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 #

Description

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

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 #

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 #

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 #

Description

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.

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 #

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 #

Description

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

Message #

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

Fields #

Description

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

Message #

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

Fields #

Description

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

Message #

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

Fields #

Description

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

Message #

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

Fields #

Description

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

Message #

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

Fields #

Description

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

Message #

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

Fields #

Description

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

Message #

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

Fields #

Description

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.

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 #

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 #

Description

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.

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 #

Description

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.

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 #

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 #

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 #

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 #

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 #

Description

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.

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

Description

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

Message #

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

Fields #

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 #

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 #

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 #

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 #

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 #

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 #

Description

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

Message #

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

Fields #

Description

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

Message #

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

Fields #

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 #

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 #

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 #

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 #

Description

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

Message #

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

Fields #

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 #

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 #

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 #

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 #

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 #

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 #

Description

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

Message #

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

Fields #

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 #

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 #

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 #

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 #

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 #

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 #

Description

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

Message #

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

Fields #

Description

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

Message #

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

Fields #

Description

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

Message #

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