18-6
Cisco 12000/10700 v3.1.1 Router Manager User Guide
OL-4455-01
Chapter 18 Fault Management
Cisco 12 000/10720 Router Trap Support
Syslog alarms have a Description in the Event Browser application in the following format:
“Asserted [<clogHistMsgText>] by facility [<clogHistFacility>], Message name
[<clogHistMsgName>]”
Where:
clog HistM sgText is th e messa ge text
clogHistFacility is the facility name (where the message came from)
clogHistMsgName is the message name
An example Sy slog A larm D esc ripti on i s
“Asserted [Critica l/high priority process ATM Periodic may not dismiss.] by facility [ SCHED], M essage
name [ EDISM SCRIT ]”
Configur ation M ana gement T rap s
Note Ca re should be taken when u sing the Con figuration Ma nageme nt ala rm feature since th ere ar e
possibilities which can result in large trap volumes This can affect the performance of the Cisco
12000/10 720 Route r Manage r (for exampl e, when ope ning an Event Browser) and hi nder effective
monitoring because of the high numbers of alarms that will be raised.
When a change is made to the configura tion of a Cisco 12000 Seri es Router, Cisco IOS can send a
“configura tion ma nage ment event trap ”. This trap is translated into a Cisco EMF alarm with the
following description:
“Config Change, Command Source: <cc mHistor yEventComm andSourc e>, Con fig Sourc e: <
ccmHistoryEventConfigSource>, Config Destination: <ccmHistoryEventConfigDestination>”
Where:
•cmHistoryEventCommandSource is the source of the command that instigated the event – either
comm and line or snmp.
•cmHi storyE ventCon figSource is t he configurat ion d ata so urce fo r the event.
•ccmHistoryEventConfigDestin ation is the configuration data destination for the event.
Table 18-5 Syslog to Cisco EMF Mappings
Trap Alarm Description
Emergency Critical
Alert Critical
Critical Critical
Error Major
Warning Minor
Notification Minor
Informational Informational
Debug Informational