Thanks all. This was my third attempt. In preparing for troubleshooting, I used 
labs I created based on several problems for each ticket. Rather than solving 
one problem tickets only, I would always add additional issues to be sure that 
I considered all possibilities when troubleshooting. Most of these I did in 
gns3 or on my switches at home. I also took different vendor labs and added to 
them. I worked on speed speed speed. Doing the same labs over and over to get 
my times lower and to get used to my steps and command outputs. 

It also helps that I teach ccie written classes for route switch and voice. So 
that kept me moving. 

But like I said, Marko was very good in his classes and his trouble tickets 
were very fun and challenging. 

I think that the way we trick ourselves is thinking that we have to do a ticket 
just once and that's it. Practice, rinse, change, repeat. That is what builds 
speed and confidence. 

On tshoot, my approach was going after small tickets first. That builds 
momentum. The tickets with just one problem and the ping tickets generally go 
faster. You can start a continuous ping from one device and then go router by 
router in the path testing. 

You have to get at least one of three point tickets so I would target the one 
that relies more on pure routing. 

Once you tackle a few small tickets, you can hopefully see time savings that 
you can use on big tickets. 

I solved 5 tickets in the first 30 mins. That really helped me relax for the 
other ones. 

Last thing to be reminded of is that lack of  full connectivity is not 
necessarily a deal breaker. I did every config task and could see all routes on 
all routers. But after finishing config section with a half hour to go, I 
decided to run pings tests. They were failing between a couple of devices. I 
couldn't find the problem even after reboots. 

After confirming all of my redistribution configuration, I decided to just step 
away.

The results speak for themselves as I got my number. I think I nailed enough 
non related final tasks to get enough points. There was nothing on the lab I 
didn't understand so I knew I did my correct solutions. (at least I felt that 
lol)

Thanks again for all the comments. I'm on to voice ccie track now. :)

Regards,
Raliegh



Sent from my iPhone

On Oct 31, 2012, at 8:06 AM, "Michel L. M. B. Perez" <[email protected]> 
wrote:

> Great job guy, next year will be my turn! :)
> 
> --
> Michel Perez
> Skype: michelmbperez
> [email protected]
> http://br.linkedin.com/in/michelmbperez
> 
> 
> 
> 2012/10/31 Mirek <[email protected]>
> Great job, congrats!!!
> 
> Mirek
> 
> On Tue, Oct 30, 2012 at 10:31 PM, Anthony Jones <[email protected]> wrote:
> 
> > Thanks to all on the list. Thanks to Marko for the great boot camps and
> > feedback.
> >
> > Regards,
> > Raliegh Anthony Jones, CCIE #37264
> >
> > Sent from my iPhone
> > _______________________________________________
> > 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