Home > Articles

Warmup for the CCIE Troubleshooting Lab 1

  • Print
  • + Share This
  • 💬 Discuss
This chapter is from the book
This chapter details the equipment requirements and pre-lab tasks to help you prepare for the troubleshooting portion of the CCIE Routing and Switching exam.

The CCIE exam commences with 2 hours of troubleshooting “tickets” followed by 5.5 hours of configuration and a final 30 minutes of additional diagnostic questions. This troubleshooting lab has been timed to last for 2 hours, with a total of 30 points, and to be representative of the format and difficulty of the tasks you are likely to encounter on your CCIE lab exam.

Ideally, you should work on this exercise for 2 hours and score yourself at that point. You may, of course, continue until you believe that you have met all the objectives, but you will need to increase your speed as you near your lab exam.

You will now be guided through the equipment requirements and pre-lab tasks in preparation for taking this troubleshooting lab.

If you do not own the seven routers and three switches used to create this troubleshooting lab, consider using the equipment available and additional lab exercises and training facilities available within the CCIE R&S 360 program. You can find detailed information about the Cisco 360 Learning Program and CCIE R&S exam at the following websites, respectively:

Equipment List

You need the following hardware and software components to begin this troubleshooting lab.

  • Seven routers loaded with Cisco IOS Software Release 15.3T Advanced Enterprise image and the minimum interface configuration as documented in Table 1-1

    Table 1-1 Hardware Required per Router

    Router

    Model

    Ethernet I/F

    R1

    3925

    2

    R2

    3925

    1

    R3

    3925

    1

    R4

    3925

    2

    R5

    3925

    2

    R6

    3925

    2

    R7

    3925

    2

  • Three 3560X switches with IOS 15.0S IP Services
  • + Share This
  • 🔖 Save To Your Account

Discussions

comments powered by Disqus