-
Cisco Unified Serviceability Administration Guide for Cisco Unity Connection Release 2.x
-
Index
-
Preface
-
Understanding Cisco Unified Serviceability
-
Using Cisco Unified Serviceability
-
Understanding Alarms
-
Configuring Alarms
-
Viewing and Updating Alarm Definitions
-
Understanding Trace
-
Configuring Trace
-
Configuring Troubleshooting Trace Settings
-
Understanding Services
-
Understanding Serviceability Reports Archive
-
Configuring Services
-
Configuring Serviceability Reports Archive
-
Feedback
Table Of Contents
Where to Find More Information
Understanding Alarms
This chapter, which provides information on Cisco Unified Serviceability alarms, contains the following topics:
•
Alarm Configuration Checklist
•
Understanding Alarms
Cisco Unified Serviceability alarms provide information on runtime status and the state of the system, so you can troubleshoot problems that are associated with your system; for example, to identify issues with the Disaster Recovery System. Alarm information, which includes an explanation and recommended action, also includes the application name, machine name, and so on, to help you perform troubleshooting.
You configure the alarm interface to send alarm information to multiple locations, and each location can have its own alarm event level (from debug to emergency). You can direct alarms to the Syslog Viewer (local syslog), Syslog file (remote syslog), an SDI trace log file, or to all destinations. When a service issues an alarm, the alarm interface sends the alarm information to the locations that you configure (and that are specified in the routing list in the alarm definition) (for example, SDI trace). The system can either forward the alarm information, or the system can write the alarm information to its final destination (such as a log file).
Tip
You use the trace and log central option in the Real-Time Monitoring Tool (RTMT) to collect alarms that get sent to an SDI trace log file. You use the SysLog Viewer in RTMT to view alarm information that get sent to the local syslog.
Alarm Configuration
You can configure alarms for services, such as Cisco Database Layer Monitor.
To configure an alarm for a service, you choose an alarm event level, such as Error, and the location(s), such as Syslog Viewer (local syslog), where you want the system to send the alarm information. Choosing an event level accomplishes the following tasks: helps you narrow the types of alarms that get collected and prevents the Syslog and trace files from becoming overloaded. For more information on how alarm configuration relates to the alarm definitions, see the "Alarm Definitions" section.
Alarm Definitions
Used for reference, alarm definitions describe alarm messages: what they mean and how to recover from them. You search the Alarm Definitions window for alarm information. When you click any service-specific alarm definition, a description of the alarm information (including any user-defined text that you have added) and a recommended action display.
You can search for definitions of all alarms that display in Cisco Unified Serviceability. To aid you with troubleshooting problems, the definitions, which exist in a corresponding catalog, include the alarm name, description, explanation, recommended action, severity, parameters, monitors, and so on.
When the system generates an alarm, it uses the alarm definition name in the alarm information, so you can identify the alarm. In the alarm definition, you can view the routing list, which specifies the locations where the system can send the alarm information. The routing list may include the following locations, which correlate to the locations that you can configure in the Alarm Configuration window:
•
•
•
•
The system sends an alarm if the configured alarm event level for the specific location in the Alarm Configuration window is equal to or lower than the severity that is listed in the alarm definition. For example, if the severity in the alarm definition equals WARNING_ALARM, and, in the Alarm Configuration window, you configure the alarm event level for the specific destination as Warning, Notice, Informational, or Debug, which are lower event levels, the system sends the alarm to the corresponding destination. If you configure the alarm event level as Emergency, Alert, Critical, or Error, the system does not send the alarm to the corresponding location.
For each Cisco Unified Serviceability alarm definition, you can include an additional explanation or recommendation. All administrators have access to the added information. You directly enter information into the User Defined Text pane that displays in the Alarm Details window. Standard horizontal and vertical scroll bars support scrolling. Cisco Unified Serviceability adds the information to the database.
Viewing Alarm Information
You view alarm information to determine whether problems exist. The method that you use to view the alarm information depends on the destination that you chose when you configured the alarm. You can view alarm information that is sent to the SDI trace log file by using the trace and log central option in RTMT or by using a text editor. You can view alarm information that gets sent to local syslog by using the SysLog Viewer in RTMT.
Alarm Configuration Checklist
Table 3-1 provides an overview of the steps for configuring alarms.
Table 3-1 Alarm Configuration Checklist
Step 1
Choose the server and service for which you want the alarm information.
Step 2
Choose the destination of the alarm.
•
•
•
•
Step 3
Choose the alarm event level.
•
Step 4
If desired, add a definition to an alarm.
Step 5
If you chose an SDI trace file as the alarm destination, collect traces and view the information with the trace and log central option in RTMT.
Real-Time Monitoring Tool Administration Guide for Cisco Unity Connection
Step 6
If you chose local syslog as the alarm destination, view the alarm information in the SysLog Viewer in RTMT.
Real-Time Monitoring Tool Administration Guide for Cisco Unity Connection
Step 7
See the corresponding alarm definition for the description and recommended action.
Viewing Alarm Definitions and Adding User-Defined Descriptions, page 5-1
Where to Find More Information
Related Topics
•
•
•
•
•
