Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Can the CSS be told not to remove sticky entries if a matching active flow exits?


With the CSS when you enable sticky connections with a timeout, it only resets the idle timer for the sticky entry when a new connection is made and ignores the fact that there is active connections/flows that match the entry.

On the ACE it seems to be differnt. The doc's say "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 "TIMEOUT ACTIVECONNS".

The CSS seems to miss the feature i've highlighted in bold. Is there a way on the CSS to have it behave the same with the ACE does, so if i make a single connection and the CSS creates a sticky entry and that connection is constantly active with data... then the CSS will either A) reset the idle time for the sticky entry because the flow is not idle or B) let the sticky entry drop to zero but just not delete the sticky entry because the flow is not idle.

Many thanks,


CreatePlease login to create content