Cisco Bug: CSCup27107 - EIGRP Stub Routers Do Not Receive Updates for Route Withdrawal
May 20, 2020
- Cisco IOS
Known Affected Releases
Symptom: EIGRP Stub routers may fail to receive EIGRP updates to withdraw prefix(es) causing connectivity issues. Conditions: EIGRP routers configured for EIGRP stub functionality may fail to receive EIGRP updates, causing traffic blackholing. Issue has been seen in the following conditions: 1. DMVPN deployment, Spoke router R2 learns a route, upon it changing to an EIGRP stub router, it fails to send an update to Spoke router R1 which is also an EIGRP stub router. 2. EIGRP stub routers R1 and R2 learn of a prefix from R3, R4, R5, and R6. R1 picks it successor route from R3, feasible successor from R2 and R5. R2's successor route is via R1, feasible successor routes are from R6 and R4. R3 and R4 lose the prefix, with the expectation that R1 and R2 reconverge and point to R5 and R6 for the route but this does not occur as R3 does not send an EIGRP update to R1, causing R1 to continue to point downstream to R3 when R3 no longer has the prefix in its RIB.
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