Cisco Bug: CSCtd86572 - DMVPN EIGRP next hop update not sent to spoke
Mar 01, 2018
- Cisco IOS
Known Affected Releases
Symptom: DMVPN EIGRP topology hub does not update spoke with new next hop information for prefix with equal cost paths. Conditions: Dual hub setup where each spoke only peers with one hub and hubs exchange information. Equal cost path next hops are on two spokes off the same hub. Hubs are configured with "no ip next-hop-self eigrp"
Related Community Discussions
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