9-16

User

Guide

for

the

Cisco

Application

Networking

Manager

5.2

OL-26572-01

Chapter

9

Configuring

Stickiness

Configuring

Sticky

Statics

The

Sticky

Groups

table

and

Sticky

Statics

tab

appears.

If

you

do

not

see

the

Sticky

Statics

tab

beneath

the

Sticky

Groups

table,

click

the

Switch

between

Configure

and

Browse

Modes

button.

Step

2

From

the

Sticky

Groups

table,

choose

the

sticky

group

that

you

want

to

configure

for

sticky

statics

Step

3

From

the

Sticky

Statics

tab,

click

Add

to

add

a

new

entry

to

the

table,

or

select

an

existing

entry,

then

click

Edit

to

modify

it.

The

St

icky

St

atics

configuration

screen

appears.

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

i

n

which

multiple

sticky

st

atic

configurations

are

applied.

The

sequence

number

indicates

the

order

in

which

multiple

sticky

static

configurations

are

applied.

Step

5

From

the

Type

drop-down

list,

choose

the

sticky

group

type.

The

ch

oices

ar

e

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.

•

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.

•

HTTP

Header—The

ACE

sticks

client

connections

to

the

same

real

server

based

on

HTTP

headers.

•

IP

Netmask—The

ACE

sticks

a

client

to

the

same

server

for

multiple

subsequent

connections

as

needed

to

complete

a

transaction

using

t

he

client

sour

ce

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.

•

V6

Prefix—(Option

that

appears

only

for

ACE

module

and

ACE

appliance

software

Version

A5(1.0)

or

later)

The

ACE

sticks

a

client

to

the

same

server

for

multiple

subsequent

connections

as

needed

to

complete

a

transaction

using

t

he

client

sour

ce

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—The

ACE

st

icks

client

connections

to

t

he

same

real

ser

ver

based

on

a

st

ring

in

the

payload

portion

of

the

Layer

4

protocol

packet.

•

RADIUS—The

ACE

sticks

client

connections

to

the

same

real

server

based

on

a

RADIUS

attribute.

•

RT

S

P

H

e

a

d

e

r

—The

ACE

sticks

client

connections

to

the

same

real

server

based

on

the

RTSP

Session

header

field.

•

SIP

Header—The

ACE

sticks

client

connections

to

the

same

real

server

based

on

the

SIP

Call-ID

header

field.

Step

6

If

you

chose

HTTP

Cookie,

HTTP,

RTSP,

or

SIP

Header

for

the

sticky

type,

in

the

Static

Value

field,

enter

the

cookie

string

value.

Valid

entries

are

unquoted

text

strings

with

a

maximum

of

255

alphanumeric

characters.

If

the

string

includes

spaces,

enclose

the

string

with

quotes.