Thanks a lot, Markku and Marko! It seems you guys have a lot in common. ;)
Seriously - I am in the clear now. Marko's post explaines everything there is to now. I think that post was written in one breath, from the heart and that is why it has such power in it. Finally the puzzle is completed and I know what should I do to get the digits. Yuo guys at ipexpert are great, thanks. Bojan *****Sent from my mobile handset***** -----Original Message----- From: Marko Milivojevic Sent: Thu 10.06.2010 21:47 To: Bojan Zivancevic Cc: CCIE_RS OnlineStudyList Subject: Re: [OSL | CCIE_RS] Sharing the experience of the lab On Thu, Jun 10, 2010 at 15:25, Bojan Zivancevic <[email protected]> wrote: [snip] > Now, here comes the point of this rant. Marko Milivojevic said that every > single time on the lab he > passed the tshoot part relatively easy... On what level we have to be, to be > able to solve three errors > in 5 minutes? On a completely new network, you have never seen it etc... How? > Imagine that skill. > AND, Marko himself told us that he passed on his THIRD attempt... So, he did > not complete the > config section two times... Markku gave you a pretty good overview of your other concerns, but I will answer the bit where you mentioned me... I completed configuration section all three times. I just made too many mistakes two times. I missed obvious things and in retrospective analysis I did later on, I knew exactly where my mistakes were. On my last attempt, I was done almost 2.5 hours before the end of the exam. I think Istvan (Proctor) was a little annoyed with me walking around, asking him if I can sign my name on the wall and stuff like that :-). Regarding troubleshooting... Yes, I passed TS every time and on average it took me 50 minutes to finish the whole section. Last time it took me around 35 minutes, actually. I literally flew through it, even though it was noticeably more complex and difficult than in my previous two attempts. Mind you, I am *extremely* fast, even by CCIE standards (Markku saw my "CCIE speed" in the bootcamp he attended). First off, don't try to understand the whole topology. It's pointless and a waste of time. We are EXPLICITLY TOLD that tickets are NOT interdependent. You can solve them in any order you like. However, if you mess things up badly, your tickets will become dependent on each other. If that happens... enjoy the lunch (there is no soft way to say that, I'm sorry). The key here is the method and I keep repeating that all the time. I will spell it out: 1. Read the problem 2. Identify affected devices 3. Access devices you need 4. Look at the problem using one of these approaches: => Top down => Bottom up => Split and divide 5. Fix the problem => Apply the simplest and the most obvious solution 6. Save => All affected devices 7. Verify 8. Read the ticket again => Just to make sure you are fixing the correct problem. 9. Verify again 10. Close all terminal windows. Those are 10 steps I performed for every single ticket I was faced with. If you take 1 minute for each one, you are left with 1-3 minutes to spare per ticket. Needless to say, many of these steps will take you probably up to 20 seconds to perform if you are well practiced. If you spend 10 minutes per ticket, given 10 tickets, you will be done in 100 minutes, which is pretty good time in any book. If you take a look at our Volume 3 walkthrough videos, even with my detailed explanations and analysis, each ticket takes less than 10 minutes to be solved! 10 minutes is a very long time, when you are ready for the lab. Now, another key point here is... when you hit 10 minutes - give up and move on. You need points, so chase the points. If there is time left, go back and fix the issue, but get as many points in the bag as you can. I can tell you that Markku is probably one of the most prepared students I've seen in my classes. The fact that he passed configuration section (which I didn't, two times), tells me a lot. He didn't pass the troubleshooting because he missed something and only he knows what that is. I'm sure he knows it for a fact. Just please remember, CCIE is an EXPERT-level test. It requires you to be an EXPERT when you are there. Experts are quick, experts are precise, experts know and understand the technology. Experts are NOT AFRAID of any task, any technology, any trick. Experts go to lab to have fun. Every time I passed, I had tremendous fun while I was there. Those two times I didn't... weren't as pleasant (even though I enjoyed TS section every time, I must admit). ;-) -- Marko Milivojevic - CCIE #18427 Senior Technical Instructor - IPexpert YES! We include 400 hours of REAL rack time with our Blended Learning Solution! Mailto: [email protected] Telephone: +1.810.326.1444 Fax: +1.810.454.0130 Web: http://www.ipexpert.com/ _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
