Cisco Bug: CSCut34247 - Non LACP traffic on inactive Bundle member link should not be accepted
May 12, 2017
- Cisco Carrier Routing System
Known Affected Releases
Symptom: traffic come from inactive member link ( link is up, but do not reach active status) is still be accepted by router. For LACP packet it is reasonable to be accepted, however for other packet it should not be accepted and should not be forwarded, if the packet come from that inactive member link. This member link is inactive, which mean this member link don't reach service status yet. Conditions: in some error configuration situation, the peer side of the bundle member link is configured as layer 3 physical interface which has ipv4 address, and the traffic was leaked into this inactive member link from the peer side interface.
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