Cisco Systems 3.6 Severity Propagation, Sequence Association and Root Cause Analysis

Chapter 1 Fault Management Overview

Severity Propagation

From an operator’s point of view, the managed entity is always a complete ticket. Operations such as Acknowledge, Force-clear or Remove are always applied to the whole ticket. The ticket also assumes an overall, propagated severity.

Sequence Association and Root Cause Analysis

There are two different types of relationships in Cisco ANA alarm management:

•Sequence Association—The association between events, which creates the event sequences and alarms.

•Root Cause Analysis—The association between alarms (event sequences) which represents the root cause relationship.

The following figure shows how both types of relationship are implemented in the ticket hierarchy:

Figure 1-6 Sequence Association vs. Root Cause Analysis

In the above figure, the alarms are correlated into a hierarchy according to root cause. Within each alarm is its respective event sequence representing the lifecycle of the alarm.

Severity Propagation

Each event has an assigned severity (user-configurable). For example, a link-up event may be assigned critical severity, while its corresponding link-up event will have normal severity.

Cisco Active Network Abstraction Fault Management User Guide, Version 3.6 Service Pack 1

1-6 OL-14284-01