7-50
User
Guide

for

the

Cisco

Application

Networking

Manager

5.2
OL-26572-01
Chapter
7






Configuring

Virtual

Servers
Configuring
Virtual

Servers

•
Click
Deploy
Later

to

save

your
entries
and
apply
them
at

a

later

time.
Related
Topics

•
Configuring
Virtual

Servers,

page
7-2

•
Configuring
Virtual

Server

Properties,

page
7-11

•
Configuring
Virtual

Server
SSL
Termination,

page
7-17

•
Configuring
Virtual
Server
Protocol

Inspection,

page
7-18
Configuring
Virtual

Server

Default

Layer

7

Load

Balancing
You
can

configure

default

Layer

7

load-balancing

actions

for

al

l

network

traffic

that

does

not

meet
previously
specified

match

conditions.
Assumption
Make
sur

e

t

hat

a

vi

rtual

ser

ver

has

been

configured

in

the

Properties

configuration

subset.

For

mor

e
information,
see

the

“Configuring

Virtual

Server

Properties”

section

on

page

7-11 .

See

the

“Configuring
Virtual
Servers”

section

on

page

7-2

for

information

on

configuring

a

virtual

server.
Procedure
Step
1
Choose
Config
>

Devices

>

context

>

Load

Balancing

>

Virtual

Servers.
The
Virtual

Servers

table

appears.
Step
2
In
the

Virtual
Servers
table,

choose

the

virtual

server

that

you

want

to

configure

for

default

Layer

7

load
balancing,
and

click

Edit.
The
Virtual

Server

configuration

window

appears.
Step
3
In
the

Virtual

Server

configuration

window,

click
Default
L7

Load-Balancing

Action.
The
Default

L7

Load-Balancing

Action

configuration

pane

appears.
Step
4
In
the

Primary

Action

field

of

the

Default

L7
Load-Balancing

Action

configuration

pane,

choose

the
default
action

that

the

virtual

server

is

to

take

in

response

to

client

requests

for

content

when

specified
match
conditions

are

not

met:

•
Drop—Client
requests
that
do

not

meet

specified

match
conditions
are

to

be

discarded.

Continue
with
Step

9

.

•
Fo
r

wa

r

d

—Client

requests
that
do

not

meet

specified
match

conditions
are
to
be

forwarded

without
performing
load

balancing

on

the

requests.

Continue

with

Step

9 .

•
Load
Balance—Client
requests
for
content
are

to

be
directed
to

a

server

farm.

Continue

with
Step
6
.

•
Sticky—Client
requests

for

content

are

to

be

handled

by

a

sticky

group

when

match

conditions

are
met.
Continue

with

Step

7 .
Step
5
(Optional)
From

the

HTTP

Header

Modify

Action

List

drop-down

list,

choose

an

existing

Action

List

or
choose
New

to

display

the

Action

List

configuration

table

and

create

a

new

one.

For

more

information,
see
th

e

“Configuring

an

HTTP

Header

Modify

Action

List”

section

on

pa

ge

14-85 .