Tag: Network Load Balancing Services

How to Configure Content Switching on NetScaler to Access Multiple Web Sites

Citrix Leave a comment

To configure the Content Switching feature on the NetScaler appliance to access multiple Web sites hosted on a Web server, complete the following procedures.

NetScaler GUI

To configure the Content Switching feature on the NetScaler appliance, complete the following procedure:

  1. To add Load Balancing Servers with the IP Address/Domain Name field set to the hostname of the web servers, complete the following sub-procedure:
    1. Expand the Traffic Management > Load Balancing node.
    2. Select the Servers node.
    3. Click Add.
    4. If IP Address is selected, enter the IP address of the web server. Or, change the selection to Domain Name and enter the FQDN of the web server. This assumes that the NetScaler is able to resolve the DNS name.
    5. Click OK.
  2. To create multiple Load Balancing Service Groups configured to point to the new Servers, complete the following sub-procedure:
    1. Expand the Traffic Management > Load Balancing node.
    2. Select the Monitors node.
    3. Click Add.
    4. Give the monitor a name. Keep in mind that you’ll have a different monitor for each website and each protocol (e.g. HTTP vs SSL)
    5. Configure the monitor as needed for your website. Usually you want a monitor that requests a healthcheck page and looks for a successful response.
    6. Click Create.
    7. Create more Monitors for each website and protocol.
  3. To create multiple Load Balancing Service Groups configured to point to the new Servers, complete the following sub-procedure:
    1. Expand the Traffic Management > Load Balancing node.
    2. Select the Service Groups node.
    3. Click Add.
    4. Give the Service Group a name. Keep in mind that you’ll create a different Service Group for each website, and a different Service Group for each protocol (e.g. HTTP vs SSL)
    5. Add the members by selecting the Load Balancing Servers created in step 1 and entering their port number (e.g. 80 or 443).
    6. Bind a monitor to the Service Group. Each Service Group usually has a website-specific monitor.
    7. Click Create.
    8. Create more Service Groups for each website and protocol.
  4. To create Load Balancing Virtual Servers (VServers) for each website, complete the following sub- procedure:
    1. Expand the Traffic Management > Load Balancing node.
    2. Select the Virtual Servers node.
    3. Click Add.
    4. Give the Virtual Server a name. Keep in mind that you’ll have a different Virtual Server for each website and each protocol (e.g. HTTP vs SSL).
    5. Change the IP Address Type to Non-addressable.

      User-added image

    6. Click Create.
    7. Create more Load Balancing Virtual Servers for each website and protocol.
  5. To create Content Switching policies for each URL, complete the following sub-procedure:
    1. Expand the Traffic Management > Content Switching node.
    2. Select the Policies node.
    3. Click Add.
    4. Give the Content Switching Policy a name. Keep in mind that you’ll need a separate Content Switching Policy for each website and protocol (e.g. HTTP vs SSL)
    5. Enter the required expression. An example hostname-based expression is: HTTP.REQ.HOSTNAME.EQ(“portal.company.com”). An example path-based expression is HTTP.REQ.URL.PATH.STARTSWITH(“/portal/”).
    6. There is no need to select an Action at this time.

      User-added image

    7. Click Create.
    8. Create more Content Switching Policies for each website and protocol.
  6. To create a Content Switching VServer, such that one Virtual IP address can access both Web sites, complete the following sub-procedure:
    1. Expand the Traffic Management > Content Switching node.
    2. Select the Virtual Servers node.
    3. Click Add.
    4. Give the Content Switching Virtual Server a name. Keep in mind that you will have a different Content Switching Virtual Server for each protocol (e.g. HTTP vs SSL). However, each protocol-specific Content Switching Virtual Server will handle all of the websites.
    5. Click where it says No Content Switching Policy Bound.
    6. Click where it says Client to Select and select one of your Content Switching Virtual Servers.
    7. In the Target Load Balancing Virtual Server field, select the Load Balancing Virtual Server that matches the Content Switching Policy. Click Bind.
    8. Repeat the Content Switching Policy bindings for each website.

      User-added image

    9. If this Content Switching Virtual Server is SSL, then bind a Server Certificate, configure ciphers, disable SSL v3, etc.
    10. Click Create to finish creating the Content Switching Virtual Server.
    11. Create another Content Switching Virtual Server for other protocols (e.g. HTTP vs SSL).

NetScaler CLI

To configure the Content Switching VServer, similar to the one configured in the preceding procedure, from the command line interface of the appliance, run the following commands:

add server webserver1 webserver1.example.comadd server webserver2 webserver2.example.comadd serviceGroup portal_svcgrp Example HTTP 80bind serviceGroup portal_svcgrp webserver1bind serviceGroup portal_svcgrp webserver2add serviceGroup www_svcgrp Example HTTP 80bind serviceGroup www_svcgrp webserver1bind serviceGroup wwww_svcgrp webserver1add lb vserver portal_vserver-http HTTP 0.0.0.0 0 -persistenceType SOURCEIP -cltTimeout 180bind lb vserver portal_vserver-http portal_svcgrpadd lb vserver www_vserver-http HTTP 0.0.0.0 0 -persistenceType SOURCEIP -cltTimeout 180bind lb vserver www_vserver-http www_svcgrpadd cs policy csw_pol_portal-http -rule "HTTP.REQ.HOSTNAME.EQ("portal.example.com")"add cs policy csw_pol_www-http -rule "HTTP.REQ.HOSTNAME.EQ("www.example.com")"add cs vserver csw_vserv-http HTTP 192.168.168.170 80 -cltTimeout 180bind cs vserver csw_vserv-http portal_vserver-http -policyName csw_pol_portal-http -priority 100bind cs vserver csw_vserv-http www_vserver-http -policyName csw_pol_www-http -priority 110

Related:

Why is the Load command in a Zeppelin notebook not working?

IBM Customer Leave a comment
The Load command will not work properly if services are not running.

Related:

Event ID 4625 — Node Cleanup Success

PCIS Support Team Leave a comment

Event ID 4625 — Node Cleanup Success

Updated: November 25, 2009

Applies To: Windows Server 2008 R2

When a failover cluster is destroyed by running the Destroy Cluster command, the Cluster service requires access to disks in storage and other resources for complete removal of the cluster configuration. If this access is unavailable, you might need to take specific actions such as running a command to complete the removal of the configuration.

Event Details

Product: Windows Operating System
ID: 4625
Source: Microsoft-Windows-FailoverClustering
Version: 6.1
Symbolic Name: NODECLEANUP_RESET_NLBSFLAGS_PRESERVED
Message: Resetting the IPSec security association timeout registry value failed during cluster node cleanup. This is because the IPSec security association timeout was modified after this machine was configured to be a member of a cluster. For manual cleanup, execute the ‘Clear-ClusterNode’ PowerShell cmdlet on this machine. Alternatively, you may reset the IPSec security association timeout by deleting the ‘%1’ value and the ‘%2’ value from HKEY_LOCAL_MACHINE in the Windows registry.

Resolve
Confirm that the action of destroying a cluster was fully completed

An operation that was part of destroying the cluster did not succeed. Try restarting the server to see if this resolves the error. If not, use commands to force cleanup on former cluster nodes, and to force the clearing of persistent reservations on disks formerly used by the cluster. These commands help ensure that the cluster configuration has been completely removed.

If you do not currently have Event Viewer open, see “Opening Event Viewer and viewing events related to failover clustering.” If the event contains an error code that you have not yet looked up, see “Finding more information about error codes that some event messages contain.”

To perform the following procedures, you must be a member of the local Administrators group on the server, or you must have been delegated the equivalent authority.

Forcing cleanup on a former cluster node after the cluster has been destroyed

To force cleanup on a former cluster node after the cluster has been destroyed:

  1. On the former cluster node that you want to clean up, open an elevated Command Prompt window. To do this, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type:

    CLUSTER NODE /FORCECLEANUP

Forcing the clearing of persistent reservations on a disk formerly used by the cluster

To force the clearing of persistent reservations on a disk formerly used by the cluster:

  1. On one or more nodes in the cluster, open Disk Management (which is in Server Manager under Storage) and see if any disks formerly used by the cluster are visible from one of the nodes. If they are, note the node and the number that Disk Management uses to refer to that disk. For example, if the disk is listed as Disk 4 in Disk Management, note the number 4.
  2. On a node from which a formerly-clustered disk is visible in Disk Management, open an elevated Command Prompt window. To do this, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  3. Type:

    CLUSTER NODE /CLEARPR:disknumber

    where disknumber is the number of the disk as it appeared in Disk Management.

Opening Event Viewer and viewing events related to failover clustering

To open Event Viewer and view events related to failover clustering:

  1. If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
  3. To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources box, select FailoverClustering. Select other options as appropriate, and then click OK.
  4. To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.

Finding more information about the error codes that some event messages contain

To find more information about the error codes that some event messages contain:

  1. View the event, and note the error code.
  2. Look up more information about the error code in one of two ways:

Verify

To verify the cleanup of a cluster node, you can rerun the command for forcing cleanup and confirm that it completes successfully.

To perform the following procedure, you must be a member of the local Administrators group on the server, or you must have been delegated the equivalent authority.

To run the command that forces cleanup of a former cluster node:

  1. On the former cluster node on which you want to confirm cleanup, open an elevated Command Prompt window. To do this, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type:

    CLUSTER NODE /FORCECLEANUP

  3. View the results and confirm that node cleanup completed successfully.

Related Management Information

Node Cleanup Success

Failover Clustering

Related:

Event ID 2506 — Shared Folders (SMB) Server Configuration

PCIS Support Team Leave a comment

Event ID 2506 — Shared Folders (SMB) Server Configuration

Updated: January 27, 2011

Applies To: Windows Server 2008

The Server Message Block (SMB) protocol is what Windows uses to share files, printers, serial ports, and communicate this information between computers. The service must be configured correctly for the server to properly manage shared resources.

Event Details

Product: Windows Operating System
ID: 2506
Source: Server
Version: 6.0
Symbolic Name: EVENT_SRV_INVALID_REGISTRY_VALUE
Message: The value named %1 in the server’s registry key %2 was not valid, and was ignored. If you want to change the value, change it to one that is the correct type and is within the acceptable range, or delete the value to use the default. This value might have been set up by an older program that did not use the correct boundaries.

Resolve
Set a new parameter value for the server

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

To set a new paramter value:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click to select the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters
  3. Right-click mis-configured parameter, obtained from the error message, and click Modify.
  4. In the Value data box, type the desired value, and then click OK.

Note: If you want to change the value of a parameter, but are unable to change to an acceptable value, delete the parameter to use the default. The value may have been set up by an older program that did not use the correct boundaries.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify SMB configuration settings:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click to select the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters
  3. Verify that the correct parameters are present and contain the correct values.

 

Related Management Information

Shared Folders (SMB) Server Configuration

File Services

Related:

Event ID 119 — NLB Extended Affinity Configuration

PCIS Support Team Leave a comment

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

PCIS Support Team Leave a comment

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

PCIS Support Team Leave a comment

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 95 — NLB Port Rules Configuration

PCIS Support Team Leave a comment

Event ID 95 — NLB Port Rules Configuration

Updated: November 13, 2007

Applies To: Windows Server 2008

In a Network Load Balancing (NLB) cluster, port rules are configured to control how each port’s cluster network traffic is handled. The NLB cluster may fail to converge unless each port rule has a unique host priority (a number between 1 and 32), the port rules are consistent on all cluster hosts, you are using the proper number of port rules, and the virtual IP address is specified in a valid IPv4 or IPv6 address format.

 

Event Details

Product: Windows Operating System
ID: 95
Source: Microsoft-Windows-NLB
Version: 6.0
Symbolic Name: MSG_WARN_INCORRECT_VPN_PORT_RULE_SETTINGS
Message: NLB cluster [%2]: The NLB driver has detected one or more %3 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.

Resolve
Ensure that all NLB hosts have identical port rules

When a Network Load Balancing (NLB) host in the cluster either contains a different number of port rules from another host, or its configured port rules conflict with the port rules of another host, the cluster will not converge until the problem is corrected. You should first ensure that all NLB hosts have identical port rules, and then, if there are port rules that are not identical and if there are not the same number of port rules on each NLB host, you should reconfigure the port rules to make them identical.

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.

Ensure that all NLB hosts have identical port rules

To ensure that all NLB hosts have identical port rules:

  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 they are identical with the rules on the other NLB hosts.

If there are port rules that are not identical and if there are not the same number of port rules on each NLB host, you should reconfigure the port rules to make them identical.

Configure 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 add a new port rule, click Add. As required, modify the cluster IP address that you want this rule to apply to, the port range, protocols and filtering mode parameters as required, and then click OK.

Verify

You can verify that the port rules configuration is correct by first checking that a specific port is operating properly, and then checking that all Network Load Balancing (NLB) hosts are in a converged state.

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.

Verify that a specific port rule is operating properly

To verify that a specific port rule is operating properly:

  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 queryportport. Specify the port rule by using a port number that is within the range of the port rule that you want to query.

Verify that all NLB hosts are in the converged state

To verify that all 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 Port Rules Configuration

NLB Cluster

Related:

Event ID 94 — Network Adapter Functionality

PCIS Support Team Leave a comment

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 89 — Network Adapter Functionality

PCIS Support Team Leave a comment

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: