-
Cisco Active Network Abstraction Administrator Guide, 3.6
-
Introducing Cisco ANA
-
Getting Started With Cisco ANA Manage
-
Deploying Cisco ANA
-
Using Cisco ANA Manage Tables
-
Managing Cisco ANA Units
-
Managing AVMs and VNEs
-
Managing Global Settings
-
Managing Links
-
Managing Workflows
-
Managing Security
-
Database Backup and Restore
-
Utility Scripts
-
Golden Source Registry
-
Ports Used By Cisco ANA
-
Drools Rules Engine
-
VNE Persistency Mechanism
-
Index
-
Feedback
Table Of Contents
Conventions Used In This Guide
Introducing Cisco ANA
This chapter describes the Cisco Active Network Abstraction (ANA) platform and architecture. In addition, it provides a brief explanation of the terms used throughout this guide. The Cisco ANA Manage maintenance application is part of an overall Cisco solution; therefore, in order to better understand the Cisco ANA Manage environment, a brief overview of Cisco ANA is required.
•
Introduction—Provides an overview of the Cisco ANA, its platform architecture and functional blocks.
•
•
•
•
Note
Introduction
Cisco ANA is a carrier-class network management platform, designed to serve as an active mediation layer between the operation and network layers. It provides a set of easy-to-use applications as well as well-defined APIs for Operation Support Systems (OSS), enabling carriers and service providers to efficiently respond to the constant market demand for new, reliable and more sophisticated services, while hiding the complexity of large, multivendor, mixed technology networks.
Cisco ANA provides solutions for diverse network environments and applications. It offers an integrated network and service auto-discovery for network modeling, intelligent fault analysis, and a highly flexible network configuration and activation engine.This enables fully correlated management of global scale networks supporting millions of subscribers and customers.
Cisco ANA is a network management solution that provides a fully integrated service-oriented solution offering:
•
•
•
•
Based on a patented innovative architecture of distributed autonomous virtual network elements (VNE), Cisco ANA enables integrated management for hybrid network environments while being scalable to support network growth and evolution.
The Cisco ANA includes the following functionality:
•
•
•
•
•
•
•
•
•
•
The Cisco ANA platform architectural diagram and functional blocks are displayed in the figure that follows.
Figure 1-1 Cisco ANA Architecture
Cisco ANA Components
The Cisco ANA system includes key components, as follows:
Autonomous VNEs
The autonomous VNEs are software entities that run as a completely autonomous process within the Cisco ANA units. Each VNE is assigned to manage a single network element (NE) instance using whatever southbound management interfaces the NE implements (for example, SNMP or Telnet). The autonomous VNEs are the entities that maintain a live model of each NE and of the entire network.
As the VNE loads, it starts investigating the NE and automatically builds a live model of the NE, including its physical and logical inventory, its configuration and its status. Following the device investigation, the VNEs begin to negotiate with peer VNEs, which represent the peer NEs determining the connectivity and topology at different layers. This model of the network topology, device state, and device inventory is constantly being updated by the VNEs, which track every change that occurs in the NE or in the network.
Messaging between VNEs is used for running different end-to-end flows in order to provide information for root-cause and impact analysis, service path tracing, and more.
Cisco ANA Servers
Cisco ANA uses two server types, each performing different activities:
Cisco ANA Gateway
The Cisco ANA gateway serves as the gateway through which all clients, including any OSS/BSS applications as well as the Cisco ANA clients can access the system. The gateway is an extended Cisco ANA unit. It enforces access control and security for all connections and manages client sessions. In addition it functions as a repository for storing configuration, network and system events and alarms.
Another important function of the gateway is to map network resources to the business context. This enables Cisco ANA to contain information that is not directly contained in the network (such as VPNs and subscribers) and display it to northbound applications.
Cisco ANA Unit
The main purpose of Cisco ANA units is to host the autonomous VNEs. The units are interconnected to form a fabric of VNEs that can communicate with other VNEs regardless of which unit they are running on. Each unit can host thousands of autonomous VNE processes (depending on the server system size). The units also allow for optimal VNE distribution, ensuring geographic proximity between the VNE and its managed NE.
Cisco ANA includes a clustered N+m high-availability mechanism. Unit availability is established in the gateway, running a protection manager process, which continuously monitors all the units in the network. After the protection manager detects a unit that is malfunctioning, it automatically signals one of the m servers in its cluster to load the configuration of the faulty unit (from the system registry), taking over all its managed NEs. The switchover to the redundant standby unit does not result in any loss of information in the system, as all the information is auto-discovered from the network, and no persistent storage synchronization is required. When a unit is configured, it can be designated as being an active or a standby unit.
For more information about high availability refer to the Cisco Active Network Abstraction High Availability User Guide.
Cisco ANA Clients
Cisco ANA provides a comprehensive suite of GUI applications to manage the network:
•
•
•
•
The clients support automatic client updates from the gateway using Web Start. When connecting with a gateway application, the system verifies that the client version is the latest available and if an upgrade is required, the system automatically updates the clients from the gateway.
Cisco ANA Manage
Cisco ANA Manage is the GUI tool used for performing various system administration activities for simple system control. It provides an interface to perform the following:
•
•
•
–
–
–
–
–
•
•
•
•
Additional Concepts and Terms
The sections below include additional concepts and terms used in Cisco ANA Manage and throughout this guide.
AVM
Cisco ANA units are divided into AVMs (Autonomous Virtual Machines). These AVMs are Java processes that provide the necessary distribution support platform for executing and monitoring multiple VNEs. AVMs and VNEs should reside on a Cisco ANA unit (as a common configuration) but they can also reside on a Cisco ANA gateway.
Some types of AVMs run on the server, but do not run VNEs. These AVMs have reserved ID numbers (AVM 0-100) and these cannot be used. In addition, there are other reserved AVM ID numbers. The following AVMs have special roles assigned to them:
•
•
•
•
•
Element Management
The base configuration for the creation of the managed element. Cisco ANA Manage enables the user to create VNEs, for example, by entering the IP address, SNMP and polling rate information and so on. This is element management.
License
Cisco ANA client applications and BQL connectivity is based on installed license files. Cisco ANA Manage enables the administrator to control and monitor the number of client and BQL connections over a limited or unlimited period of time based on the client licenses installed. Two types of licenses are supported: fixed (the number of installed users are identified by usernames or IP addresses or both) or floating (the number of installed users operating concurrently).
Managed Element
After Cisco ANA Manage installs and runs the process, samples the device, and collects the data a VNE (Managed Element) is created. The VNE includes logical inventory (for example, forwarding tables) and physical inventory (for example, modules and ports). The managed element can be accessed using NetworkVision.
Network Element
A network component existing in the network, for example, the devices displayed in Cisco ANA and in NetworkVision.
Network Element Components
Components of an NE, such as ports, blades, contexts and so on.
Permission
The user's ability to perform certain tasks. There are two types of permissions, default and NE related.
•
•
Polling Group
A polling group is defined as a group of polling rates that can be specified for a device. For more information, see Polling Groups Overview, page 7-5.
Polling Intervals
The unit servers poll the NEs to discover and display accurate and up-to-date information of the network. The system periodically triggers polling at set intervals. Cisco ANA provides three out-of-the-box polling intervals for the VNEs, see Polling Groups Overview, page 7-5.
Protection Group
A protection group is a cluster to which units and standby units are related. In case of unit failover then the redundant unit will be taken from the same protection group.
Redundant Unit
The Cisco ANA unit comes with built-in redundancy for maximum up-time and automatic switching. A threshold configurable watchdog constantly monitors the units and gateway, and can make an automatic or manual (operator approved) switchover when there is no response from the monitored entity. The system is always up-to-date via real-time investigation of the network. The redundancy mechanism ensures synchronization of the active and backup units. Once activated, the standby node is immediately synchronized with the network.
Roles
Cisco ANA implements a security engine that combines a role-based security mechanism that is applied on scopes of NEs granted per user. The system supports user accounts creation, multiple NE scope definition, and a set of five pre-defined roles for security and access control to allow different system functions:
•
•
•
•
•
Roles can be granted per scope or at an application level (default permission) for all the activities that are related to GUI functionality, not the activities related to devices. The default permission includes:
•
•
•
•
•
Scopes
A scope is a named collection of managed NEs that have been grouped in order to allow a user to view and manage the NEs according to a given role. Grouping can be based on geographical location, NE type (such as DSLAM, router, software, etc.), NE category (such as access, core, etc.) or any other division according to the network administrator's requirements.
Using NetworkVision, a user that has been assigned a scope can view and manage the NEs within this scope according to the role assigned to the user as per the scope. The user cannot view any information regarding NEs, including basic properties, inventory, and alarms, that are outside the user's scope.
Static Link
A static link is a physical link that is not automatically discovered by the system. The user manually creates the static link between NEs by selecting the two end ports from the NE physical inventories.
Transport Link
A transport link is a logical link used for communication between the units and for transferring information.
Users
In order for a user to work with Cisco ANA the following requirements must be met:
•
•
•
For more information about users see Chapter 10, "Managing Security".
Workflow
A workflow consists of several tasks grouped together and arranged in a flowchart. All workflows are stored on the gateway. After a workflow is deployed, it can be accessed using Cisco ANA Manage in order to view its properties and status. Deployed workflow templates can be invoked with the Cisco ANA API using BQL. In addition, the user can view a history of the invoked workflows using EventVision. For more information refer to this guide and the Cisco Active Network Abstraction Workflow User Guide.
Conventions Used In This Guide
Command syntax descriptions use the following conventions:
Nested sets of square brackets or braces indicate optional or required choices within optional or required elements. For example:
[x {y | z}]
Braces and a vertical line within square brackets indicate a required choice within an optional element.
Examples use the following conventions:
Related Documentation
For more detailed information see the following publications:
•
•
•
•
•
•
•
