-
Cisco CallManager Serviceability Administration Guide, Release 3.3(3)
-
Index
-
Preface
-
Introduction
-
Alarm Configuration
-
Alarm Definitions
-
Alarm Information
-
Trace Configuration
-
Trace Collection Configuration
-
Trace Analysis Configuration
-
Q.931 Translator
-
Service Activation
-
Control Center
-
Real-Time Monitoring Configuration
-
Phone Problem Reports Viewer
-
CDR Analysis and Reporting
-
CAR System Configuration
-
CAR Report Configuration
-
CAR User Reports Configuration
-
CAR System Reports Configuration
-
CAR Device Reports Configuration
-
CDR Search Configuration
-
Microsoft Performance
-
Bulk Trace Analysis
-
Overview of CiscoWorks2000
-
Path Analysis Configuration
-
System Log Management Configuration
-
Cisco Discovery Protocol Support Configuration
-
Cisco Secure Telnet Configuration
-
Show Command Line Interface
-
Simple Network Management Protocol Configuration
-
Understanding CAR Reports
-
Feedback
Table Of Contents
Configuring or Updating an Alarm for a Service
Applying an Alarm Configuration to All Nodes in a Cluster
Alarm Configuration
This chapter provides procedural information to configure Serviceability Alarms and contains the following topics:
•
Configuring or Updating an Alarm for a Service
•
Cisco CallManager Serviceability Alarms provides a web-based interface that has two main functions: configure alarms and events and provide alarm message definitions. Both functions assist the system administrator and support personnel in troubleshooting Cisco CallManager problems.You can configure alarms for Cisco CallManager servers that are in a cluster and services for each server, such as Cisco CallManager, Cisco TFTP, and Cisco CTIManager (see the "Configuring or Updating an Alarm for a Service" section).
You use Alarms to provide runtime status and state of the system and to take corrective action for problem resolution; for example, to determine whether phones are registered and working. Alarms contain information such as explanation and recommended action. Alarm information includes application name, machine name, and cluster name to help you perform troubleshooting for problems that are not on your local Cisco CallManager.
You configure the Alarm interface to send alarm information to multiple destinations, and each destination can have its own alarm event level (from debug to emergency).
You can forward alarms to a Serviceability Trace file. An administrator configures Alarms and Trace parameters and provides the information to a Cisco TAC engineer. You can direct Alarms to the Win2000 Event Log, Syslog, an SDI trace log file, an SDL trace log file (for Cisco CallManager and CTIManager only), or to all destinations. Use Trace to collect and analyze the alarms.
When a service issues an alarm, the alarm interface sends the alarm to the chosen monitors (for example, SDI trace). The monitor forwards the alarm or writes it to its final destination (such as a log file).
Note
Configuring or Updating an Alarm for a Service
This section describes how to configure an alarm for any Cisco CallManager service.
Note
Goto HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\Cisco Java Applications\Monitors\Event Log. Set the Enabled key to a value of 0 to turn off Event Log, or 1 to turn it on.
Goto HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\Cisco Java Applications\Monitors\Event Log. Set the Enabled the Severity key to a value between 0 and 7 to set the Alarm Event Level. Refer to the "Alarm Event Level Settings" section for event level settings.
If you change the registry entries, then JavaApplications must be restarted in order for the configuration changes to take effect.
Note
Refer to your online OS documentation for more information on how to use your standard registry editor.
Procedure
Step 1
The Cisco CallManager Serviceability window displays.
Step 2
Step 3
The server you chose displays, and a box with available services for alarms displays.
Step 4
The service that you chose displays after the Current Service title, along with the current server that you chose. A list of alarm monitors with the event levels displays in the Alarm Configuration window.
Note
Step 5
Step 6
A list with event levels displays.
Step 7
Step 8
Note
Related Topics
•
•
Applying an Alarm Configuration to All Nodes in a Cluster
This section describes how to apply an alarm configuration for all nodes in a Cisco CallManager cluster.
Procedure
Step 1
The Cisco CallManager Serviceability window displays.
Step 2
Step 3
The server that you chose displays, and a box with available services for alarms displays.
Step 4
The service that you chose displays after the Current Service title, along with the current server that you chose. A list of alarm monitors with the event levels displays in the Alarm Configuration window.
Note
Step 5
Step 6
A list with eight event levels displays.
Step 7
Step 8
Step 9
Note
Related Topics
•
Alarm Destination Settings
Table 2-1 describes the alarm destination settings.
Table 2-1 Alarm Destinations
Enable Alarm for Event Viewer
Windows 2000 Event Viewer program. The program logs Cisco CallManager errors in the Application Logs within Event Viewer and provides a description of the alarm and a recommended action.
Enable Alarm for SDI Trace
The SDI trace library. Ensure this alarm destination is configured in Trace configuration of Cisco CallManager Serviceability.
Enable Alarm for Syslog
The Syslog file. Check this check box to enable the Syslog messages and configure the Syslog server name. If this destination is enabled and no server name is specified, Cisco CallManager sends Syslog messages to the local host. This box remains unchecked by default.
Enable Alarm for SDL Trace
The SDL trace library. This destination applies only to Cisco CallManager and CTIManager services. Configure this alarm destination using Trace SDL configuration. See the "Configuring SDL Trace Parameters" section on page 5-39.
Related Topics
•
•
Alarm Event Level Settings
Table 2-2 describes the alarm event level settings.
Related Topics
•
•
