7021541: Using Verastream Host Integrator with a Third-Party Load Balancer

Comparing Host Integrator vs. Third-Party Load Balancing

Load balancers distribute client requests across multiple servers. When choosing a load balancing solution appropriate for your environment, consider the following:

  • Host Integrator built-in Session Server load distribution requires no additional hardware or software products. Version 7.0 or higher uses a weighted pseudorandom distribution (see Technical Note 10108). Version 6.6 or earlier measures “load” based on the quantity of concurrent sessions in use by clients, as a percent of a configured maximum.
  • An external third-party load balancer (such as products from F5, Cisco, or Foundry Networks) can measure other factors, such as CPU utilization, or distribute clients in a round-robin or pseudorandom fashion. This option may be desired if your organization already uses a third-party load balancing product to fulfill monitoring and reporting functions.

Note: This information has been successfully applied in customer environments. However, Attachmate does not officially endorse any third-party load balancer, nor perform regular interoperability testing.

Configuring your Host Integrator Environment

To set up Host Integrator to use an external third-party load balancer:

  1. Install Host Integrator software on your server systems.

Note: Do not configure any domains in Administrative Console (version 7.0 or higher) or Administrative WebStation (version 6.6 or earlier). Domains are used only for Host Integrator built-in load balancing.

  1. Configure your load balancer and/or DNS to create a new common host name or IP address that will be load balanced.
    • If using a common host name, the new name should be different than the names entered when installing the Host Integrator software.
    • If using a common IP address, the new address should be different than the actual IP addresses of the Host Integrator servers.

Note: The individual Host Integrator session server IP addresses must also be reachable from the client. (The load-balanced connection is an initial command channel; the session servers provide their IP address and port information to the client connector for subsequent session communication.)

  1. Configure your external load balancer to monitor the health of Host Integrator Session Server services and systems (at a periodic “heartbeat” interval) using one or more of the following approaches:

Note: Do not send any data on the Host Integrator service connection. Session Server uses a proprietary binary communication and does not support any text command interface.

  1. Configure your external load balancer to distribute load across “alive” servers on a round-robin, random, or least-loaded basis. To determine the least-loaded server, use monitoring tools to retrieve the CPU usage of the systems or Session Server processes.
  2. When deploying models (using activatemodel and deactivatemodel commands, or Design Tool), use the specific Session Server system names (not the load balanced common name or address created in step 2 above).
  3. Since Host Integrator domains are not being used, your client code should use the ConnectToModel() or ConnectToSession() connector API method calls. For the server parameter, specify the load balanced name or address created in step 2 above.

Note: The suspendConnection() and resumeConnection() methods are not supported when using a third-party load balancing technology. Use of these methods in such environments may produce undesired results, such as the inability to resume suspended sessions.

Related:

Ghost 3.1 multicast issue

I need a solution

Hi

We have ghost 3.1 that deploy an image to multiple computers in multicast, and it works fast and doing it job.

When we try to deploy another image at the same time to multiple diferent computers from the same ghost machine, it fail to work in multicast, and works slow in unicast. it does not matter which image is the first and which one is second, the first one works in multicast and the second in unicast.

So, the question is basicly, is it an option to deploy two different images at the same time in a single ghost 3.1 server and both of them will work in multicast?

Thanks in advance

Ran

0

Related:

Event ID 4096 — NLB Host Configuration

Event ID 4096 — 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: 4096
Source: Microsoft-Windows-NLB
Version: 6.1
Symbolic Name: IDS_INSTALL_WITH_MSCS_INSTALLED
Message: Configuration completed. Microsoft Cluster Service is also installed on this machine, and this may prevent the proper operation of both.

Resolve
Separate MSCS and NLB clusters

You cannot install Network Load Balancing (NLB) on a computer that is already a member of a failover cluster. This can interfere with a failover cluster’s use of network adapters, and therefore, this configuration is not supported.

You must use a separate group of computers for Failover Clustering and for NLB Clustering.

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

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

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: