Help Center

Threshold - cmaServerAlert

Properties

Nodes to Run On: #DefaultNode

Threshold Conditions

CiscoServiceDown

Where Clause:

STATUSE = 0

Alarm Interval:

Every5 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\CLUSTERS,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\CLUSTERS,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\CLUSTERS,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\CLUSTERS,
#All Telephony Systems\Cisco Emergency Responder\Clusters

Record:

CMASRVCE

Recommended action:

This event is generated when one of the critical services is not running.

To further analyse why the service stopped, check to see if there are any core files, by logging in via CLI interface and use commands such as utils core active list. Once the core dump instance has been identified via the list command, the next step is to obtain the core file backtrace for review using command utils core active analyze <CoreFileName>.
If this occurs frequently, contact Cisco TAC with the information.

Depending on the service stopped, collect the relevant trace logs files for further analysis.
You can start the service manually via the Control Center for Feature or Network Services under the Unified Serviceability page.

Message Destinations:

SNMP Trap

Message

^srcnode@: @CMASRVCE.CMNAME@: @CMASRVCE.SRVNAME@ service is down.

Severity

 Critical

Problem Summary

Event No

0

Message

^srcnode@: @CMASRVCE.CMNAME@: @CMASRVCE.SRVNAME@ service is down.

Severity

 Critical

Dispatch Manager

Message

^srcnode@: @CMASRVCE.CMNAME@: @CMASRVCE.SRVNAME@ service is down.

Severity

 Critical

CmaCallManagerUp%Low

Where Clause:

TYPE = "THRESHOLD" AND SUBID2 = "CUCM" AND (DAY%UP > 95 AND DAY%UP < 99) AND THLDCOND = "CmaServerDown"

Alarm Interval:

Every1 Day(s)

Nodes to Monitor:

#CurrentNode

Record:

MpAvailability

Recommended action:

The server is only contactable from the Prognosis monitoring node between 95-99% of today.

Check the various services needed for Prognosis monitoring are running on the server. These include:

Cisco AXL Web Service
Cisco CallManager SNMP service,
SNMP Master Agent,
SOAP - Perfomrnace Monitoring APIs

These can be found either under Servicability -> Tool -> Control Center - Feature Services or Control Center - Network Services.
Restart them if necessary.

Ensure the user set up for Prognosis monitoring has the roles for "Standard AXL API access" to allow access to invoke AXL query, "Standard CCM Admin users" to access to the Cisco Applicaiton web site, "Standard CCMADMIN Read Only" to allow read access to all configuration information and "Standard SERVICEABILITY" to allow access to download CDRs.

Message Destinations:

Problem Summary

Event No

0

Message

@AVMON.ID@ is up @AVMON.DAY%UP@ % today.(^srcnode@)

Severity

 Warning

SNMP Trap

Message

@AVMON.ID@ is up @AVMON.DAY%UP@ % today.(^srcnode@)

Severity

 Error

Dispatch Manager

Message

@AVMON.ID@ is up @AVMON.DAY%UP@ % today.(^srcnode@)

Severity

 Warning

CmaCallManagerUp%TooLow

Where Clause:

TYPE = "THRESHOLD" AND SUBID2 = "CUCM" AND DAY%UP < 95 AND THLDCOND = "CmaServerDown"

Alarm Interval:

Every1 Day(s)

Nodes to Monitor:

#CurrentNode

Record:

MpAvailability

Recommended action:

The server is contactable from the Prognosis monitoring node for less than 95% of today.

Check the various services needed for Prognosis monitoring are running on the server. These include:

Cisco AXL Web Service
Cisco CallManager SNMP service,
SNMP Master Agent,
SOAP - Perfomrnace Monitoring APIs

These can be found either under Servicability -> Tool -> Control Center - Feature Services or Control Center - Network Services.
Restart them if necessary.

Ensure the user set up for Prognosis monitoring has the roles for "Standard AXL API access" to allow access to invoke AXL query, "Standard CCM Admin users" to access to the Cisco Applicaiton web site, "Standard CCMADMIN Read Only" to allow read access to all configuration information and "Standard SERVICEABILITY" to allow access to download CDRs.

Message Destinations:

Problem Summary

Event No

0

Message

@AVMON.ID@ is up @AVMON.DAY%UP@ % today.(^srcnode@)

Severity

 Error

SNMP Trap

Message

@AVMON.ID@ is up @AVMON.DAY%UP@ % today.(^srcnode@)

Severity

 Critical

Dispatch Manager

Message

@AVMON.ID@ is up @AVMON.DAY%UP@ % today.(^srcnode@)

Severity

 Error

CmaCallsRejected

Where Clause:

GOS > 0.05

Alarm Interval:

Every5 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES

Record:

CMAPERF

Recommended action:

GOS is represents the proportion of calls that are rejected due to call throttling.
Call Manager will start throttling (rejecting) new calls when there are a large amount of calls going through the system.
For example, one cause for ICT call throttling occurs when calls across an ICT enter a route loop condition as the threshold limit of 140 calls per 5 seconds is met, the ICT will start throttling (rejecting) new calls.
CCM/SDI and SDL trace files record call throttling events and can provide useful information.
Generally, repeated call throttling events require assistance from the Cisco Technical Assistance Center (TAC). TAC will likely request these trace files for closer examination.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: CUCM rejected @CMAPERF.GOS@ % of the calls (^srcnode@)

Severity

 Critical

SNMP Trap

Message

^srcnode@: CUCM rejected @CMAPERF.GOS@ % of the calls (^srcnode@)

Severity

 Critical

Availability

Entity Name

^srcnode@ Calls Rejected %

Primary Sub ID

@CMAPERF.CLUSTER@

Secondary Sub ID

CUCM

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: CUCM rejected @CMAPERF.GOS@ % of the calls (^srcnode@)

Priority

2

Timeout on stop

1 Day(s)

Dispatch Manager

Message

^srcnode@: CUCM rejected @CMAPERF.GOS@ % of the calls (^srcnode@)

Severity

 Critical

CmaCallsRejectedOk

Where Clause:

GOS < 0.05 OR GOS = 0.05

Alarm Interval:

Every5 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES

Record:

CMAPERF

Recommended action:

No action is required.

Message Destinations:

Availability

Entity Name

^srcnode@ Calls Rejected %

Primary Sub ID

@CMAPERF.CLUSTER@

Secondary Sub ID

CUCM

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: CUCM call rejection is back within limits: @CMAPERF.GOS@ % (^srcnode@)

Priority

2

Timeout on stop

1 Day(s)

CmaCCMAgtProcessDown [Disabled]

Where Clause:

INSTNAME CONTAINS "ccmAgt"

Alarm Interval:

Every10 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES

Record:

CMAPROC

Recommended action:

The ccmAgt service provides SNMP access to provisioning and statistics information that is available for the Cisco Server.
Logon to the Cisco Unified Servicability web admin page of the server,
select Tools -> Control Center - Feature Services from the menu bar,
select the server in question from the drop down list and hit Go,
and check the status of the Cisco CallManager SNMP Service.
Restart the service if it is necessary.
To further analyse why the service stopped, check to see if there are any core files, by logging in via CLI interface and use commands such as utils core active list. Once the core dump instance has been identified via the list command, the next step is to obtain the core file backtrace for review using command utils core active analyze <CoreFileName>.
If this occurs frequently, contact Cisco TAC with the information.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: A CUCM service is down -the ccmAgt process is not running.

Severity

 Warning

SNMP Trap

Message

^srcnode@: A CUCM service is down -the ccmAgt process is not running.

Severity

 Warning

Availability

Entity Name

^srcnode@ CCMAGT

Primary Sub ID

^srcnode@

Secondary Sub ID

PROCESS

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: A CUCM service is down -the ccmAgt process is not running.

Priority

1

Timeout on stop

15 Minute(s)

Dispatch Manager

Message

^srcnode@: A CUCM service is down -the ccmAgt process is not running.

Severity

 Warning

CmaCCMAgtProcessUp [Disabled]

Where Clause:

INSTNAME CONTAINS "ccmAgt"

Alarm Interval:

Every10 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES

Record:

CMAPROC

Recommended action:

No action is required.

Message Destinations:

Availability

Entity Name

^srcnode@ CCMAGT

Primary Sub ID

^srcnode@

Secondary Sub ID

PROCESS

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: A CUCM service is up -the ccmAgt process is now running.

Priority

1

Timeout on stop

15 Minute(s)

CmaCCMProcessDown [Disabled]

Where Clause:

(INSTNAME CONTAINS "CCM") AND (INSTNAME NOT CONTAINS "ccmAgt")

Alarm Interval:

Every10 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES

Record:

CMAPROC

Recommended action:

Either the Cisco CallManager (ccm) or the Cisco DirSync (CCMDirSync) services is not running:
Logon to the Cisco Unified Servicability web admin page of the server,
select Tools -> Control Center - Feature Services from the menu bar,
select the server in question from the drop down list and hit Go,
and check the status of the Services and restart the service if it is necessary.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@:CUCM service is down -the CCM process is not running.

Severity

 Warning

SNMP Trap

Message

^srcnode@:CUCM service is down -the CCM process is not running.

Severity

 Critical

Availability

Entity Name

^srcnode@ CCMProcess

Primary Sub ID

^srcnode@

Secondary Sub ID

PROCESS

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: CUCM service is down -the CCM process is not running.

Priority

1

Timeout on stop

15 Minute(s)

Dispatch Manager

Message

^srcnode@:CUCM service is down -the CCM process is not running.

Severity

 Warning

CmaCCMProcessUp [Disabled]

Where Clause:

(INSTNAME CONTAINS "CCM") AND (INSTNAME NOT CONTAINS "ccmAgt")

Alarm Interval:

Every1 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES

Record:

CMAPROC

Recommended action:

No action is required.

Message Destinations:

Availability

Entity Name

^srcnode@ CCMProcess

Primary Sub ID

^srcnode@

Secondary Sub ID

PROCESS

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: CUCM service is up -the CCM process is now running.

Priority

1

Timeout on stop

15 Minute(s)

CmaCertAboutToExpire

Where Clause:

NOTAFTER < CURRENTTIME + 60 days AND CURRENTTIME < NOTAFTER

Alarm Interval:

Every1 Day(s)

Nodes to Monitor:

#All Telephony Systems\Cisco CallManager Appliance\All Nodes,
#All Telephony Systems\Cisco Emergency Responder\All Nodes,
#All Telephony Systems\Cisco Unified Presence\All Nodes,
#All Telephony Systems\Cisco Unity Connections\All Nodes

Record:

CMACERTS

Recommended action:

Please check certificates and generate new ones if necessary.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: Certificate @CMACERTS.FILENAME@ is due to expire on @CMACERTS.NOTAFTER@

Severity

 Warning

SNMP Trap

Message

^srcnode@: Certificate @CMACERTS.FILENAME@ is due to expire on @CMACERTS.NOTAFTER@

Severity

 Warning

Dispatch Manager

Message

^srcnode@: Certificate @CMACERTS.FILENAME@ is due to expire on @CMACERTS.NOTAFTER@

Severity

 Warning

CmaCertExpired

Where Clause:

CURRENTTIME > NOTAFTER AND CURRENTTIME < NOTAFTER + 60 days

Alarm Interval:

Every1 Day(s)

Nodes to Monitor:

#All Telephony Systems\Cisco CallManager Appliance\All Nodes,
#All Telephony Systems\Cisco Emergency Responder\All Nodes,
#All Telephony Systems\Cisco Unified Presence\All Nodes,
#All Telephony Systems\Cisco Unity Connections\All Nodes

Record:

CMACERTS

Recommended action:

Please check certificate, generate new ones and removed old expired certificates.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: Certificate @CMACERTS.FILENAME@ expired on @CMACERTS.NOTAFTER@.

Severity

 Error

SNMP Trap

Message

^srcnode@: Certificate @CMACERTS.FILENAME@ expired on @CMACERTS.NOTAFTER@.

Severity

 Error

Dispatch Manager

Message

^srcnode@: Certificate @CMACERTS.FILENAME@ expired on @CMACERTS.NOTAFTER@.

Severity

 Error

CmaClusterNotContactable

Where Clause:

CNTBL = 0

Alarm Interval:

Every10 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\CLUSTERS,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\CLUSTERS,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\CLUSTERS,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\CLUSTERS,
#All Telephony Systems\Cisco Emergency Responder\Clusters

Record:

IpTelephonyGenericRecord

Recommended action:

This alert occurs when non of the server is reachable by Prognosis monitoring node to retrieve any statistics for any of the performance objects.

Check the various services needed for Prognosis monitoring are running on all the servers within the cluster where applicable. These include:

Cisco AXL Web Service
Cisco CallManager SNMP service,
SNMP Master Agent,
SOAP - Perfomrnace Monitoring APIs

These can be found either under Servicability -> Tool -> Control Center - Feature Services or Control Center - Network Services.
Restart them if necessary.

Ensure the user set up for Prognosis monitoring has the roles for "Standard AXL API access" to allow access to invoke AXL query, "Standard CCM Admin users" to access to the Cisco Applicaiton web site, "Standard CCMADMIN Read Only" to allow read access to all configuration information and "Standard SERVICEABILITY" to allow access to download CDRs.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: Cluster @IPTGEN.DISPNAME@ is NOT contactable.

Severity

 Critical

SNMP Trap

Message

^srcnode@: Cluster @IPTGEN.DISPNAME@ is NOT contactable.

Severity

 Critical

Dispatch Manager

Message

^srcnode@: Cluster @IPTGEN.DISPNAME@ is NOT contactable.

Severity

 Critical

CmaCodeRedEntry

Where Clause:

CODEREE = 1

Alarm Interval:

Every5 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES

Record:

CMAPERF

Recommended action:

Unified CM has entered Code Red condition and will restart due to the fact that Unified CM has been in Code Yellow state for an extended period and is unlikely to recover on its own. The Cisco CallManager service automatically restarts in an attempt to clear the condition that is causing the Code Yellow state.
Memory problems or high CPU usage are generally at the root of a Code Yellow condition. A bad disk could also be the cause. Also, trace level settings can consume tremendous amounts of CPU (especially when the Enable SDL TCP Event Trace checkbox is enabled on the SDL Trace Configuration window in Cisco Unified Serviceability). Use RTMT to check for memory leaks, causes of any CPU spikes, and determine whether the server has sufficient memory for the tasks expected of this server. Run server diagnostics to determine if the disk is bad, and examine/reconfigure the SDL trace settings in Unified Serviceability to ensure that trace settings are not contributing to Code Yellow. You can determine the level of fragmentation on the hard disk by issuing the File Fragmentation command from the CLI for the trace directories. After taking one or more of these corrective actions, monitor the situation and collect existing trace files. If the CodeYellow condition does not disappeared in a reasonable amount of time as deemed by your organization, or if the system is frequently triggering the CodeYellowEntry alarm, contact the Cisco Technical Assistance Center (TAC) and supply the trace information you have collected.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: CUCM entered Code Red state (call throttling mode).

Severity

 Critical

SNMP Trap

Message

^srcnode@: CUCM entered Code Red state (call throttling mode).

Severity

 Critical

Dispatch Manager

Message

^srcnode@: CUCM entered Code Red state (call throttling mode).

Severity

 Critical

CmaCodeYellowEntry

Where Clause:

CODEYEE = 1

Alarm Interval:

Every5 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES

Record:

CMAPERF

Recommended action:

Unified CM has initiated call throttling due to unacceptably high delay in handling incoming calls.
Memory problems or high CPU usage are generally at the root of a Code Yellow condition. A bad disk could also be the cause. Also, trace level settings can consume tremendous amounts of CPU (especially when the Enable SDL TCP Event Trace checkbox is enabled on the SDL Trace Configuration window in Cisco Unified Serviceability). Use RTMT to check for memory leaks, causes of any CPU spikes, and determine whether the server has sufficient memory for the tasks expected of this server. Run server diagnostics to determine if the disk is bad, and examine/reconfigure the SDL trace settings in Unified Serviceability to ensure that trace settings are not contributing to Code Yellow. You can determine the level of fragmentation on the hard disk by issuing the File Fragmentation command from the CLI for the trace directories. After taking one or more of these corrective actions, monitor the situation and collect existing trace files. If the CodeYellow condition does not disappeared in a reasonable amount of time as deemed by your organization, or if the system is frequently triggering the CodeYellowEntry alarm, contact the Cisco Technical Assistance Center (TAC) and supply the trace information you have collected.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: CUCM entered Code Yellow state (call throttling mode).

Severity

 Error

SNMP Trap

Message

^srcnode@: CUCM entered Code Yellow state (call throttling mode).

Severity

 Error

Dispatch Manager

Message

^srcnode@: CUCM entered Code Yellow state (call throttling mode).

Severity

 Error

CmaCpuBusy

Where Clause:

INSTNAME CONTAINS "Total" AND (CPUUSE > 60 AND CPUUSE < 90)

Alarm Interval:

Every10 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES,
#All Telephony Systems\Cisco Emergency Responder\All Nodes

Record:

CMACPU

Recommended action:

This event occurs when the percentage of CPU load on a server is heavy for a period of time. To prevent execessive CPU on the server where it might start to affect it normal operations, check whether there are specific processes using excessive CPU by going to the CPU utilization details page for the server to see the top 5 processes by CPU usage. Once the process is identified, check trace log settings for the process and verify whether there is anything unexpected and follow up by further analysis on the process itself.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: The CPU is @CMACPU.CPUUSE@ % busy. (^srcnode@)

Severity

 Warning

SNMP Trap

Message

^srcnode@: The CPU is @CMACPU.CPUUSE@ % busy. (^srcnode@)

Severity

 Warning

Dispatch Manager

Message

^srcnode@: The CPU is @CMACPU.CPUUSE@ % busy. (^srcnode@)

Severity

 Warning

CmaCpuTooBusy

Where Clause:

INSTNAME CONTAINS "Total" AND CPUUSE > 90

Alarm Interval:

Every15 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES,
#All Telephony Systems\Cisco Emergency Responder\All Nodes

Record:

CMACPU

Recommended action:

This event occurs when the percentage of CPU load on a server is overloaded for a period of time. The most common reason for this event is that one or more processes are using excessive CPU. Check CPU usage of the various processes by going to the CPU utilization details page for the server to see the top 5 processes by CPU usage. Once the process is identified, check trace log settings for the process and verify whether there is anything unexpected and follow up by further analysis on the process itself.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: The CPU is too busy - @CMACPU.CPUUSE@ %. (^srcnode@)

Severity

 Critical

SNMP Trap

Message

^srcnode@: The CPU is too busy - @CMACPU.CPUUSE@ %. (^srcnode@)

Severity

 Critical

Dispatch Manager

Message

^srcnode@: The CPU is too busy - @CMACPU.CPUUSE@ %. (^srcnode@)

Severity

 Critical

CmaCTIManagerProcessDown [Disabled]

Where Clause:

INSTNAME CONTAINS "CTIManager"

Alarm Interval:

Every1 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES

Record:

CMAPROC

Recommended action:

The CTI Manager contains the CTI components that interface with applications. With CTI Manager, applications (JTAPI/TAPI) can access resources and functionality of all Cisco Unified Communications Manager in the cluster. If CTI manager is requried on this server,
logon to the Cisco Unified Servicability web admin page of the server,
select Tools -> Control Center - Feature Services from the menu bar,
select the server in question from the drop down list and hit Go,
and check both the status and activtation status of Cisco CTIManager under CM services.
Restart the service if it is necessary.
To further analyse why the service stopped, check to see if there are any core files, by logging in via CLI interface and use commands such as utils core active list. Once the core dump instance has been identified via the list command, the next step is to obtain the core file backtrace for review using command utils core active analyze <CoreFileName>.
If this occurs frequently, contact Cisco TAC with the information.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: A CUCM service is down -the CTIManager process is not running.

Severity

 Warning

SNMP Trap

Message

^srcnode@: A CUCM service is down -the CTIManager process is not running.

Severity

 Warning

Availability

Entity Name

^srcnode@ CTIManager

Primary Sub ID

^srcnode@

Secondary Sub ID

PROCESS

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: A CUCM service is down -the CTIManager process is not running.

Priority

1

Timeout on stop

15 Minute(s)

Dispatch Manager

Message

^srcnode@: A CUCM service is down -the CTIManager process is not running.

Severity

 Warning

CmaCTIManagerProcessUp [Disabled]

Where Clause:

INSTNAME CONTAINS "CTIManager"

Alarm Interval:

Every10 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES

Record:

CMAPROC

Recommended action:

No action is required.

Message Destinations:

Availability

Entity Name

^srcnode@ CTIManager

Primary Sub ID

^srcnode@

Secondary Sub ID

PROCESS

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: A CUCM service is up -the CTIManager process is now running.

Priority

1

Timeout on stop

15 Minute(s)

CmaDBmonpProcessDown [Disabled]

Where Clause:

INSTNAME CONTAINS "DBmon"

Alarm Interval:

Every10 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES

Record:

CMAPROC

Recommended action:

The Cisco Database Layer Monitor service monitors aspects of the database layer. This server takes responsibility for change notification and monitoring.This might lead to Change Notification Requests queued in the database being "stuck" and system changes are not taking effect.
The command for restarting the Cisco Database Layer Monitor service is:
utils service restart Cisco Database Layer Monitor
You can restart the Cisco Database Layer Monitor service on all servers in the cluster.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: A CUCM service is down -the DBmon process is not running.

Severity

 Warning

SNMP Trap

Message

^srcnode@: A CUCM service is down -the DBmon process is not running.

Severity

 Warning

Availability

Entity Name

^srcnode@ DBMon

Primary Sub ID

^srcnode@

Secondary Sub ID

PROCESS

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: A CUCM service is down -the DBmon process is not running.

Priority

1

Timeout on stop

15 Minute(s)

Dispatch Manager

Message

^srcnode@: A CUCM service is down -the DBmon process is not running.

Severity

 Warning

CmaDBmonProcessUp [Disabled]

Where Clause:

INSTNAME CONTAINS "DBmon"

Alarm Interval:

Every10 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES

Record:

CMAPROC

Recommended action:

No action is required.

Message Destinations:

Availability

Entity Name

^srcnode@ DBMon

Primary Sub ID

^srcnode@

Secondary Sub ID

PROCESS

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: A CUCM service is up -the DBmon process is now running.

Priority

1

Timeout on stop

15 Minute(s)

CmaDiskPartitionFull

Where Clause:

DISKUSED = 100

Alarm Interval:

Every2 Hour(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES,
#All Telephony Systems\Cisco Emergency Responder\All Nodes

Record:

CMAPART

Recommended action:

This event occurs when the percentage of space used for a parition on a server is completely full. Check percentage space used for the various partitions by going to the server summary page for the server in questions to see the top 5 partitions by disk space usage.
The most common issues that causing space used issues are core dump files or too many log files being stored on the partition.
To check for core dump files, log in the CLI interface and use commands such as utils core active list or file list activelog core. If the files exist, collect crash dump using RTMT and then considered deleting the core files by using the command: file delete activelog core.
As for log files, check both the LogPartitionLowWaterMarkExceeded and the LogPartitionHighWaterMarkExceeded values and lower them to a more desire value and let the system purge the files using these settings automatically.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: Disk partition @CMAPART.INSTNAME@ is full. (^srcnode@)

Severity

 Critical

SNMP Trap

Message

^srcnode@: Disk partition @CMAPART.INSTNAME@ is full. (^srcnode@)

Severity

 Critical

Availability

Entity Name

^srcnode@ disk @CMAPART.INSTNAME@

Primary Sub ID

@CMAPART.CLUSTER@

Secondary Sub ID

DISK

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: Disk partition @CMAPART.INSTNAME@ usage is @CMAPART.DISKUSED@ % (@CMAPART.DISKUSMB@ Mb), Total: @CMAPART.DISKTOTL@ Mb, (^srcnode@)

Priority

1

Timeout on stop

1 Day(s)

Dispatch Manager

Message

^srcnode@: Disk partition @CMAPART.INSTNAME@ is full. (^srcnode@)

Severity

 Critical

CmaDiskPartitionNearFull

Where Clause:

DISKUSED > 90 AND DISKUSED < 100

Alarm Interval:

Every2 Hour(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES,
#All Telephony Systems\Cisco Emergency Responder\All Nodes

Record:

CMAPART

Recommended action:

This event occurs when the percentage of space used for a parition on a server is high. Check percentage space used for the various partitions by going to the server summary page for the server in questions to see the top 5 partitions by disk space usage.
The most common issues that causing space used issues are core dump files or too many log files being stored on the partition.
To check for core dump files, log in the CLI interface and use commands such as utils core active list or file list activelog core. If the files exist, collect crash dump using RTMT and then considered deleting the core files by using the command: file delete activelog core.
As for log files, check both the LogPartitionLowWaterMarkExceeded and the LogPartitionHighWaterMarkExceeded values and lower them to a more desire value and let the system purge the files using these settings automatically.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: Disk partition @CMAPART.INSTNAME@ is nearly full. Usage is @CMAPART.DISKUSED@ % (@CMAPART.DISKUSMB@ Mb, Total: @CMAPART.DISKTOTL@ Mb), (^srcnode@)

Severity

 Error

SNMP Trap

Message

^srcnode@: Disk partition @CMAPART.INSTNAME@ is nearly full. Usage is @CMAPART.DISKUSED@ % (@CMAPART.DISKUSMB@ Mb, Total: @CMAPART.DISKTOTL@ Mb), (^srcnode@)

Severity

 Error

Dispatch Manager

Message

^srcnode@: Disk partition @CMAPART.INSTNAME@ is nearly full. Usage is @CMAPART.DISKUSED@ % (@CMAPART.DISKUSMB@ Mb, Total: @CMAPART.DISKTOTL@ Mb), (^srcnode@)

Severity

 Error

CmaDiskPartitionNotFull

Where Clause:

DISKUSED < 100

Alarm Interval:

Every2 Hour(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES,
#All Telephony Systems\Cisco Emergency Responder\All Nodes

Record:

CMAPART

Recommended action:

No action is required.

Message Destinations:

Availability

Entity Name

^srcnode@ disk @CMAPART.INSTNAME@

Primary Sub ID

@CMAPART.CLUSTER@

Secondary Sub ID

DISK

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: Disk partition @CMAPART.INSTNAME@ usage is @CMAPART.DISKUSED@ % (@CMAPART.DISKUSMB@ Mb, Total: @CMAPART.DISKTOTL@ Mb), (^srcnode@)

Priority

1

Timeout on stop

1 Day(s)

CmaFreeMemoryLow

Where Clause:

MEMUSEDP > 90

Alarm Interval:

Every10 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES,
#All Telephony Systems\Cisco Emergency Responder\All Nodes

Record:

CMAMEM

Recommended action:

This event occurs when the percentage of physical memory on a server is low for a period of time. The most common reason for this event is that one or more processes have a memory leak. It is important to identify which process is using excessive memory. Check memory usage of the various processes by going to the memory utilization details page for the server to see the top 5 processes by memory usage. Once the process is identified, if you suspect a memory leak where the memory usage for a process increases continually, you may want to consider restart that process at a conveinent time. Otherwise, you might want to consider increasing the physical memory for this server.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: Memory used is @CMAMEM.MEMUSEDP@ % and is Low. (^srcnode@)

Severity

 Warning

SNMP Trap

Message

^srcnode@: Memory used is @CMAMEM.MEMUSEDP@ % and is Low. (^srcnode@)

Severity

 Warning

Dispatch Manager

Message

^srcnode@: Memory used is @CMAMEM.MEMUSEDP@ % and is Low. (^srcnode@)

Severity

 Warning

CmaFreeVirtualMemoryLow

Where Clause:

VMEMUSEP > 90

Alarm Interval:

Every10 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES,
#All Telephony Systems\Cisco Emergency Responder\All Nodes

Record:

CMAMEM

Recommended action:

This event occurs when the percentage of vritual memory on a server is low for a period of time. The most common reason for this event is that one or more processes have a memory leak. It is important to identify which process is using excessive memory. Check memory usage of the various processes by going to the memory utilization details page for the server to see the top 5 processes by memory usage. Once the process is identified, if you suspect a memory leak where the memory usage for a process increases continually, you may want to consider restart that process at a conveinent time.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: Virtual memory used is @CMAMEM.VMEMUSEP@ % and is Low. (^srcnode@)

Severity

 Warning

SNMP Trap

Message

^srcnode@: Virtual memory used is @CMAMEM.VMEMUSEP@ % and is Low. (^srcnode@)

Severity

 Warning

CmaJavaProcessDown [Disabled]

Where Clause:

INSTNAME CONTAINS "java"

Alarm Interval:

Every10 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES

Record:

CMAPROC

Recommended action:

This alert will be raised when the java process is not running.
It is not an essential proces to have and that's why this alert conditiion is start disabled.
It serves jsut an example. Ignore and remove the condition if necessary.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: A CUCM service is down -the Java process is not running.

Severity

 Warning

SNMP Trap

Message

^srcnode@: A CUCM service is down -the Java process is not running.

Severity

 Warning

Availability

Entity Name

^srcnode@ Java

Primary Sub ID

^srcnode@

Secondary Sub ID

PROCESS

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: A CUCM service is down -the Java process is not running.

Priority

1

Timeout on stop

15 Minute(s)

Dispatch Manager

Message

^srcnode@: A CUCM service is down -the Java process is not running.

Severity

 Warning

CmaJavaProcessUp [Disabled]

Where Clause:

INSTNAME CONTAINS "java"

Alarm Interval:

Every10 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES

Record:

CMAPROC

Recommended action:

No action is required.

Message Destinations:

Availability

Entity Name

^srcnode@ Java

Primary Sub ID

^srcnode@

Secondary Sub ID

PROCESS

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: A CUCM service is up -the Java process is now running.

Priority

1

Timeout on stop

15 Minute(s)

CmaPhoneLicenseUsed90%

Where Clause:

(FEATTYPE = 2) AND ((USEDUN * 100 / LICUN) > 90)

Alarm Interval:

Every5 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\CLUSTERS

Record:

CMALICD

Recommended action:

The system is operating with close to the phone license limit.
If more phones are to be added to the systems, you will need to consider to other more phone license. Otherwise, the system might go into license
shortage, and you will no longer be able to provision users and devices.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: More than 90% phone licenses have been used.

Severity

 Warning

SNMP Trap

Message

^srcnode@: More than 90% phone licenses have been used.

Severity

 Warning

CmaProcessUsageHigh [Disabled]

Where Clause:

(MEMUSE > 50 OR CPUUSE > 50) AND INSTNAME NOT CONTAINS "CCM"

Alarm Interval:

Every5 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES

Record:

CMAPROC

Recommended action:

This event occurs when the percentage of CPU load on a non-CCM process is over 50%. To prevent execessive CPU on the server where it might start to affect it normal operations. Once the process is identified, check trace log settings for the process and verify whether there is anything unexpected and follow up by further analysis on the process itself.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: Process @CMAPROC.INSTNAME@ is using @CMAPROC.CPUUSE@ % of CPU and @CMAPROC.MEMUSE@ % of Memory. (^srcnode@)

Severity

 Error

SNMP Trap

Message

^srcnode@: Process @CMAPROC.INSTNAME@ is using @CMAPROC.CPUUSE@ % of CPU and @CMAPROC.MEMUSE@ % of Memory. (^srcnode@)

Severity

 Error

Dispatch Manager

Message

^srcnode@: Process @CMAPROC.INSTNAME@ is using @CMAPROC.CPUUSE@ % of CPU and @CMAPROC.MEMUSE@ % of Memory. (^srcnode@)

Severity

 Error

CmaReplicationStatusErr

Where Clause:

REPSTAT = 3 OR REPSTAT = 4

Alarm Interval:

Every5 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#All Telephony Systems\Cisco Unified Presence\All Nodes,
#All Telephony Systems\Cisco Unity Connections\All Nodes

Record:

CMAREPS

Recommended action:

This alert is raised when replication on a particular server is bad or the replication setup did not succeed.
It is recommended that you run utils dbreplication status on the CLI to determine the location and cause of failure.
In addition, follow the information as described under the Troubleshooting technotes on the Cisco web site for "Steps to Troubleshoot Database Replication"

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: CallManager replication status is @CMAREPS.REPSTAT@

Severity

 Error

SNMP Trap

Message

^srcnode@: CallManager replication status is @CMAREPS.REPSTAT@

Severity

 Error

CmaServerDown

Where Clause:

CNTBL = 0

Alarm Interval:

Every5 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES

Record:

CMAPERF

Recommended action:

The server is no longer contactable from the Prognosis monitoring node.

Check the various services needed for Prognosis monitoring are running on the server. These include:

Cisco AXL Web Service
Cisco CallManager SNMP service,
SNMP Master Agent,
SOAP - Perfomrnace Monitoring APIs

These can be found either under Servicability -> Tool -> Control Center - Feature Services or Control Center - Network Services.
Restart them if necessary.

Ensure the user set up for Prognosis monitoring has the roles for "Standard AXL API access" to allow access to invoke AXL query, "Standard CCM Admin users" to access to the Cisco Applicaiton web site, "Standard CCMADMIN Read Only" to allow read access to all configuration information and "Standard SERVICEABILITY" to allow access to download CDRs.

Message Destinations:

SNMP Trap

Message

^srcnode@: CUCM is not contactable.

Severity

 Critical

Availability

Entity Name

^srcnode@ CUCM Status

Primary Sub ID

@CMAPERF.CLUSTER@

Secondary Sub ID

CUCM

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: CUCM is not contactable.

Priority

1

Timeout on stop

1 Day(s)

Problem Summary

Event No

0

Message

^srcnode@: CUCM is not contactable.

Severity

 Critical

Dispatch Manager

Message

^srcnode@: CUCM is not contactable.

Severity

 Critical

CmaServerOK

Where Clause:

CNTBL <> 0

Alarm Interval:

Every5 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES

Record:

CMAPERF

Recommended action:

No action is required.

Message Destinations:

Availability

Entity Name

^srcnode@ CUCM Status

Primary Sub ID

@CMAPERF.CLUSTER@

Secondary Sub ID

CUCM

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: CUCM is contactable.

Priority

1

Timeout on stop

1 Day(s)

CmaSNMPProcessDown [Disabled]

Where Clause:

INSTNAME CONTAINS "snmpd"

Alarm Interval:

Every10 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES

Record:

CMAPROC

Recommended action:

The main SNMP process on the server is not running. It is likely that SNMP notifications can no longer be sent from the server and 3rd party monitoring tool will no longer be able to poll the server to monitor it.
You can start the service manually via the Control Center - Network Services under the Unified Serviceability page.

Message Destinations:

Problem Summary

Event No

0

Message

^srcnode@: A CUCM service is down -the SNMPD process is not running.

Severity

 Warning

SNMP Trap

Message

^srcnode@: A CUCM service is down -the SNMPD process is not running.

Severity

 Warning

Availability

Entity Name

^srcnode@ SNMPD

Primary Sub ID

^srcnode@

Secondary Sub ID

PROCESS

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: A CUCM service is down -the SNMPD process is not running.

Priority

1

Timeout on stop

15 Minute(s)

Dispatch Manager

Message

^srcnode@: A CUCM service is down -the SNMPD process is not running.

Severity

 Warning

CmaSNMPProcessUp [Disabled]

Where Clause:

INSTNAME CONTAINS "snmpd"

Alarm Interval:

Every10 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNITY CONNECTIONS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO CONTACT CENTER EXPRESS\ALL NODES,
#ALL TELEPHONY SYSTEMS\CISCO UNIFIED PRESENCE\ALL NODES

Record:

CMAPROC

Recommended action:

No action is required.

Message Destinations:

Availability

Entity Name

^srcnode@ SNMPD

Primary Sub ID

^srcnode@

Secondary Sub ID

PROCESS

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: A CUCM service is up -the SNMPD process is now running.

Priority

1

Timeout on stop

15 Minute(s)

CmaTftpFilesNotFound

Where Clause:

REQFFNFI > 0

Alarm Interval:

Every1 Hour(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES

Record:

CMATFTP

Recommended action:

This alert indicates that there are TFTP requests for which the requested file was not found. When the TFTP server does not find the requested file, a message gets sent to the requesting device. If the cluster is configured as secure, this event usually indicates an error condition and further analysis of the TFTP trace log might be required.
If, however, the cluster is configured as non-secure, it is normal for the CTL file to be absent (not found), which results in a message being sent to the requesting device and a corresponding increment in this counter. For non-secure clusters, then, this normal occurrence does not represent an error condition and user might consider to disable this alert condition for this cluster.

Message Destinations:

SNMP Trap

Message

^srcnode@: TFTP requests failed - files not found. (^srcnode@)

Severity

 Error

Problem Summary

Event No

0

Message

^srcnode@: TFTP requests failed - files not found. (^srcnode@)

Severity

 Error

Dispatch Manager

Message

^srcnode@: TFTP requests failed - files not found. (^srcnode@)

Severity

 Error

CmaTftpHeartBeatOk

Where Clause:

NUMHEBE > 0

Alarm Interval:

Every5 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES

Record:

CMATFTP

Recommended action:

No actrion is required.

Message Destinations:

Availability

Entity Name

^srcnode@ TFTP Heartbeat

Primary Sub ID

@CMATFTP.CLUSTER@

Secondary Sub ID

TFTP

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: TFTP Heart Beat present. TFTP Service is now Up. (^srcnode@)

Priority

1

Timeout on stop

1 Day(s)

CmaTftpHeartBeatProblem

Where Clause:

NUMHEBE = 0

Alarm Interval:

Every5 Minute(s)

Nodes to Monitor:

#ALL TELEPHONY SYSTEMS\CISCO CALLMANAGER APPLIANCE\ALL NODES

Record:

CMATFTP

Recommended action:

Heartbeat counter for TFTP has not been incremented for a while and it indicates that the TFTP server is not up and running. Hence the TFTP server might be down. Check the status of the TFTP service and restart it if necessary.

Message Destinations:

SNMP Trap

Message

^srcnode@: TFTP service is down - no heartbeat. (^srcnode@)

Severity

 Critical

Problem Summary

Event No

0

Message

^srcnode@: TFTP service is down - no heartbeat. (^srcnode@)

Severity

 Critical

Availability

Entity Name

^srcnode@ TFTP Heartbeat

Primary Sub ID

@CMATFTP.CLUSTER@

Secondary Sub ID

TFTP

Monitored Type

THRESHOLD 

Target Entity Type

Configure new entity 

Event Text

^srcnode@: No TFTP Heart Beat, TFTP service may be down. (^srcnode@)

Priority

1

Timeout on stop

1 Day(s)

Dispatch Manager

Message

^srcnode@: TFTP service is down - no heartbeat. (^srcnode@)

Severity

 Critical

Provide feedback on this article