7-47
User
Guide

for

the

Cisco

Application

Networking

Manager

5.2
OL-26572-01
Chapter
7






Configuring

Virtual

Servers
Configuring
Virtual

Servers
Ta
b

l

e


7-15
Sticky
Group

Attributes
Field
Description
Group
Name
Unique
identifier

for

the

sticky

group.

You

can

either

accept

the

automatically

incremented

entry

that

was
provided
or

you

can

enter

your

own.

Valid

entries

are

unquoted

text

strings

with

no

spaces

and

a

maximum
of
64

al

phanumeric

ch

aracters.

Type
Method
to

be

used

when

est

ablishing

st

icky

connections

and

configure

any

type-specific

at

tributes:
Note
The
available

selections

listed

in

the

Type
drop-down
list
will

vary
depending
on
your

selection

for
Application
Protocol

in

the

Properties

configuration

subset

(see

Ta

b

l

e


7-2 ).

For

example,

if

you
chose
HTTP

or

HTTPS

as

the

application

protocol,

only

IP

Netmask,

HTTP

Cookie,

HTTP

Header,
and
HTTP

Content

appear

as

selections

in

the

Type

drop-down

list.


HTTP
Content—The

virtual

server
is
to
stick
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

virtual
server
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.
See

Ta

b

l

e


9-3

for

additional

configuration

options.


HTTP
Header—The

virtual
server

is

to

stick

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
virtual
server

is

to

stick

a

client
to
the
same

server

for

multiple

subsequent
connections
as

needed

to

complete

a

transaction

using

the

client

source

IPv4

address,

the

destination
IPv4
address,

or

both.

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
s
ession

persis

tence.


V6
Prefix—(Requires

ACE

module

and

ACE

appliance

software

Version
A5(1.0)
or

later)
Indicates
that
the

virtual

server

is

to

stick

a

client

to

the

same

server

for

multiple

subsequent

connections

as
needed
to

complete

a

transaction

using

the

client

source

IPv6

address,

the

destination

IPv6

address,

or
both.
See

Ta

b

l

e


9-6

for

additional

configuration

options.


Layer
4

Payload—The

virtual

server

is

to

stick

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
virtual
server
is

to

stick

client

connections

to

the

same
real
server
based
on

a

RADIUS
attribute.


RTS
P


H

e

a

d

e

r

—The
virtual
server

is
to
stick

client
connections

to

the

same
real
server

based

on

the
RTSP
Session

header

field.

Ta

b

l

e


9-9

for

additional

configuration

options.


SIP
Header—The

virtual

server

is

to

stick

client

connections
to
the

same
real
server

based
on
the

SIP
Call-ID
header

field.
Sticky
Server
Farm
Existing
server
farm

that

is

to

act

as

the

primary

server

farm

for

this
sticky
group.

You

can

choose
*New*
to
create

a

new

server

farm.

If

you

chose

*New*,

configure

the

server

farm

using

the

information

in
Ta
b

l

e


7-13 .
Backup
Server

Farm
Existing

server

farm

that

is

to

act

as

the

backup

server

farm

this

sticky

group.

You

can

choose

*New*

to
create
a

new

server

farm.

If


you

chose

*New*,

configure

the

server

farm

using

the

information

in
Ta
b

l

e


7-13 .