Guest

Cisco Line Cards

Field Notice: FN - 62406 - GSR OC48/SRP-SR-SC-B Linecards May Experience Memory Issue - Replace Affected Hardware


Revised August 8, 2007
June 19, 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

Product Affected Top Assembly Comments
Part Number Revision
OC48/SRP-SR-SC-B
800-05619-08
D0
Also any cards prior to -08 suffix (See the How to Identify Hardware Levels section)

Serial Numbers

Sequential #
From SAD06240000 to SAD0630FFFF

Problem Description

Upgrading to 12.0.28S5 or higher may result in the line card OC48/SRP-SR-SC-B failing during upgrade. The failure symptoms outlined below have been experienced due to a possible memory pin issue.

Background

The black connector used on the OC48/SRP-SR-SC-B line card at J16 has a slightly larger footprint than the alternatively used white connector (see pictures below). Due to the component spacing, the test hardware which was used during the production board test caused pressure to a neighbor memory component at U75.

A number of cards within the production range of SAD0624 and SAD0630, which used the black connector, have been found with solder joint damage on U75. If the pins are damaged, the later IOS releases which start to use these pins during upgrade have been seen to experience the symptoms outlined below.

Problem Symptoms

Five symptoms have been seen due to the issues on the memory component:

1. RAM successfully downloads, and then the card fails to upgrade the ROM Agent and hangs.
2. RAM Agent download fails, and then the ROM Agent hangs.
3. RAM Agent download fails, and then the card runs from ROM.
4. RAM successfully downloads, and then the card resets back into ROM, then loops attempting download.
5. RAM successfully downloads, and then hangs.

Example failure message:
%MBUS-3-EEPROM: Failed read EEPROM location 1 in slot 7 detecting bad h/w at startup

Workaround/Solution

Although an upgrade program had previously been provided to replace potentially affected but otherwise working product, the upgrade program is now over and Cisco will only replace product which has actually failed. The standard RMA process should be used to replace failed product.

Cisco recommends a fix-on-fail strategy for this problem.

Service Logistics has known-good inventory at this time. The standard RMA process and delivery times are in effect.

How To Identify Hardware Levels

If BOTH of the following are true:

a) In the show diag output, the last 2 digits of the top assembly number 800-05619-xx is below 10, for example, 800-05619-08. Top assembly number 800-05619-09 was not used/shipped.

AND

b) The connector at J16 is black, as shown in the first picture below. The second picture shows the alternate white connector, which is not vulnerable to this failure mechanism.


Revision History

Revision Date Comment
1.1 08-AUG-2007 Removed Upgrade Form, reworded Workaround/Solution section and title to reflect the change
1.0 19-JUN-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.