Skip to content

This Packet Tracer lab explores the configuration of floating static routes in a network to ensure redundancy and maintain connectivity in the event of a link failure. It covers dynamic routing protocol identification, static route configuration, and failover testing.

License

Notifications You must be signed in to change notification settings

ro-drick/Floating-Static-Routes-Configuration

Repository files navigation

Packet Tracer Lab: Floating Static Routes

Lab Overview

This lab explores the use of dynamic routing protocols and floating static routes within an enterprise network. It demonstrates how to configure static routes that act as backups when primary links fail, ensuring network connectivity between key devices like PC1 and SRV1.

Lab Instructions

1. Checking Routing Protocols and Routes

Tasks:

  • Check the routing tables of both R1 and R2.
  • Identify the dynamic routing protocol being used in Enterprise A.
  • Determine which route is selected when PC1 attempts to:
    • Access SRV1.
    • Access the remote server at IP 1.1.1.1 over the Internet.
  • Test connectivity by pinging SRV1 and the remote server (1.1.1.1).

Expected Results:

  • You'll identify the dynamic routing protocol and the correct route for accessing SRV1 and the remote server.
  • Successful pings indicate correct routing.

2. Configuring Floating Static Routes

Tasks:

  • Configure floating static routes on R1 and R2 to allow PC1 to reach SRV1 in case the link between R1 and R2 fails.
  • Verify if the newly configured routes are added to the routing tables of both routers.

Expected Results:

  • The floating static routes should not be visible in the routing table immediately, as they act as backup routes.

3. Simulating Link Failure

Tasks:

  • Shut down the interface G0/2/0 on either R1 or R2.
  • Observe if the floating static routes are now added to the routing tables of both routers.
  • Ping from PC1 to SRV1 to confirm network connectivity.

Expected Results:

  • The floating static routes should enter the routing table after the link failure.
  • PC1 should successfully ping SRV1, indicating that the backup route is functioning correctly.

Configuration Notes

  • The lab demonstrates how floating static routes provide redundancy in the event of a link failure.
  • Proper configuration ensures that the network remains operational even if the primary route fails.

How to Use the Lab

  1. Open the Packet Tracer file (Floating Static Routes Solved.pkt).
  2. Follow the steps outlined above to observe and configure routing protocols.
  3. Experiment by shutting down interfaces and testing network connectivity.
  4. Modify the configurations as needed to understand the behavior of floating static routes.

Conclusion

This lab demonstrated the critical role of floating static routes in ensuring network resiliency. By implementing dynamic routing protocols alongside backup static routes, the network can automatically reroute traffic in the event of a link failure, maintaining connectivity without manual intervention. Through configuring and testing the failover process, you gained hands-on experience with how floating static routes operate and their importance in enterprise network design. Proper redundancy planning, as shown in this lab, is key to maintaining uninterrupted network service, even in the face of disruptions.

Acknowledgements

Special thanks to Jeremy's IT Lab for providing valuable resources and tutorials that greatly contributed to the completion of this exercise. His in-depth explanations and practical demonstrations have been instrumental in enhancing my understanding of Cisco networking concepts and the effective use of Packet Tracer.

For more information and additional resources, visit Jeremy's IT Lab and check out his YouTube for the full course, Jeremy's IT Lab Free CCNA 200-301 | Complete Course

About

This Packet Tracer lab explores the configuration of floating static routes in a network to ensure redundancy and maintain connectivity in the event of a link failure. It covers dynamic routing protocol identification, static route configuration, and failover testing.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published