Just a quick wrap-up on this one...
Two defects created for this problem are CSCup27726 and CSCup27133.
- Dan
From: Wes Sisk (wsisk) [mailto:ws...@cisco.com]
Sent: Wednesday, May 21, 2014 2:50 PM
To: Daniel Pagan
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Heartbeat Failure SNRD
...@cisco.com]
*Sent:* Wednesday, May 21, 2014 2:50 PM
*To:* Daniel Pagan
*Cc:* cisco-voip@puck.nether.net
*Subject:* Re: [cisco-voip] Heartbeat Failure SNRD
Hi Daniel,
Great find!
For the document:
http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified
Folks:
CUCM ES 8.6.2.24122-1 appears to be creating an issue where CallManager
heartbeat fails to increment upon startup and the condition that must be met is
very specific. On a problematic node, SDL traces show the following error
exactly one hour after the start of the CCM service:
To be more specific, SDL traces show MMManInit sending a DeviceInitStart to
DeviceManager, and then, immediately after, DeviceManager creating SNRD. All
process creation and startup signals die at this point. This is observable and
reproducible in two different environments running the same ES
Hi Daniel,
Great find!
For the document:
http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/46806-cm-crashes-and-shutdowns.html
The initialization process and timers have changed *significantly* since 4.x.
Some examples include:
