From: Scott Morris (smorris@xxxxxxxxxxxxxx)
Date: Fri Apr 06 2001 - 21:47:26 GMT-3
Just like I tell my students in CIT:
EVERYTHING IS FAIR GAME!!!
That's not breaking NDA, but it's definitely keeping things up in the air!
Expect it all! :)
As for points, you'll find it doesn't exactly correlate, because you may
"solve" something in multiple steps that's really just one problem. Or you
may fix some problems that YOU left in there rather than the proctor putting
it in.
As for methodology, do whatever works best for you! I would strongly
suggest troubleshooting by the layers! Start with physical and go from
there! It doesn't matter how nice the config is, 'cause if you don't have
wires plugged in, it just ain't gonna work! (grin)
Many people do troubleshoot by scanning the config. That may be a good
place to start. It depends on how your mind works.
All in all, troubleshooting is like network design, there are very few right
or wrong answers. Just some that work better for some people than others!
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Chuck Church
Sent: Friday, April 06, 2001 8:35 PM
To: ccielab@groupstudy.com
Subject: Couple of lab troubleshooting questions
Anyone,
I trying to develop a strategy for troubleshooting in the lab. Is it
best to start with looking through the configs for things that don't look
right, or should I just dive in with show commands looking for missing
routes, neighbors, etc? Is every error worth 1 point (in other words, are
there always 25 errors)? Finally, without breaking any NDA, just how hard
is troubleshooting? Can I expect stuff like unplugged cables, or is it more
added/deleted/changed lines in the configs? Or is it really sinister, like
loading a different IOS that has a different default than what you built
your network with? I'm just trying to get a feel for that section.
TIA,
Chuck
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:42 GMT-3