A network engineer is configuring a DMVPN Phase 3 deployment with EIGRP as the routing protocol. The hub router has multiple spoke routers behind a single physical interface. The engineer notices that spoke-to-spoke traffic is being forwarded through the hub instead of directly. The spoke routers have the correct NHRP and mGRE configuration. What is the most likely cause of this issue?
Trap 1: The hub router is configured with 'no ip next-hop-self eigrp' under…
Incorrect because disabling next-hop-self would actually help spokes learn the real next hop of remote spokes. The issue is that next-hop-self is still enabled, causing spokes to see the hub as the next hop.
Trap 2: The spoke routers have 'ip nhrp shortcut' configured but the hub…
Incorrect. NHRP redirect is used on the hub to inform spokes that a better path exists. Without it, spokes may still forward through the hub, but the primary cause here is the next-hop-self behavior in EIGRP.
Trap 3: The spoke routers are using static NHRP mappings to the hub only,…
Incorrect. Dynamic NHRP registration is needed for spokes to learn each other, but the scenario describes correct NHRP and mGRE configuration. The routing protocol's next-hop behavior is the key issue.
- A
The hub router is configured with 'no ip next-hop-self eigrp' under the tunnel interface.
Why wrong: Incorrect because disabling next-hop-self would actually help spokes learn the real next hop of remote spokes. The issue is that next-hop-self is still enabled, causing spokes to see the hub as the next hop.
- B
The hub router is configured with 'ip next-hop-self eigrp' under the tunnel interface.
Correct. With next-hop-self enabled, the hub advertises routes with its own IP as the next hop, preventing spokes from learning the remote spoke's tunnel IP and thus no direct tunnel is built.
- C
The spoke routers have 'ip nhrp shortcut' configured but the hub does not have 'ip nhrp redirect'.
Why wrong: Incorrect. NHRP redirect is used on the hub to inform spokes that a better path exists. Without it, spokes may still forward through the hub, but the primary cause here is the next-hop-self behavior in EIGRP.
- D
The spoke routers are using static NHRP mappings to the hub only, without dynamic NHRP registration.
Why wrong: Incorrect. Dynamic NHRP registration is needed for spokes to learn each other, but the scenario describes correct NHRP and mGRE configuration. The routing protocol's next-hop behavior is the key issue.