Re: CCIE Troubleshooting Rules

On my last attempt I tried to ask the proctor how specific we needed to be
in modifying access-lists, and he would not give me a definitive answer. He
said if we don't resrict it it is fair game. The restriction I had
specifically said something very much like: Do not remove any config unless
that is the only way to solve the ticket.

So I took that to interpret that it is better to make an access-list say
permit ip any any even if that means it is pointless, than to remove it.

On Fri, May 25, 2012 at 11:28 AM, marc edwards <renorider_at_gmail.com> wrote:

> 100% agree that reading the instructions is priority. I also got into
> habbit of reading all tshoot tickets and configuration section before
> banging around on keyboard. I did significantly better with that strategy.
> In tshoot on IOU, reloads are instantaneous but I agree that it is really
> an unnecessary. Reading all tickets and nailing out familiar ones allows
> for more time on the involved ones.
>
> How about static null0 routes? remove or rest next hop?
>
> Some things chalk up to experience and I find it a little upsetting Cisco
> gives low/ no guidance after taking an exam where your configuration was
> off. I am not saying it is a little unfair, really very unfair.
>
> The more I study, the more I understand what it takes. But to legitamately
> call oneself CCIE takes an almost un human amount of intelligence and
> exposure to the exam . It is not a best practices test and while the blue
> print covers so much, we are only tested on a subset of what is in it.
>
> All food for thought.
>
> On Fri, May 25, 2012 at 8:58 AM, Brad Ellis <brad_at_ccbootcamp.com> wrote:
>
> > I would definitely suggest reading the instructions! What if something
> > small changed or was updated since the last time you took the exam? Or
> > if you hadn't taken it yet, what if something you were under the
> > impression before taking the exam, was just completely wrong...idk, I
> > think reading the instructions is a good thing...unless you're putting
> > together a child's toy...then you absolutely don't read instructions
> > because "it's a guy thing!"
> >
> >
> > thanks,
> > Brad Ellis
> > CCIE#5796 (R&S / Security)
> > CCSI# 30482
> > CEO / President
> > CCBOOTCAMP - Cisco Premier Partner Offering Certification Training
> > Email: brad_at_ccbootcamp.com
> > Toll Free: 877-654-2243
> > International: +1-702-968-5100
> > Skype: skype:ccbootcamp?call
> > FAX: +1-702-446-8012
> > Training And Remote Racks: http://www.ccbootcamp.com
> >
> > -----Original Message-----
> > From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
> > Vincent Tay
> > Sent: Friday, May 25, 2012 8:14 AM
> > To: Stephen Lynch
> > Cc: Maarten Vervoorn; john matijevic; Ccielab_at_groupstudy.com
> > Subject: Re: CCIE Troubleshooting Rules
> >
> > Yeah. It make no sense say to amend the access list by permit ip any
> > any. Instead, we can remove it from the interface to save time if allow.
> > Anyone read the troubleshooting instructions in the actual exam?
> > Definitely we do not want to spend time reading instructions in the exam
> > when time is so precious.
> >
> > Vincent Tay
> >
> > On 25 May, 2012, at 10:45 PM, 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
> >
> > _______________________________________________________________________
> > 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
>
>
>
>
>
>
>
>

-- 
Marc Abel
CCIE #35470
(Routing and Switching)
Blogs and organic groups at http://www.ccie.net