nerdexam
Cisco

300-730 · Question #23

Which two changes must be made in order to migrate from DMVPN Phase 2 to Phase 3 when EIGRP is configured? (Choose two.)

The correct answer is D. Enable EIGRP next-hop-self on the hub. Migrating from DMVPN Phase 2 to Phase 3 with EIGRP requires enabling next-hop-self on the hub, reversing the Phase 2 requirement, because Phase 3 relies on NHRP redirect and shortcut mechanisms rather than routing next-hop preservation.

Site-to-site VPNs on Routers and Firewalls

Question

Which two changes must be made in order to migrate from DMVPN Phase 2 to Phase 3 when EIGRP is configured? (Choose two.)

Options

  • AAdd NHRP shortcuts on the hub.
  • BAdd NHRP redirects on the spoke.
  • CDisable EIGRP next-hop-self on the hub.
  • DEnable EIGRP next-hop-self on the hub.
  • EAdd NHRP redirects on the hub.

How the community answered

(30 responses)
  • A
    3% (1)
  • B
    3% (1)
  • C
    7% (2)
  • D
    73% (22)
  • E
    13% (4)

Why each option

Migrating from DMVPN Phase 2 to Phase 3 with EIGRP requires enabling next-hop-self on the hub, reversing the Phase 2 requirement, because Phase 3 relies on NHRP redirect and shortcut mechanisms rather than routing next-hop preservation.

AAdd NHRP shortcuts on the hub.

NHRP shortcuts ('ip nhrp shortcut') are configured on the spokes in Phase 3, not on the hub, so adding them to the hub has no effect.

BAdd NHRP redirects on the spoke.

NHRP redirects ('ip nhrp redirect') are configured on the hub in Phase 3, not on the spoke, making this placement incorrect.

CDisable EIGRP next-hop-self on the hub.

Disabling EIGRP next-hop-self is the Phase 2 requirement - it is what must be undone (reversed to enabled) when migrating to Phase 3, not a new step.

DEnable EIGRP next-hop-self on the hub.Correct

In DMVPN Phase 2, the hub must disable EIGRP next-hop-self ('no ip next-hop-self eigrp') so that spokes receive routing updates that point directly to the originating spoke for spoke-to-spoke traffic. Phase 3 removes this dependency by using NHRP redirects on the hub and NHRP shortcuts on spokes to dynamically build direct paths, so the hub must re-enable next-hop-self ('ip next-hop-self eigrp') to advertise itself as the routing next-hop while NHRP handles dynamic shortcut resolution.

EAdd NHRP redirects on the hub.

Adding NHRP redirects on the hub is a valid Phase 3 configuration step, but it is an NHRP-layer change rather than the EIGRP-specific routing change that the question focuses on when EIGRP is configured.

Concept tested: DMVPN Phase 2 to Phase 3 EIGRP next-hop-self migration

Source: https://www.cisco.com/c/en/us/support/docs/security-vpn/dynamic-multipoint-vpn-dmvpn/211702-Configure-DMVPN-Phase-3-with-EIGRP.html

Topics

#DMVPN Phase 3#NHRP redirects#EIGRP next-hop-self#DMVPN migration

Community Discussion

No community discussion yet for this question.

Full 300-730 Practice