Contents

• Configure alarms
• Configure alarm for Feature or Network Service
• Configure alarm for service using Cisco Tomcat
• Service groups
• Alarm settings

Configure alarms

---

This chapter contains the following topics:

• Configure alarm for Feature or Network Service
• Configure alarm for service using Cisco Tomcat
• Service groups
• Alarm settings

Configure alarm for Feature or Network Service

This section describes how to add or update an alarm for a feature or network service that you manage through Cisco Unified Serviceability.

Note	Cisco recommends that you do not change SNMP Trap and Catalog configurations.

Procedure

---

Step 1	In Cisco Unified Serviceability, choose Alarm > Configuration. The Alarm Configuration window displays.
Step 2	From the Server drop-down list box, choose the server for which you want to configure the alarm and click Go.
Step 3	From the Services Group drop-down list box, choose category of service, for example, Database and Admin Services, for which you want to configure the alarm and click Go.
Step 4	From the Services drop-down list box, choose the service for which you want to configure the alarm and click Go. Only services that support the service group and your configuration display. Tip    The drop-down list box displays active and inactive services. In the Alarm Configuration window, a list of alarm monitors with the event levels displays for the chosen service.In addition, the Apply to All Nodes check box displays. In a High Availability (HA) deployment, you can apply the alarm configuration for the service to all servers in the cluster by checking the Apply to All Nodes check box.
Step 5	Configure the settings, as described in Table 1, which includes descriptions for monitors and event levels.
Step 6	To save your configuration, click Save. Note    To set the default, click Set Default and click Save.

---

Configure alarm for service using Cisco Tomcat

Some services in Unified Serviceability use Cisco Tomcat for alarm generation. For example, the system login alarm AuthenticationFailed uses Cisco Tomcat. To generate alarms for such services, perform the following procedure:

Procedure

---

Step 1	In Cisco Unified Serviceability, choose Alarm > Configuration.
Step 2	From the Server drop-down list box, choose the server for which you want to configure the alarm and Click Go.
Step 3	From the Services Group drop-down list box, choose Platform Services and Click Go.
Step 4	From the Services drop-down list box, choose Cisco Tomcat and Click Go.
Step 5	Configure the settings, as described in Table 1, which includes descriptions for monitors and event levels.
Step 6	To save your configuration, click Save.

---

Tip

The system sends the alarm if the configured alarm event level for the specific destination 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, which are higher severity levels, the system does not send the alarm to the corresponding location.

Service groups

The table below lists the services that correspond to the options in the Service Group drop-down list box in the Alarm Configuration window.

Note	Not all listed service groups and services apply to all system configurations.

Table 1 Service Groups in Alarm Configuration

Service Group	Services
Performance and Monitoring Services	Cisco AMC Service and Cisco RIS Data Collector
Backup and Restore Services	Cisco DRF Local and Cisco DRF Master
System Services	Cisco Trace Collection Service
Platform Services	Cisco Tomcat

Related References

Understanding Services

Alarm settings

The table below describes all alarm configuration settings, even though the service may not support the settings.

Table 2 Alarm configuration settings

Name	Description
Server	From the drop-down box, choose the server for which you want to configure the alarm; then, click Go.
Service Group	From the drop-down box, choose the category of services, for example, Database and Admin Services, for which you want to configure the alarm; then, click Go.
Service	From the Service drop-down box, choose the service for which you want to configure the alarm; then, click Go. Only services that support the service group and your configuration display. Tip    The drop-down list box displays active and inactive services.
Apply to All Nodes	To apply the alarm settings for the service to all servers in a cluster, check the check box.
Enable Alarm for Local Syslogs	The SysLog viewer serves as the alarm destination. The program logs errors in the Application Logs within SysLog Viewer and provides a description of the alarm and a recommended action. You can access the SysLog Viewer from the Cisco Unified Real-Time Monitoring Tool. For information on viewing logs with the SysLog Viewer, refer to the Cisco Unified CCX Real-Time Monitoring Tool Administration Guide.
Enable Alarm for Remote Syslogs	The Syslog file serves as the alarm destination. Check this check box to enable the Syslog messages to be stored on a Syslog server and to specify the Syslog server name. If this destination is enabled and no server name is specified, Cisco Unified Serviceability does not send the Syslog messages. Tip    In the Server field, enter the name or IP address of the remote Syslog server that you want to use to accept Syslog messages. For example, if you want to send the alarms to CiscoWorks Lan Management Solution, specify the CiscoWorks Lan Management Solution server name. Tip    Do not specify a Cisco Unified CCX server as the destination because the Cisco Unified CCX server does not accept Syslog messages from another server.
Enable Alarm for SDI Trace	The SDI trace library serves as the alarm destination. To log alarms in the SDI trace log file, check this check box and check the Trace On check box in the Trace Configuration window for the chosen service. For information on configuring settings in the Trace Configuration window in Cisco Unified Serviceability, see the Configure trace parameters.
Alarm Event Level	From the drop-down list box, choose one of the following options: Emergency—This level designates system as unusable. Alert—This level indicates that immediate action is needed. Critical—The system detects a critical condition. Error—This level signifies an error condition exists. Warning—This level indicates that a warning condition is detected. Notice—This level designates a normal but significant condition. Informational—This level designates information messages only. Debug—This level designates detailed event information that Cisco TAC engineers use for debugging.