DMVPN Lab 3 RIPv2 to EIGRP transition

Previous  Next

Download Lab: EVE-NG

Image needed: Cisco IOSv 

Originally DMVPN topology came with RIPv2 as the routing protocol but as new DMVPN neighbors start coming up, routing issues related to this distance vector protocol started to pile up, it has been decided that new protocol is necessary to improve stability of VPN infrastructure, implement the smooth transition to EIGRP without impacting any traffic flow. Lab details included within the .unl file.

Currently, DMVPN topology runs RIPv2 for its routing needs, due to this routing protocol limitations, the owner of this network asks you to help him migrate to the faster protocol of EIGRP. The transition has to be accomplished smoothly that there would be no loss of data during this operation. Begin the process of changing RIP to EIGRP with enabling EIGRP on the HQ routers first and then adjust the administrative distance in the way that new routing protocol will not modify the state of routing information base. With the EIGRP network command advertise all necessary networks on the HQ router. Then repeat similar steps to enable EIGRP on the spoke routers. Before removing RIPv2 from routers' configuration, enable on HQ router, redistribution of routes into EIGRP topology from RIPv2, this will prevent loss of communication between spokes LANs and HQ LAN. Starting with router R4 and work your way to HQ router, disable RIPv2.



Transition to EIGRP:
Step1: Enable EIGPR on the HQ router with AS of 15
Step2: Adjust AD to the 130
Step3: Advertise HQ routes.
Step4: Enable redistribution of the RIP into EIGRP.
Step5: Save configuration on the HQ.
Step6: Configure EIGRP on the spoke routers.
Step7: Save configurations on the spoke routers
Step8: Back on the HQ router, verify that HQ has all EIGRP neighbors.
Step9: Disable RIPv2 on the router R6, then verify that it has all necessary routes to reach HQ LAN and the other spoke LANs via EIGRP.
Step10: Ping from VPC15, hosts in the HQ LAN and other spokes LANs if successful proceed to the next step.
Step11: Remove RIPv2 on the R5, then repeat the same actions as in steps 9 and 10 according to the topology.
Step12: Remove RIPv2 on the R4, then repeat the same actions as in steps 9 and 10 according to the topology.
Step13: Remove RIPv2 on the R3, then repeat the same actions as in steps 9 and 10 according to the topology.
Step14: Remove RIPv2 from the HQ router and disable redistribution of the RIP into EIGRP, this will complete this lab.
Step15: Do not forget to save configurations.

Troubleshooting Task1:

The problem:
According to the transitional requirements, you failed the implementation phase because, the connectivity between hosts in the spoke LANs, is broken.
The implementation policy missing statement regarding the split-horizon issue in the DMVPN topology. After RIPv2 has been removed, HQ router learned about spoke routes via EIGRP but failed to advertised these networks back to spokes routers, this is incorrect and has to be resolved in a timely fashion.
Step1: For documentation purposes, verify that host in network unable to access the hosts in
Step2: Fix the issue.
Step3: Verify again connectivity between the hosts in the spoke LANs.

Troubleshooting Task1:

The problem:
Network technician opens a ticket, it states that the traffic path from VPC15 to VPC9 is wrong and the problem has to be fixed, he derives his opinion from the output of the traceroute he performed recently on the VPC15. According to the output, the traffic goes from network to network via HQ router which is not supposed to happen. In DMVPN topology spoke routers have to establish dynamic tunnels between them and route data directly to each other. Investigate the issue and fix the problem.
Step1: Verify traffic path.
Step2: Implement the solution to this problem.
Step3: Verify if the problem has been fixed.

Command reference:

interface Tunnel0
no ip split-horizon eigrp 15
no ip next-hop-self eigrp 15


Popular Posts