Re: CCIE Troubleshooting Rules

Stephen makes a brilliant point about vendor specific videos.

I know the whole idea is for us to be experts here, but you can only learn from the best and from what iv been reading the t shooting strategy is critical.

--
BR
Tony
CCNP CCNA R&S JNCIS-SEC MCSE 
Sent from my iPhone on 3
On 25 May 2012, at 15:45, Stephen Lynch <slynch_at_absnt.com> wrote:
> Assuming a ticket has no restrictions, and its been said in this thread you
> should never remove configuration unless absolutely necessary - what would
> you do in the following scenario? Let's just say we need to ping 10.10.10.2
> from a source of 10.10.10.1
> 
> A) Remove sequence 10
> B) Add a specific ICMP permit statement before sequence 10 for a source
> (10.10.10.1) and destination of (10.10.10.2)
> C) If we remove sequence 10, this ACL no longer does anything so why not
> just remove it?
> 
> Router# show access-lists
> *Extended IP access list DENY_ICMP*
> *    10 deny icmp any any*
> *    20 permit ip any any*
> 
> By the way, vendors should really do a "Troubleshooting 101" video talking
> about the restrictions and the best way to solve the tickets given certain
> restrictions.
> 
> -SL
> 
> 
> On Fri, May 25, 2012 at 10:18 AM, Maarten Vervoorn <mr.vervoorn_at_gmail.com>wrote:
> 
>> Not sure if I would reload the routers and backup the config. I didn't in
>> my exam. You have 2 hours and 11 tickets. This means avarage 10min per
>> ticket. Reloading and backup the config a set of routers will take out lots
>> of time which you could spend in troubleshooting the dificult tickets.
>> During my exam I had the following appoach:
>> 
>> 1. Troubleshoot the issue with show commands
>> 2. If still the problem is not solved I would go for debug
>> 3. fix the configuration issue
>> 4. Verify the issue is solved
>> 5. Go to the next ticket
>> 6. If finished before the 2 hour I would spend the time verifying the fixes
>> of the tickets again.
>> 
>> Kind regards,
>> 
>> Maarten Vervoorn
>> CCIE#27144
>> 
>> 2012/5/25 john matijevic <john.matijevic_at_gmail.com>
>> 
>>> Hello Team,
>>> 
>>> Good question on approach to Troubleshooting section:
>>> 
>>> My strategy will be to fix config if there is error in order to fix a
>>> particular section.
>>> Then I will reload router or switch to make sure its still working
>>> after I fix the problem on a router or set of routers, or switches.
>>> Then I will save the config on that router and/or switches and any
>>> other router or switch that I fixed.
>>> I will use debugging as a troubleshooting tool, when I am fixed issue
>>> I will turn off debugging when finished.
>>> I will use notepad to copy config to so I can revert back to if
>>> necessary if option of notepad is available.
>>> 
>>> Regards
>>> John
>>> 
>>> On 5/25/12, Andrew Podosenin <andrew.podosenin_at_gmail.com> wrote:
>>>> I believe that they specifically state something like "fix without
>>> disabling
>>>> authentication". I think it is reasonable to ask the proctor in a
>>> particular
>>>> case.
>>>> 
>>>> Here is a question that I have - do we care in the TS section about:
>>>> 1. Saving periodically
>>>> 2. Saving at the end
>>>> 3. Turning off all debugging
>>>> 
>>>> Per my proctor this is optional in the TS. I wonder if this is really
>> the
>>>> case.
>>>> 
>>>> 
>>>> 
>>>> Sent via BlackBerry from T-Mobile
>>>> 
>>>> -----Original Message-----
>>>> From: marc abel <marcabel_at_gmail.com>
>>>> Sender: nobody_at_groupstudy.com
>>>> Date: Fri, 25 May 2012 07:42:38
>>>> To: Vincent Tay<vtay.75_at_gmail.com>
>>>> Reply-To: marc abel <marcabel_at_gmail.com>
>>>> Cc: Ccielab_at_groupstudy.com<ccielab_at_groupstudy.com>
>>>> Subject: Re: CCIE Troubleshooting Rules
>>>> 
>>>> You should fix them rather than remove any config. Only removed config
>> if
>>>> it is the only way to solve the ticket.
>>>> 
>>>> On Fri, May 25, 2012 at 7:24 AM, Vincent Tay <vtay.75_at_gmail.com>
>> wrote:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> I am wondering.
>>>>> 
>>>>> Anyone knows the rules of troubleshooting for the CCIE R and S? Are we
>>>>> allow to remove any misconfiguration statement such as access-list,
>>>>> passwords or we can only amend and fix them to get through the
>> section?
>>>>> 
>>>>> Regards
>>>>> Vincent Tay
>>>>> 
>>>>> 
>>>>> Blogs and organic groups at http://www.ccie.net
>>>>> 
>>>>> 
>> _______________________________________________________________________
>>>>> Subscription information may be found at:
>>>>> http://www.groupstudy.com/list/CCIELab.html
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> --
>>>> Marc Abel
>>>> CCIE #35470
>>>> (Routing and Switching)
>>>> 
>>>> 
>>>> Blogs and organic groups at http://www.ccie.net
>>>> 
>>>> _______________________________________________________________________
>>>> Subscription information may be found at:
>>>> http://www.groupstudy.com/list/CCIELab.html
>>>> 
>>>> 
>>>> Blogs and organic groups at http://www.ccie.net
>>>> 
>>>> _______________________________________________________________________
>>>> Subscription information may be found at:
>>>> http://www.groupstudy.com/list/CCIELab.html
>>> 
>>> 
>>> Blogs and organic groups at http://www.ccie.net
>>> 
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>> 
>> 
>> Blogs and organic groups at http://www.ccie.net
>> 
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
> 
> 
> Blogs and organic groups at http://www.ccie.net
> 
> _______________________________________________________________________
> Subscription information may be found at: 
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net