So this may be more of a troubleshooting tip in general, but it is something that I was taught long ago, early in my career that I found myself using a lot on the TSHOOT Exam. Now from the Demo Exam on Cisco’s site, you have an idea what the exam is like. A certain device might not be able to communicate with a web server or something like that. It if your job to find the solution to the problem. My big tip to save some time is to try to focus on where the problem really lies as quickly as possible. I do this with a simple ping. Establish what you can ping and find out where the breakdown is. Most of the time, this will lead you right to the problem router or switch.

For Example, look at the following topology:


If it were me troubleshooting a problem between the workstation and the server, I would see if the workstation could ping Router0, then 1-2-3 and so on. You can even try to do the ping from the other side and determine if the problem is a link between two routers or the config on a single router, like a routing issue for instance. The overall goal is to find the problem device(s) as quick as possible, so you can actually start combing through the config where the problem actually is instead of a device that is actually configured correctly.

That tip was a favorite of mine for a long time and I hope it can help someone else.


Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.