Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
How to delete the preconfigured alerts in the Real Time Monitoring Tool
CallProcessingNodeCpuPegging This alert is triggered when the percent CPU load on a call processing server is over the configured percentage for the configured period of time on the Cisco CallManager Publisher and Subscriber. If the CPU load is high, it affects call processing and other functionality.
NonCallProcessingNodeCpuPegging This alert is triggered when the percent CPU load on a non call processing server is over the configured percentage for the configured period of time. This includes the Music on Hold (MOH) server.
Note: High CPU can comprise a number of issues. The best course of action in this instance is to collect the Event Viewer logs and open a TAC service request.
LowInAvailableHeartbeatRate (LowCallManagerHeartbeatRate) This alert is triggered when the Cisco CallManager heartbeat rate is lower than the configured value.
LowTFTPServerHeartbeatRate This alert is triggered when the Trivial File Transfer Protocol (TFTP) server heartbeat rate is lower than the configured value.
LowTcdServerHeartbeatRate This alert is triggered when the Telephony Call Dispatcher (TCD) server heartbeat rate is lower than the configured value.
Note: The heartbeat acts as an indicator of the life of whatever it monitors. In order to find out when the heartbeat loss is detected, click the blinking icon.
DirectoryConnectionFailed This alert is triggered when the directory connection fails. When the customer directory connection fails between Cisco CallManager, with either the Lightweight Directory Access Protocol (LDAP) Data Connection Directory (DCD) or Active Directory (AD).
DirectoryReplicationFailed This alert is triggered when directory replication fails. If AD is integrated, this alarm can be disabled.
With both the DirectoryConnectionFailed and the DirectoryReplicationFailed, it is good to complete these steps:
Check the Application and System logs in the Event Viewer.
Check all of the logs from the C:\dcdsrvr\log folder.
Check the EVyyyymmdd*.* files from the C:\dcdsrvr\run\dcx500 folder.
If the CDR Analysis and Reporting Tool is in use, check the size of these files under C:\Program Files\Microsoft SQL Server\MSSQL\Data:
If these files are too large, they must be shrunk. Also, there are scripts to run that backup, clean and restore the directory replication.
Code Yellow This alert is triggered when a Cisco CallManager CodeYellowEntry event is generated. This is usually the last stage before a critical event occurs, such as a service shutting down.