This document explains how the CSS automatically removes entries from the sticky table. This process is completely automated, however, there is a sticky purge command in debug mode that can be used to force this behavior. This is sample command output:
css1# llama css1(debug)# sticky-purge all-sticky ALL Sticky Purge on Slot 5, subslot 1: Total number of entries purged is 0. css1(debug)#
For more information on document conventions, see the Cisco Technical Tips Conventions.
Readers of this document should be knowledgeable of:
concept of sticky as used with the CSS
For more information, refer to Configuring Stickiness on a Cisco CSS 11000 Using HTTP Redirects .
The information in this document is based on the software and hardware versions below.
WebNS versions 6.x / 7.x and higher
CSS 11000 Series and CSS 11500
The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.
The CSS has a 32K sticky table that contains entries for the sticky source-ip command and sticky Secure Socket Layer (SSL). This amount increased to 128K entries if the Service Connection Manager (SCM) has 288Mb of memory on board.
Sticky cookies are not maintained in the sticky table on the CSS. After the cookie is assigned to a client, the client stores the cookie locally and provides it to the CSS when in session. The CSS does not need to store the cookie since the client always provides it.
These are three reasons for an entry to be removed from the sticky table:
By default, using a First In First Out (FIFO) method. Entries remain in the table until the 32K or 128Kbuffer is full. At that time, any new entries cause the CSS to remove an entry based on FIFO.
The default behavior changes if the sticky-inact-timeout minutes command is issued. If this command is used, the CSS removes an idle sticky entry according to the number of minutes configured in the content rule. This is an example:
owner arrowpoint content L5sticky vip address 126.96.36.199 add service test1 add service test2 protocol tcp port 443 url "/*" advanced-balance ssl application ssl sticky-inact-timeout 9 !--- The entry is removed after nine minutes. active
Note: When the sticky-inact-timeout command is issued, the CSS has filled the 32K or 128K buffer, and no entries are set to timeout, the CSS rejects the next sticky request.
When a content rule is suspended and reactivated, the sticky table entries applied to that rule are removed.
To view the sticky table entries, issue this command:
CSS# show sticky-table all-sticky ALL Sticky List on Slot 5, subslot 1: Entries for page 1. Entry Hash Rule Rule Srv Srv Time(Sec) Hit Col Elem Inact Number Value Indx State Indx State Elapsed Cnt Cnt Type Cfg(Min) ------------------------------------------------------------------------------ Total number of entries found is 0. CSS#
The Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers.
Refer to Cisco Technical Tips Conventions for information on conventions used in this document.