Installation guide

7-22
Device Manager Guide, Cisco ACE 4700 Series Application Control Engine Appliance
OL-26645-02
Chapter 7 Configuring Stickiness
Configuring Sticky Statics
Step 4 In the Sequence Number field, either accept the automatically incremented number for this entry or enter
a new sequence number.The sequence number indicates the order in which multiple sticky static
configurations are applied.
Step 5 In the Type field, confirm that the correct sticky group type is selected. If you select multiple sticky
groups and are creating a new static sticky entry, select the sticky group type to use as shown in
Table 7-10.
Table 7-10 Sticky Group Types
Sticky Group Description
HTTP Content Indicates that the ACE appliance is to stick a client to a server based on the
content of an HTTP packet. You can specify a beginning pattern and ending
pattern, the number of bytes to parse, and an offset that specifies how many
bytes to ignore from the beginning of the data.
HTTP Cookie Indicates that the ACE appliance is either to learn a cookie from the HTTP
header of a client request or to insert a cookie in the Set-Cookie header of
the response from the server to the client, and then use the learned cookie to
provide stickiness between the client and server for the duration of the
transaction.
HTTP Header Indicates that the ACE appliance is to stick client connections to the same
real server based on HTTP headers.
IP Netmask Indicates that the ACE appliance is to stick a client to the same server for
multiple subsequent connections as needed to complete a transaction using
the client source IP address, the destination IP address, or both based on the
IPv4 netmask. You can optionally configure an IPv6 prefix length with this
sticky type.
Note If an organization uses a megaproxy to load balance client requests
across multiple proxy servers when a client connects to the Internet,
the source IP address is no longer a reliable indicator of the true
source of the request. In this situation, you can use cookies or
another sticky method to ensure session persistence.
IPv6 Prefix Indicates that the ACE appliance is to stick a client to the same server for
multiple subsequent connections as needed to complete a transaction using
the client source IP address, the destination IP address, or both based on the
IPv6 prefix length. You can optionally configure an IPv4 netmask with this
sticky type.
Layer 4 Payload Indicates that the ACE appliance is to stick a client to a server based on the
data in Layer 4 frames. You can specify a beginning pattern and ending
pattern, the number of bytes to parse, and an offset that specifies how many
bytes to ignore from the beginning of the data.
RADIUS Indicates that the ACE appliance is to stick client connections based on the
following RADIUS attributes: Calling station ID or Username.
RTSP Header Indicates that the ACE appliance is to stick client connections based on
information in the RTSP session header. With RTSP header stickiness, you
can specify a header offset to provide stickiness based on a unique portion
of the RTSP header.
SIP Header Indicates that the ACE appliance is to stick client connections based on the
SIP Call-ID header field. SIP header stickiness requires the entire SIP
header, so you cannot specify an offset.