Events And Alarm Logs - Cisco BTS 10200 Troubleshooting Manual

Managing Events and Alarms

Events and Alarm Logs

It is recommended that you manage the event and alarm logs in a manner that permits the operator to
access all events and alarms and watch for unexpected events or alarms. For example, if any of the
following anomalies are seen, investigate promptly to determine the required action:
•
•
•
•
•
•
•
Viewing Event or Alarm Logs
Use the following show commands to view event or alarm logs. The event and alarm logs are typically
used if the user session is disrupted, or if all events or alarms of one kind are needed in a single report.
show event-log id=<sn>; type=<type>; number=<num>; severity=<severity>;
component-id= <component-id>; origin=<process-id>;
start-time=<yyyy-mm-dd hh:mm:ss>; end-time=<yyyy-mm-dd hh:mm:ss>;
show alarm-log id=<sn>; type=<type>; number=<num>; severity=<severity>;
component-id=<component-id>; origin=<process-id>;
start-time=<yyyy-mm-dd hh:mm:ss>; end-time=<yyyy-mm-dd hh:mm:ss>;
If the show event-log or show alarm-log commands are issued without any tokens (parameters),
Note
all events or alarms of all types and all severities for all components are displayed.
Issuing the show event-log or show alarm-log commands with any combination of optional tokens
limits the display to a subset of events or alarms as determined by the optional tokens specified.
By default the 30,000 entries are maintained in the Event/Alarm logs (currently in MySql database). For
every 30 minute interval the event generator (EGA) retains the most recent 30,000 entries in the log. All
entries above this are deleted, i.e. if you do a show alarm-log limit=1; and reply says 1 of 32008, then
EGA would delete the 8 oldest entries.
If the show event-log or show alarm-log commands are issued without any tokens (parameters), up to
Note
30,000 entries may be scrolled across the screen with no way to stop it. It may take an extended period
of time to display all entries. These commands should ordinarily be issued with optional tokens.
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
1-14
Congestion warnings
Routing errors
Termination failures
Billing errors
Security warnings
Diagnostic failures
Process failovers
Chapter 1 Troubleshooting Overview
OL-8723-19