SUMMARY STEPS
1.
configure
2.
logging correlator rule correlation-rule { type { stateful | nonstateful }}
3.
rootcause { msg-category group-name msg-code }
4.
nonrootcause
5.
alarm msg-category group-name msg-code
6.
commit
7.
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
PurposeCommand or Action
configure
Step 1
Configures a logging correlation rule and enters submodes
for stateful and nonstateful rule types.
logging correlator rule correlation-rule { type { stateful |
nonstateful }}
Step 2
Example:
RP/0/RSP0/CPU0:router(config)# logging correlator
rule rule_stateful
•
Stateful correlations can change specifically if the
root-cause alarm is bistate.
•
Nonstate correlations cannot change. All
non-root-cause alarms remain in the correlation
buffers.
Configures a root-cause alarm message.
rootcause { msg-category group-name msg-code }
Step 3
Example:
RP/0/RSP0/CPU0:router(config-corr-rule-st)#
rootcause CAT_BI_1 GROUP_BI_1 CODE_BI_1
•
This example specifies a root-cause alarm under
stateful configuration mode
Enters the non-root-cause configuration modenonrootcause
Example:
RP/0/RSP0/CPU0:router(config-corr-rule-st)#
nonrootcause
Step 4
Specifies a non-root-cause alarm message.
alarm msg-category group-name msg-code
Step 5
Example:
RP/0/RSP0/CPU0:router(config-corr-rule-st-nonrc)#
alarm CAT_BI_2 GROUP_BI_2 CODE_BI_2
•
This command can be issued with the
nonrootcause command, such as
nonrootcause alarm msg-category group-name
msg-code
commit
Step 6
Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide, Release 4.2.x
12
Implementing and Monitoring Alarms and Alarm Log Correlation
Configuring Root-cause and Non-root-cause Alarms