Table Of Contents
Preface
About this Guide
Audience for this Guide
Conventions Used in this Guide
Basic Cisco ANA Terminology
Acronyms
Basic Concepts and Terms
Related Documentation
Obtaining Documentation and Submitting a Service Request
Preface
This preface describes:
•
About this Guide
•Audience for this Guide
•Conventions Used in this Guide
•Basic Cisco ANA Terminology
•Related Documentation
•Obtaining Documentation and Submitting a Service Request
About this Guide
This guide describes the Cisco Active Network Abstraction (Cisco ANA) 3.6.5 applications that enable system administrators to view the network, and networking engineers to analyze and manage faults:
•Cisco ANANetworkVision—The main GUI for Cisco ANA. Used in network based environments as a surveillance tool that provides total visibility for multiple-vendor, multiple-tier, and multiple-technology networks. For more information, see Chapter 2, "Working with the NetworkVision Client."
•Cisco ANA EventVision—The intuitive interface used by administrators for viewing system events and tickets that are generated within the Cisco ANA system. For more information, see Chapter 3, "Working with the EventVision Client."
•Cisco ANA Fault Management—Used for analyzing and managing faults using fault detection, identification and correlation. For more information, see Chapter 4, "Understanding Fault Management."
describes the contents of this guide.
Table 1 Guide Structure and Contents
Part
|
Topics
|
Overview
|
•Chapter 1, "Cisco ANA Client Overview"
•Chapter 2, "Working with the NetworkVision Client"
•Chapter 3, "Working with the EventVision Client"
|
Fault Management
|
•Chapter 4, "Understanding Fault Management"
•Chapter 5, "Causality Correlation and Root Cause Analysis"
•Chapter 6, "Advanced Correlation Scenarios"
•Chapter 7, "Working with Unmanaged Segments"
|
Device and Network Management
|
•Chapter 8, "Working with NetworkVision Maps"
•Chapter 9, "Using PathTracer to Diagnose Problems"
•Chapter 10, "Viewing Device Properties"
•Chapter 11, "Viewing Network Device Inventory"
•Chapter 12, "Working with Links"
•Chapter 13, "Working with Business Tags"
|
Event Management
|
•Chapter 14, "Working with Tickets"
•Chapter 15, "Tracking Faults Using EventVision"
|
Troubleshooting Faults
|
•Chapter 16, "Supported Service Alarms"
•Chapter 17, "Source OIDs of Alarms Generated by Cisco ANA"
•Chapter 18, "Event and Alarm Configuration Parameters"
|
Appendices
|
•Appendix A, "Cisco ANA Integrity Service"
•Appendix B, "Icon Reference"
•Appendix C, "Error Reference"
|
Audience for this Guide
The intended audience for this Guide includes:
•Network viewers, who monitor the network and perform basic (nonprivileged) system functions.
•Network operators, who perform day-to-day operations such as creating business tags, maps, and managing alarms.
•Network configurators, who activate services and configure network elements.
•System administrators, who manage and configure users, network elements, the Cisco ANA system, and overall security.
•System managers or administrators who periodically review and manage the events list using EventVision.
•Networking engineers who are interested in understanding how the Cisco ANA fault and root cause analysis mechanism works. These engineers should have networking knowledge at CCNA level, and have received Cisco ANA basic and administrative training.
Conventions Used in this Guide
The following conventions are used in this Guide:
Table 2 Guide Conventions
Convention
|
Description
|
[ ]
|
Square brackets (used in the examples) enclose either of the following:
•The event and the location of the event
•The event only.
Note: This convention is used specifically in Chapter 6, "Advanced Correlation Scenarios."
|
|
Text in Courier indicates commands and keywords that the user enters.
|
Basic Cisco ANA Terminology
This section provides a brief explanation of the acronyms, basic concepts, and terms used in this Guide.
Acronyms
The following acronyms are used throughout this Guide:
Table 3 Acronyms
Acronym
|
Full Name
|
Description
|
General
|
Cisco ANA, ANA
|
Active Network Abstraction
|
Refers to the entire Cisco Active Network Abstraction solution.
|
VNE
|
Virtual Network Element
|
Refers to a network and device agent
|
Client
|
ANA
|
Active Network Abstraction
|
User command-line interface (CLI)
|
EV
|
Cisco ANA EventVision
|
|
NV
|
Cisco ANA NetworkVision
|
|
VNE
|
DC
|
Device Component
|
|
NE
|
Network Element
|
|
AVM
|
Autonomous Virtual Machine
|
|
Basic Concepts and Terms
This section provides a description of the concepts and terms used throughout this Guide.
Table 5 Definitions
Term
|
Description
|
Event
|
An event is a representation of a distinct incident occurring at a specific point in time, such as, port status change, connectivity loss between protocol processes on peer routers, device reset, device unreachable by management station.
|
Alarm
|
An alarm represents a scenario which involves a fault in the network, the managed element, or the management system. An alarm is characterized by a sequence of related events, such as port-down and port-up.
|
Ticket
|
A ticket represents the complete hierarchy of correlated alarms representing a single specific fault scenario.
A ticket points to the root cause alarm that is the top-most alarm in the correlation hierarchy. The attributes of the ticket, such as short description, are derived from the root cause alarm.
Both Cisco ANA NetworkVision and Cisco ANA EventVision display tickets and allow drilling down to view the consequent alarm hierarchy.
From an operator's point of view, a fault is always represented by a complete ticket. Operations such as Acknowledge or Remove are applied to the whole ticket.
|
Severity Propagation
|
The network objects' calculated status is propagated from the source/children (namely, the network element component) to the final destination (namely, the network element and tree) via defined relationships.
|
Aggregation/ Aggregated Node
|
Zero or more map elements joined together as an aggregation.
|
Physical Element
|
A user named physical component/device existing in the network.
|
Logical Element
|
A user named logical component, for example, a routing table.
|
Business Element
|
Cisco ANA supports the mapping of service-related information to the network resources. This mapping is achieved using a business element that is a wrapper to a network element or service. The VPN is a business element, which represents a set of interconnected Sites forming a single virtual private network over a public network. Cisco ANA organizes the business elements in a way that creates a containment hierarchy that reflects the VPN structure.
|
Managed Element
|
Anything managed by the system, usually a component managed by the VNE, for example, a device, cloud, ICMP VNE.
|
Link
|
A physical or logical link between:
•Two devices in the network
•A device and an aggregation
•Two aggregations
|
Physical Link
|
A link between physical Network Objects, for example, a connection between two physical ports.
|
Logical Link
|
An association between two logical elements (based on a chain of physical elements), for example, a tunnel.
|
Business Link
|
An association between:
•Logical (protocol oriented configuration) to physical
•Logical to logical
•Business link to anything
For example, in a VPN an association between the physical IP interface and VRF (which is the associated routing table).
|
Device/Network Element (NE)
|
A user named physical component/device existing in the network.
|
Device/Network Element Components
|
A component of a network element, for example, a port, routing table and so on.
|
Network Object
|
Network Objects include network element components, network elements and links.
|
Virtual Cloud / Unmanaged Network
|
Virtual clouds are used for representing unmanaged network segments and are displayed as a cloud. Cisco ANA establishes if network problems emanate from the unmanaged network, namely, the cloud.
|
VPN
|
The VPN is a business element, which represents a set of interconnected Sites forming a single virtual private network over a public network.
|
Business Tag
|
A "business" tag is a record that points to a network object. Each business tag has a "key" field, which is a unique identifier for the entity and its name (refer to Business Element).
There are three types of tags, namely, subscriber, provider, and label. Business tags are stored in the Cisco ANA Gateway database.
|
Provider
|
The party providing the service.
|
Subscriber
|
The party receiving the service.
|
Related Documentation
Note We sometimes update the documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.
describes the additional documentation that is available.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
Feedback
