5-9
User
Guide

for

the

Cisco

Application

Networking

Manager

5.2
OL-26572-01
Chapter
5






Importing

and

Managing

Devices
Modifying
the

ANM

Timeout

Setting

to

Compensate

for

Network

Latency

•
Update
the

management

interface

on

ACE2

with

IP

address

10.10.10.12

to

have

10.10.10.10

as

the
peer
IP

address.
An
ACE

module

or

appliance

may

have

many

other

management

interfaces

defined,

but

ANM

is
particularly
interested

only

in

the

management

interface

whose

IP

address

is

used

for

importing

into
ANM.
When
ANM

is

unable

to

determine

a

unique

ACE

HA

peer

pair,

it

displays

an

Inconclusive

state

in

the
ACE
HA

State

column

of

the

All

Virtual

Contexts

table

(Config

>

Devices

>

Virtual

Context
Management)
or

the

Virtual

Contexts

listing

page.

The

Inconclusive

state

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.

You

must

then

perform

the

actions
outlined
in

this

section

to

fix

the

ACE

that

is

in

this

state.
More
information

will

appear

in

the

tooltip

for

the

Inconclusive

state

to

specify

whether

this

state

was
reached
because

the

FT

interface

VLAN

and

the

IP

address/peer

IP

address

was

not

unique,

or

because
the
peer

IP

address

on

the

management

interface

was

not

unique.
Based
on

the

information

provided

to

you

in

the

tooltip

for

the

Inconclusive

state,

you

must

update

the
ACE
configuration

as

described

in

the

configuration

requirements

outlined

above.

After

you

make

these
configuration
changes,

resynchronize

the

affected

ACE

devices

in

ANM

to

update

the

configuration

and
HA
mapping.

For

more

information

about

synchronizing

virtual

contexts,

see

the

“Creating

Virtual
Contexts”
procedure

on

pa

ge

6-2 .
Modifying
the

ANM

Timeout

Setting

to

Compensate

for

Network
Latency
You
can

adjust

the

amount

of

time

that

ANM

waits

for

a

response

from

a

device

that

you

want

ANM

to
import.
You

may

need

to

adjust

the

timeout

value

when

network

latency

prevents

ANM

from

establishing
a
communication

link

with

the

device

to

be

imported.
To
establish

communications

between

ANM

and

the

device

during

the

device

import

process,

the

device
sends
requests

to

ANM

for

the

required

device

username

and

password

information.

After

ANM
provides
the

device

username,

it

waits

two

seconds

for

the

device

to

make

the

next

request

for

the
password.
If


network

latency

pr

events

the

password

request

from

arriving

within

two

seconds

of
providing
the

username,

the

connection

times

out,

preventing

ANM

from

importing

the

device.
This
type

of

issue

can

occur

when

importing

devices

that

are

Telnet-managed

or

require

remote

user
authentication.
To

compensate

for

the

resulting

network

latency,

you

can

modify

the

default

two-second
timeout
value

by

editing

the

ANM

cs-config.properties

file.
Procedure
Step
1
Modify
the

timeout

value

to

20000
milliseconds
(20
seconds)

as

follows:

•
ANM
Server—Open

the

/opt/CSCOanm/etc/cs-config.properties

file

in

a

text

editor
and
add
the
following
line

to

the

end

of

the

file:
telnet.transport.login.timeout=20000

•
ANM
Virtual

Appliance—Enter
the
following

command:
anm-property
set

telnet.transport.login.timeout

20000