I agree with sticking to you guns in regards to the time allocated to a ticket. I found that I kept telling myself that I was close to solving the ticket and wasted 30 minutes on a single ticket :(
Attempt the ones you are most comfortable with setting a time limit then circle around an work on the ones you feel were more difficult On Sun, Apr 3, 2011 at 8:53 AM, Jay Taylor <[email protected]> wrote: > Agreed... I did a quick run through of the tickets and for most just noted > the ticket number and the OSI layer I had to deal with which took maybe > 10-15 minutes. After that I gave myself 5 minutes a ticket and if I wasn't > making progress by then I moved to the next one. > > > On Sun, Apr 3, 2011 at 8:27 AM, Don Lundquist <[email protected] > >wrote: > > > Read them and make special note to spend a specified amount of time on > > each. Be very strict about doing this. The 2 hrs you have to troubleshoot > > goes by very quickly and it is no fun when your time runs out and you are > > unaware of it... > > > > > > > > On 4/2/11 9:17 PM, "marc abel" <[email protected]> wrote: > > > > >To anyone who has taken the troubleshooting section of the lab, did > > >you read through all the tickets before starting or did you tackle > > >each ticket as you read it? > > > > > >Thank you, > > > > > >Marc > > >_______________________________________________ > > >For more information regarding industry leading CCIE Lab training, > please > > >visit www.ipexpert.com > > > > _______________________________________________ > > For more information regarding industry leading CCIE Lab training, please > > visit www.ipexpert.com > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
