6-78
User
Guide

for

the

Cisco

Application

Networking

Manager

5.2
OL-26572-01
Chapter
6






Configuring

Virtual

Contexts
Configuring
Security

with

ACLs
This
option

appears

only

when

you

have

sel

ected

a

spe

cific

device

for

the

copy

operation

in

Step

2.


If
you
selected

multiple

devices

in

Step

2,

then

each

device

copies

its

latest

successful

backup

file

to

the
remote
ser

ver.
Step
5
Click
the

radio

button

of

the

transfer

protocol

to

use.

•
FTP—File
Transfer

Protocol

•
SFTP—Secure
File

Transfer

Protocol

•
TFTP—Trivial
File

Transfer

Protocol
Step
6
In
the
Username

field,
enter
the

username

that

the

remote

server

requires

for

user
authentication.
This
field

appears

for

FTP

and

SFTP

onl

y.
Step
7
In
the
Password
field,
enter

the

password

that

the

remote

server

requires

for
user
authentication.
This
field

appears

for

FTP

and

SFTP

onl

y.
Step
8
In
the

IP

Address

field,
enter
the

IP

address

of

the

remote

server.
Step
9
In
the
Backup
File
Path

in

Remote

System

field,
enter
the

full

path
for
the

remote

server.
Step
10
Click
OK
to

begin

the

copy

process.
ANM
copies

t

he

backup

files

fr

om

each

device

to

t

he

remote

server.

A

popup

message

displays

to
indicate
whether

a

copy

operation

was

successful

or

failed.
Related
Topics

•
Backing
Up
Multiple
Device

Configuration
and
SSL

Files,

page
6-69

•
Performing
Device

Backup

and
Restore
Functions,

page
6-59
Configuring
Security

with

ACLs
An
access

control

list

(ACL)

consists

of

a

series

of

statements

called

ACL

entries

that

collectively

define
the
network

traffic

profile.

Each

entry

permits

or

denies

network

traffic

(inbound

and

outbound)

to

the
parts
of

your

network

specified

in

the

entry.

In

addition

to

an

action

element

(permit

or

deny),

each

entry
also
contains

a

filter

element

based

on

criteria

such

as

the

source

address,

the

destination

address,

the
protocol,
or

the

protocol-specific

parameters.

An

implicit

“deny

all”

entry

exists

at

the

end

of

every

ACL,
so
you

must

configure

an

ACL

on

every

interface

where

you

want

to

permit

connections;

otherwise,

the
ACE
den

ies

al

l

tr

affic

on

th

e

i

nterface.
ACLs
provide

basic

security

for

your

network

by

allowing

you

to

control

network

connection

setups
rather
than

processing

each

packet.

Such

ACLs

are

commonly

referred

to

as

security

ACLs.
You
can

configure

ACLs

as

parts

of

ot

her

features;

for

example,

security,

network

address

t

ranslation
(NAT),
or

server

load

balancing

(SLB).

The

ACE

merges

these

individual

ACLs

into

one

large

ACL
called
a

merged

ACL.

The

ACL

compiler

then

parses

the

merged

ACL

and

generates

the

ACL

lookup
mechanisms.
A

match

on

this

merged

ACL

can

result

in

multiple

actions.

You

can

add,

modify,

or

delete
entries
to

an

ACL

already

in

the

summary

table,

or

add

a

new

ACL

to

the

list.
When
you

use

ACLs,

you

may

want

to

permit

all

email

t

raffic

on

a


circuit,

but

bl

ock

FTP

traffic.

You
can
also

use

ACLs

to

allow

one

cl

ient

to

access

a

part

of


the

network

and

prevent

another

client

from
accessing
that

same

ar

ea.
When
configuring

ACLs,

you

must

apply

an

ACL

to

an

interface

to

control

traffic

on

that

interface.
Applying
an

ACL

on

an

interface

assigns

the

ACL

and

its

entries

to

that

interface.