Purpose
Command or Action
(Optional) Displays the correlator rules that are defined.
show logging correlator rule
{
all
|
correlation-rule1...correlation-rule14
} [
context
Step 7
context1...context 6
] [
location node-id1...node-id6
] [
rulesource
{
internal
|
user
}] [
ruletype
{
nonstateful
|
stateful
}] [
summary
|
detail
]
Example:
RP/0/RSP0/CPU0:router# show logging correlator rule
all
Configuring Hierarchical Correlation Rule Flags
Hierarchical correlation is when a single alarm is both a root cause for one correlation rule and a non-root
cause for another rule, and when alarms are generated resulting in a successful correlation associated with
both rules. What happens to a non-root-cause alarm hinges on the behavior of its correlated root-cause alarm.
There are cases in which you want to control the stateful behavior associated with these hierarchies and to
implement flags, such as reparenting and reissuing of nonbistate alarms. This task explains how to implement
these flags.
See the
Reparent Flag, on page 8
and
Reissue Nonbistate Flag, on page 8
sections for detailed information
about these flags.
SUMMARY STEPS
1.
configure
2.
logging correlator rule correlation-rule
{
type
{
stateful
|
nonstateful
}}
3.
reissue-nonbistate
4.
reparent
5.
commit
6.
show logging correlator rule
{
all
|
correlation-rule1...correlation-rule14
} [
context context1...context
6
] [
location node-id1...node-id6
] [
rulesource
{
internal
|
user
}] [
ruletype
{
nonstateful
|
stateful
}] [
summary
|
detail
]
DETAILED STEPS
Purpose
Command or Action
configure
Step 1
Configures a logging correlation rule.
logging correlator rule correlation-rule
{
type
{
stateful
|
nonstateful
}}
Step 2
•
Stateful correlations can change specifically if
the root-cause alarm is bistate.
Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide, Release 4.2.x
13
Implementing and Monitoring Alarms and Alarm Log Correlation
Configuring Hierarchical Correlation Rule Flags
