November 6, 2008
THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.
Revision Date Comment 1.0 06-NOV-2008 Initial Public Release
Products Affected Comments Cisco Unified Communications Manager (CallManager) - 5.0.(X) All releases of 5.0(X) Cisco Unified Communications Manager (CallManager) - 5.1.(X) All releases of 5.1(X) Cisco Unified Communications Manager (CallManager) - 6.0.(X) All releases of 6.0(X) Cisco Unified Communications Manager (CallManager) - 6.1.(X) All releases of 6.1(X)
After 248 days of system uptime the Cisco CallManager service and the Cisco CTIManager service will crash.
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.
If the system reaches 248 consecutive days of uptime, the CCM and CTIManager system services will crash, resulting in a loss of call services and JTAPI services.
Directly before the event a message
Avoided negative deltaTimewill print in the CUCM SDL traces. There is no indication of this message in the RTMT or event logs.
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.
The Cisco Unified Communications Operating System Guide provides information about using the Cisco Unified Communications the command line interface (CLI) to perform many common system- and network-related tasks.
This issue is addressed in the following Cisco Unified Communications Manager versions and beyond:
-5.1(3d) which numerically is 220.127.116.1100-3
-6.1(2)SU1a which numerically is 18.104.22.1682-1
Customers running Cisco Unified Communications Manager 5.0.X or 5.1.X must upgrade to Cisco Unified Communications Manager 5.1(3d). Cisco Unified Communications Manager 5.1(3d) can be found at the following location:
Customers running Cisco Unified Communications Manager 6.0(X) or 6.1(1) must install Cisco Unified Communications Manager 6.1(2), then proceed to install Cisco Unified Communications Manager 6.1(2)SU1a.
Cisco Unified Communications Manager 6.1(2) can be found at the following location:
Customers running Cisco Unified Communications Manager 6.1(2) must install Cisco Unified Communications Manager 6.1(2)SU1a. Cisco Unified Communications Manager 6.1(2)SU1a can be found at the following location:
Note: Prior to installing 6.1(2)SU1a, all nodes in the cluster must be on 6.1(2).
To follow the bug ID link below and see detailed bug information, you must be a registered customer and you must be logged in.
DDTS Description CSCso96280 (registered customers only) Cisco CallManger and Cisco CTIManager services crash
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
Receive Email Notification For New Field Notices
Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.