Cisco ASR 9000 Serie

PurposeCommand or Action
Example:
RP/0/RSP0/CPU0:router(config)# logging correlator
rule rule_stateful type nonstateful
•
Nonstateful correlations cannot change. All
non-root-cause alarms remain in the correlation
buffers.
Issues nonbistate alarm messages (events) from the
correlator log after its root-cause alarm clears.
reissue-nonbistate
Example:
RP/0/RSP0/CPU0:router(config-corr-rule-st)#
reissue-nonbistate
Step 3
Specifies the behavior of non-root-cause alarms after
a root-cause parent clears.
reparent
Example:
RP/0/RSP0/CPU0:router(config-corr-rule-st)# reparent
Step 4
commit
Step 5
(Optional) Displays the correlator rules that are
defined.
show logging correlator rule { all |
correlation-rule1...correlation-rule14 } [ context
context1...context 6 ] [ location node-id1...node-id6 ] [
Step 6
rulesource { internal | user }] [ ruletype { nonstateful |
stateful }] [ summary | detail ]
Example:
RP/0/RSP0/CPU0:router# show logging correlator rule
all
What to Do Next
To activate a defined correlation rule and rule set, you must apply them by using the logging correlator apply
rule and logging correlator apply ruleset commands.
Applying Logging Correlation Rules
This task explains how to apply logging correlation rules.
Applying a correlation rule activates it and gives a scope. A single correlation rule can be applied to multiple
scopes on the router; that is, a rule can be applied to the entire router, to several locations, or to several contexts.
When a rule is applied or if a rule set that contains this rule is applied, then the rule definition cannot be
modified through the configuration until the rule or rule set is once again unapplied.
Note
Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide, Release 4.2.x
14
Implementing and Monitoring Alarms and Alarm Log Correlation
Applying Logging Correlation Rules