Re: What about the troubleshooting part - allowed commands

Hi Nadeem,

Thanks for the kind words.

You can read all about it at http://dans-net.com

HTH,
Dan #13685 (RS/Sec/SP)
Troubleshooting blog: http://dans-net.com

On Wed, Jan 27, 2010 at 7:41 PM, Nadeem Rafi <nrafia_at_gmail.com> wrote:

> Thanks Dan, i have seen your blog and a great offer for a free TS workbook.
> In a separate post can you put detail for all ccie candidate about this WB.
>
> On Wed, Jan 27, 2010 at 8:35 PM, Dan Shechter <danshtr_at_gmail.com> wrote:
>
>> Hi Dennis,
>>
>> I have never heard of such a restriction.
>>
>> A good trouble-shooting technique is always a combination of "show run"
>> commands, and other show and debug commands.
>>
>> For example: sometimes its so much easier to troubleshoot by comparing
>> configurations of two routers.
>>
>> There are even some TS tasks which you just can't use show commands to
>> solve, as they can't be tested in the lab, such as some IP services, some
>> QoS tasks... etc.
>>
>> At the end, you will always need the "show run" command to verify that the
>> fix you want to apply to the running configuration actually makes sense.
>>
>> Note: never use just "show run". You always need to be more specific, like
>> "show run | section eigrp". To be more specific, you will need the other
>> show commands.
>>
>> Last, but not least, make sure you practice TS labs only after you have
>> finished all other practice labs. You will really need all your skills to
>> do
>> TS.
>>
>> HTH,
>> Dan #13685 (RS/Sec/SP)
>> Troubleshooting blog: http://dans-net.com

Blogs and organic groups at http://www.ccie.net
Received on Wed Jan 27 2010 - 23:08:04 ART