Lab Simulation 46
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 host route on R5 for the destination of 10.200.225.6.
- Configure a static default route on R1 preferring the path through R3 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 R2 towards R6 if the link to R3 should fail.
- Configure the administrative distance for 200.
- Configure a static route on R2 to forward the return traffic towards 10.100.115.0/25.
- After shutting interface e0/1 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 Path Verification
Step 1: Configure a host route on R5 for the destination 10.200.225.6: On R5, add a static route for 10.200.225.6 pointing to its next hop, which is R2:
ip route 10.200.225.6 255.255.255.255 10.100.115.2
Step 2: Configure a static default route on R1 preferring the path through R3 towards R6: On R1, add a default route with the next hop as R3:
ip route 0.0.0.0 0.0.0.0 10.133.13.3
Step 3: Verify reachability from R5 to R6 using traceroute and ping: On R5, use the following commands to test connectivity:
traceroute 10.200.225.6
ping 10.200.225.6
The traceroute should show the path through R1 → R3 → R4 → R6. The ping should confirm reachability.
Task 2: Floating Static Route and Return Path Configuration
Step 1: Configure a floating static default route on R1: Add a backup static route on R1 preferring the path through R2 if the link to R3 fails. Assign it an administrative distance of 200 to make it less preferred than the default route through R3:
ip route 0.0.0.0 0.0.0.0 10.122.12.2 200
Step 2: Configure a static route on R2 for the return traffic to 10.100.115.0/25: Add a static route on R2 for the 10.100.115.0/25 network pointing to R5:
ip route 10.100.115.0 255.255.255.128 10.100.115.5
Step 3: Simulate link failure on R1 by shutting down interface e0/1: On R1, shut down the interface connecting to R3:
interface Ethernet0/1
shutdown
Step 4: Verify the new path using traceroute and ping: On R5, use the following commands to verify:
traceroute 10.200.225.6
ping 10.200.225.6
The traceroute should show the path now going through R1 → R2 → R4 → R6. The ping should confirm continued reachability to R6.
Summary of Commands:
On R5:
ip route 10.200.225.6 255.255.255.255 10.100.115.2
traceroute 10.200.225.6
ping 10.200.225.6
On R1:
ip route 0.0.0.0 0.0.0.0 10.133.13.3
ip route 0.0.0.0 0.0.0.0 10.122.12.2 200
interface Ethernet0/1
shutdown
On R2:
ip route 10.100.115.0 255.255.255.128 10.100.115.5