ALL >> Computers >> View Article
Two Types Of Troubleshooting
There are two types of troubleshooting that you'll run into on the
href="http://www.cathayschool.com">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 ccie routing and switching 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 something, 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 r&s lab training, it's much easier to laugh
about it all!
Add Comment
Computers Articles
1. Why To Choose Java Outsourcing Development For Your Project?Author: goodcoders
2. Why Use Expressjs Over Nodejs For Server-side Development?
Author: goodcoders
3. Why Use Kotlin Over Java For Android Development?
Author: goodcoders
4. 10 Ways To Get The Most Out Of Las Vegas Phone Repair
Author: Fones Gone Wild
5. Why The Discovery Phase Is Important To Your Software Development Project?
Author: goodcoders
6. Why Should Your Business Invest In An End-to-end Custom Software Solution?
Author: goodcoders
7. Why Small Businesses Are Developing Mobile Apps?
Author: goodcoders
8. What Should You Do If Your Laptop Stops Functioning?
Author: Joshua Kirby
9. How Customer Awareness Is Crucial For Buying Refurbished Laptops
Author: usedstore
10. It Staff Augmentation: A Model To Extend Your Team And Succeed
Author: ICSI
11. Why Should You Hire Managed It Services For Your Business?
Author: goodcoders
12. Why Should Enterprises Use Xamarin Forapp Development?
Author: goodcoders
13. Why Micro Teams Are The Future Of Software Development?
Author: goodcoders
14. Indicators That It's Time To Visit A Computer Repair Shop
Author: Anna Paquin
15. Can Mickey Mouse Power Cord Be Used As A Laptop Battery Charger?
Author: Jennifer Truong