Lab Simulation 45
Guidelines
This is a lab item in which tasks will be performed on virtual devices.
- Refer to the Tasks tab to view the tasks for this lab item.
- Refer to the Topology tab to access the device console(s) and perform the tasks.
- Console access is available for all required devices by clicking the device icon or using the tab(s) above the console window.
- All necessary preconfigurations have been applied.
- Do not change the enable password or hostname for any device.
- Save your configurations to NVRAM before moving to the next item.
- Click Next at the bottom of the screen to submit this lab and move to the next question.
- When Next is clicked, the lab doses and cannot be reopened.
Topology

Tasks
Task 1
- Configure a static default route on R5 per the topology.
- Configure a static default route on R1, preferring the path through R2 towards R6.
- From R5, use traceroute and ping to verify the path towards and reachability of R6.
Task 2
- Configure a floating static default route on R1, preferring the path through R3 towards R6 if the link to R2 should fail.
- Configure the administrative distance for 200.
- Configure a static route on R3 to forward the return traffic towards 10.100.110.0/25.
- After shutting interface e0/0 on R1, use traceroute and ping from R5 to verify path towards and reachability of R6.
Correct Answer:
See the below explanation
Explanation:
Task 1: Static Routes and Verification
1. Configure a static default route on R5:
- Connect to R5 console.
- Enter the following command: R5(config)# ip route 0.0.0.0 0.0.0.0
10.100.110.1
- This sets a default route, sending all traffic from R5 to R1 (assuming 10.100.110.1 is R1's IP on the e0/2 interface).
2. Configure a static default route on R1 preferring the path through R2:
- Connect to R1 console.
- Enter the following command: R1(config)# ip route 0.0.0.0 0.0.0.0 10.122.12.2
- This sets a default route from R1 to R2, which in turn connects to R6.
3. Verification on R5:
- On R5, use pingand tracerouteto verify the path to R6:
R5# ping 10.200.200.6
R5# traceroute 10.200.200.6
- Ensure that the traffic follows the path from R5 to R1, then to R2, and finally to R6.
Task 2: Floating Static Route, Administrative Distance, and Static Route on R3
1. Configure a floating static default route on R1 (via R3) with an AD of 200:
- Connect to R1 console.
- Enter the following command: R1(config)# ip route 0.0.0.0 0.0.0.0 10.34.34.3
200
- This configures a secondary route through R3 with a higher administrative distance (200), making it a backup route if the primary route through R2 fails.
2. Configure a static route on R3 for return traffic:
- Connect to R3 console.
- Enter the following command to route traffic back to 10.100.110.0/25 network via R2:
R3(config)# ip route 10.100.110.0 255.255.255.128 10.33.13.2
3. Verification after interface shutdown:
- On R1, shut down interface e0/0 to simulate a failure.
R1(config)# interface e0/0
R1(config-if)# shutdown
- Go back to R5 and use pingand tracerouteagain to verify that the path to R6 now goes through R3.
R5# ping 10.200.200.6
R5# traceroute 10.200.200.6
Following these configurations should allow R5 to reach R6 via the primary path and, in case of failure on R1's e0/0 interface, switch over to the secondary path through R3.