Guest

Cisco ONS 15454 Series Multiservice Transport Platforms

Field Notice: FN - 63602 - ONS 15454 MSTP TNC/TSC/TNCE/TSCE Cards with Release 9.6.0 Software Shipped Prior to December 31, 2012 Experience BKUPMEMP Alarm Declaration

Field Notice: FN - 63602 - ONS 15454 MSTP TNC/TSC/TNCE/TSCE Cards with Release 9.6.0 Software Shipped Prior to December 31, 2012 Experience BKUPMEMP Alarm Declaration

March 14, 2013


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.

Revision History

Revision Date Comment
1.0
14-MAR-2013
Initial Public Release

Products Affected

Products Affected Comments
15454-M-TNC-K9
Cards with Release 9.6.0 software shipped prior to December 31, 2012
15454-M-TNC-K9=
Cards with Release 9.6.0 software shipped prior to December 31, 2012
15454-M-TSC-K9
Cards with Release 9.6.0 software shipped prior to December 31, 2012
15454-M-TSC-K9=
Cards with Release 9.6.0 software shipped prior to December 31, 2012
               
15454-M-TNCE-K9
Cards with Release 9.6.0 software shipped prior to December 31, 2012
15454-M-TNCE-K9=
Cards with Release 9.6.0 software shipped prior to December 31, 2012
15454-M-TSCE-K9
Cards with Release 9.6.0 software shipped prior to December 31, 2012
15454-M-TSCE-K9=
Cards with Release 9.6.0 software shipped prior to December 31, 2012

Problem Description

Units with Release 9.6.0 software shipped prior to December 31, 2012 receive a a BACKUPMEMP alarm within 2 to 3 days after a reset. A genuine memory corruption also results in BACKUPMEMP alarm. This particular issue does not impact service, but the workaround in this document should be implemented to correct the situation.

Background

TNC/TSC/TNCE/TSCE cards with Release 9.6.0 software shipped prior to December 31, 2012 contain a file with an additional empty line (CR/LF). This leads to a CRC audit process failure for the file when the regular CRC audit runs on the controller card. This failure raises the BACKUPMEMP alarm on the controller card. Since the audit process runs periodically, this alarm is seen within 2 to 3 days and not instantaneously.

Problem Symptoms

The BKUPMEMP alarm is raised on certain TNC/TSC/TNCE/TSCE cards. The impacted cards are captured in the "How To Identify Hardware Levels" section.

Workaround/Solution

In order to resolve the issue, load the Release 9.6.0 or later software from CCO to both partitions of the impacted controller cards. For a node which has mastershelf or subtended shelf with impacted controllers, the steps to resolve this issue are as follows:

Note: If you use ETSI (SDH) mode with a mastershelf controller of 15454-M-TNCE-K9, 15454-M-TNCE-K9=, 15454-M-TSCE-K9, or 15454-M-TSCE-K9=, then use either TL1 or use CTC of a future software release (9.6.0.3 or later) for the software download.

  1. If this is a provisioned node, back up the database.
  2. Download the software. Each controller has two software partitions, Active and Protect (for example, P1 and P2). The software is downloaded to the Protect partition (P2) of the Active and Standby Controller of mastershelf and subtended shelves.
  3. Perform an Activate to make the new load just downloaded the working load. P2 is now the Active Partition.
  4. Download the software again to replace the load in the current Protect partition (P1). The correct software is now in both partitions, P1 and P2, in the controller.
  5. If USB flash memory is present in M2/M6, perform an Activate to copy the new software to flash memory.

How To Identify Hardware Levels

TNC/TSC/TNCE/TSCE cards listed in the "Products Affected" section that shipped with Release 9.6.0 software prior to December 31, 2012 experience BKUPMEMP alarm declaration.

Customers should check their TNC/TSC/TNCE/TSCE card serial number against the serial number validation tool provided below. The serial number validation tool identifies affected hardware. Customers who identify their hardware as affected should follow the workaround procedure described in the "Workaround/Solution" section to avoid this issue.

Serial Number Validation Tool

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

Cisco Notification Service—Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.