I have a question about sticky for MS Terminal services. Now I have one 4710 demo box and MS terminal servers farm containg 15 servers. All servers running Windows 2003 Standard Edition. ACE working in bridge mode. Sticky config:
sticky ip-netmask 255.255.255.255 address both SG1
All working fine, but sticky timeout decreased for active clients. In Administration Guide present following:
The sticky timeout specifies the period of time that the ACE keeps (if possible) the IP address sticky information for a client connection in the sticky table after the latest client connection terminates. The ACE resets the sticky timer for a specific sticky-table entry each time that the appliance opens a new connection or receives a new HTTP GET on an existing connection matching that entry. High connection rates may cause the sticky table entries to age out prematurely.
By default, the ACE ages out a sticky table entry when the timeout for that entry expires and no active connections matching that entry exist. To specify that the ACE time out IP address sticky table entries even if active connections exist after the sticky timer expires, use the timeout activeconns command.
What's happened after 120 minutes for active clients? Sticky entry removed from table and if session is broken and client try to reconnect ACE connect it to different server? How avoid this?