9-8
User
Guide

for

the

Cisco

Application

Networking

Manager

5.2
OL-26572-01
Chapter
9






Configuring

Stickiness
Configuring
Sticky

Groups
Ta
b

l

e


9-1
Sticky
Group

Attributes
Field
Description
Group
Name
Sticky
group

identifier.

Valid

entries

are

unquoted

text

strings

with

no

spaces

and

a

maximum

of
64
alphanumeric

characters.
Ty
p

e
Method
to

be

used

when

est

ablishing

st

icky

connections

and

to

configure

any

t

ype-specific
attributes.
The

choices

are

as

follows:

•
HTTP
Content—The

ACE

sticks

client

connections

to
the
same

real

server

based

on

a
string
in
the

data

portion

of

the

HTTP

packet.

See

Ta

b

l

e


9-2

for

additional

configuration

options.

•
HTTP
Cookie—The

ACE

either

learns

a

cookie

from

the
HTTP

header

of

a

client

request

or
inserts
a

cookie

in

the

Set-Cookie

header

of

the

response

from

the

server

to

the

client

and

then
uses
the

learned

cookie

to

provide

stickiness

between

the

client

and

server

for

the

duration

of
the
transaction.

See

Ta

b

l

e


9-3

for

additional

configuration

options.

•
HTTP
Header—The

ACE

sticks

client

connections

to
the

same

real

server

based

on

HTTP
headers.
See

Ta

b

l

e


9-4

for

additional

configuration

options.

•
IP
Netmask—The

ACE

sticks
a
client
to
the

same

server

for
multiple
subsequent
connections
as
needed

to

complete

a

transaction

using

the

client

source

IPv4

IP

address,

the

destination
IPv4
IP

address,

or

both.

You

can

optionally

configure

an

IPv6

prefix

length

with

this

sticky
type.
IPv6

requires

ACE

module

and

ACE

appliance

software

Version

A5(1.0)

or

later.

See
Ta
b

l

e


9-5

for

additional

configuration

options.
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.

•
V6
Prefix—(Option
that

appears

only

for

ACE

module

and

ACE

appliance

software

Version
A5(1.0)
or

later.)

The

ACE

appliance

sticks

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

their

IPv6

prefix.

You

can

optionally

configure

an
IPv4
netmask

with

this

sticky

type.

See

Ta

b

l

e


9-6

for

additional

configuration

options.

•
Layer
4

Payload—The

ACE

sticks

client
connections

to

the

same

real

server

based

on

a

string
in
the

payload

portion

of

the

Layer

4

protocol

packet.

See

Ta

b

l

e


9-7

for

additional
configuration
options.

•
RADIUS—The
ACE

sticks

client
connections
to

the

same
real

server

based
on
a
RADIUS
attribute.
See

Ta

b

l

e


9-8

for

additional

configuration

options.

•
RTS
P


H

e

a

d

e

r

—The

ACE

sticks
client

connections

to

the

same

real

server

based
on
the
RTSP
Session
header

field.

See

Ta

b

l

e


9-9

for

additional

configuration

options.

•
SIP
Header—The

ACE

sticks

client

connections

to

the

same

real

server

based

on

the

SIP
Call-ID
header

field.
Cookie
Name
This
option

appears

for

sticky

type

HTTP

Cookie.
Enter
a

unique

identifier

for

the

cookie.

Valid

entries

are

unquoted

text

strings

with

no

spaces

and
a
maximum

of

64

a

lphanumeric

characters.