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 can 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).
Alarm Configuration and Settings
By configuring alarms, we will receive notification to help us perform troubleshooting.
Perform the following,
1.First navigate to the Unified Serviceability page
2.To configure Alarms,
Go to Cisco Unified Serviceability. Click on Alarm > Configuration:
Select the Server and other fields from drop-down list and click Go
•Server* - 192.168.1.8 -> Go
•Services Group* - CM services -> Go
•Service* - Cisco CallManager (Active) -> Go
3. Under the Local syslogs section, check Enable Alarm as shown in the image and set the Alarm Event Level as necessary.
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.
4. Under the Remote syslogs section, check Enable Alarm as shown in the above image and set the Alarm Event Level from the drop-down and specify the Server name. 5. If desired, check Enable Alarm under the SDI and SDL Trace section as shown on the above image. Set the Alarm Event level as necessary 6. Click “Save”
Alarm settings description
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 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.
To prevent too many alarms flooding the system, you can check the Exclude End Point Alarms checkbox. This ensures that the endpoint phone-related events get logged into a separate file.
Exclude End Point Alarms checkbox is displayed only for the Call Manager services, and is not selected by default. You need to select the Apply to All Nodes also, while selecting this checkbox. The configuration options for endpoint alarms are given in Table 4-3.
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 Communications Manager server as the destination because the Cisco Unified Communications Manager 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.
Enable Alarm for SDL Trace
The SDL trace library serves as the alarm destination. This destination applies only to the Cisco CallManager service and the CTIManager service. Configure this alarm destination by using Trace SDL configuration.
To log alarms in the SDL trace log file, check this check box and check the Trace On check box in the Trace Configuration window for the chosen service.