Cisco Bug: CSCuj35600 - Client port has stuck SYNCLOSS alarm when FEC on trunk modified
Oct 04, 2020
- Cisco ONS 15454 Series Multiservice Provisioning Platforms
Known Affected Releases
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
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases