
Deploying Equalizer with MS Terminal Services
Deployment Guide
© 2010 Coyote Point Systems, Inc. All Rights Reserved. | www.coyotepoint.com 12
Configuration Example 2:
MSTS/Equalizer Deployment with IP Redirect Session Services
Overview
The obvious pitfall of the previous example configuration is that the power of
Equalizer's load balancing algorithms (a key advantage over using MS load
balancing solutions like NLB or Session Broker load balancing) gets applied to a
particular client at a specified interval set by the MSTS session timer and cluster
sticky timer, and not on each new login.
This disadvantage is overcome by employing MSTS Session Broker (on MSTS 2008;
Session Directory on MSTS 2003) to manage sessions across the server farm.
Equalizer and MSTS session services cooperate to allow an existing server
session to continue on client reconnect, even if Equalizer initially load balances
the client connection to another server.
In contrast to the previous configuration, this configuration requires:
• An Equalizer cluster sticky time of 0.
• If running on MSTS 2008, each MSTS server has Session Broker Load
Balancing disabled.
• On both MSTS 2003 and 2008, each MSTS server must have IP redirection
enabled.
• For session redirection to work, clients must appear to Equalizer and the
servers behind it to be on the same subnet as Equalizer's internal
interface (in single network mode) or external interface (in dual network
mode).
MSTS servers must be able to connect directly to clients on the internal
or external interface subnet, depending on the network mode. This may
require NAT on firewalls between clients and Equalizer, a VPN, or special
routing, depending on your network configuration.
• The spoof option must be disabled on the cluster.
Deployment Steps
The steps required to set up the example configuration involve defining the
Equalizer cluster and the associated parameters, and defining the servers and
server settings:
Kommentare zu diesen Handbüchern