Cisco BTS 10200 Troubleshooting Manual page 76

Managing Events and Alarms
Message Type and Number
The message type and number describe the type of alarm or event, the number assigned to the message,
and the message text as it is displayed on the operator console or in a log file.
BTS 10200 events and alarms are categorized into the following eleven types:
•
•
•
•
•
•
•
•
•
•
•
Event Level
The event level designates the severity levels of the event or alarm information that is sent to the operator
interface. Each event or alarm report is tagged with one of the following event level designations, listed
from highest to lowest severity.
•
•
•
•
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
1-20
AUDIT—Events or alarms generated by the audit subsystem. Refer to
Troubleshooting."
BILLING—Events or alarms generated by the billing subsystem. Refer to
Troubleshooting."
CALLP—Events or alarms generated by call processing. Refer to
Troubleshooting."
CONFIG—Events or alarms generated that provide information about system configuration. Refer
to Chapter 5, "Configuration Troubleshooting."
DATABASE—Events or alarms generated by the database. Refer to
Troubleshooting."
MAINTENANCE—Events or alarms that provide information about maintenance. Refer to
Chapter 7, "Maintenance Troubleshooting."
OSS—Events or alarms generated by the OSS. Refer to
Troubleshooting."
SECURITY—Events or alarms generated by the billing subsystem. Refer to
Troubleshooting."
SIGNALING—Events or alarms generated by signaling protocols or interfaces. Refer to
Chapter 10, "Signaling Troubleshooting."
STATISTICS—Events or alarms that provide information about system statistics. Refer to
Chapter 11, "Statistics Troubleshooting."
SYSTEM—Events or alarms that convey information about system status or trouble. Refer to
Chapter 12, "System Troubleshooting."
CRITICAL—Service can be severely affected and an alarm is raised. A critical alarm indicates a
critical situation exists somewhere in the system. Critical alarms can cause failovers (active server
switches processing to standby server). Critical alarms must be investigated and cleared
immediately.
MAJOR—Service can be degraded and an alarm is raised. A major alarm indicates that a serious
situation exists that can disrupt service. Major alarms differ from critical alarms in that they usually
do not cause failovers. Major alarms should also be investigated and cleared immediately.
MINOR—Service (call processing) is not affected; however, an alarm is raised. Minor alarms
should be noted and cleared as soon as possible.
WARNING—Warning messages provide cautionary advice about a potential service impact. They
indicate conditions that should be investigated immediately to ensure that the situation does not
progress into an alarmed state.
Chapter 1 Troubleshooting Overview
Chapter 2, "Audit
Chapter 3, "Billing
Chapter 4, "Call Processing
Chapter 6, "Database
Chapter 8, "Operations Support System
Chapter 9, "Security
OL-8723-19