Pushing past the obstacle

dmacomber

I have taken the ICND2 too many times. I am seriously close to burning out on Cisco, but really want to finish and move forward. The frustrating part for me is that I can setup routers and switches, I just test really poorly on it. My failings have been in the troubleshooting areas, I do not currently work in the networking field and have to find time to study/lab. I finally starting working in packet tracer and it really is better than I thought. Long story short... How can I get the troubleshooting down to get past the test. I have been within 7 points of passing.

Thanks

DM

heliuminside

Well, troubleshooting is not something that you learn to do off the book. You need to apply the concepts in the book to a real life lab or packet tracer topology in order to see how they work, and if they don't work as supposed than there is a issue here, something wrong you have typed or merely a device fault. If you understand how something works, and than it is a piece of cake to troubleshoot tickets.

If you've read the book and understood it, you'd have seen that there are tons of methods to use. Cisco recommends using OSI's 7-layer model for different troubleshooting scenarios. It has three approaches like: Bottom-up, Divide-and-conquer, and Top-down. Believe me if you'd apply one of these three approaches into a lab or real life scenario, and you check every single layer of the OSI model on that device if they are working correctly, you shall solve any scenario. But if you think that OSI is dull, and takes to much time for troubleshooting, then you can try to guess where the problem is related from, and go straight to that part and apply skills that you've learned through the book, it may take time for some of the newbies but you'll get used to it after you solve a few.

Also in order to become a better troubleshooting person you need to explore the IOS, there are tons of debug and show commands that you didn't know of, and don't go just as the book says you to do so, try doing something that you are not sure what results you will get, after you see a few failed configurations, you will start to recognize the same appropriate error in the other scenarios, than your mind immediately would go "Ah-ha" here is the portion where you start saying "I know this issue that has occurred me in several situations let me check what is wrong with the debug and show commands that I managed to learn", and also this is the part where troubleshooting gets easier. Without practicing you cannot succeed.