ALL >> Computer-Programming >> View Article
Ccie Troubleshooting
There are two types of troubleshooting that you'll run into on the ccie lab:
1. The Proctor is Evil Troubleshooting
2. The Self-Induced Troubleshooting
The latter type is by far the more time-consuming but also the most important. Basically you messed something up, therefore you have to fix it! (At least if
you want the points) The reason it is the most time-consuming is because it could be ANY silly mistake or combination of silly mistakes along the way, and
there is no predicting what kinds of things can be done to mess with your own head!
The most important rule with this kind of troubleshooting is time management. Set a time limit of 15 minutes. If you can't figure something out in 15
minutes (no, I don't care how close you think you are!) go do something else. Whether this involves a bathroom break, a soda/snack break, standing on
your head on the high-quality lab chairs or simply moving on to another service or security task of your lab makes no difference. The idea is to
separate your brain from staring at the same ...
... thing over and over.
The longer you stare at ccie routing and switching lab training, the
more you see what you want and not what's really there. Most self-induced errors are really small, and fairly inane. You know. Those DUH! moments once
we figure it out. But time management is the consequence we suffer due to silly mistakes. Avoid it!
Anyway on to the more exciting things. The unpredictable nature of the Proctor is Evil Troubleshooting. Having started my training career specializing
in the old CIT (Cisco Internetwork Troubleshooting) class, I can greatly appreciate some of the humorous things that MAY get thrown into lab exams. The
question becomes, if I don't know what they are and there are many different things that could go wrong What the heck do I do about it?!?!
We've had many different posts and blogs about the things you should be doing in your lab exam. You know The stuff about reading your exam, re-drawing
your diagrams, L2 diagramming, etc. Been there, done that. But then there's troubleshooting. Some things are easy to spot. Others are not! Some things may
obvious, others are just plain obnoxious.
The one thing to remember is that during the lab exam, you are there for your proctor's entertainment. As long as this goes through your head, you'll
understand why some things are done. It's all in good fun! And once you pass the ccie sp lab boot camp, it's much easier to laugh about it all!
Add Comment
Computer Programming Articles
1. How To Use Linkedin Market Your Business?Author: brainbell10
2. 5 Reasons To Choose Business Central
Author: Modern businesses need a connected ERP solution th
3. How To Create A Wordpress Lms Website For Your Employees?
Author: brainbell10
4. Why Every Business Should Conduct Security Awareness Assessments Regularly
Author: Sam Vohra
5. Why Invest In Professional E-commerce Website Development? | Complete Guide For Growing Businesses
Author: Rudram Technology Solutions
6. How To Use Motion Design To Make App Experience Interesting?
Author: brainbell10
7. How To Prototype A Mobile App?
Author: brainbell10
8. Sql Server Tutorial – Learn Database Management With Step-by-step Examples
Author: Tech Point
9. Sql Tutorial For Beginners: Learn Database Management And Sql Queries Step By Step
Author: Tech Point
10. Dynamics 365 Data Migration Best Practices: A Guide
Author: brainbell10
11. How Does The Fintech And Banking Sector Use Apis?
Author: brainbell10
12. Dynamics 365 Case Management Features
Author: brainbell10
13. Everything You Need To Know About Mhealth Apps
Author: brainbell10
14. E-scooter Mobile App Development Cost & Features
Author: brainbell10
15. Rockhard 500
Author: Mukesh Mehta






