Cisco Unified Communications Manager (CallManager)

Revised February 27, 2007

February 21, 2007

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

Problem Description

If a customer receives a MCS-7835-H2 or MCS-7845-H2 and attempts to upgrade to CallManager 5.1(1a), the upgrade will result in an error state and the server will not boot up.

Background

MCS-7835-H2 and MCS-7845-H2 require new BIOS and will not be backward compatible with the older BIOS that is bundled with CallManager 5.1(1a).

Problem Symptoms

During the upgrade process to CallManager 5.1(1a), customers using a MCS-7835-H2 or MCS-7845-H2 server will experience the system being put in an error state. As a result, the system will not boot up.

Workaround/Solution

Customers should upgrade to CallManager 5.1(1b). It is available at the Cisco Unified CallManager 5.1 Software Downloads (registered customers only) page.

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.

Revision History

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:

• Open a service request on Cisco.com
• By email
• By telephone

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.