Troubleshooting guide

3-4
Cisco Broadband Local Integrated Services Solution Troubleshooting Guide
OL-5169-01
Chapter 3 Trouble Isolation Procedures
Finding System Information
The elements of the reply for an alarm (or an event) are defined as follows:
• Serial Number (ID)—All events and alarms have a unique, system-assigned serial number.
• Type—Type is the designated category of the report: Audit, Billing, Callp, Config, Database,
Maintenance, Oss, Security, Signaling, Statistics, or System.
• Number—Event or alarm numbers are preset in the Cisco BTS 10200. They are not user
provisionable.
• Description—Up to an 80-character description of the event or alarm.
• Status—Status for an alarm can be ALARM_ON, ALARM_OFF, ALARM_IGNORE, or
ACKNOWLEDGED.
• Severity—Severity of the alarm: CRITICAL, MAJOR, MINOR (or event: WARNI NG , or INFO)
•
Date and Time—Date and time of report in the format yyyy-mm-dd hh:mm:ss. Year, month, and
day plus hours, minutes, and seconds of an alarm or event, displayed in Greenwich Mean Time
(GMT).
• Component ID—ID for the component reporting the event or alarm.
• Origin—ID for the process generating the event or alarm.
• Thread—Thread within the BTS process that initially issued the alarm, when applicable.
• DataWordn—Header for additional data fields to an event or alarm. Up to 8 data fields can be
reported, depending on the event or alarm.
Event Message and Alarm Logs
It is recommended that you manage the event and alarm messages and 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 cause(s) and required action:
• Congestion warnings
• Routing errors
• Termination failures
• Billing errors
• Security warnings
• Diagnostic failures
• Process failovers
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=<comp-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=<comp-id>; origin=<process-id>; start-time=<yyyy-mm-dd hh:mm:ss>;
end-time=<yyyy-mm-dd hh:mm:ss>;