Lab 3: RIPv2 Challenge Lab
)
This lab should be conducted on the Enterprise POD.
Lab Setup:
If you are using EVE-NG, and you have imported the EVE-NG topology from the EVE-NG-Topology folder, ignore the following tickets and use Lab 3-RIPv2 Challenge Lab in the RIPv2 folder in EVE-NG.
To copy and paste the initial configurations, go to the Initial-config folder → RIPv2 folder → Lab-3.
Ticket 1
R1 is configured to filter its Lo41. However, this interface is still reachable from R5.
Restrictions:
Do not configure another access list, prefix list, or route map.
Use only two commands to accomplish this task.
Ticket 2
R7 is configured to filter all even third octet networks (for example, x.x.2.x, x.x.4.x, x.x.6.x) with the mask /24. However, this has affected all routes, and none of them are reachable from R2.
Ticket 3
R4 can’t reach R1’s Lo42 using its Lo0 as the source:
Use a single command to fix this problem.
Ticket 4
R2 is configured to filter its G0/7 interface with the IP address 5.100.212.2/24, but R5 can’t reach R2’s Lo0.
Ticket 5
R4 can’t reach R2’s Lo0 interface.
Restrictions:
Do not configure the neighbor command.
Do not change the DMVPN phase or configure DMVPN in a dynamic manner.
Ticket 6
R3 can’t ping R1’s Lo0.
Ticket 7
R3 is configured to filter all routes received from R5. However, the routes are still there. Do not use another method to fix this problem; correct the existing problem.
Ticket 8
R7 should not have any RIPv2 routes in its routing table. You must configure an outbound filter using a standard numbered ACL and a distribute-list command on the G0/7 interface of R2 to accomplish this task. You are allowed to remove one command.
Ticket 9
Erase the startup configuration and reload the devices before proceeding to the next lab.