300-730 · Question #161
Which feature must be disabled in EIGRP for DMVPN spokes to learn routes to other DMVPN spokes?
The correct answer is A. split-horizon. EIGRP split-horizon must be disabled on the DMVPN hub's tunnel interface so the hub can re-advertise routes learned from one spoke out the same interface to all other spokes.
Question
Options
- Asplit-horizon
- Bbandwidth percent
- Cnext-hop-self
- Dhold time
How the community answered
(46 responses)- A89% (41)
- B7% (3)
- C2% (1)
- D2% (1)
Why each option
EIGRP split-horizon must be disabled on the DMVPN hub's tunnel interface so the hub can re-advertise routes learned from one spoke out the same interface to all other spokes.
By default, EIGRP split-horizon prevents a router from advertising a route back out the same interface it was received on, which on a multipoint GRE hub interface means routes learned from one spoke are never forwarded to other spokes connected on that same interface. Disabling split-horizon on the hub's tunnel interface allows the hub to redistribute spoke prefixes to all DMVPN participants, enabling full spoke-to-spoke route reachability.
The bandwidth percent command controls the maximum share of interface bandwidth EIGRP may consume for routing traffic and has no bearing on which routes are advertised between DMVPN nodes.
Next-hop-self is a BGP feature that forces a router to set itself as the next hop for advertised prefixes; it is not an EIGRP parameter and does not affect DMVPN spoke-to-spoke route propagation.
Hold time governs how long EIGRP waits before declaring a neighbor unreachable after missing hellos and does not influence the advertisement or suppression of routes across DMVPN spoke interfaces.
Concept tested: EIGRP split-horizon disabled for DMVPN spoke-to-spoke routing
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_eigrp/configuration/xe-16/ire-xe-16-book/ire-dmvpn.html
Topics
Community Discussion
No community discussion yet for this question.