Revised March 1, 2007
Feburary 23, 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
|
Products Affected |
|---|
|
CallManager - 5.1(1a) |
Problem Description
The machine type and model string (MTM) handling change is applicable to software only IBM servers that were purchased after IBM rolled out their Xcellator ordering process are impacted, thus the install will fail with CallManager 5.1(1a).
Background
CallManager 5.1(1a) install fails due to a manufacturing change in the machine type and model (MTM) string. CallManager install uses a hardware table with the MTM to determine if a server is supported, and it checks on the first 6 digits of the MTM string.
Manufacturing's new ordering process changes the trailing 2 digits of the MTM string even though the server configuration still looks the same as before. This change causes all IBM servers to not be recognized by CallManager 5.1(1a) and the installation fails.
Problem Symptoms
Due to a manufacturing process change, the MTM string handling was changed, resulting in failure to install Cisco Unified CallManager 5.1(1a).
Workaround/Solution
Option #1:
Recommendation is for customers to upgrade to CallManager 5.1(1b). It is available at Software Download Cisco Unified CallManager 5.1 (registered customers only)
Option #2 :
To manually change MTM strings with the help from IBM field support, follow these steps:
-
Check the Machine Type and Model from label on the Box, or by booting into BIOS setup utility when system comes up by pressing "F1".
-
If the server has a Machine Type and Model (MTM) with following, then contact IBM field support to change the MTM strings to corresponding new value mentioned below:
|
Description |
Current MTM |
Change MTM Back to |
|---|---|---|
|
MCS-7815-I2 |
8485AC1 |
84857AU |
|
MCS-7815-I2 |
8490AC1 |
84907AU |
|
MCS-7825-I2-2800 |
8849AC1 |
8849G2U |
|
MCS-7825-I2-2800 |
8491AC1 |
8491G2U |
|
MCS-7825-I2-3400 |
8849AC1 |
8849K2U |
|
MCS-7825-I2-3400 |
8491AC1 |
8491K2U |
|
MCS-7835-I1 |
8840AC1 |
88403RU |
|
MCS-7845-I1 |
8840AC1 |
88403RU |
|
MCS-7835-I2 |
7979AC1 |
79795AU |
Customers will need to contact IBM field support to manually change the Machine Type and Model (MTM) on the above mentioned servers to work around the issue. Once the IBM field support has changed the MTM strings, the server will be recognized as official and will be supported by CallManager 5.1(1a).
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 |
|---|---|
|
CSCsh50685 (registered customers only) |
5.1.1b Adds new MTM entries for IBM's SW only servers |
Revision History
|
Revision |
Date |
Comment |
|---|---|---|
|
1.1 |
01-MAR-2007 |
Removed manual steps and updated chart in Workaround/Solution section. |
|
1.0 |
23-FEB-2007 |
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.