Re: Strategy for Troubleshooting Section in Exam

imran ,

Good books that you should read for this purpose:

1. Troubleshooting IP Routing Protocols ;
2. Routing-Bits Handbook & RS_Short-Notes-4.2 (after each chapter you will
see tshoot tips);
3. CCNP TSHOOT 642-832 Official Certification Guide.

Brgs,
Alessandro Braga

2011/5/5 imran ali <immrccie_at_gmail.com>

> it would be great if some one can post summary of most usefull show
> commands
> in a section wise manner
>
> example
>
> ospf
>
> sh ip ospf nei
> sh ip ospf int f0/0
> sh ip ospf
> sh ip ospf virtual-links
> sh ip ospf database
>
> Rip
>
> eigrp
>
> multiasting
>
> ipv6
>
> bgp
>
> mpls
>
> ldp
>
> vpnv4
>
> zbf
>
> dhcp
>
> nat
>
> ntp
>
> frame-relay
>
> ppp
>
> hdlc
>
> switching
>
>
> etc etc
>
> On Thu, May 5, 2011 at 8:34 PM, Nadeem Rafi <nrafia_at_gmail.com> wrote:
>
> > Hi
> > I think you can start from any vendor's workbook to understand and
> enhance
> > your TS skills. Then you should create your own topology for 30-40
> routers
> > in Dynamips. Try to put as many configs as possible and then break them,
> you
> > can get help from your friends to break your configs and don't let you
> know
> > whats have been broken. This can help a lot, and it helped me a lot. I
> was
> > able to fix at least 9 out of 10 tickets with proper verification during
> my
> > lab attempt "first and final".
> >
> > To solve issues, diagram in lab is very crucial, it has every thing you
> > need to understand the scenario. But plz dont waste time to understand in
> > depth whats going on, its not required to do so.
> > Time is very important factor to solve the lab, given 120 minutes for 10
> > tickets, if you stuck on any ticket it will give you a lot of stress
> while
> > solving other tickets. First try to solve tickets which you feel are easy
> to
> > fix and then return to other tickets. Solving each ticket is not required
> > but at least 8 are must. TS is all about basic skills, not in dept or
> > gotcha/tricky commands. If you know basic skills its more than enough to
> > pass TS.
> >
> > Try to increase the speed which can only be done through practice. This
> > practice will help you to make your plan to solve tickets in different
> > approaches, like top down approach, from down to upward or try to solve
> it
> > from middle. No single approach can help, and practice will give you what
> > all you need to work with TS. TS is best part of Lab which i liked and it
> > helped me a lot to understand things in quick and precise manner.
> >
> > Try to work with debug and show commands as much as possible, but don't
> > forget that there is no restriction to "do sh run". You just have to find
> a
> > proper equilibrium among sh run and other show/debug commands.
> >
> > HTH
> >
> >
> >
> > On Thu, May 5, 2011 at 7:14 PM, Roy Waterman <roy.waterman_at_gmail.com
> >wrote:
> >
> >> 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
> >>
> >> _______________________________________________________________________
> >> 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
Received on Thu May 05 2011 - 22:27:59 ART