[cisco-voip] CCM 4.1(3)sr3b test timer exceeded

[Ryan Ratliff]

That is the heartbeat that CM uses to see if it is getting enough cpu  
time.   It should be getting cpu time each second, and that tells you  
that something with at least the same priority as ccm.exe took up so  
much cpu time that our timer didn't get cpu time for 11 seconds.  I  
*think* 16 is the threshold where we force a divide by zero crash.

-Ryan

On Jul 5, 2007, at 5:07 PM, Erick Bergquist wrote:

Anyone know what would cause this and how to fix it?  Have a client
with a single server cluster and occassionally when they are making
changes in CCMAdmin, sometimes a bunch of phones unregister along with
IP media stream service, etc.

This was in the CCM Detailed trace when it happened, before all the
phones started to unregister. Phones unregistered due to reason code 8
and in ccm trace saids keepalive timed out.

07/05/2007 13:05:33.204 CCM|CMProcMon::star_sdlVerification - Test
Timer exceeded minimum timer latency threshold of 1000 milliseconds,
Actual latency: 11016
milliseconds|<CLID::CM01-Cluster><NID::10.10.9.10><CT:: 
0,0,0,0.0><IP::><DEV::>

It is currently on CCM 4.1(3)sr3b and OS 2000.4-2sr16, I am thinking
of putting latest 4.1(3) SR on there.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip