6-43
User
Guide

for

the

Cisco

Application

Networking

Manager

5.2
OL-26572-01
Chapter
6






Configuring

Virtual

Contexts
Using
Resource

Classes
Related
Topics

•
Managing
ACE

Licenses,

page
6-36

•
Installing
ACE

Licenses,

page
6-37

•
Viewing
ACE

Licenses,

page
6-36

•
Uninstalling
ACE
Licenses,

page
6-39
Using
Resource

Classes
Resource
classes

are

the

means

by

which

you

manage

virtual

context

access

to

ACE

resources,

such

as
concurrent
connections

or

bandwidth

rate.

ACE

devices

are

preconfigured

with

a

default

resource

class
that
i

s

applied

to

the

Admin

context

and

any

user

context

upon

cr

eation.

The

default

resource

class

i

s
configured
to

allow

a

context

to

operate

within

a

range

that

can

vary

from

no

resource

access

(0%)

to
complete
resource

access

(100%).

When

you

use

the

default

resource

class

with

multiple

contexts,

you
run
the

risk

of

oversubscribing

ACE

resources.

This

means

that

the

ACE

permits

all

contexts

to

have

full
access
to

all

resources

on

a

first-come,

first-served

basis.

When

a

resource

is

utilized

to

its

maximum
limit,
the

ACE

denies

additional

requests

made

by

any

context

for

that

resource.
To
avoid

oversubscribing

resources

and

to

help

guarantee

access

to

a

resource

by

any

context,

you

can
create
customized

resource

cl

asses

that

you

associate

wi

th

one

or

mo

re

contexts.

A

context

becomes

a
member
of

the

resource

class

when

you

make

the

association.

Creating

a

resource

class

allows

you

to

set
limits
on

the

minimum

and

maximum

amounts

of

each

ACE

resource

that

a

member

context

is

entitled
to
use.

You

define

the

minimum

and

maximum

values

as

a

percentage

of

the

whole.

For

example,

you
can
create

a

resource

class

that

allows

its

member

contexts

access

to

no

less

that

25%

of

the

total

number
of
SSL

connections

that

the

ACE

supports.
You
can

limit

and

manage

the

allocation

of

the

fol

lowing

ACE

resources:

•
ACL
memory

•
Buffers
for


syslog

messages

and

TCP

out-of-order

(OOO)
segments

•
Concurrent
connections

(through-the-ACE

t

raffic)

•
Management
connections

(t

o-the-ACE

traffic)

•
Proxy
connections

•
Set
resource

limit

as
a
rate
(number
per

second)

•
Regular
expression

(regexp)

memory

•
SSL
connections

•
Sticky
entries

•
Static
or

dynamic

network

address

translations

(Xlates)
When
you

discover

ACE

devices,

the

ANM

detects

the

resource

class

information

and

imports

it

with
other
device

information.

If

an

ACE

is

not

configured

for

a

resource

class,

it

inherits

the

resource

class
configuration
of

the

virtual

context

it

is

associated

with.

If

an

ACE

does

have

a

resource

class
configuration
but

it

differs

from

one

configured

in

the

ANM,

the

discrepancy

is

logged

as

an

anomaly
but
otherwise

has

no

impact

on

the

import

process

or

the

ACE.
Ta
b

l

e


6-9

on

page

6-45

identifies

and

defines

the

resources

that

you

can

establish

for


resource

classes.
Related
Topics

•
Global
and
Local
Resource

Classes,

page
6-44