From: michael.dennis (michael.dennis@xxxxxxxx)
Date: Sun Feb 25 2001 - 11:35:09 GMT-3
I think that would be the best way to test your networking skills. I'm
currently working on a project where the ccie's have to plan and migrate the
world's largest token ring to ethernet. Given the complexity of the network
and the constant harassment of the workers here, its a good test of their
patience and competence. So, given someone else's network to fix or
troubleshoot just makes you a better network engineer.
-md
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Erick B.
Sent: Saturday, February 24, 2001 7:05 PM
To: Chuck Larrieu; CCIE_Lab Groupstudy List
Subject: Re: Cruel Lab Tricks OR what goes around
This is acceptable. What happens when your shop gets a
call from some company/organization with a down
network and they have no info to go off of? You have
to piece it together and find out whats what.
This is what I do daily. Troubleshoot networks that I
have no information for most of the time. This is good
practice and you get to see some poorly designed
networks and/or installs. The best part is when you're
able to correct the mistakes and make their network
work better. I would love to be the one to be
responsible of breaking someones lab for the
troubleshooting part.
--- Chuck Larrieu <chuck@cl.cncdsl.com> wrote:
> There's been discussion on this list about
> troubleshooting, and the question
> about whether you troubleshoot your own network or
> someone else's.
>
> There has also been discussion about the importance
> of a good diagram.
>
> Suddenly it occurs to me - a most cruel lab proctor
> trick.
>
> You re given someone else's network to troubleshoot,
> and the only
> documentation you have is a diagram prepared by
> someone exactly the way you
> prepared yours. ;->
>
> Ouch!
>
> Chuck
> ----------------------
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:00 GMT-3