Field Notice: FN - 62560 - Potential Loss of CallManager Services While Upgrading From Any Release of 5.x To Any Other Release of 5.x.

Available Languages

Updated:October 27, 2006
Document ID:FN62560

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.


October 27, 2006

NOTICE:

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.

Products Affected

Products Affected

CallManager - CallManager 5.0

Problem Description

During a Callmanager, Linux to Linux upgrade, the Callmanager may become starved for CPU resources during the initial FTP download of the patch file and restart. This causes any registered phone to unregister and call processing to stop.

Background

During a Linux to Linux upgrade of a cluster, the Cisco CallManager (CCM) Service may experience outages due to the lack of CPU resources. The CPU resources during the upgrade process will consume a very high amount of disk I/O. This will cause the CCM Service and others, to exit CCM and restart Service Manager.

Problem Symptoms

The Cisco CallManager(CCM) Service will stop and any active phone calls will be dropped.

Workaround/Solution

The upgrade from any CallManager release of 5.x to any other release of 5.x.should be applied during a Maintenance Window to ensure the least amount of outages to the users.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCsd84481 (registered customers only)

High Disk I/O Wait Cause CCM Service Outage During L2 Upgrades

Revision History

Revision

Date

Comment

1.0

27-Oct-2006

Initial Public Release

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.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products