Alarm Configuration

You can use the Alarm Configuration window in Cisco CallManager Serviceability to define where CallManager will store the alarms and which level of alarms CallManager should store. You can define the alarm level for each destination individually. Destinations for alarms are as follows:

• Locally on the Cisco CallManager system in Microsoft Windows Event Log
• Locally on the Cisco CallManager system in trace log files
• Remotely on any syslog server; for example, Kiwi Syslog Daemon, a third-party application that runs on Windows systems

Configuring Alarms

To configure alarms in Cisco CallManager, follow this procedure:

Step 1.	From Cisco CallManager Serviceability, choose Alarm > Configuration.
Step 2.	Choose the appropriate server, which will then be displayed under Servers on the left side of the window and at the top of the window. A box with available services for alarms appears.
Step 3.	From the Configured Services drop-down list, choose the service for which you want to configure the alarm. The CallManager displays the chosen service at the top of the window in the Current Service area, along with the currently chosen server. A list of alarm monitors with event levels, similar to the one shown in Figure 32-1 (which shows the alarm configuration for the Cisco CallManager service), appears.   Figure 32-1. CallManager Alarm Configuration
Step 4.	Check the check box for each desired alarm destination.

Note

Only the Cisco CallManager and CTIManager services can use SDL Traces and only these services will have the check box for Enable Alarm for SDL Trace available.

Step 5.	From the Alarm Event Level drop-down menu, choose the desired alarm event level for each of the available alarms.
Step 6.	Save the configuration by clicking the Update button.

Note

To apply the current settings for selected services to all nodes in a cluster, check the Apply to All Nodes check box. To restore the default Cisco CallManager settings, click the SetDefault button and then the Update button.

 

Configuring Alarms for Java Applications

You cannot configure alarms for Java-based applications, such as Java Telephony Application Programming Interface (JTAPI) using the alarm configuration web pages. Use the Registry Editor provided with the operating system to view the alarm configuration and to change Registry entries. The Registry can be accessed by running the RegEdt32.exe or RegEdit.exe Registry Editors. Go to HKEY_LOCAL_MACHINESOFTWARECisco Systems, Inc.Cisco Java ApplicationsMonitorsEvent Log in the Registry (as shown in Figure 32-2) and set these values:

• Set the Enabled key to a value of 0 to turn off Event Log or to 1 to turn it on (by default, Event Log is enabled for Java-based applications).
• Set the Severity key to a value between 0 and 7 to set the alarm event level (the default severity level for Java-based applications on Cisco CallManager systems is 6).

Figure 32-2. CallManager Java Application Alarm Configuration

If you change the Registry entries, you must restart Java applications for the configuration changes to take effect.

Caution

It is recommended that you not change the Simple Network Management Protocol (SNMP) Trap and Catalog configurations. Those settings influence SNMP traps generated by the Cisco CallManager system. Those traps are used by network management applications, such as CiscoWorks. Changing the settings could cause malfunctioning of the entire network management system. Likewise, editing the Windows Registry is a dangerous process and can cause the entire operating system to crash. Be sure you exercise caution when making changes to the Windows Registry.

 

Alarm Details

Alarm definitions describe alarm messages. The definitions show what the alarms mean and how to recover from them.

To reach the alarm message definition details for an alarm, complete these steps:

Step 1.	From Cisco CallManager Serviceability, choose Alarm > Definition.
Step 2.	From the Equals drop-down menu, choose the service for which to check alarm definitions and click Find.
Step 3.	From the window that opens (an example is shown in Figure 32-3), select the alarm to see details. Figure 32-4 illustrates the alarm details for the CallManagerFailure alarm.

Figure 32-3. Listing of Available Alarm Definitions

Figure 32-4. Alarm Details for the CallManagerFailure Alarm

Cisco CallManager stores alarm definitions and recommended actions in a Structured Query Language (SQL) server database. You can search the database for definitions of all the alarms. The definition includes the alarm name, description, explanation, recommended action, severity, parameters, and monitors. This information aids you in troubleshooting problems that Cisco CallManager encounters.

Note

Administrators can add their own text to the alarm definition by simply entering information in the User Defined Text pane (not shown in Figure 32-4).

Trace Configuration