Event ID 119 — NLB Extended Affinity Configuration

Event ID 119 — NLB Extended Affinity Configuration

Updated: November 25, 2009

Applies To: Windows Server 2008 R2

In a Network Load Balancing (NLB) cluster, port rules are configured to control how each port’s cluster network traffic is handled. One of the settings for port rules is whether extended affinity is enabled. The NLB cluster may fail to converge unless the extended affinity setting on each port rule is identical on all cluster hosts.

Event Details

Product: Windows Operating System
ID: 119
Source: Microsoft-Windows-NLB
Version: 6.1
Symbolic Name: MSG_WARN_CLIENT_STICKINESS_CONFLICT
Message: NLB cluster [%2]: The NLB driver has detected an inconsistency in the extended affinity configuration between cluster host %5 and cluster host %6. A client IP address is listed on the extended affinity exception list on both hosts. You should run the PowerShell cmdlet ‘Set-NlbClusterNode -Reload’ followed by ‘Start-NlbClusterNode’.

Resolve
Confirm that all NLB hosts have identical extended affinity configurations

Confirm that the extended affinity configurations for all port rules are identical on all Network Load Balancing (NLB) hosts. 

When you are using NLB Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running NLB Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

Confirm all NLB hosts have identical extended affinity configurations

To confirm that all NLB hosts have identical extended affinity configurations:

  1. 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.
  2. If NLB Manager does not already list the cluster, connect to the cluster.
  3. Right-click the cluster, and then click ClusterProperties.
  4. Click the Port Rules tab, and review the port rules to verify that the settings for extended affinity are identical with the rules on the other NLB hosts. If there are extended affinity port rule settings that are not identical, you should reconfigure the port rules to make them identical.

Configure extended affinity on port rules

To configure port rules:

  1. 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.
  2. If NLB Manager does not already list the cluster, connect to the cluster.
  3. Right-click the cluster, and then click ClusterProperties.
  4. Click the Port Rules tab.
  5. In the Defined port rules list, click a rule, and then click Edit. If you need to enable extended affinity for a port rule, click Timeout and provide an appropriate timeout value. When done, click OK.

Verify

When you are using nlb.exe, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running nlb.exe from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

To verify that all Network Load Balancing (NLB) hosts are in the converged state:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type nlb.exe query, which displays the current cluster state and the list of host priorities for the current hosts of the cluster.
  3. Confirm that all hosts display converged as their current state.

 

Related Management Information

NLB Extended Affinity Configuration

NLB Cluster

Related:

Event ID 108 — NLB Host Configuration

Event ID 108 — NLB Host Configuration

Updated: November 25, 2009

Applies To: Windows Server 2008 R2

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.

 

Event Details

Product: Windows Operating System
ID: 108
Source: Microsoft-Windows-NLB
Version: 6.1
Symbolic Name: MSG_WARN_VIRTUAL_IP_ADDR
Message: NLB cluster [%2]: The virtual IP (VIP) address %3 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.

Resolve
Check that the virtual IP address is valid

The virtual IP address must be in a valid IPv4 or IPv6 format.

When you are using Network Load Balancing (NLB) Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running NLB Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

To check that the virtual IP address is in a valid IPv4 or IPv6 format:

  1. 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.
  2. If NLB Manager does not already list the cluster, connect to the cluster.
  3. Right-click the cluster, and then click Cluster Properties.
  4. 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.

Verify

When you are using nlb.exe, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running nlb.exe from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

To verify that all Network Load Balancing (NLB) hosts are in the converged state:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type nlb.exe query, which displays the current cluster state and the list of host priorities for the current hosts of the cluster.
  3. Confirm that all hosts display converged as their current state.

Related Management Information

NLB Host Configuration

NLB Cluster

Related:

Event ID 98 — Network Adapter Functionality

Event ID 98 — Network Adapter Functionality

Updated: November 13, 2007

Applies To: Windows Server 2008

The network adapter to which Network Load Balancing (NLB) is bound must be properly configured and capable of performing NLB operations. If the adapter is not properly configured, the NLB driver may fail to bind to the adapter.

Event Details

Product: Windows Operating System
ID: 98
Source: Microsoft-Windows-NLB
Version: 6.0
Symbolic Name: MSG_ERROR_ATTACH_FAIL
Message: NLB cluster [%2]: The NLB driver failed to attach to adapter ‘%3’ due to error %5. 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.

Resolve
Disable and re-enable NLB network adapters

When the Network Load Balancing (NLB) driver fails to attach to the network adapter or fails to register with the Network Driver Interface Specification (NDIS), the host will not be an active member of the NLB cluster. You should disable and re-enable the network adapter before attempting to bind NLB to the adapter again.

Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.

To disable and re-enable all network adapters:

  1. Open Network and Sharing Center, and then click Manage network connections.
  2. Right-click the network adapter you want to disable, and click Disable. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
  3. Right-click the network adapter you want to enable, and click Enable. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.

Verify

When you are using nlb.exe, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running nlb.exe from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

To verify that the network adapters are properly configured:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type nlb.exe query, which displays the current cluster state and the list of host priorities for the current members of the cluster.
  3. Type nlb.exe display, which displays details on the current cluster configuration and the IP configuration on the host operating system and the network adapter. Verify the configuration of the network adapter.

 

Related Management Information

Network Adapter Functionality

NLB Cluster

Related:

Event ID 94 — Network Adapter Functionality

Event ID 94 — Network Adapter Functionality

Updated: November 13, 2007

Applies To: Windows Server 2008

The network adapter to which Network Load Balancing (NLB) is bound must be properly configured and capable of performing NLB operations. If the adapter is not properly configured, the NLB driver may fail to bind to the adapter.

Event Details

Product: Windows Operating System
ID: 94
Source: Microsoft-Windows-NLB
Version: 6.0
Symbolic Name: MSG_ERROR_MCAST_LIST_UPDATE
Message: NLB cluster [%2]: 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 ‘nlb reload’ from a command prompt.

Resolve
Disable and re-enable NLB network adapters

When the Network Load Balancing (NLB) driver fails to attach to the network adapter or fails to register with the Network Driver Interface Specification (NDIS), the host will not be an active member of the NLB cluster. You should disable and re-enable the network adapter before attempting to bind NLB to the adapter again.

Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.

To disable and re-enable all network adapters:

  1. Open Network and Sharing Center, and then click Manage network connections.
  2. Right-click the network adapter you want to disable, and click Disable. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
  3. Right-click the network adapter you want to enable, and click Enable. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.

Verify

When you are using nlb.exe, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running nlb.exe from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

To verify that the network adapters are properly configured:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type nlb.exe query, which displays the current cluster state and the list of host priorities for the current members of the cluster.
  3. Type nlb.exe display, which displays details on the current cluster configuration and the IP configuration on the host operating system and the network adapter. Verify the configuration of the network adapter.

 

Related Management Information

Network Adapter Functionality

NLB Cluster

Related:

Event ID 88 — NLB Cluster Control

Event ID 88 — NLB Cluster Control

Updated: November 13, 2007

Applies To: Windows Server 2008

The Network Load Balancing (NLB) cluster operates normally when all NLB components are compatible. If some components are incompatible, then you may run into issues managing and controlling the cluster.

 

 

Event Details

Product: Windows Operating System
ID: 88
Source: Microsoft-Windows-NLB
Version: 6.0
Symbolic Name: MSG_ERROR_REGISTERING_DEVICE
Message: NLB cluster [%2]: 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.

Resolve
Disable and enable NLB network adapters

If the Network Load Balancing (NLB) driver fails to register a device, such as a network adapter, the cluster will converge and operate normally, but controlling the cluster might not work properly. You should disable all network adapters with NLB bound on this host, and then re-enable the adapters.

Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.

To disable and re-enable all network adapters by using Network and Sharing Center:

  1. Click Start, click Network, and then click Network and Sharing Center.
  2. Under Tasks, click Manage network connections.
  3. Right-click the network adapter you want to disable, and click Disable. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
  4. Right-click the network adapter you want to enable, and click Enable. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.

Verify

You ensure that you can control the Network Load Balancing (NLB) host by using NLB Manager.

When you are using NLB Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running NLB Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

To ensure that the NLB host is controllable:

  1. 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.
  2. Right-click Network Load Balancing Clusters, and then click Connect to Existing.
  3. Type the name of one of the cluster hosts, and then click Connect. The NLB clusters that exist on that host will be listed at the bottom of the dialog box.
  4. Click the cluster name that you want to manage from NLB Manager, and then click Finish.
  5. Test whether you can control the host. For example, you could attempt to stop or start handling cluster traffic.

 

 

Related Management Information

NLB Cluster Control

NLB Cluster

Related:

Event ID 89 — Network Adapter Functionality

Event ID 89 — Network Adapter Functionality

Updated: November 13, 2007

Applies To: Windows Server 2008

The network adapter to which Network Load Balancing (NLB) is bound must be properly configured and capable of performing NLB operations. If the adapter is not properly configured, the NLB driver may fail to bind to the adapter.

Event Details

Product: Windows Operating System
ID: 89
Source: Microsoft-Windows-NLB
Version: 6.0
Symbolic Name: MSG_ERROR_ATTACH_FAIL_UNKNOWN_ADAPTER
Message: NLB cluster [%2]: The NLB driver failed to attach a network adapter due to error %5. 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.

Resolve
Disable and re-enable NLB network adapters

When the Network Load Balancing (NLB) driver fails to attach to the network adapter or fails to register with the Network Driver Interface Specification (NDIS), the host will not be an active member of the NLB cluster. You should disable and re-enable the network adapter before attempting to bind NLB to the adapter again.

Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.

To disable and re-enable all network adapters:

  1. Open Network and Sharing Center, and then click Manage network connections.
  2. Right-click the network adapter you want to disable, and click Disable. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
  3. Right-click the network adapter you want to enable, and click Enable. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.

Verify

When you are using nlb.exe, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running nlb.exe from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

To verify that the network adapters are properly configured:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type nlb.exe query, which displays the current cluster state and the list of host priorities for the current members of the cluster.
  3. Type nlb.exe display, which displays details on the current cluster configuration and the IP configuration on the host operating system and the network adapter. Verify the configuration of the network adapter.

 

Related Management Information

Network Adapter Functionality

NLB Cluster

Related:

Event ID 79 — NLB General Functionality

Event ID 79 — NLB General Functionality

Updated: November 13, 2007

Applies To: Windows Server 2008

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.

Event Details

Product: Windows Operating System
ID: 79
Source: Microsoft-Windows-NLB
Version: 6.0
Symbolic Name: MSG_INFO_HOST_STATE_PERSIST_SUSPENDED
Message: 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 ‘nlb resume’ followed by ‘nlb start’ from a command prompt.

Resolve

This is a normal condition. No further action is required.

Related Management Information

NLB General Functionality

NLB Cluster

Related:

Event ID 74 — NLB Host State Persistence

Event ID 74 — NLB Host State Persistence

Updated: November 25, 2009

Applies To: Windows Server 2008 R2

When configured to do so, the Network Load Balancing (NLB) host state will persist whenever the NLB cluster shuts down and restarts.

 

Event Details

Product: Windows Operating System
ID: 74
Source: Microsoft-Windows-NLB
Version: 6.1
Symbolic Name: MSG_WARN_HOST_STATE_UPDATE
Message: NLB cluster [%2]: 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}\%3 registry value, which will cause the state at the next system restart to revert to the user-specified preferred initial host state.

Resolve
Confirm that the initial host state is correct

To check the initial Network Load Balancing (NLB) host state, you must first delete the registry key defined in the event log, and then confirm that the initial host state is correct.

Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on your computer.

Delete the registry key defined in the event log entry

To delete the registry key defined in the event log entry:

  1. Open Registry Editor.
  2. To set the state of the NLB host at the next restart, delete the following registry key, if it exists: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WLBS\Parameters\Interface\{GUID}\HostState. Deleting this key ensures that on the next restart, NLB will use the preferred initial host state.

The GUID is the globally unique identifier of the network adapter that is experiencing the problem. This will be the network adapter that is bound to NLB. If NLB is, or has been, bound to multiple network adapters, you can find the correct adapter by looking at the value for the ClusterIPAddress key for each GUID entry in the registry.

When you are using NLB Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running NLB Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

Confirm that the NLB initial host state is correctly configured

To confirm the NLB initial host state is correctly configured:

  1. 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.
  2. If NLB Manager does not already list the cluster, connect to the cluster.
  3. Right-click the host that you want to configure, and then click Host Properties.
  4. Click the Host Parameters tab, and then verify that the value in Initial host state is correct.

 

Verify

To ensure that the Network Load Balancing (NLB) host is functioning properly, you should check that the host state persists across cluster shutdowns and restarts.

When you are using NLB Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running NLB Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

To check that the NLB host state persists across cluster shutdowns and restarts, after the cluster restarts, perform the following procedure.

  1. 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.
  2. If NLB Manager does not already list the cluster, connect to the cluster.
  3. Right-click the host that you want to configure, and then click Host Properties.
  4. Click the Host Parameters tab, and then verify that the value in Initial host state is correct.

 

Related Management Information

NLB Host State Persistence

NLB Cluster

Related:

Event ID 69 — NLB General Functionality

Event ID 69 — NLB General Functionality

Updated: November 13, 2007

Applies To: Windows Server 2008

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.

Event Details

Product: Windows Operating System
ID: 69
Source: Microsoft-Windows-NLB
Version: 6.0
Symbolic Name: MSG_INFO_CONVERGING_MEMBER_LOST
Message: NLB cluster [%2]: NLB is initiating convergence on host %5 because host %6 is leaving the cluster.

Resolve

This is a normal condition. No further action is required.

Related Management Information

NLB General Functionality

NLB Cluster

Related:

Event ID 34 — NLB Host Configuration

Event ID 34 — NLB Host Configuration

Updated: November 25, 2009

Applies To: Windows Server 2008 R2

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.

 

Event Details

Product: Windows Operating System
ID: 34
Source: Microsoft-Windows-NLB
Version: 6.1
Symbolic Name: MSG_ERROR_REGISTRY
Message: NLB cluster [%2]: NLB failed to query parameters from the registry key HKLM\SYSTEM\CurrentControlSet\Services\WLBS\Parameters\Interface\%3. 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’.

Resolve
Confirm NLB configuration settings

If Network Load Balancing (NLB) is unable to process its configuration settings, you should confirm that the settings are correctly configured, and then, if changes are made, restart the NLB cluster.

When you are using NLB Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running NLB Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

Confirm the NLB configuration

To confirm the NLB configuration:

  1. 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.
  2. If NLB Manager does not already list the cluster, connect to the cluster.
  3. Right-click the cluster, and then click Cluster Properties.
  4. As required, reconfigure the properties.

When you are using nlb.exe, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running nlb.exe from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

Restart the NLB cluster

To restart the NLB cluster:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type nlb.exe reload, which reloads the NLB driver’s current parameters from the registry.
  3. Type nlb.exe start, which starts cluster operations on the specified hosts.

Verify

When you are using nlb.exe, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running nlb.exe from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer.

To verify that all Network Load Balancing (NLB) hosts are in the converged state:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type nlb.exe query, which displays the current cluster state and the list of host priorities for the current hosts of the cluster.
  3. Confirm that all hosts display converged as their current state.

Related Management Information

NLB Host Configuration

NLB Cluster

Related: