I think that a lot of folks study configuration to meet requirements to
pass the lab. There is always a layer of user induced troubleshooting that
takes place to get some things working. Now with the changes to the lab
and the troubleshooting section, you have to take that configuration
knowlege and add to it the associated show / debugging commands /
processes required to test and troubleshoot the issues.
In my experience I found that connectivity to the BB devices ( i.e.
forming routing relationships, L2 / L3 connectivity ) could be resolved by
utilizing the proper suite of debugging commands or turning on logging to
the console to get an idea of what was failing. Many times it is a mistake
in typing in an IP address or VLAN on a switchport.
When connecting to the BB devices, it is similar to making a connection to
devices under your control. In the case of the BB devices, you have to
trust that the BB side is configured properly. You take over from the
point where it hits the switch ( or router if directly connected ).
So how would you normally trouble shoot a connectivity issue to a service
provider? I use the service prvider as an example since you do not have
access to their equipment. Check the interface on the switch or router to
verify L1 and L2 status. Once L1 and L2 is verified move to L3. Do you
have a proper route to the device? Is the route following the correct
path? Is the next hop reachable?
My point is that you probably posess the "tools" to troubleshoot and
resolve these connectivity issues in your "arsenal" of knowlege and just
need to think of applying it to the backbone connectivity issues. We can
get so used to having access to both sides of the items we are configuring
(which gives us a big advantage to troubleshooting) that we forget how to
think about troubleshooting without visibility into the far end device -
and probably don't think to practice it.
Anthony also brings up a good point concerning the logical versus physical
connectivity diagrams that you will see.
Thanks
-- Larry Hadrava, Larryh_at_INE.com CCIE #12203 (R&S) Internetwork Expert, Inc. http://www.INE.com >----- Original Message ----- From: "John Wayne" <john.wayne.ccie_at_gmail.com> Sent: Thu, September 24, 2009 14:50 Subject:Re: My First $1.750 Lunch (Finally, but it's not Final) What are the issues? A lot of people have them and it seems we hear it from a lot of candidates. It is consistently a reason people say they failed. On Thu, Sep 24, 2009 at 2:10 PM, Anthony Sequeira <asequeira_at_ine.com> wrote: > All of the respected CCIE Training Vendors are now teaching Troubleshooting > if they were not before. Properly troubleshooting Layer 2 and Layer 3 > connectivity to the backbone is a fundamental part of our training courses. > > Warmest Regards, > > Anthony J. Sequeira, CCIE #15626 > http://www.INE.com <http://www.ine.com/> > > Test your Core Knowledge today! > Q: If you run MVR and see IGMP states appearing in the source router, what > MVR mode is used? > A: Dynamic Mode > More Info: > http://www.cisco.com/en/US/docs/switches/lan/catalyst3550/software/release/12.2_25_see/configuration/guide/swigmp.html > > > > On Sep 24, 2009, at 1:54 PM, Johnny B CCIE wrote: > > A lot of people have this problem. Who is teaching us how to fix it. >> >> On Thu, Sep 24, 2009 at 10:10 AM, ospfv2 <ospfv2_at_gmail.com> wrote: >> >> Finally i did the lunch, the most expensive ever in my life >>> >>> hope i don't break the NDA >>> >>> proctor was nice and friendly, very helpful >>> we were on the same desk, its mobile lab, no cubicles >>> >>> first the core questions >>> it was four of them >>> u need to make three of them right >>> >>> my core was so easy, it was ccna level, my report for this was excellent >>> >>> pressed submit button >>> >>> then the real big thing, it was there on the binder >>> >>> for L2, i thought it was easy, until it waste me an hour to found the >>> error. >>> >>> so make sure you read your L2 diagram carefully >>> >>> what you see is not what you think >>> >>> Just do INE mocklabs (all of them), u will know what i mean >>> do the mocklab on rack, dont just read the lab and type the answer in >>> your notepad >>> do it like a real lab, u will find problems >>> >>> finally i'm done with L2, but some of my BBs is not reachable >>> i'm still have no idea how to fix it >>> so when your L2 is not right yet, it will cause you loosing points for >>> the next Qs. >>> make sure you understand what problems those BBs could give u >>> and how to handle it >>> >>> next, with BB headache still in my head, i try to move on with RIP >>> the RIP gave me headache as well >>> using debug ip rip i know my config isn't right yet >>> RIP waste more time than i thought >>> finally my debug ip rip is right >>> >>> >>> EIGRP was not tought, but due to my BB problem, i know my EIGRP wont >>> fulfill the requirement. >>> >>> i went back to L2 technology >>> a lot of them, easy but it test your accuracy & details >>> >>> OSPF was easy (in my opinion,not in cisco report) >>> >>> Redistribution >>> not so hard, but... >>> again with BB problems, my redistribution solution will not satisfy >>> the requirement. >>> >>> BGP >>> i think you know why i cannot get full point for BGP >>> >>> so i really lost a lot of points due to dependancy at L2/BB >>> >>> non core topic, make sure u repeat your lab to gain speed and accuracy >>> >>> >>> >>> unfortunately the docs was not working as i expected >>> Jesus Christ,i clicked the link and it take almost a century to load >>> i think cisco better provide the DVD to avoid this kind of problem >>> so make sure u don't rely too much on the doc, in case u have the same >>> problem >>> >>> >>> i just remember that i always have problem with BBs reachability, even >>> in INE mocklab >>> so i need to get those BB things right first before my next v4 >>> but i dont know what is the the problem anyway >>> Scott i think i will need your help on this, if u dont mind :) >>> >>> >>> total damage = $1.750+$1000 ++ (for travel expenses) , almost $ 3.000 >>> >>> i hope my next lunch with proctor will be the last one >>> lunch with number offcourse >>> >>> >>> wish you all the best with v3 >>> see u all in v4 >>> >>> >>> >>> >>> Ok Mr President, u make me feel better with those words...( plenty of >>> failure along the way) >>> >>> Making your mark on the world is hard. If it were easy, everybody would >>> do >>> it. >>> But it's not. It takes patience, it takes commitment, and it comes >>> with plenty of failure along the way. The real test is not whether you >>> avoid this failure, because you won't. It's whether you let it harden >>> or shame you into inaction, or whether you learn from it; whether you >>> choose to persevere. (Barack Obama) >>> >>> did he really say that ? >>> >>> >>> 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.netReceived on Thu Sep 24 2009 - 14:18:38 ART
This archive was generated by hypermail 2.2.0 : Sun Oct 04 2009 - 07:42:04 ART