Last 40 days of CCIE Lab preparation

June 17, 2008

Postmortem

Filed under: CCIE — antoniehenning @ 1:50 am

After the lab we went to Rio for a few days to unwind, this was very welcome. If anyone travels to brazil to write the lab I would highly recommend visiting this beautiful city, even if its just for a day. I arrived back home today after another exhausting 10000km trip. I reconstructed the lab and was amazed at how much is possible to recall from the lab. I mainly did this to determine where I could have possibly lost points and to determine wether to go for a remark. I dont have my configs but I pretty much know what I did and did not do. I managed to rewrite the lab except for one question, but hopefully I’ll remember this one later. Of course If I didnt pickup a hidden keyword this is not on my reconstructed lab and Im not 100% sure about the points allocation. I managed to reverse the points from the % from the score and questions where Im sure about the points per question. I now have a good idea of how many points I needed to pass. This is in a grey area where I think a remark might do it, but due to the 0.3% fail to pass conversion rate I have my doubts. Also I would guess that Cisco would be very reluctant to change a grade. Before anyone loose their marbles, I took a read through the NDA to see if reconstructing the lab is a violation, which Im happy to say is not, as long as I dont share it to a third party, which of course I wont. That said I can say that the IE workbooks I used have all the questions I had on the lab, maybe not to the exact word but enough to lead me to believe that the IE workbooks are “based” on a mixture of various real lab questions.

About the lab:
The lab is easier than what people make out of it. I made a decision before writing the lab that I would write the exam same information whether I fail or pass. Of course I want to say that it was extremely hard withall weird and wonderful things on. To give the lab a rating of 10/10 would do my shattered ego the world of good but the truth is, it is not. Reading through the questions I have to kick myself. I failed it all on my own. In IE terms I would rate it at 6, definitely not higher than that. Yes, I missed a few key words but that was my own undoing. The questions are to the point, there is no beating around the bush: configure X to accomplish Y without using Z. Judging from the sections where I didnt loose points I can say that they dont look for configuration that was not requested in the question. E.g. The solution to one question did not make real sense, yes, I could see what they wanted me to do and thats what I did. The output from my solution would match the requirement but if a change in the topology would have had to happen, the required configuration would not be enough. I verified this with the proctor to which the answer was: “The lab is not beautiful or perfect, the questions are constructed to test a certain piece of knowledge”. Since there was no requirement to do more than just provide the output in the requirements so thats where I left it. In short, no hidden configuration needed. The hardest question in any lab is probably redistribution and this I would rate at about 7, all sections ranged between level 5 and 7. The lab is short, I checked twice to see if I have all the pages in the binder. The assessor can be considered as a 3/4 or 75% of a full lab.

About the venue:
First impression was horrible. I arrived at 7:45am, 1 hour before, as I understood, the lab was supposed to start (8:45am). Since I dont speak portuguese or spanish it was quite difficult to explain to the building reception that I have to go to the cisco offices on the 26th floor asap. Cisco employees only start to arrive after 9am, the reception arrived at 9:15. At this point I already thought that Im at the wrong place or that cisco was not aware that there was supposed to be a lab on that day. I was wondering whether they expected the lab to be on the 6th as the original arrangement and that they were not aware of the 11th date. Luckily after the reception arrived and notified the proctor things started to settle down. We had a quick “tour” in other words to show us where the restrooms are and to choose lunch. The menu is in portuguese so I would recommend the proctors choice which was quite good. After the lunch was choosen we got the usual rundown most of which we already knew. The lab started officially at 9:34. Lunch was at 12 and ended at 6:04pm. I will post a pic of the building with un update, but due to rushing to checkout and catching the next flight the photo does not say much. I stayed in the Time Othon hotel which is almost literally a stones through from the “Torre Oeste” builing which either I think means “East Tower” but might mean south tower because the sister tower is the “Torre Norte”. Other buildings around are the World trade center and the Hilton hotel. A taxi ride from the airport to cisco will be about R$107 or 43 euro and about R$120 back. It takes about 1h30minutes, but it depends on the traffic. I would not recommend renting a car in sao paulo, the people there drive like maniacs. The taxi driver couldnt speak english but understood two words “crazy driver” to which his response was “first time sao paulo”.

Some pics of the area (Note, just quick pics I took on the way out with my phone, except for the first one ofcourse which is from google earth)

Cisco is on the 26th floor on the left tower. The time othon hotel is the building in the top right corner. The tower at the bottom is the Hilton hotel. The WTC hotel can also been seen at the top center.
Hilton on the left, Torre Norte in front and Torre Oeste on the right. Just a glimps of the WTC Hotel on the far right.
Another look at the Torre Oeste

Lab strategy:
This is probably one of the biggest contributing factors to the failure. The initial plan was to arrive a day early, take as much rest as possible in the off day to compensate for any jetlag. This was not to be, someone left a parcel unattended which lead to the airport being evacuated and therefore all flights were delayed. This lead to missing the international flight to brazil and the next flight was only the next day. This also ment having to deal with lost baggage which were not heading where they were supposed to go. With all the things that went wrong upto the point of the lab I had a bit of a negative attitude, which I was aware of. I knew it was the wrong attitude but I just couldnt get myself motivated. I was physically and mentally tired. My goal hours before the lab seemed to have gone from passing the lab to just getting over with it. The night before the lab I had to remind myself that I need be alert and focus, that the lab is important, that this “getting over with it” was planning to fail and not planning to pass. During the lab I used the restroom a few times to do this as well. I took the lab way to casually, I was less stressed than I was during the assessors and some of the mock labs. The intensity was definitely lacking. I worked at a reletively slow pace, so it felt. At some point I thought I might not finish with time left to verify. That was how the lab was constructed but by lunchtime I had completed my configuration for full reachability, this was about 3:30minutes into the lab. After lunch I tested reachability and all was fine and went on the complete the lab in 5:45minutes. I had just over 2 hours for verification which I did once slowly and then came back to questions I wanted to verify with the proctor. During this two hours I didnt make any changes, big mistake, I spent time on the questions where I wanted to double check my interpretation of the question. I should have spent that time on the questions I was 100% sure I got right, because those are the areas where I lost points. Again, being to casual was a big contributor here. I did not have to use the doccd to find solutions to the answers. I used it on two questions, one to verify that this feature will work in the condition that they specified and the second to check that the option I was using would match the requirement. This was the only optional command that I havent configured before the lab.

Positives:
The lab is most definitely passable. I definitely had the right preparation. I actually think I over did it. One month before the lab I thought I have a chance of passing and I dont think this was way off. Lab is passable for anyone that really wants to pass the exam. It is not how smart you are but more a case of “have you done this before” and being as “articulate” on the day of the lab as possible. The last is probably just as important as good preparation. It is important to include the configuration that cant be verified or not critical to the solution to “make it work”.

Negatives:
Somehow I get the impression that the accuracy required in the lab is like subtracting points for spelling mistakes in a maths/science exam. What I mean is that if you get to the right answer you should receive all the points irrespective if you did the calculation in your head or used a different name to reference a variable, or in networking terms, using a difference process name.

updated

June 12, 2008

D-day

Filed under: CCIE — antoniehenning @ 9:34 am

Unfortunately I didnt make it. When I walked out I thought I nailed it. The exam it self was quite easy, but I obviously missed some important detail. I cant believe it, is what I’ve been saying for the last hour. I genuinely can not believe it. I will have to accept it quickly and get a strategy to take it again as soon as possible. The test is easy, to the point, its not an IQ test, its more of a accuracy test. Thats my take on it. Why and how I lost points I have no idea. I can guess on one or two questions that I might have missed something, but on one particular section I have no idea how it could have been wrong. Looking at the score report, I have to say that I can genuinely not believe it. I will think about asking for a remark, but for now I will take a break for a few days.

Another sad part is that I travelled 10 000km to take the exam while this very week cisco has a mobile lab right on my doorstep. I found that out when the proctor asked “where you from?”. The trip to here was a bit of a desaster, due to a bomb scare we missed our flights to brazil and we arrive at the hotel at sao paulo with the lab starting in 12 hours. I had a feeling of sea sickness during the lab that I dont quite know what it was, that didnt help, but I dont think this was the reason for the failure.

On the bright side, now I have a chance at getting ccie 21337, which would more than make up for one failure. I will write some more about the lab in a few days when I get back home.

June 8, 2008

2 Days to go

Filed under: CCIE — antoniehenning @ 9:20 pm

Today I spent browsing/reading the doccd, nothing intense, just browsing, noting where most things are. Im not sure how well I should know the doccd, but I can pretty much find everything I configured thus far. Also came across somethings I forgot already, so I think the review was good. Dynagen has been loaded on the laptop just incase I want to see the syntax of a particular command. The cpu should handle atleast one instance. Bags are packed and ready for the long trip tomorrow.

June 7, 2008

3 Days to go

Filed under: CCIE — antoniehenning @ 11:40 pm

1:40am Did quite a bit of reviewing. I saw some things I forgot already, so it was a good to review. Tomorrow I will browse the doccd. I will try not to read too much as I find myself often distracted by trying to find out to much detail regarding a specific feature or technology.

Last thought regarding the Assessor lab: Im not quite sure what to think about the ability to use the assessment report only during the first 4 hours. During the first 4hours I see it as a test, why allow access to the assessment report before the time runs up. I was just thinking because I made such silly mistakes I could have easily fixed them. Just maybe it would be better to use the feature in the second session. Im probably missing some point somewhere…

Mock lab scores summary:
Mock lab 3 53 to go = 71
Mock lab 2 44 to go = 79
Mock lab 5 40 to go = 42
Assessor 1.6A 33 to go = 74
Mock lab 6 25 to go = 74
Mock lab 1 12 to go = 80
Assessor 2b 5 to go = 72

The 70’s seem to be my lucky number, but on every lab there were debatable points which I hope to squeeze out of the proctor somehow. This plus working carefully, I think its doable.

June 6, 2008

4 Days to go

Filed under: CCIE — antoniehenning @ 5:14 pm

6:40pm Ok did the assessor 2b today without any hassles, which was nice. After the lab I felt I nailed it, sure I passed. Then the report came and I failed, 72%. I didnt go through the answers to check what I got wrong so I immediately started to feel a bit disposed. How is it possible that after ending the lab Im sure I passed yet the score says a different story? Is it at all possible to pass? After the one hour break I went through the answer to see what I got wrong and the mood changed. All 14 points that I lost was due to reading errors. It is interesting to note that I lost all 14 points in the sections that I did 1hour after the lab started untill just after 2hours into that lab. That means in a period of about one hour to 1 hour and 15 minutes. This directly aligns with the period that I thought Im not going to be able to complete the lab. After the 2hour 30minute mark I realised I will complete the lab and slowed down. I finished with 25 minutes to spare. But this time went quick, I was able to make one change that actually added points but only covered the first hours work when the time ran out. Ok, this might sound ironic but Im glad I made those mistakes in the assessor. That is something I can learn from, I dont have to rush, I will complete the lab, do it right the first time. How I lost points:

No spoilers:
1) Didnt configure easy requirement on all devices. Unforced Error
2) Skipped an easy requirement. Completely missed the line. Unforced Error
3) Cisco hates route-maps. Ok ok, I got the point already. Avoid route-maps at all cost. Should’ve learned from assessor 1.6.
4) Questions says use a specific value and I went and used my own favorite value. Didnt not see the difference in the question e.g. If you use bbb.ddd often and you dyslexic like me, when you read ddd.bbb, they are one and the same thing. Next time I’ll be prepared.
5) Again question says use a specific value and I didnt care to take notice.

All soft issues, the route-map is again debatable. In cisco land a line calling a route-map is one “command”. In programming land that would be called, a subfunction, but I guess cisco makes the rules in cisco land.

After seeing my mistakes and knowing why I made them, I gained hope again. It is possible.

2:25am Spent quite a bit of time reviewing today. Updated the checklist, will print this out, just in case.

June 5, 2008

5 Days to go

Filed under: CCIE — antoniehenning @ 7:34 am

9:30am Woke up this morning with half the answer to the multicast issue yesterday. I obviously was not thinking straight at the time. I’ll work some more on it this morning, I think it will be useful. Today I want to review some sections of the technology focused labs. Some of the features are only covered there and its been a few months since I did them. Ip Services will be one of them. After that I want to read through the vol2 ip services sections. Depending how much time is left, I might read through the multicast sections as well.

Brazil is 5 hours behind my local time, everyday my schedule starts and ends 30 minutes later. Trying to compensate a bit for any jet lag there might be.

11:40pm Today felt like I put a lot of effort while not making much ground. I’ve been at the reviewing for 12 hours but it feels like I made an hours progress. A bit frustrating at this point. I came across Ethan’s Doit Notes while searching for the nssa fa-suppress feature. Im glad I got there because I started to go through his other doit lab notes as well. Also used Arden’s blog to review 6to4 tunnels and the bgp inject map. There are very valuable information on these two blogs, will definitely revisit some of the links. Tomorrow morning I have the last assessor, last time they had some technical issues so this is a retake. Will give it my best, this is the last of the assessor/mock labs.

Ok is that 100hours left untill the lab? oh no… On the bright side I can still put in 50hours of reviewing.

June 4, 2008

6 Days to go

Filed under: CCIE — antoniehenning @ 5:12 pm

* Mock Lab2 spoiler ahead :)

7pm Mock lab2 complete, made one mistake from what I can spot with the eye. Again on the same multicast question I lost marks on the first time. Requirement is for auto-rp mapping agent not to allow any other rp to group mappings. The solution is to create two mappings for the known two rp’s and then to make a third rp to group mapping denying ANY group:

ip pim rp-announce-filter rp-list NOT_R2_OR_R4 group-list NO_GROUPS
!
ip access-list standard NO_GROUPS
deny any
!
ip access-list standard NOT_R2_OR_R4
deny 150.1.2.2
deny 150.1.4.4
permit any

Starting mock lab6 now, trying to complete it by 12am which gives me 5 hours.

1:30am Mock lab6 completed. Havent gone through the answer sheet yet, will do that tomorrow. Completed in 5hours 15minutes with. Had to take a 1hour break since 7pm.

I came across the same problem I had while did the lab for real. One of the routers would respond to two multicast pings and after that timeout. I found a way to fix it but Im not sure whether I should spend time trying to find out why this fixed to problem or why to problem occured in the first place. I now know it has something to do with the topology and not the equipment. Not much time to explain this, but here is the output on the mapping agent during the first two pings (R5 is the mapping agent and also the first hop from the RP R3 where the packets are coming from, going to the destination R2 239.2.2.2 ):

Rack2R5(config-if)#
*Mar  1 04:52:55.018: MRT(0): Reset the z-flag for (176.2.35.3, 239.3.2.2)
*Mar  1 04:52:55.018: MRT(0): Set the F-flag for (176.2.35.3, 239.3.2.2)
*Mar  1 04:52:55.018: MRT(0): Create (176.2.35.3,239.3.2.2), RPF Ethernet0/1/0.0.0.0
*Mar  1 04:52:55.018: MRT(0): WAVL Insert interface: Serial0/0 in (176.2.35.3,239.3.2.2) Successful
*Mar  1 04:52:55.022: MRT(0): set min mtu for (176.2.35.3, 239.3.2.2) 0->1500
*Mar  1 04:52:55.022: MRT(0): Add Serial0/0/224.0.0.2 to the olist of (176.2.35.3, 239.3.2.2), Forward state – MAC not built
*Mar  1 04:52:55.026: IP(0): s=176.2.35.3 (Ethernet0/1) d=239.3.2.2 (Serial0/0) id=248, prot=1, len=100(100), mforward
Rack2R5(config-if)#
*Mar  1 04:52:57.166: MRT(0): Update Serial0/0/224.0.0.2 in the olist of (*, 239.3.2.2), Forward state – MAC built
*Mar  1 04:52:57.166: MRT(0): Update Serial0/0/224.0.0.2 in the olist of (176.2.35.3, 239.3.2.2), Forward state – MAC built

Ok so at this point the timeouts start. I fixed it with a “no ip mroute-cache” on the interface between the RP and Mapping agent. If I run into something similar this is one option to try, but I would like to know why this solved the problem and why it occured in the first place and why the IE solution guide does not 1) detect the problem and 2) not have a solution to it. I cant see that Im doing anything different from the rest of the solution guide, but then again it is 1:30am.

June 3, 2008

7 Days to go

Filed under: CCIE — antoniehenning @ 9:07 pm

23:03 Today I redid mock lab 3 (5h15) and mock lab 5 (5h30). It is interesting that I made or almost made the same mistakes as when I wrote them “for real”. I missed the same words or phrases. I got the mock lab 1 score as well, I scored a highly disappointing 80 because the ipv6 ip that I wrote about on 11 Days to go and the error in the initial configs that I fixed but changed to the original due to the lab restrictions cost 14 points. The inconsistency with tracking frame-relay interfaces that I wrote about also cost 3 points. How and why this could be wrong is beyond me. I made one genuine mistake, I removed a route-map without removing it from the bgp neighbor which caused all routes from that neighbor to be dropped. I should’ve got 97 for this one, i went as far as to write IE a mail about the result. Maybe Im just getting a bit edgy with 7 days to go. Well today is gone, 4 full days of labbing left. Tomorrow Im redoing mock lab 2 and 6. Im hoping these two would go under 5 hours. What does amaze me though is that it feels that I am working slower than when I did them for real but Im finishing way earlier. Thursday I will do what I cant get done tomorrow, but Im hoping to complete both tomorrow. I dont have any material at the moment to review, I will have to come up with something.

June 2, 2008

8 Days to go

Filed under: CCIE — antoniehenning @ 5:08 am

7am Long day planned, have to get as far as possible into vol3 lab7,8 and 9 today. The more done today, the less to do tomorrow which means more time to review the mock labs.

9:25pm Vol3 Labs 1 – 10 complete. Im glad I finished one day early as two days is about as much as these labs are worth. If you are paying for lab preparation yourself, I would suggest you give these labs a skip. The labs are very light on switching and bgp, medium on WAN and heavy on IGP. The switching, wan and bgp take roughly 1hour while the IGP take 2hours+. Redistribution is especially “involve” and takes at least a 1/4 of the total lab time. Almost every lab is designed around discontinued ospf areas that either has to be bridged with many virtual-links, tunnels or redistributing between two ospf processes. That was my experience. Glad that is over, now I can focus on redoing the mock labs. Im eager to get back into multicast and ipv6. Been missing the security and ip services sections as well. This reminds me I need to make a note to review all ip services sections of the vol2 labs. What I did enjoy about the labs is that quite a few had bridging in the wan section which Im glad I got right without the SG. This used to be a weak area, which I think Im okay on now.

+-70hours of preperation left. I can still patch a few holes in this time.

9:50pm Just read an article in the press that our company is up for sale. More reason to get back to labbing, make that 80hours to come.

00:35am Had a bumper 14 hour day today, but paying for it now, as usual it takes a while to shutdown. Will probably loose a few hours tomorrow. The initial configs for lab3 are loaded. I think Im addicted to labs. They have become a part of life. I might keep the rack, we have developed a strong bond. I just had a look at the calendar and its the 3rd June, labbing has kept my mind occupied so I havent been thinking about the lab. In a way this is good on the other side I need to make sure Im mentally prepared as well. Just need to take it easy, still have 70-80hours to patch the holes. Will use the doccd a bit more than needed when redoing the mock labs. Thats probably the next area that needs a bit of meat. I read these 20 tips for the ccie lab before but read it again on the groupstudy mailing list. The one that stands out the most to me:

12) Don’t forget that a router’s greatest emotional need is to feel
appreciated

June 1, 2008

9 Days to go

Filed under: CCIE — antoniehenning @ 4:58 pm

Took some reset today, but felt the urge to try another vol3 lab. I will start lab6 now. The more I look at what still has to be done before the 9th the more I realise that today was probably the last day of relaxing before the lab.

Recap of what has been done and what still has to be done:

Completed:
Technology Focussed labs x 2
Vol2 Labs 1 – 20 x 2
Vol3 Labs 1 – 5 x 1
Assessor v1.6 x 1
IE Mock labs x 5

Still to be done
Vol3 Labs 6 – 10 x 1 : 2 – 3 June
Redo Mock Labs 3 and 5 : 4th June
Redo Mock Labs 2 and 6 : 5th June
CCIE Assessor Lab v2.0b : 6th June
Review notes and configs : 7th June
Quality time with the doccd : 8th June
Reread Assessor lab configs : 9th June while traveling

Schedule for the past week:

22:20 Lab6 complete. It took roughly 4hours but the redistribution alone took 1 hour. My solution was totally different from the SG. What is the possibility of completing 7,8,9 and 10 tomorrow?

Blog at WordPress.com.