Re: What about the troubleshooting part - allowed commands

On Wed, Jan 27, 2010 at 17:25, Narbik Kocharians <narbikk_at_gmail.com> wrote:
> You see, IB agree with Anthony.
>
> In our TS labs we do not restrict the students from any SHOW commands but we
> have tried our best to use all the other show and debug commands so the
> students can see and learn them.
> But you should NOT think that a "Show run" command is a bad one or is NOT a
> CCIE level command.

This is becoming weird - me agreeing with you, 100%.

In our Vol.3 labs that are out on the market just now, that also mimic
the real thing, there are no artificial restrictions. You can use
whatever you like. Our solutions include everything from "show run |
sect x" to debugging actual packets. However, once faced with the real
deal and in all my 15 years of production experience - 95+% of the
problems were solvable with some form of "show run" on multiple
devices.

Now, since 100% of the trouble tickets in the TS section are some form
of misconfiguration, well-prepared student need not do anything other
than compare what she sees with what she knows needs to be done. As
Tyson said - troubleshooting is a developed craft (a thing our
structured learning approach is designed to do, btw) and everyone will
develop their own style. Some people simply think using "show run" is
nasty CCNA level command and they would rather use debug commands. I
say fine. If it takes you the same time and you can solve simple
netmask mismatch in 30 seconds using both... go ahead.

Personally, I rather look at the trouble ticket, decide on the
approach to solve it before I type anything. More often than not,
experience and technology understanding helps pinpoint the problem
even before I need to type any commands.

--
Marko Milivojevic - CCIE #18427
Senior Technical Instructor - IPexpert
Mailto: markom_at_ipexpert.com
Telephone: +1.810.326.1444
Fax: +1.810.454.0130
Community: http://www.ipexpert.com/communities
Blogs and organic groups at http://www.ccie.net