Re: Strategy for Troubleshooting Section in Exam

Just an additional thing to Nathan's essential recommendation to read the
restrictions is to ideally (after solving each ticket), verify that in the
resolution of that ticket, that you haven't violated any restrictions.
It's all too easy to read the restrictions at the start & then to
potentially forget them in the heat of battle.
It's also all too easy to believe that in verifying the solution works, you
have your points, when in fact you've violated some restriction.

It may well be overkill to some to check restrictions after each ticket, but
it's what I'm going to do when I next pay a visit to the lab.

Regards
Roy
@routelaker

On 5 May 2011 16:59, Ahmed <ahmedsalim_at_gmail.com> wrote:

> I would also add that to move on if you;r stuck in a particular question
> and
> come back to that later. Time is of the essence.
>
> On Thu, May 5, 2011 at 6:51 PM, Nathan Falcon <nathan.falcon_at_gmail.com
> >wrote:
>
> > Simple thing to remember, but make sure you read the restrictions.
> > They're easy to miss in the troubleshooting section.
> >
> >
> >
> > On Thu, May 5, 2011 at 10:32 AM, Carl Gosselin
> > <carl.gosselin_at_altizone.com>wrote:
> >
> > > A great source of information in the troubleshooting section of the lab
> > is
> > > the overall network diagram.
> > >
> > > You have 10 to 12 minutes to solve a ticket.
> > >
> > > You should take 30 seconds to a minute (max) to study the network and
> > scope
> > > the routers that are invoved in the current ticket and potential
> issues.
> > > For example...
> > > Traffic flow ?
> > > Redistribution points ?
> > > OSPF areas ?
> > > Authentication ?
> > >
> > > The rest depends on your preparation and knowledge of the material and
> > > knowing when to skip and go to the next ticket...
> > >
> > > IMHO
> > >
> > > Goodluck!
> > >
> > > -Carl
> > >
> > >
> > > On Thu, May 5, 2011 at 8:57 AM, imran ali <immrccie_at_gmail.com> wrote:
> > >
> > > > not an expert yet but i suggest the following
> > > >
> > > > 1)identify the problem fist ...make sure what is being asked
> > > > 2)check on what routers u need to configure
> > > >
> > > > 3)use sh run | in ...sh run | sec ....sh run | beg ...and other
> > relavent
> > > > show commans
> > > >
> > > > then comes resolution ...
> > > >
> > > >
> > > >
> > > > On Thu, May , 2011 at 2:51 PM, Paul Tim <paultim68_at_gmail.com> wrote:
> > > >
> > > > > Hi
> > > > > Seeking for Experts point of view on "Strategy for Troubleshooting
> > > > Section
> > > > > "
> > > > >
> > > > > cheers
> > > > > Paul
> > > > >
> > > > >
> > > > > 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
>
>
>
>
>
>
>
>

-- 
Regards
Roy
Blogs and organic groups at http://www.ccie.net