Guest

Preview Tool

Cisco Bug: CSCuj35600 - Client port has stuck SYNCLOSS alarm when FEC on trunk modified

Last Modified

Oct 04, 2020

Products (1)

  • Cisco ONS 15454 Series Multiservice Provisioning Platforms

Known Affected Releases

9.221 9.23

Description (partial)

Symptom:
SYNCLOSS on OTU2-XP ports that will not clear until a hard reseat of the card.

Conditions:
When making a change to the provisioning on Client or Trunk but only placing one or the other into the OOS-DSBLD state, on moving the OOS-DSBLD back to IS the whole ASIC for the client/trunk is reconfigured.  Polling on the hardware not placed in OOS-DSBLD can result in the SYNCLOSS alarm.

Related Community Discussions

Synchronization Loss on Data Interface
Hello, We are in the process of turning up two new sites and are using 15454 MSTP platform with DWDM between sites. The connectivity is a mixture of 10gb FibreChan, 10gb Ethernet and 1gb Ethernet. The problem we are having is that after all of the 10gb FibreChan circuits were turned online, we started to recieve Synchronization Loss on Data Interface errors on multiple of the Fibre Chan interfaces on the OTU2 cards. The TX power on the client port is reporting -40 db which is very odd. We have tried ...
Latest activity: Mar 26, 2014
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.