13-8
User
Guide

for

the

Cisco

Application

Networking

Manager

5.2
OL-26572-01
Chapter
13






Configuring

High

Availability
Understanding
ACE

Redundancy

•
Inconclusive—Indicates
that
ANM
was

able

to

determine

that

the

given
ACE
was

configured

in
HA,
however
ANM

was

able

to

find

more

than

one

ACE

module

or

ACE

appliance

that

appeared

to

be

a
peer.
In

this

case,

ANM

was

unable

to

conclusively

find

a

unique

HA

peer

for

the

given

ACE

module
or
ACE

appliance.

For

additional

details

on

ad

dressing

this

st

ate,

see

the

“ANM

Requirements

for
ACE
High

Availability”

section

on

page

5-8

for

details.
Inconclusive
is

not

shown

in

the

HA

State

field

but

is

shown

in

the

HA

Peer

field.

It

is

possible

that
a
context

HA

peer

is

inconclusive,

but

its

HA

State

and

HA

Peer

state

are

still

shown

normally
because
these

states

are

from

context

polling

from

the

ACE

device.
Note
When
you

upgrade

or

downgrade

the

ACE

from

one

software

version

to

another,

there

is
a

point
in
the

process

when

the

two

ACEs

have

different

software

versions

and,

therefore,

a

software
incompatibility.
When

the

Standby

Warm

state

appears,

this

means

that

the

active

ACE

will
continue
to

synchronize

configuration

and

state

information

to

the

standby

even

though

the
standby
may

not

recognize

or

understand

t

he

software

commands

or

st

ate

information.

This
standby
state

al

lows

the

st

andby

ACE

to

come

up

with

best-effort

support.
Related
Topics

•
ACE
High

Availability

Polling,
page
13-7

•
ACE
Redundancy

Protocol,

page
13-8
ACE
Redundancy

Protocol
You
can

configure

a

maximum

of

two

ACEs

of

the

same

type

(peers)

for

redundancy

in

the

same

Catalyst
6500
switch

or

in

different

chassis

for

redundancy.

Each

peer

ACE

can

contain

one

or

more

fault-tolerant
(FT)
groups.

Each

FT

gr

oup

consists

of

t

wo

members:

one

active

context

and

one

standby

context.

An
FT
gr

oup

has

a

unique

gr

oup

ID

that

you

assign.
Note
For
t

he
replication
process
t

o

function
properly
and
successfully
replicate
the

configuration
for

a

use

r
context
when

switching

from

the

active

context

to

the

standby

context,

ensure

that

each

user

context

has
been
added

to

the

FT

group.

All

applicable

user

contexts

must

be

part

of

an

FT

group

for

redundancy

to
function
properly.
One
virtual

MAC

address

(VMAC)

is

associated

with

each

FT

group.

The

format

of

the

VMAC

is:
00-0b-fc-fe-1b-groupID.
Because

a

VMAC

does

not

change

upon

switchover,

the

client

and

server

ARP
tables
does

not

require

updating.

The

ACE

selects

a

VMAC

from

a

pool

of

virtual

MACs

available

to

it.
For
more

information,

see

the

“Configuring

Virtual

Contexts”

section

on

page

6-8 .
Each
FT

group

acts

as

an

independent

redundancy

instance.

When

a

switchover

occurs,

the

active
member
in

the

FT

group

becomes

the

standby

member

and

the

original

standby

member

becomes

the
active
member.

A

switchover

can

occur

for

the

following

reasons:

•
The
active

member

becomes

unr

esponsive.

•
A
tracked

host

or

interface

fails.

•
You
force

a

switchover

for

a

high

availability

group
by
clicking
Switchover
in

the

HA

Groups

table
(see
the

“Switching

Over

an

ACE

High

Availability

Group”

section

on

page

13-22 ).