<div>and who has a CM that has not been rebooted in 248 days? ;-)</div>
<div> </div>
<div>Scott<br><br></div>
<div class="gmail_quote">On Fri, Nov 7, 2008 at 9:19 AM, <span dir="ltr"><<a href="mailto:Thorsten.Mayr@barclayscapital.com">Thorsten.Mayr@barclayscapital.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">>From CCO:<br><br>Problem Description:<br>After 248 days of system uptime the Cisco CallManager service and the<br>
Cisco CTIManager service will crash.<br><br>Background:<br>Cisco Unified Communications Manager has an internal system timer that<br>monitors system uptime along with other components. Cisco has found that<br>once this internal timer value reaches 248 days, the internal value is<br>
mis-handled, causing Cisco CallManager and Cisco CTIManager services to<br>crash.<br><br><br>Workaround:<br>It is recommended that customers schedule a reboot of affected nodes<br>before 248 days of system uptime elapses (since the last reboot).<br>
Note: You must reboot the server to restart the timer to 248 days. Cisco<br>CallManager or Cisco CTIManager service restarts alone will not reset<br>the timer.<br>To verify system uptime, perform the following CLI command on each node<br>
in the cluster.<br>show status<br><br><br>Thought other ppl might interested in the above - I have opened a case<br>with HTTS to clarify if the CTI Manager / CCM Service already crashed<br>and the uptime is greater 248 days, whether a restart is still required<br>
or not. Will post outcome back into the group so not everybody has to<br>ask HTTS/TAC/CROS whoever... as soon as BU team has clarified this.<br><br>Pls check the Fiel Notice if your version of CallManager is affected or<br>
not.<br><br><a href="http://www.cisco.com/en/US/ts/fn/631/fn63174.html" target="_blank">http://www.cisco.com/en/US/ts/fn/631/fn63174.html</a><br><br><br>Cheers<br>Thorsten<br>_______________________________________________<br>
<br>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: <a href="http://www.barcap.com/emaildisclaimer" target="_blank">www.barcap.com/emaildisclaimer</a>. 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!<br>
ce at 1 Churchill Place, London, E14 5HP. This email may relate to or be sent from other members of the Barclays Group.<br>_______________________________________________<br>_______________________________________________<br>
cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div><br>