Cisco Bug: CSCus82231 - Enabling OAM remote loopback Shuts the peer interface down with TEFP
Jan 30, 2017
- Cisco ASR 920 Series Aggregation Services Router
Known Affected Releases
Symptom: Enabling OAM remote loopback Shuts the peer interface down with TEFP Conditions: 1. Enable ethernet OAM remote loopback on the interfaces as shown in the topology 2. Start ethernet OAM remote loopback in the Pegasus 3. Observe that the Pegasus enters to master mode 4. Observe that the striker Peer interface goes to admin down 5. Thus not allowing the possibility of sending the traffic via striker interface for loopback at Pegasus end (Remote end) 6. RFC 4878 say that, ? Remote loopback is a link state where the peer Ethernet entity echoes every received packet (without modifications) back onto the link. Remote loopback is intrusive in that the other end of the link is not forwarding traffic from higher layers out over the link. This document defines objects controlling loopback operation and reading the status of the loopback state?
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