Field Notice: FN74286 - Cisco NCS2006 Node Controller Shelf Unreachable Through EMS Port with Specific NCS2006-ECU-S Batches and Dual TNCS2/TNCS2O Cards - Replace on Failure

Available Languages

Updated:July 15, 2025
Document ID:FN74286

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Medium
Impact Rating:
Medium
First Published:
2025-Jul-15
Last Published:
2025-Jul-15
Revision:
1.0
Cisco Bug IDs:

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


Affected Product Name Description Comments
NCS2006-ECU NCS 2006 External Connections Unit  
NCS2006-ECU-S= NCS 2006 External Connections Unit - w/2x USB 3.0 Ports  
NCS2015-ECU NCS 2015 External Connections Unit  




Defect Information


Defect IDHeadline
CSCwo63326TNCS2/TNCS2O: Node becomes unmanaged on DCN network with dual controller card with a specific batch of ECU Units

Problem Description


A limited number of Cisco Network Convergence System (NCS) 2006/2015 Node Controllers may become unreachable on the network through the element management system (EMS) port when installed with a specific batch of NCS2006-ECU-S, NCS2006-ECU, and NCS2015-ECU external connections units in combination with dual Cisco NCS2000 Series Transport Node Controller cards TNCS2/TNCS2-O.

This issue may occur in the following scenarios:

  • Bootup of an affected Cisco node controller chassis with dual TNCS2/TNCS2O cards.
  • Upgrade from legacy controller cards to TNCS2/TNCS2O controllers cards with the affected external connections units (NCS2006-ECU-S, NCS2006-ECU, or NCS2015-ECU).
  • Simultaneous or rolling reboot (cold or warm) of both TNCS2/TNCS2O controller cards in an existing node.
  • Online insertion and removal (OIR) of affected NCS2006-ECU-S, NCS2006-ECU, and NCS2015-ECU units..
  • OIR of the STANDBY TNCS2/TNCS2O unit.

Background


Cisco has determined that the issue described in this field notice originates with an internal switch component present in the NCS2006-ECU-S/NCS2006-ECU and NCS2015-ECU units. This component, which was sourced from a specific vendor, triggers signal interference between active and standby TNCS2/TNCS2O controller cards, impacting the functionality of the EMS port with a dual controller card node. This issue is limited to a small batch of NCS2006-ECU-S/NCS2006-ECU and NCS2015-ECU units.

 


Problem Symptom


The following symptoms and conditions have been observed on Cisco NCS2006-ECU-S, NCS2006-ECU, and NCS2015-ECU units that are affected by this issue:

  • The EMS port of the node ceases to respond to ping packets and fails to process other network traffic, making the node unreachable on the Data Communication Network (DCN) through the EMS port.
  • The issue occurs only with specific batches of NCS2006-ECU-S/NCS2006-ECU and NCS2015-ECU units in combination with dual TNCS2/TNCS2O controller cards.

The issue does not occur when the shelf runs on a single TNCS2/TNCS2O controller card with the same ECU units.


Workaround/Solution


Cisco recommends replacing the affected NCS2006-ECU-S/NCS2006-ECU and NCS2015-ECU cards upon failure. To determine if a serial number is affected, see the Serial Number Validation section of this field notice.


How to Identify Affected Products


To determine if a serial number is affected, see the Serial Number Validation section of this field notice.


Serial Number Validation


Cisco provides the Serial Number Validation Tool to verify whether a device is impacted by this issue. To check the device, enter the serial number in the Serial Number Validation Tool.

Important: For security reasons, you must click the Serial Number Validation Tool link that is provided in this section. Do not copy and paste the link into a browser. Use of the Serial Number Validation Tool URL external to this field notice will fail.

Revision History


VersionDescriptionSectionDate
1.0Initial Release—2025-JUL-15

For More Information

For further assistance or for more information about this field notice, contact the Cisco Technical Assistance Center (TAC) using one of the following methods:

Receive Email Notification About New Field Notices

To receive email updates about Field Notices (reliability and safety issues), Security Advisories (network security issues), and end-of-life announcements for specific Cisco products, set up a profile in My Notifications.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products