Implementing Secure Solutions with Virtual Private Networks - Cisco Exam 300-730-SVPN: DMVPN Phase 2 to Phase 3 Migration with EIGRP Configuration

Migrating from DMVPN Phase 2 to Phase 3 with EIGRP Configuration

Question

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

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

CE.

DM VPN (Dynamic Multipoint VPN) is a VPN technology that allows multiple sites to connect with each other over the internet securely. DM VPN has different phases, and each phase introduces new features and improvements. DM VPN Phase 2 allows spoke-to-spoke communication and hub-to-spoke communication, while DM VPN Phase 3 introduces support for multicast traffic and spoke-to-spoke communication without going through the hub.

EIGRP (Enhanced Interior Gateway Routing Protocol) is a routing protocol that is commonly used in DM VPN environments. It allows the different sites to exchange routing information and determine the best path for traffic to take. When migrating from DM VPN Phase 2 to Phase 3, there are two changes that need to be made when EIGRP is configured. These changes are:

A. Add NHRP shortcuts on the hub: NHRP (Next Hop Resolution Protocol) is used in DM VPN to map the public IP addresses of the spokes to their private IP addresses. NHRP shortcuts are entries in the NHRP cache that allow the hub to directly communicate with the spokes without having to go through the internet. When migrating from DM VPN Phase 2 to Phase 3, the hub needs to have NHRP shortcuts configured to support spoke-to-spoke communication without going through the hub.

E. Add NHRP redirects on the hub: NHRP redirects are used in DM VPN to update the NHRP caches of the spokes with new information about the location of other spokes. When migrating from DM VPN Phase 2 to Phase 3, the hub needs to have NHRP redirects configured to support spoke-to-spoke communication without going through the hub.

C. Disable EIGRP next-hop-self on the hub: EIGRP next-hop-self is a feature that causes the hub to advertise its own IP address as the next hop for traffic destined for other spokes. When migrating from DM VPN Phase 2 to Phase 3, this feature should be disabled on the hub to allow spoke-to-spoke communication without going through the hub.

D. Enable EIGRP next-hop-self on the hub: This is the opposite of option C and is not required when migrating from DM VPN Phase 2 to Phase 3.

B. Add NHRP redirects on the spoke: This is not required when migrating from DM VPN Phase 2 to Phase 3.