I like that, "be the packet".  I hope that isn't copywrite!

Regards,
Jay McMickle- CCNP,CCSP,CCDP
Sent from iJay

On Feb 21, 2012, at 11:53 PM, Joe Danrich <[email protected]> wrote:

> 
> Don
> 
> Back in the 90's when I got my CCIE, the labs were a bit different with 
> troubleshooting being last. With that being said, it's still feels odd to 
> most people to work on networks that they haven't designed or installed.
> 
> For me when troubleshooting a network issue I try to do the following:
> 
> 1. Be the packet.. Usually if you can figure the correct path your supposed 
> to be on, you'll see oddities more clearly and problems with the path 
> selection.
> 2. Break the problem in half if you can. Troubleshoot from the beginning to 
> the middle. If that's good, then go mid to end. If the problem is in the 
> first half, then you might have to break that portion in half also.
> 
> Some things you can try, but you'll need someone to help you.
> 
> - Create various networks.
> - Have someone come in a break them in multiple places.
> - Have them write down what the problems are in the same vague way that Cisco 
> does in the lab.
> 
> Lastly, if you can work in an area of a company as nothing but a 
> troubleshooter, like a help desk on a network you know nothing about then 
> you'll increase the skill sets.
> 
> Ta ,
> 
> Joe
> 
> 
> 
> On 02/21/2012 04:31 PM, Tim Miller wrote:
>> Hey Don:
>> Troubleshooting is my albatross too.
>> The following improved my TS skills, but they are still subpar:
>> 1) read the "Troubleshooting<technology>  Guide" on the DocCD.
>> 2) list the five (or whatever)  most important TS commands for that 
>> technology.
>> 3) make Anki (ankisrs.net) cards and memorize them so as soon as you see a 
>> ticket with say Multicast, your mind rattles off the commands before you 
>> even have a chance to think.
>> 4) try to use labs that a friend made for you.
>> Hope it helps.
>> Tim
>> 
>> 
>> Sent from my iPhone
>> 
>> On Feb 21, 2012, at 1:43 PM, Don Pezet<[email protected]>  wrote:
>> 
>>> I need some advice. I have unsuccessfully attempted the lab exam twice now.
>>> I am doing fine on the configuration section and on my second attempt I
>>> passed with almost an hour left to check my configurations so I don't have
>>> any worries there. However, I failed the troubleshooting section both
>>> times. The first time I solved 7/10 tickets before running out of time so I
>>> came really close. I then spent three months focused on troubleshooting and
>>> attempted the exam a second time, confident I would pass. On my second
>>> attempt I tried to do better time management and focus on tickets that I
>>> knew I could solve. I marked down that I solved 8, however when I got my
>>> score report I only solved 5/10 tickets so I actually did worse than my
>>> first attempt. The test definitely seemed more difficult, but I think it is
>>> obvious that my study methods are not paying off. Apparently when I setup
>>> the network myself (the config section) I have no problems, but when
>>> someone else sets up the network (the troubleshooting section) I am stuck.
>>> So, I am looking for advice on what I can do to strengthen my
>>> troubleshooting skills.
>>> 
>>> Here is what I have been doing so far:
>>> 
>>> - I have watched all of the BLS content multiple times.
>>> - I have performed the CCIE R&S Workbook Volume I and Volume III labs
>>> multiple times on Proctor Labs equipment as well as in simulators.
>>> - I have performed the troubleshooting labs from Volume III enough times
>>> that I have the solutions memorized so it is not really troubleshooting any
>>> more.
>>> - I have memorized countless template configurations so I know what
>>> commands are needed / not-needed when setting up things like MPLS,
>>> Frame-Relay, AutoRP, etc.
>>> 
>>> At this point I am scratching my head as to what to do next. Does anyone
>>> have any advice on what I can do to get better at troubleshooting? Does
>>> IPExpert have any additional products outside of the BLS bundle that covers
>>> this better? Or a live class? I am thinking about repeating the CCNP TSHOOT
>>> class to see if that helps, but the tickets on the lab exam are more
>>> advanced and cover topics not included in TSHOOT.
>>> 
>>> Thanks for your time,
>>> 
>>> Don
>>> _______________________________________________
>>> For more information regarding industry leading CCIE Lab training, please 
>>> visit www.ipexpert.com
>>> 
>>> Are you a CCNP or CCIE and looking for a job? Check out 
>>> www.PlatinumPlacement.com
>>> 
>>> http://onlinestudylist.com/mailman/listinfo/ccie_rs
>> _______________________________________________
>> For more information regarding industry leading CCIE Lab training, please 
>> visit www.ipexpert.com
>> 
>> Are you a CCNP or CCIE and looking for a job? Check out 
>> www.PlatinumPlacement.com
>> 
>> http://onlinestudylist.com/mailman/listinfo/ccie_rs
> 
> _______________________________________________
> For more information regarding industry leading CCIE Lab training, please 
> visit www.ipexpert.com
> 
> Are you a CCNP or CCIE and looking for a job? Check out 
> www.PlatinumPlacement.com
> 
> http://onlinestudylist.com/mailman/listinfo/ccie_rs
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

http://onlinestudylist.com/mailman/listinfo/ccie_rs

Reply via email to