This lab is part of the Bitsize series, where you are set out to troubleshoot the network to find out why OSPF are malfunctioning.
OSPF Stub Areas
You will find all the labs in the Bitsize series on my GitHub, link to repo: CML-bitsize-labs.
Learning Objectives
- Real-world troubleshooting in a small network
- Verify OSPF configurations.
- Ticket documentation
Lab Overview
This is a short one, a quick troubleshooting lab to test your skills to find the errors and practice how to handle it like a real-world ticket.
If you need to brush up on the concepts, I have some study notes that you are more than welcome to review, here is the link, I’m sure it will help you in your journey towards mastering OSPF, OSPF stub areas and virtual links.
Design decisions
This lab is designed to give you hands-on experience with troubleshooting OSPF. The lab topology is designed to be simple and easy to understand, while still providing enough complexity to allow you to practice the concepts of OSPF.
Lab Instructions
- Setup: Clone the lab repository and navigate to the
./ospf/03-Troubleshootingfolder. Review the provided startup configurations for the routers in the lab topology. - Configuration: Import the
03-OSPF_Troubleshooting_Lab.yamlfile into the CML environment. Follow the instructions in the Lab Tasks to troubleshoot the OSPF on all the appropriate routers. Use the CLI to apply the necessary commands and verify your configuration. - Testing: After the troubleshooting, test the network connectivity to ensure that the hosts are able to comunicate with eachother.
Lab Tasks
- Review the Lab Environment: Familiarize yourself with the lab environment and the routers involved.
- Review the ticket: Read the ticket
ticket.txtfound in the folder. - Solve the ticket and document the changes: Verify configuration as you go along and document the changes in the
lab-notebook.txt, you should also include the show commands you use to verify the configuration.