Guest

Cisco ONS 15454 Series Multiservice Transport Platforms

Field Notice: FN - 63801 - ONS 15454 MSTP M6/M2: OC-3 OSC on TNCE Cards Show OSC Termination Fail Alarm in Some Cases - Workaround Available

Field Notice: FN - 63801 - ONS 15454 MSTP M6/M2: OC-3 OSC on TNCE Cards Show OSC Termination Fail Alarm in Some Cases - Workaround Available

May 1, 2014


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
01-MAY-2014
Initial Public Release

Products Affected

Products Affected Comments
NCS 2000 - 15454-M-TNCE-K9 
This issue is seen in Releases 9.6.0.5, 9.8.0, 9.8.1, 10.0, and 10.0.1.
ONS 15454 MSTP - 15454-M-TNCE-K9
This issue is seen in Releases 9.6.0.5, 9.8.0, 9.8.1, 10.0, and 10.0.1.

Problem Description

If Optical Service Channel (OSC) is configured as an OC-3 on the controller card in any of the mentioned software releases, the customer might see an Embedded Operations Channel (EOC) alarm (DCC Termination Failure Alarm). This does not impact the OSC when configured as Fast Ethernet (FE) or Gigabit Ethernet (GE).

Background

OSC failure can result in a node that becomes unreachable for remote management. The upgrade process has to be completed carefully in order to avoid truck-roll and avoid a segment that loses connectivity. If a span has two Network Elements (NEs) and any one of the NEs hits this, the other NE on the span will also have this alarm.

Problem Symptoms

Release 9.6.0.5

This impacts the Transport Node Controller Enhanced (TNCE) controller card only. This impacts the OSC configured on the standby TNCE controller. This alarm can occur either in the upgrade process to Release 9.6.0.5, or when a hard reset (removal and insertion, or a new card) is inserted as standby controller.

Releases 9.8.0, 9.8.1, 10.0, and 10.0.1

Transport Node Controller (TNC) and TNCE cannot be mixed in the same shelf where an OC-3 OSC is used. If only TNCs are used, or only TNCEs are used, then this issue does not impact the shelf or node.

Workaround/Solution

In Release 9.6.0.5, a soft reset of a standby TNCE will correct the issue. If an OSC link is on the standby TNCE on both ends, a soft reset of standby on both the ends might need to be completed. 

In Releases 9.8.0, 9.8.1, 10.0, and 10.0.1, the workaround is to not mix TNC and TNCE in the same shelf where an OC-3 OSC is required. 

Cisco plans a fix for this in Release 9.6.0.7, which is to be available on Cisco.com in June 2014.

How To Identify Hardware Levels

This impacts the software/hardware combination as shown in the table in the Products Affected section.

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.