NLB General Functionality

Updated: November 25, 2009

Applies To: Windows Server 2008 R2

General Functionality provides information about whether the hosts are functioning properly, such as when a new host has started load balancing traffic, when an inactive host has suspended cluster operations, and when NLB cluster is initiating convergence because a new host is joining the cluster.

Events

Event ID Source Message

5

Microsoft-Windows-NLB

NLB cluster [%2]: This host is an active member of the NLB cluster. The host priority (unique host identifier) is %5, and it will start load balancing traffic as soon as it converges with the rest of the cluster hosts.

6

Microsoft-Windows-NLB

NLB cluster [%2]: This host is no longer an active member of the NLB cluster.

23

Microsoft-Windows-NLB

NLB cluster [%2]: This host will start handling new load balanced traffic for rule containing port %3.

24

Microsoft-Windows-NLB

NLB cluster [%2]: This host will stop handling new load balanced traffic for rule containing port %3.

26

Microsoft-Windows-NLB

NLB cluster [%2]: 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.

28

Microsoft-Windows-NLB

NLB cluster [%2]: Host %5 converged with host(s)%3. It is now an active member of the NLB cluster and will start load balancing traffic.

29

Microsoft-Windows-NLB

NLB cluster [%2]: Host %5 converged with host(s)%3. 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.

36

Microsoft-Windows-NLB

NLB cluster [%2]: Registry parameters successfully reloaded.

39

Microsoft-Windows-NLB

NLB cluster [%2]: This host has drained all connections for port rule containing port %3. It will not handle any new load balanced traffic for this port rule.

41

Microsoft-Windows-NLB

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

42

Microsoft-Windows-NLB

NLB cluster [%2]: This host will start handling new load balanced traffic for all port rules.

43

Microsoft-Windows-NLB

NLB cluster [%2]: This host will stop handling new load balanced traffic for all port rules.

44

Microsoft-Windows-NLB

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

45

Microsoft-Windows-NLB

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

47

Microsoft-Windows-NLB

NLB cluster [%2]: This host has resumed cluster operations. Once it is started, this host will be an active member of the cluster.

48

Microsoft-Windows-NLB

NLB cluster [%2]: This host has suspended cluster operations. Until it is resumed, this host will not be an active member of the cluster.

52

Microsoft-Windows-NLB

NLB cluster [%2]: Registry parameters successfully reloaded without resetting the driver.

58

Microsoft-Windows-NLB

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

61

Microsoft-Windows-NLB

NLB cluster [%2]: 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.

63

Microsoft-Windows-NLB

NLB cluster [%2]: NLB is initiating convergence on host %5 because host %6 is joining the cluster.

64

Microsoft-Windows-NLB

NLB cluster [%2]: NLB is initiating convergence on host %5 because host %6 has a configuration that conflicts with other hosts.

65

Microsoft-Windows-NLB

NLB cluster [%2]: NLB is initiating convergence on host %5 because host %6 is converging for an unknown reason.

66

Microsoft-Windows-NLB

NLB cluster [%2]: NLB is initiating convergence on host %5 because host %6 is configured with the same host priority.

67

Microsoft-Windows-NLB

NLB cluster [%2]: NLB is initiating convergence on host %5 because host %6 is configured with a conflicting number of port rules.

68

Microsoft-Windows-NLB

NLB cluster [%2]: NLB is initiating convergence on host %5 because host %6 has changed its port rule configuration.

69

Microsoft-Windows-NLB

NLB cluster [%2]: NLB is initiating convergence on host %5 because host %6 is leaving the cluster.

76

Microsoft-Windows-NLB

NLB cluster [%2]: 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.

77

Microsoft-Windows-NLB

NLB cluster [%2]: 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'.

78

Microsoft-Windows-NLB

NLB cluster [%2]: 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'.

79

Microsoft-Windows-NLB

NLB cluster [%2]: 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'.

100

Microsoft-Windows-NLB

NLB cluster [%2]: The NLB driver successfully attached (bound) to adapter '%3'.

101

Microsoft-Windows-NLB

NLB cluster [%2]: The NLB driver successfully detached (unbound) from adapter '%3'.

113

Microsoft-Windows-NLB

NLB cluster [%2]: NLB is initiating convergence on host %5 because host %6 is an unsupported legacy host.

116

Microsoft-Windows-NLB

NLB cluster [%2]: NLB is initiating convergence on host %5 to synchronize the extended affinity configuration between all cluster hosts after the initial attempt failed with error code %6.

12288

Microsoft-Windows-NLB

Configuration update %2 started by %1 on adapter %3

12289

Microsoft-Windows-NLB

Configuration update %2 completed with status %1 on adapter %3. Information log contains:
%4

Related Management Information

NLB Host

NLB Cluster

Community Additions

ADD
Show: