Cisco Bug: CSCut13111 - Trace back Observed on REP as %SM-4-BADEVENT: Event 'pre_empt_ind'
Jan 29, 2017
- Cisco ASR 920 Series Aggregation Services Router
Known Affected Releases
Symptom: Trace back observed on REP as follows, Feb 23 17:49:11.827 IST: %SM-4-BADEVENT: Event 'pre_empt_ind' is invalid for the current state 'FAILED_PORT': rep_pr Po1 - pr -Traceback= 1#313d03e0b07d0e22698c10dcfdd71206 :10000000+E9DFF4 :10000000+E9E3A4 :10000000+36B60F8 :10000000+37D231C :10000000+37D80E0 :10000000+37D8214 :10000000+48F7634 :10000000+48F79B8 :10000000+31F7234 :10000000+31F4970 :10000000+31F6FDC :10000000+4940784 :10000000+31ED364 :10000000+31EE8E8 :10000000+31EEA54 iosd_pegasus_unix:5955000+1C170 Conditions: 1. Load the attached configuration file which has scaled configurations. (medium scaled config) 2. Observe that the protocols are in settled state 3. Pump the traffic in G8032,REP rings, IP SLA & some of the L2 VPNs (X-connects) 4. Mac scaling is around 1500 entries 5. Observe the protocols are in settled state. 6. Perform flapping on all the interfaces using ?range? command. 7. Perform un flapping on all the interfaces using ?range command? 8. Observe the trace back as sited above
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