13-5
User
Guide

for

the

Cisco

Application

Networking

Manager

5.2
OL-26572-01
Chapter
13






Configuring

High

Availability
Understanding
ANM

High

Availability
Related
Topics

•
Understanding
ANM

High

Availability
Processes,
page
13-3
Ta
b

l

e


13-2
CLI
Sub-commands

for

Processes
Command
Sub-command
Description
/opt/CSCOanm/bin/anm-tool
info-services
Indicates
the

state

of

all

ANM

processes.

This

command

does

not

return
process
status

if

monit

is

not

running.
stop-services
Stops
all

ANM

processes,

including

monit.
Note
Monit
must

be

running

i

n
order

for

the

i

nfo-services
command
to
provide

status

information.
Note
When
ANM

is

running

in

HA

mode

and

the

standby

ANM

is

just
starting
up,

the

active

ANM

copies

its

entire

database

to

the
standby
ANM.

During

the

copy

process,

the

active

ANM

cannot
be
stopped

or

restarted

using

the

anm-tool

command.

Check

the
Admin
>

ANM

Management

page

for

the

HA

Replication

Status
and
wait

until

the

status

is

set

to

OK

before

attempting

to

stop
ANM.
start-services
Starts
the

relevant

ANM

processes.
restart-services
Restarts
the

relevant

ANM

processes.
Note
When
ANM

is

running

in

HA

mode

and

the

standby

ANM

is

just
starting
up,

the

active

ANM

copies

its

entire

database

to

the
standby
ANM.

During

the

copy

process,

the

active

ANM

cannot
be
stopped

or

restarted

using

the

anm-tool

command.

Check

the
Admin
>

ANM

Management

page

for

the

HA

Replication

Status
and
wait

until

the

status

is

set

to

OK

before

attempting

to

restart
ANM.
info
Provides
additional

information
(state,
whether
running
or

stopped,

start
time,
and

PID)

regarding

the

Java

processes.

Monit

need

not

be

running
for
this

command

t

o

return

i

nformation.

/opt/CSCOanm/bin/anm-ha
check
Checks
the

local

node’s

high

availability

configuration.
If
errors
are
returned,
HA

might

not

function

correctly

until

you

fix

the

errors.
Note
You
must

run

this
command
on

both
the
active

and

standby

node.
While
errors

might

indicate

a

problem,

they

could

also

simply

indicate
a
known

condition.

For

example,

you

receive

a

warning

i

f

the

ANM
cannot
ping

the

peer

node

via

either

of

the

specified

IP

ad

dresses;
however,
if

the

peer

is

down,

the

warning

can

be

ignored

because

this

is
a
known

issue.

It

is

al

so

possible

t

hat

no

e

rror

mi

ght

be

returned

even
though
there

is

a

configuration

problem.

For

example,

the

configuration
of
the

two

nodes

must

match;

however

the

check

sub-command

cannot
validate
that

the

configurations

match.
active
Forces
the

local

node

to

become

active

and

the

peer

node

to

become

the
standby
node.
standby
Forces
the

local

node

to

become

standby

and

the

peer

node

to

become
the
active

node.