What could cause a lowCallManagerHeartBeat alert within RTMT

Unanswered Question
Mar 6th, 2008

Guys,


Currently running version CM 4.1.3. Customer reporting numerous network issues - call drops etc. I have taken a look at the topology - Couple Cisco 4507's with a couple of 28xx's. Issues is affecting both internal and external. Can see no obvious network related routing issues.


I have however noted the above alert - cannot find much useful information on really what this indication means and what the affects of this following below threshold - any good document/comments out there?


Regards


Carl

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Zin.Karzazi Thu, 03/06/2008 - 06:01

are you having high CPU utilisation? maybe BARS running? Antivirus doing update? huge CDR

records`?


w422266 Thu, 03/06/2008 - 06:14

Hey - Zin - no BARS running, No Anti Virus, CPU is normal and CDR is well within normal working limits?

w422266 Thu, 03/06/2008 - 06:36

CCM Trace when alert central reports heartbeat failure.


03/06/2008 14:27:59.182 CCM|CMProcMon::star_sdlVerification - Test Timer exceeded minimum timer latency threshold of 1000 milliseconds, Actual latency: 1515 milliseconds|


Zin.Karzazi Thu, 03/06/2008 - 06:39


The error basically means that your Callmanager is not responding to heartbeat requests in a timely manner.

restarting the CCM service maybe helps.


Zin.Karzazi Thu, 03/06/2008 - 06:42

The Cisco CallManager generally checks the timer threads once every second. Cisco CallManager adds 1 second to the current operating system time and stores that value away as “expected time.” Then, Cisco CallManager sleeps for 1 second. After Cisco CallManager awakes, it checks the new operating system time and subtracts the expected time. If the difference between these two times is more than 1 second, this warning statement appears in the Cisco CallManager trace:


CMProcMon::star_sdlVerification - Test Timer exceeded minimum timer latency

threshold of 1000 milliseconds, Actual latency: 1630 millisecondsActual latency in this statement shows that the internal Cisco CallManager SDL timer thread runs slow. Here, the difference between the Cisco CallManager expected time and the actual operating system time is 1.63 seconds.


If this difference exceeds 16 seconds, the Cisco CallManager shuts down and provides the shutdown reason code of 4.


The most likely cause of an SDL timer thread shutdown is a lack of CPU time for Cisco CallManager. Another application, such as VirusScan or STI Backup, has used most of the CPU resources for at least 16 seconds. Perfmon logs are vital to determine the root cause of this type of shutdown.





http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00801df0ed.shtml

Actions

This Discussion