user manual
Table Of Contents
- Cisco Active Network Abstraction Fault Management User Guide Version 3.6 Service Pack 1
- Contents
- About This Guide
- Fault Management Overview
- Fault Detection and Isolation
- CiscoANA Event Correlation and Suppression
- Advanced Correlation Scenarios
- Device Unreachable Alarm
- IP Interface Failure Scenarios
- Multi Route Correlation
- Generic Routing Encapsulation (GRE) Tunnel Down/Up
- BGP Process Down Alarm
- MPLS Interface Removed Alarm
- LDP Neighbor Down Alarm
- Correlation Over Unmanaged Segments
- Event and Alarm Configuration Parameters
- Impact Analysis
- Supported Service Alarms
- Event and Alarm Correlation Flow
7-6
Cisco Active Network Abstraction Fault Management User Guide, Version 3.6 Service Pack 1
OL-14284-01
Chapter 7 Impact Analysis
Disabling Impact Analysis
Disabling Impact Analysis
You can disable impact analysis for a specific alarm. This option can be set in the Cisco ANA Registry.
If impact analysis is disabled the system will report the event with no impact information. The settings
can be changed dynamically during system runtime.
The following alarms can be disabled:
• Link down
• Port down
• Dropped or discarded packets
• MPLS black hole
• BGP neighbor loss
• MPLS TE tunnel down
• L2 tunnel down
Accumulating Affected Parties
This section describes how NetworkVision automatically calculates the accumulation of affected parties
during automatic impact analysis. This information is embedded in the ticket along with all the
correlated faults.
In the example below the following types of alarms exist in the correlation tree:
• Ticket root-cause alarm (Card out).
• An alarm which is correlated to the root cause and has other alarms correlated to it (Link A down).
• An alarm with no other alarms correlated to it (Link B down and BGP neighbor loss).
An event sequence is correlated to each of these alarms.
Figure 7-3 Correlation Tree Example
NetworkVision provides a report of the affected parties for each type of alarm. This report includes the
accumulation of:
• The affected parties reported on all the events in the alarm event sequence. This also applies to
flapping alarms.
• The affected parties reported on the alarms that are correlated to it.
Each report includes the accumulation of the affected report of all the events in its own correlation tree.
For example, in the diagram:
• BGP neighbor loss includes the accumulation of the affected report of its own event sequence.
Card out
|
----- Link A down
| |
| ------BGP neighbor loss
|
----- Link B down
Card out
|
----- Link A down
| |
| ------BGP neighbor loss
|
----- Link B down
180110