[cisco-voip] FN - 63174 - Cisco Unified Communicatons Manager - ccm and cti crashes after 248 days on timer expirery....

[Lelio Fulgenzi]

windows versions, yeah, i can see wanting to reboot those, but this is 5.x and 6.x . 

i'm hoping we can go a year without rebooting our telephone servers when it's on linux. 


--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Scott Voll" <svoll.voip at gmail.com> 
To: cisco-voip at puck.nether.net 
Sent: Friday, November 7, 2008 4:31:33 PM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] FN - 63174 - Cisco Unified Communicatons Manager - ccm and cti crashes after 248 days on timer expirery.... 


and who has a CM that has not been rebooted in 248 days? ;-) 

Scott 


On Fri, Nov 7, 2008 at 9:19 AM, < Thorsten.Mayr at barclayscapital.com > wrote: 


>From CCO: 

Problem Description: 
After 248 days of system uptime the Cisco CallManager service and the 
Cisco CTIManager service will crash. 

Background: 
Cisco Unified Communications Manager has an internal system timer that 
monitors system uptime along with other components. Cisco has found that 
once this internal timer value reaches 248 days, the internal value is 
mis-handled, causing Cisco CallManager and Cisco CTIManager services to 
crash. 


Workaround: 
It is recommended that customers schedule a reboot of affected nodes 
before 248 days of system uptime elapses (since the last reboot). 
Note: You must reboot the server to restart the timer to 248 days. Cisco 
CallManager or Cisco CTIManager service restarts alone will not reset 
the timer. 
To verify system uptime, perform the following CLI command on each node 
in the cluster. 
show status 


Thought other ppl might interested in the above - I have opened a case 
with HTTS to clarify if the CTI Manager / CCM Service already crashed 
and the uptime is greater 248 days, whether a restart is still required 
or not. Will post outcome back into the group so not everybody has to 
ask HTTS/TAC/CROS whoever... as soon as BU team has clarified this. 

Pls check the Fiel Notice if your version of CallManager is affected or 
not. 

http://www.cisco.com/en/US/ts/fn/631/fn63174.html 


Cheers 
Thorsten 
_______________________________________________ 

This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays. Any views or opinions presented are solely those of the author and do not necessarily represent those of Barclays. This e-mail is subject to terms available at the following link: www.barcap.com/emaildisclaimer . By messaging with Barclays you consent to the foregoing. Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered offi!
  
ce at 1 Churchill Place, London, E14 5HP. This email may relate to or be sent from other members of the Barclays Group. 
_______________________________________________ 
_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 


_______________________________________________ cisco-voip mailing list cisco-voip at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081107/372fff9b/attachment.html>