Implementing and Monitoring Alarms and Alarm Log Correlation
Capacity Threshold Setting for Alarms
The capacity threshold setting determines when the alarm system begins reporting threshold crossing alarms.
The capacity threshold for generating warning alarms is generally set at 80 percent of buffer capacity, but
individual configurations may require different settings.
Hierarchical Correlation
Hierarchical correlation takes effect when the following conditions are true:
• When a single alarm is both a root cause for one rule and a non-root cause for another rule.
• When alarms are generated that result in successful correlations associated with both rules.
The following example illustrates two hierarchical correlation rules:
Rule 1
Root Cause 1
Non-root Cause 2
Rule 2
Root Cause 2
Non-root Cause 3
If three alarms are generated for Cause 1, 2, and 3, with all alarms arriving within their respective correlation
timeout periods, then the hierarchical correlation appears like this:
Cause 1 -> Cause 2 -> Cause 3
The correlation buffers show two separate correlations: one for Cause 1 and Cause 2 and the second for Cause
2 and Cause 3. However, the hierarchical relationship is implicitly defined.
Stateful behavior, such as reparenting and reissuing of alarms, is supported for rules that are defined as
Note
stateful; that is, correlations that can change.
Context Correlation Flag
The context correlation flag allows correlations to take place on a "per context" basis or not.
This flag causes behavior change only if the rule is applied to one or more contexts. It does not go into effect
if the rule is applied to the entire router or location nodes.
The following is a scenario of context correlation behavior:
Category
Cat 1
Cat 2
Cat 2
Cat 3
Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide, Release 4.2.x
Capacity Threshold Setting for Alarms
Group
Code
Group 1
Code 1
Group 2
Code 2
Group 2
Code 2
Group 3
Code 3
7