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 timeout 120 serverfarm TSTERM
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 timeoutactiveconns 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?
The sticky table uses a timer to expire entries in its table. 2 possibilities exist here:
- Active connects cannot timeout: When a client connects the first time, an entry in the sticky table is created. As long as connections from that client are seen, the timer is reset. That means that if the timer is 2 hours, an idle time from that client needs to be 2 hours before the entry is removed. Everytime that client reconnects within the 2 hours, the timer is reset.
- Active connects do timeout: When a client connects the first time, an entry in the sticky table is created, and the expire timer is started. If the client is idle or new connections are made, the expire timer is never reset and keeps running. When the timer expires, the entry is removed from the sticky table, and a new load-balancing decision is made on the frist connection after the timer has expired.
For you scenario, the best is not to timeout active connections. This is also the default behaviour of the ACE.
In any case, you can configure "no timeout activeconns" in your sticky serverfarm config.
Have you concidered RDP load-balancing on ACE?
You need a Session Director that passes routing tokens.
In my config "Active connects cannot timeout", but for RDP it's doesn't work. Timer isn't reset and continue to decrease. I verify this with sh stiscky database command for active client. And I can't use Session Directory because server farm must running Windows Enterprise or Datacenter Editon. We use Standard Edition.
class-map type management match-any remote_access 2 match protocol xml-https any 3 match protocol icmp any 4 match protocol telnet any 5 match protocol ssh any 6 match protocol http any 7 match protocol https any 8 match protocol snmp any class-map match-all slb-TSTERM-vip 2 match virtual-address 10.0.0.126 tcp eq rdp
policy-map type management first-match remote_mgmt_allow_policy class remote_access permit
policy-map type loadbalance rdp first-match slb-TSTERM-vip class class-default sticky-serverfarm SG-TSTERM
I changed policy to include all traffic, but it doesn't work. Sticky timer continue to decrease for active RDP sessions. I think it's ok, because ACE reset sticky timer only for new TCP session or HTTP request.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...