Guest

Preview Tool

Cisco Bug: CSCuq35539 - DMVPN EIGRP Hub suppresses poison update to spoke, stale topology

Last Modified

Aug 14, 2017

Products (84)

  • Cisco IOS
  • Cisco 892W Integrated Services Router
  • Cisco 1905 Serial Integrated Services Router
  • Cisco 888W Integrated Services Router
  • Cisco 819 Hardened Integrated Services Router
  • Cisco 886VA-CUBE Integrated Services Router
  • Cisco C892FSP Integrated Services Router
  • Cisco 881SRSTW Integrated Services Router
  • Cisco 812 CiFi Integrated Services Router
  • Cisco VG204XM Analog Voice Gateway
View all products in Bug Search Tool Login Required

Known Affected Releases

15.4(2)T1

Description (partial)

Symptom:
A stale EIGRP Topology table entry and routing table entry exists on a DMVPN spoke router [Spoke B] after the tunnel interface goes down on another spoke router [Spoke A].  The stale routing entries on Spoke B are advertised into EIGRP by redistribution on Spoke A.  The HUB router correctly removes the entries but does not properly update Spoke B about the EIGRP topology change.

Conditions:
Observed in a DMVPN configuration where the HUB router is configured with EIGRP manual summarization, using a leak-map to allow specific routes to be advertised from the summary.  The affected routes are covered by this EIGRP summary and allowed in the leak-map.
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.