Cisco Bug: CSCuw29872 - Improper Removal severity change causes transient SYNCLOSS on all lanes
Jul 29, 2018
- Cisco Carrier Routing System
Known Affected Releases
5.2.41.BASE 6.0.0.BASE 6.0.1.BASE
The model here is clear and re-declare of the same alarm, since legacy NMS will not take an update on alarm severity. Now when a client does an explicit clear and redeclare of the precedence alarm, FM logic re-runs the precedence suppression algorithm again, and faults lower that the fault being cleared and re-declared are affected. What we need is an update mechanism, where client will call an update API, and FM will do a clear and re-raise with updated severity. This is enhancement from Fault manager POV. Symptom: transient alarms appears. Conditions: Alarm profile apply/remove on Breakout controllers.
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