18-52
User
Guide

for

the

Cisco

Application

Networking

Manager

5.2
OL-26572-01
Chapter
18






Administering

the

Cisco

Application

Networking

Manager
Managing
ANM

•
Virtual
Center
Plugin

Registration—Allows

you
register

the

ANM

plugin

to

integrate

ANM

in

a
VMware
virtual

data

center

environment.

See

Appendix

B,

“Using

the

ANM

Plug-In

With

Virtual
Data
Centers.”
Checking
the

Status

of

the

ANM

Server
Note
Your
user

role

det

ermines
whether
you

can
use
this
option.
You
can

check

i

f

ANM

has

a

ba

ckup

server

and

to

vi

ew

t

he

server

st

atus.
The
ANM

server

can

be

configured

as

either

of

the

following:

•
A
non-HA

ANM.

The

non-HA

ANM

consists

of

onl

y
one
hos

t

and

is

referred
to
as
a
standalone
ANM.

•
An
HA

(high
availability
or

fault-tolerant)

ANM,

which
consists
of

two
hosts:
an

active
ANM

and
a
st

andby

ANM.

An

HA

ANM

has

a

virtual

IP

address

t

hat

i

s

always

assigned

to

t

he

active

ANM.
Users
log

into

this

virtual

IP

address—they

never

log

into

the

real

IP

addresses

of

the

hosts.

In
addition,
an

HA

ANM

has

a

secondary

NIC

and

IP

ad

dress

on

ea

ch

host


over

which

“heartbeat”
messages
are

used

to

arbitrate

which

host

is

active

and

which

is

standby.
Procedure
Step
1
Choose
Admin
>

ANM

Management

>

ANM.
The
ANM

Server

status

window

appears.

This

window

contains

the

following

information:
Ta
b

l

e


18-12
ANM
Server

Status

Information
Field
Description
HA
Replication

State
HA
replication

state

as

follows:

•
OK—This
is
an
HA

ANM

and

is

running

properly.

•
Standalone—This
is

a

non-HA

ANM;

therefore,

the

HA

attributes

and

operations
are
not
meaningful.

•
Stopped—This
is
HA
ANM

and

this
state
indicates

that
the

active

ANM

is

copying

its
entire
database

contents

to

the

standby

ANM.

This

normally

happens

when

the

standby
ANM
initially

starts

up

or

it

has

been

stopped

and

restarted

later.

This

process

normally
takes
a

few

seconds

to

a

few

minutes

depending

on

the

size

of

the

ANM

configuration

data
and
monitoring

data.

During

this

time,

the

active

ANM

cannot

be

stopped,

restarted,

or
fail
over.

•
Failed—This
is

an

HA

ANM

and
database
replication
cannot

proceed.

Most

likely

this

is
because
the

standby

ANM

is

unresponsive

or

is

unreachable.
Ve
r

s

i

o

n
Version
of


the

ANM

software.
Build
Number

and

Build
Ti
me

s

t

a

mp
Build
identification
information.
Time
Server

Started
Date
and

time

the

ANM

server

started.