1-22
Device Manager Guide, Cisco ACE 4700 Series Application Control Engine Appliance
OL-26645-02
Chapter 1 Overview
Understanding ACE Appliance Device Manager Terminology
• ICMPv6 traffic is not automatically allowed. You must configure the corresponding management
traffic policy to allow the ping request to ACE. However, the necessary ND (neighbor Discovery)
messages for ARP, duplication address detection are automatically permitted.
• All the management traffic used by the network management server or DM is required to send over
IPv4 protocol. IPv6 is not supported.
• Copying files over IPv6 to or from devices are not supported.
• The ACE supports IPv6 HA:
–
All the FT transport (ft vlan) is still on IPv4.
–
Track IPv6 host /peer will be supported
Understanding ACE Appliance Device Manager
Terminology
It is useful to understand the following terms when using the ACE Appliance Device Manager:
• Virtual context
A virtual context is a concept that allows users to partition an ACE appliance into multiple virtual
devices. Each virtual context contains its own set of policies, interfaces, and resources, allowing
administrators to more efficiently manage system resources and services.
• Virtual server
In a load-balancing environment, a virtual server is a construct that allows multiple physical servers
to appear as one for load-balancing purposes. A virtual server is bound to physical services running
on real servers in a server farm and uses IP address and port information to distribute incoming
client requests to the servers in the server farm according to a specified load-balancing algorithm.
• Role-Based Access Control
Managing users using role-based access allows administrators to set up users, roles, and domain
access to your virtual contexts. Each user is assigned a role and a domain which defines what virtual
contexts they can view and configure. Roles determine which commands and resources are available
to a user. Domains determine which objects they can use. Only users associated with an admin
virtual context are allowed to see other virtual contexts.
There are two types of virtual contexts:
–
Admin context
The Admin context, which contains the basic settings for each virtual device or context, allows
a user to configure and manage all contexts. When a user logs into the Admin context, he or she
has full system administrator access to the entire ACE appliance and all contexts and objects
within it. The Admin context provides access to network-wide resources, for example, a syslog
server or context configuration server. All global commands for ACE appliance settings,
contexts, resource classes, and so on, are available only in the Admin context.
–
User context
A user context has access to the resources in which the context was created. For example, a user
context that was created by an administrator while in the Admin context, by default, has access
to all resources in an ACE appliance. Any user created by someone in a user-defined context
only has access to the resources within that context. In addition, roles and domains create access
parameters for each user. For a description of the predefined user roles, see Managing User
Roles, page 15-14.
Comments to this Manuals