Brett Saling
CCIE V4 experience...
http://ieoc.com/forums/t/9303.aspx
I debated for some time before I decided to do a write up on my 2nd attempt at 4.0. But I think a part of me just needs to get this out there so I can put it behind me and get ready for my next attempt.
I first took v4.0 on October 23rd, the first week it came out. I did a write up of my experience and posted it here for all to see. I went back to the original place of my destruction (San Jose) exactly 30 days after that attempt, on Nov 23. During those 30 days, I put extra effort into all those areas that were clearly weaknesses for me, namely, some of the new blueprint topics and even a couple of older topics under 7.00 Implementing Network Services and 10.00 Optimizing the Network. Needless to say, I went back with a huge lift in confidence and telling myself that I was finally going to pass. At the same time, I was nervous as hell because I just didn't know what to expect and I was actually fearful that I would get topics that I didn't focus any efforts on (Scott Morris has a saying about this 
).
There was one other guy, Vince (I think?), who had just recently completed an INE bootcamp. It was his first attempt at 4.0 and I gave him a quick rundown of what to expect on the new format. I told him my strategy for this time around was to be strict about time management, which was a killer for me the first time. That, and a lot of coffee. When the proctor finally brought us back, I immediately put myself into the zone and started on the test.
OEQs are OEQs. You answer with as short and concise an answer as you can and reread the questions at least 3 times. This is the 2nd time where I re-read a question, realized something was wrong with my initial answer, and changed it (hopefully for the better). Needless to say, I spent about 15 minutes total on the section and once I closed it out, I completely put them out of my mind.
I opened the troubleshooting section and to my surprise, the interface didn't bother me, not even a little. I opened my tickets list, and immediately set about looking for my routers. Later during lunch, I did make a suggestion to the proctor (I wish I could remember his name, cuz he was really cool), that they could use some kind of coordinate mapping system to help find the affected routers and hosts faster. He liked the idea. Anyway, the first few tickets were pretty straightforward and then I ran into my first head scratcher. First off, the interface shown on the map didn't match up with the interface on the router that needed to be fixed. Secondly, I just couldn't figure out why I couldn't get it to work. It seemed like a simple issue. I had given myself 10 minutes to look for a solution and once that 10 minute time limit hit, I immediately put the ticket aside and proceeded with the other tickets. I ran into another head scratcher a few tickets later, did my 10 minute time limit, and went on without a solution. I was able to complete all but those 2 tickets and I had about 30 minutes left. I guess working on the other tickets was helpful in 2 ways: 1) it gave my mind a chance to take a break from the problem, and 2) I was able to get the remaining tickets. When I came back, I tried a couple things and ultimately got a working solution. I even had 10 minutes to spare which I used all of it to double-check all my solutions. I was feeling high and mighty at this point.
As with the OEQs, once I closed the section out, I put all that behind me and focused solely on the configuration tasks. This time, unlike the last time, I actually spent 30 minutes drawing up a map, creating a score tally, making notes, and reading the entire exam. Just as I hopped onto the first switch to start configuring, the proctor called for lunch and we went. As we walked to the cafeteria, I could tell by Vince's expression that he already knew he wasn't going to pass. I was still feeling good and my confidence was even higher, even after reading through the config tasks. There were a couple of items that I wasn't sure about, but I determined that if I nailed all the other tasks, I'd have enough points to pass.
For lunch, I had a burger, some tea, and a Red Bull. In hindsight, the Red Bull was a mistake. I only got it because I wanted to make sure that I wouldn't get sleepy or tired later in the afternoon. That part of my plan worked to perfection. However, since I only occasionally drink Red Bull, the side effect I got from it probably did more damage. Basically, I got really jittery and could not keep my hands still. I can say that normally I type around 50-55 words per minute, but after the Red Bull, I must have been typing around 75 words per minute with major mistakes. With all the backspacing I had to do that first hour after lunch, I probably was averaging only 40 words per minute 
Anyhow, we got back to the lab, and I immediately started typing/backspacing/typing with the intention that I was going to have Layer 2 and Layer 3 done in 2.5 hours, which would leave me with 2.5 hours for all the other stuff. I put in my configs, double-checked everything twice, and then BAM 
, got nailed by my first big problem in Layer 3. I spent maybe 15 minutes trying to figure it out, and it was even on a topic I had spent extra time on (only I never quite set it up the way the Lab had me do it). I backed it out so that I at least had connectivity to everything, then finished up with the Layer 3 section. I was already at my 2.5 hour mark and I did a quick review of the tasks yet to complete. I was pretty confident I could knock them out so I decided to give myself 30 more minutes to try and fix that problem. 30 minutes later, I was still no where to getting it fixed, so I backed it out and proceeded with the remaining tasks 
.
Unfortunately, even though I had configured most of those remaining tasks at one point or another in my studies, I didn't know them like I did L2/L3 configuration and that's what got me. I ended up spending too much time referring to the command references and config guides, and I even caught myself reading an overview section on a particular feature which I really should have known already. Those remaining 2 hours flew by, but I had at least touched all the tasks I said I was going to touch. I only left 2 tasks completely untouched because I knew I was going to have to look those configs up in the config guides and I was only going to attempt them if I had time. I didn't. But I pretty much knew where everything else was supposed to be, went right to the spot in the documentation, got the config put in, and went on to the next task.
When the proctor called time, I was putting in the last few lines for a task, but by then my confidence about passing the lab had slipped considerably. In my heart, I was 100% confident that I had done what I was supposed to do on only a few tasks. I knew I had achieved most of the task requirements on others, but I wasn't 100% sure. To give you an idea of what I'm talking about, a given config task, i.e. EIGRP, may tell you to set it up based on what you see on the map, then apply some protocol specific config, then redistribute it, and finally apply some kind of filter or ACL or what not. In most cases, I was confident I got 3 of the 4 subtasks, but I was never sure if I got that last one. As I tallied up my final score, I realized that I was only really confident about 20% of my answers, unsure on 60% and down right certain I missed those 20% I couldn't fix or didn't attempt.
In any case, I walked out of there light hearted knowing that I solved all the troubleshooting tickets and was looking forward to my score to see how many of my unsures on the config section were actually correct. So, let's fast forward to when I got my test results.
I was surprised to see the email saying my results were in only 4 hours after I had left the lab. I knew I hadn't passed, and I wasn't nervous or apprehensive or anything as I logged in to view my score. I just wanted to know where I needed to do more work. In fact, I had already started a gameplan on what areas to focus studies on for my next attempt. Then I saw the scores and my emotions literally went like this: 
cool I passed OEQ, WTF!? 
I failed troubleshooting?!?, 
I'm sick to my stomach right now!, 
there's a rain on my parade, WTF!!!, 
I'm speechless, This is no good, 
I so ashamed right now, 
I don't drink, but I could use one now, 
.
I had failed again, and my so called confidence was all a bunch of nothing. I had failed way worse than before and my score report, due to all the 0% (yes, that' zero percent) was of no use to me. At least my previous attempt showed me that I could at least work on a few areas which is what I did. And as if I wasn't feeling terrible already, I physically got sick, not quite the flu, but like it. I closed my computer, quietly put my study notes away, packed my bag for the next morning's flight, and put Cisco, the test, and 9 months of lab work, out of my mind. Officially, at that moment in time, I had decided that my journey was done and I wasn't going to think about any future attempts...
...
...
15 minutes later I was online trying to remember all the different tasks that I had problems with and looking up solutions. Over the next 3 hours, I hit all my old workbooks, searched through Cisco's documentation, Google'd stuff, so forth and so on. I finally decided that if I was ever going to pass this test, I'd need to go back to basics, which I'll admit I had taken for granted the past several months. I had spent so much time learning about MPLS (and I still didn't know enough), that I figured it was time to take next month's lab attempt money and invest in some new workbooks. Fortunately for me, INE later ran a cool weekend special for workbooks I didn't have and also a killer deal on lab rental. I took my December money and applied it to that and my intent is to go back to the beginning, but with a fresh, somewhat dated yet new to me look, at the basics. Because that's where I screwed up. I'm not quite sure where I went wrong, or how I could even fix it, but I think a lot of it had to do with me not interpreting what was being asked of me. In hindsight, I really should have annoyed the hell out of the proctor with question after question, but in my mind I thought I knew what I was doing.
So, my time management game plan actually worked out well enough because I threw in a config for everything I expected to. However, I really need to go back to Layer2/3 basics but using a different perspective which I hope to get from my recent workbook purchase. I'm actually more pumped than ever right now to go back and retake the lab, but I'm going to force myself to take 2-3 months of back-to-basics training and really make sure that my IPv6, multicast, MPLS, security, QOS, etc. is as good as my L2/L3. When I retake, my goal is to only go to the documentation site for maybe 10-15% of the tasks. And even then, it should be a quick lookup to confirm that I put the config in correctly. In truth, my goal is to be an expert. Just like Cisco expects me to be.
Until next time...
-Congratulations........
His words....
What a roller-coaster ride the last few months have been. At the moment Im just as relieved as glad to have the digits. I’ll be lying if I say I dont want to go again, but for now I’ll be happy to enjoy some free time. Im looking forward to some “bored” moments.
Thank You’s
First of all I have to say thanks for some devine intervention. After the first attempt thinking I passed but failed I realised that I need a bit of help. I needed things to go right, I needed some favors and that is how things turned out on the second run. From day 1 everything went according to plan. Thanks Dad.
Thanks to the best supporter in the world, my best lady for all her patience and understanding. I owe her big time, more than buying something shiny can make up for.
It would also have been very difficult if it was not for my current job/managers. I think it definitely counted in my favor that my first line manager and his manager were both ccie candidates who went big in management. I think they understood what the CCIE lab requires. Every leave application was approved without any questions, a tremendous help, I genuinely appreciate this. Also for the use of company equipment, some devices that were supposed to go into production. I definitely owe my colleagues a beer for making life at work harder for them. After passing the written one manager said that the company would support me as much as possible and I can say they went beyond my expectation.
Preparation
The day I got back home from the first attempt, I looked for seats and was lucky to pickup the Dubai date. In fact I was still in brazil when I start looking for dates. I was quite fortunate to get the dubai date as I booked it within a few hours of it being dropped. I knew that if I could just maintain my level of preparedness for the second attempt and just focus a bit better I could make it. I came up with a plan to just review what I have already done, so everyday after work I reviewed vol2 labs 1-20. I would read the question, think the solution/configuration through, check the solution guide, whether I had the same idea, look whether I missed anything important then move to the next question. It took on average 3 to 4 hours per lab. If I wasnt completely sure about my solution, I would setup a simple scenario and do some testing. This worked well up until a few days before the attempt. I started to think that I need to practise some labs, as I havent done labs for almost a month. I then did the IPexpert sample mock lab, which I am very glad I did. I missed a line in an ACL, or in another question I didnt match the same routes the question asked for. I also lost two questions due to changes I made at the end or reloading the devices. Im glad I made these mistakes, because I made a decision at the end of the cisco lab to look for this type of errors. Again, Im very glad I made those mistakes in the mock lab. This was the only full lab I did before the second attempt. I also worked through the “Lab debrief” of the CCIE RS practical labs shortcut book. I would highly highly recommend working this book. Even if you dont read everything, at least work through the Lab debrief. If you look carefully, there are some differences in the way common tasks are done in this book. I would suggest using this book’s (Cisco) method. After arriving at the hotel I had two days to recover from the traveling, luckily only a 9 hour trip this time, so I started doing some IE vol3 labs. Although I didnt have that feeling you have after getting off a trampoline, which I had in Brazil, I was very tired the day of arriving and the next day. This was mainly due to the flight being during the night and not getting proper sleep on the plane. In this two days I did lab 7 to 10. It was good to get some lab practise, which I feel helped. The core lab is a good concept, but I would not recommend fussing to make your redistribution work as in the SG. One main reason is that the core labs do not have to be graded, so corners are cut. In the cisco lab, there will be very clearly stated how the redistribution should be and should not be done. The redistribution makes sense, as it also has to be graded. After the two core labs a day, I went through Michael Zuo’s notes. Good reviewing material.
Venue
Dubai is hot, very hot, as in desert hot. They say the weather is better in the winter, but I dont know, I think it will still be hot. Two things I will always remember from my trip to dubai: The crane forest and the heat. I had planned to take photo’s of the area to make the scenery a bit more familiar for the next person but got caught up in the moment and totally forgot about this. The taxi drivers all know where the “Dubai Media Center (DMC)”, “Dubai Internet City (DIC)” and “Knowledge Village” are. All three are located close to each other. Cisco Systems are located in building 10, DIC, the driver might confuse DMC with DIC, just something to note. The taxi drivers are mostly from either pakistan or india and work 12 to 14 hours a day with no days off, so to tip is not a bad idea. The 15-20 minute ride from the Ibish World Trade Center hotel to cisco cost about 45 dirhams which is about $10 usd. The hotel is located close to the highway. Apparently you get traffic on the way into the city, but Cisco is located on the way out of the city if I understood correctly. Once you get to the cisco building, if you look like you are lost the building reception would ask you “Cisco exam?” and point you to the 12th floor, after which you get into the elevator and then straight back out because it only goes to floor 4. They will confirm that it is indeed level “twelve” while giving a three finger signal, you get it. Once you walk out on the third floor there is a sign on the right that says “CCIE lab” and “use next door” which points to the kitchen/canteen area. If you are lucky someone will be there already and open for you. Else I guess the next step would be to go to the 4th floor where the Cisco reception is. Once the proctor arrives you go to the lab, no tour or the usual run down, just “Bags there, start time, end time, ok…” Thats the signal to start. He did mention that if any hardware errors are found to let him know as soon as possible. You only get the time back it takes the proctor to fix the problem and not the time it takes for you to determine that it is a hardware problem. I would suggest having a strategy for this as well. If it takes you 15 minutes to determine it is a hardware fault. You go to the proctor to let him know. You go back to your desk and continue with another task, read the lab again, whatever. 15 minutes later he comes back to let you know its fix. At the end you get 15 minutes extra. Use it to your advantage. Lunch was 5 hours into the lab. I would recommend taking some snacks with if you writing at Dubai (and Sau Paulo) as the lunch is not much. At lunch the proctor cleared some common misconceptions regarding the lab and grading. Lunch was a bit short, only 20 minutes and the lab ended 10minutes earlier. Personally I would have preferred a 30 minute break and finish on time.
Proctor comparison
Proctors do vary. Yusuf the proctor at Dubai is tight, water tight. You either get a “Yes/No” or “What you are asking me is a syntax related question, I can not answer you a syntax related question”. He reminds me of Apu Nahasapeemapetilon, for some reason. My favourite response to a question on the day was “Am I the proctor?”. It wasnt funny at the time, but when I think back about it, he has a very dry but cool sense of humor.
Lab comparison
The look and feel of the two labs were totally different. Im convinced they are designed by two different people. One also spell better than the other 
not that Im a literature giant, quite the opposite, but it was something different between the two. The diagrams also looked night/day apart. The wording was also slightly different, with a few questions adding some additional info through words e.g “users have been…, or the network manager wants to…”. This lab had one or two questions that referred to a feature within a technology that I havent configured before, but gave enough clues in the question to find it on the doc cd. Again the questions were not difficult to configure. The first set of questions were particularly ambiguous. A big difference from the first lab. The proctor could not really help here, so I went with a guess that the questions follow on each other and if they didnt give specifics, the question is probably related to the previous question. This was a guess, I could be totally wrong, but couldnt make sense of it in any other way. This was a big time waster for something I think did not test anything on the blueprint. Maybe I missed a keyword. Overall on a scale of 1 to 10 I would rate the lab a 7, two or three sections a 5/6, one section a 8, but only due to the cryptic wording.
Random thought: Why dont they put less emphasis on wording and more on configuration? I mean the best question I have seen to date was in the CCIEpractical studies shortcuts book. The question says exactly what needs to be done. I thought hard and long about it but couldnt figure it out.
This time round I spent more time reading the lab the first time. I also took care in getting my crt windows just right. Fortunately the resolution was higher than in Brazil, so I could get 4 windows aligned, the same way I did in preparation. I was prepared to change the font size from 10 to 8, but did not need to do this as the resolution was good. The workstation was sufficient. The keyboard was exactly the same rubbish they have at brazil, some logitech keyboard that does not have a dedicated “Insert” button. This was highly frustrating the first time to have to put num lock on and off when copy/pasting. SecureCRT probably has some function somewhere to change the copy/paste keys, but I havent figured that out. I practised the two days at the hotel on the laptop, in other words without a keypad, so in the lab I left the num lock off so that I could use the “0″ as the “Insert” button and used the normal numerical buttons for ip addresses/acl’s etc. This worked way better.
The Wait
After the lab if you have to take a taxi back to the hotel, the best would be to go back to the cisco reception. They have the cab company on speed dial and all the details on a pamphlet what you might need to give the operator. Most people have difficulty sleeping the night before the lab, I didnt have this problem, but for me waiting for the results was even worse. I kept thinking “what if”, what if I missed something. What if I didnt check my verification properly. What if something I did broke something else. Very tense moments. I actually labbed a scenario up and made some changes to see if what I did could possibly have broken another. Sigh of relief, it still works. Just after 3am I jumped up at the sound of what I think was a mail coming in, the results email was there. I think it helps to be half asleep or half awake when checking the mail, cause you dont really think what you are doing. I was dreading that moment scrolling down to that section where the PASS/FAIL is written, but as the window opened my eye caught two “PASSES” one for the written and another, it took about 300 milliseconds to realize I passed. What a relief. Open the score report, which only shows the number. Am I seeing right? 21500? cant be, the night before I was looking at recent numbers on groupstudy and worked out that 21500 will be issued somewhere between the day before my lab and the day after. Thats the one that was available that I wanted.
