FeedbackTable Of Contents
Where to Find More Information
Alerts
This chapter contains information on the following topics:
•
Where to Find More Information
Understanding Alerts
RTMT, which supports alert defining, setting, and viewing, contains preconfigured and user-defined alerts. Although you can perform configuration tasks for both types, you cannot delete preconfigured alerts (whereas you can add and delete user-defined alerts). The Alert menu comprises the following menu options:
•
Note
•
•
•
•
•
•
•
•
•
•
In RTMT you can configure alert notification for perfmon counter value thresholds, for schedule for alert checking, and for status change of device (for example, port is out of service).
The Tools tab below the Quick Launch Channel includes the Alert Central category. Alert Central provides both the current status and the history of all the alerts in the Cisco CallManager cluster. To monitor Cisco CallManager alerts, use the Tools tab in conjunction with the Alert menu option under the Tools menu.
Preconfigured Alerts
RTMT comprises a set of preconfigured alerts. You cannot delete these alerts; however, you can enable or disable them in Alert Central.
The following list comprises the preconfigured alerts in RTMT:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Alert Customization
You can configure both preconfigured and user-defined alerts in RTMT; however, you cannot delete preconfigured alerts. You can also disable both preconfigured and user-defined alerts in RTMT. You can add and delete user-defined alerts in the performance-monitoring window.
Table 7-1 provides a list of fields that you will use to configure each alert; users can configure preconfigured fields, unless otherwise noted.
Table 7-1 Alert Customization
Alert Name
High-level name of the monitoring item with which RTMT associates an alert
Descriptive name. For preconfigured alerts, you cannot change this field. See the "Enabling Trace Download" section.
Description
Description of the alert
You cannot edit this field for preconfigured alerts. See the "Enabling Trace Download" section.
Perfmon Counters
List of source perfmon counters
For preconfigured alerts, you cannot change this field.
Value Threshold
Condition to raise alert (value is...)
Specify up < - > down, less than #, %, rate greater than #, %, rate.
Evaluation Method
Method used to check the threshold condition
Specify value to be evaluated as absolute, delta (present - previous), or % delta.
Duration Threshold
Condition to raise alert (how long value threshold has to persist before raising alert)
Options include right away and specify at least X minutes.
Number of Events Threshold
Raise alert only when a configurable number of events exceed a configurable time interval (in minutes).
For ExcessiveVoiceQualityReports, the default thresholds equal 10 to 60 minutes. For RouteListExhausted and MediaListExhausted, the defaults equal 0 to 60 minutes.
Node IDs
Cluster or list of nodes to monitor
Cisco CallManager nodes, Cisco TFTP node, or first node.
Note
Alert Action ID
ID of alert action to take (System always logs alerts no matter what the alert action.)
Alert action gets defined first (see the "Alert Action Configuration" section). If this field is blank, that indicates that e-mail is disabled.
Disabled
Alert disabled
Options include enabled or disabled.
Clear Alert
Resets alert (change the color of an alert item from red to black) to signal that the alert has been resolved
After an alert has been raised, its color will automatically change to red and stay that way until you manually clear the alert. Use Clear All to clear all alerts.
In Safe Range
Indicates whether an alert threshold condition has been met (not configurable)
This field does not apply to MaliciousCall and Registered YYY types of alerts. For DChannel OOS alert, this field remains YES only when you no longer have any outstanding OOS devices. The Code Yellow alert will be back in safe range only when you receive a CodeYellowExit event from Cisco CallManager.
Alert Details
Displays the detail of an alert (not configurable)
For VoiceQualityReports, RouteListExhausted, and MediaListExhausted, up to 30 current event details display in the current monitoring interval if an alert has been raised in the current interval. Otherwise, the previous 30 event details in the previous interval displays. For DChannel OOS alert, the list of outstanding OOS devices at the time the alert was raised displays.
Alert Generation Rate
How often to generate alert when alert condition persists
Specify every X minutes. (Raise alert once every X minutes if condition persists.)
Specify every X minutes up to Y times. (Raise alert Y times every X minutes if condition persists.)
User Provide Text
Administrator to append text on top of predefined alert text
N/A
Severity
For viewing purposes (for example, show only Sev. 1 alerts)
Specify defaults that are provided for predefined (for example, Error, Warning, Information) alerts.
Collection Polling Rate
Same rate for both preconfigured and user-defined alerts
Although not configurable through RTMT Alert Central, you can customize this through Cisco CallManager Administration in Service Parameters.
Alert Action Configuration
In RTMT, you can configure alert actions for every alert that is generated and have the alert action sent to e-mail recipients that you specify in the alert action list.
Table 7-2 provides a list of fields that you will use to configure alert actions. Users can configure all fields, unless otherwise marked.
Enabling Trace Download
Some preconfigured alerts will allow you to initiate a trace download based on the occurrence of an event. You can automatically capture traces when a particular event occurs by checking the Enable TCT Download check box in Set Alert/Properties for the following alerts:
•
•
Caution
Understanding Alert Logs
The alert log stores the alert, which is also stored in memory. The memory gets cleared at a constant interval, leaving the last 30 minutes of data in the memory. When the service starts/restarts, the last 30 minutes of the alert data load into the memory by the system reading from the alert logs that exist in all servers in the cluster. The alert data in the memory gets sent to the RTMT clients on request.
Upon RTMT startup, RTMT shows all logs that occurred in the last 30 minutes in the Alert Central log history. Alert log periodically gets updated, and new logs get inserted into the log history window. After the number of logs reaches 100, RTMT removes the oldest 40 logs.
The following file name format for the alert log applies: AlertLog_MM_DD_YYYY_hh_mm.csv.
The alert log includes the following attributes:
•
•
•
•
•
•
•
•
The first line of each log file comprises the header. Details of each alert gets written in a single line, separated by a comma.
Where to Find More Information
Related Topics
•
•
