Alteon Application Switch Operating System Application Guide
Persistence
598
Document
ID:
RDWR-ALOS-V2900_AG1302
For information on how to configure your network for SLB, see
Server Load Balancing, page 165
2. If a proxy IP address is not configured on the client port, enable DAM for real servers.
3. Select session ID-based persistence as the persistent binding option for the virtual port.
4. Enable client processing on the client port.
Windows Terminal Server Load Balancing and Persistence
Windows Terminal Services refers to a set of technologies that allow Windows users to run Windows-
based applications remotely on a computer running as the Windows Terminal Server. Alteon includes
load balancing and persistence options designed specifically for Windows Terminal Services.
In a load-balanced environment, a group of terminal servers have incoming session connections
distributed in a balanced manner across the servers in the group. The Windows session director is
used to keep a list of sessions indexed by username. This allows a user to reconnect to a
disconnected user session.
The session director provides functionality that allows a group of terminal servers to coordinate the
reconnection of disconnected sessions. The session director is updated and queried by the terminal
servers whenever users log on, log off, or disconnect their sessions while leaving their applications
active.
The client can be reconnected to the terminal server where the user's disconnected session resides
using the routing token information. The session director passes the routing token information to
the client with the correct server IP address embedded. The client presents this routing token to the
load balancer when it reconnects to the virtual IP address. The load balancer deciphers the token
and sends the client to the correct terminal server.
In some instances, a dedicated session director may not exist. If this is the case, enable the
userhash functionality to perform the terminal server binding operation based on user name
hashing.
By default, Windows Terminal Server traffic uses TCP port 3389 but it can configured to work on any
non-standard port.
For further information regarding Windows Terminal Services, refer to the Microsoft Web site.
Figure 97 - Windows Terminal Server Load Balancing Network Topology, page 599
illustrates a
sample Windows Terminal Server Load Balancing network topology:
>> # /cfg/slb/adv/direct ena
>> # /cfg/slb/virt <virtual server number> /service <virtual port> pbind sslid
>> # /cfg/slb/port <port number> /client ena