13-31
User
Guide

for

the

Cisco

Application

Networking

Manager

5.2
OL-26572-01
Chapter
13






Configuring

High

Availability
Synchronizing
ACE

High

Availability

Configurations
Note
Although
a
context
mi

ght

have
been
configured

for

sysl

og

notification,

changes

applied
to

t

he

st

andby
ACE
configuration

can

change

syslog

not

ification

configuration

so

that

you

are

not

notified

of

t

he
out-of-sync
configurations.

As

a

re

sult,

i

t

is

important

for

you

t

o

manually

synchronize

ANM

with

the
standby
ACE.
Synchronizing
configuration

files

for

the

standby

ACE

requires

the

following:
1.
Auditing
the

standby
ACE
to

confirm

that

its

configuration
does

not

agree

with

the
ANM-maintained
configuration

data

for

the

ACE.

See

Synchronizing

Virtual

Context
Configurations,
page

6-105 .
2.
Uploading
the

configuration
from

the

standby

ACE

to
the
ANM

server.

See
Synchronizing
Virtual
Context
Configurations,

page

6-105 .
3.
Ensuring
that
the
SSL

certificate/keys

are

imported

and
identical

for
the
pair.

See
Synchronizing
SSL
Certificate

and

Key

Pairs

on

Both

ACE

Peers,

page

13-32 .
4.
For
an

Admin

context,
uploading

configurations

on

any

newly

imported

user

contexts.

If

new

user
contexts
are

not

updated,

they

cannot

be

managed

usi

ng

ANM.
Synchronizing
Virtual

Context

Configurations

in

High

Availability

Mode
When
configuration

changes

ar

e

made

from

ANM

on

any

of

t

he

ACE

devices

i

n

a

HA

pair,

ANM
automatically
detects

the

active

HA

peer

and

deploys

the

configuration

changes

to

the

active

ACE

alone.
ANM
does

not

attempt

to

deploy

a

configuration

to

a

standby

ACE

even

if

you

selected

the

standby

ACE
from
the

ANM

device

tree.

ANM

detects

the

active

ACE

and

will

always

deploy

configuration

changes
only
to

the

active

ACE.

In

addition,

if

ACE

HA

auto-sync

is

enabled,

after

the

deployment

is

successful,
ANM
will

locally

replicate

the

configuration

in

the

ANM

database

on

the

standby

as

well

to

ensure

that
the
ANM

configuration

is

in

synchronization

with

that

of

the

two

ACE

peers.
In
a

high

availability

pair,

the

two

configured

virtual

contexts

synchronize

with

each

other

as

part

of

their
ongoing
communications.

However,

their

copies

do

no

t

synchronize

in

ANM

and

the

configuration

on
the
standby

member

may

become

out-of-sync

with

the

configuration

on

the

ACE.
After
the

active

member

of

a

high

availability

pair

fails

and

the

standby

member

becomes

active,

the
newly
active

member

detects

any

out-of-sync

virtual

context

configurations

and

reports

that

status

in

the
Virtual
Contexts

table

so

that

you

can

synchronize

the

virtual

context

configurations.
Note
If
a

context

is
put
into

an
out-of-sync
state,
this
context

will
be
automatically

synchronized
by

the
backend
ANM.

It

is

not

necessary

for

you

to

perform

an

explicit

synchronization

to

take

care

of

the
out-of-sync
state.
For
i

nformation

on

syn

chronizing

virtual

context

configurations,

see

Synchronizing

Virtual

Context
Configurations,
page

6-105 .
Related
Topics

•
Configuring
ACE
High

Availability

Peers,

page
13-15

•
Configuring
ACE

High

Availability

Groups,

page
13-17

•
Synchronizing
Virtual

Context

Configurations,

page
6-105