CCIE Pursuit Blog

March 31, 2008

Internetwork Expert: Mock Lab I Review

Mock Lab: 1
Difficulty Level: 6
Date Completed: 26 March, 2008
Final Score: 89

NOTE: I will be discussing very few details about the actual tasks on this lab.  If you are planning on taking this Mock Lab then you can read this post as will have few (if any) “spoilers”.   🙂 

I purchased 4 of Internetwork Expert’s Graded Mock labs back in December when they were on sale for $99.  The current cost is $129.  I completed the first of my 4 labs last Wednesday.

On your IE member page you’ll see a section for Graded Mock Labs (emphasis mine):

Your mock lab number will be locked in 1 hour prior to your session start. Once your session has started, a “Start” button will appear. Click the “Start” button to receive your lab, topology, physical topology, and configs.

If you do not click the “Start” button within 1 hour of the start of your session, it will automatically be started for you. Once your mock lab has started, you have 8.5 hours to complete it, and a timer will appear telling you how much time you have left. You will be automatically kicked off your rack at the end of the 8.5-hour lab.

Your mock lab will be graded by 9 PM PDT on the second business day.

Click “View” to open a pop-up window displaying your graded mock lab. Click “Overdue” to automatically send a support ticket about not receiving your graded mock lab.

NOTE: The password to open password-protected PDFs is your e-mail address.

My lab was scheduled for 10 am PDT (noon for me).  Sure enough, once noon rolled around there appeared a button to start the lab.  Once you click this button you will be presented with links for the PDF files for the lab, the topology, and the physical topology (cabling).  Anyone who has done the IE Volume II (or Volume III labs) will be familiar with the documentation.  You’ll get a logical Layer 3 document as well as a routing protocol map.  Although I did not need to provide a password, if you are prompted for a password for any of the PDFs, use the email address that you have registered with you IE account.

One thing to note is that the instructions on how to access your rack is located in a different part of your IE membership page.  It’s in the “My Current and Future Rack Rental Sessions” section.  You’ll probably want to familiarize yourself with the rack documentation.  I’ve rented IE racks before so I was familiar with the process.  Although I didn’t do it (only because I didn’t think about it), it’s probably a good idea to log into your rack and open your reverse telnet session before you click the button to get your documents.

One thing to be aware of is that as soon as you click the button to begin the lab the clock will start ticking.  You’re given 8.5 hours to complete the lab.  There is a cool countdown widget on your IE member page that will run through your lab so you can easily see how much time has elapsed and how much time you have left.

Mock Lab 1 Timer

As soon as you click the “start lab” button the clock starts counting down.  I didn’t think about printing the lab until after the lab had started.  Since I was at home I had to load drivers on my laptop before I could print to my ancient Canon printer.  By the time I had printed all of the documentation and logged into each of the devices I had already lost 15 minutes.  As I mentioned above, it’s a good idea to log into your rack before starting your lab.

One of the resources that becomes available once you start the lab is a zip file of the initial configurations.  I had already lost 15 minutes printing and logging in to the rack.  I was a little pissed that I would need to apply the initial configurations.  The initial configurations are already loaded on your rack so you don’t need to worry about that.  The intial configurations are provided so you can redo the lab later (or rebuild your rack if you really fuck up).  Whew!!!

So I was up and running with 8 hours and 15 minutes to go.  The IE documentation states that after 8.5 hours you will automatically be kicked off of your rack.  I’ll spare you the task of reading the rest of this post and just tell you that this did not happen in my case.  When the timer finally hit zero I was not kicked off of the rack. I didn’t make any changes at that point and the initial grading script ran within 1 hour of my time elapsing.  [I can’t remember when it ran, it may have run right after time expired, but the score was on my member page less than an hour later]  Your experience my not be the same, so I would just assume that your going to be booted off. 

As I posted earlier the grading script will run and give you an initial grade.  Don’t get too depressed about your initial score from the script as it is likely that you will get more points once a proctor reviews your lab. 

Initial Scoresheet Graded By Script

Within two business days a proctor will manually grade your lab and you’ll be able to see a web page with your final grade along with the proctor’s comments and feedback. 

Proctor Feedback

I read the complete lab and made notes before I started configuring anything.  Reading the lab and creating a simple layer 2 diagram took 22 minutes.  After that I kept track of the when I completed each task as well as how confident I was that I had earned the points.  I had completed IGP redistribution and basic BGP peering just before I took “lunch”.  Lunch turned out to be the 20 minutes I spent picking up my son from school.  🙂

I had finished all of the tasks that I felt I could complete with about 30 minutes left.  I ended up not attempting 3 tasks. I spent quite a bit of time troubleshooting an issue that was probably due to an IOS bug, but I had plenty of time to complete the lab.  I did start getting mentally fatigued about 6 hours into the lab.  If I could have stayed a little more focused I could have finish about 30 minutes earlier.  When I finished, I felt pretty good about meeting my goal of getting 80 points.

When your time expires you’ll see a new link to the solution guide.  I didn’t have the energy or inclination to look through it at the time.  I looked at it briefly this weekend.  There are no breakdowns like in the Volume II labs, only the correct configuration as well as some good verification commands.  The Graded Mock Labs are supposed to include a Class On Demand breakdown of the lab.  I haven’t received a link to that yet.  That will probably include the task breakdowns.

I’m not going to go into details about the lab itself other than to say that it was fairly easy.  The lab has a difficulty level of 6 which is easier than the actual lab.  After spending most of the prior 10 days getting my ass handed to me on level 8 labs, this lab seemed pretty easy by comparison.

On Sunday I got the email saying that my lab had been graded by the proctor.  I was very happy (and a little shocked) to find that I had scored an 89.  Since I had skipped 9 points, so I only failed one of the tasks that I attempted.  I missed it due to a stupid mistake in an ACL, but I’m not complaining because there were at least 3 tasks that I got full credit on which I was unsure about my solution. 

Proctor Graded Scoresheet

Random Thoughts:

Finishing with 30 minutes to spare is nice, but I didn’t have time to go back over my tasks to catch stupid mistakes.  I still need to increase my speed.  As I stated earlier, there was a period about 6 hours in where I lost my edge.  I was making silly mistakes and I would end up reading and rereading tasks as well as configuring things twice (because I forgot I had just configured it) as well as forgetting what device I was on.  Nothing major, but in a more difficult lab this could have been a big problem.  As it was, I think that I probably lost 20 – 30 minutes during that stretch just to lack of focus.

I need to limit myself to items that will only be available in the lab as well as curb practices that will not be allowed in the actual lab.  I’m still using Tera Term as my telnet client.  It’s not hugely different from SecureCRT, but I need to make sure that I am more familiar with SecureCRT, especially the cut and paste hot-keys/options.  I also need to stop writing notes on the lab and lab diagrams.  This is not allowed in the actual lab.  I also need to start getting used to using notepad without saving or closing the notepad instances.  Finally, I keep the lab topology open on my laptop so that it’s visible in the background while I’m working.  This is not allowed in that lab, so I need to nix that habit as well.

I was lucky.  I done over 60 hours of IE labs over the 9 days prior to my mock lab so I had more practice with some technologies that I am normally weak on.  I also watched the IEATC session on setting up a logging server and configuring NTP the night before the lab.  Normally, I would have spent much more time using the DOC CD for those topics and I probably would not have received any of the points for NTP because I totally misunderstood key aspects of that technology until literally the night before the mock lab.  Multicast was very simple.  This is the first time that I’ve ever received all of the points for Multicast so you know it was dead easy.  🙂

I knew which technology to use for each task I attempted as well as how to implement it with minimal need of the DOC CD.  I’m not saying this to brag.  I’m saying it because I still finished with only 30 minutes left.  A more difficult lab would have meant more time mining the DOC CD and therefore more time to complete the lab.  I also completely skipped three tasks.  I somehow need to pick up my speed.

Anyhoo….I’m pretty pleased with my score, but I still realize that I have a LONG ways to go before I am ready for the actual lab.

Question Of The Day: 31 March, 2008

Topic: IPv6

FastEthernet0/0 is up, line protocol is up
  Hardware is AmdFE, address is cc00.17b4.0000 (bia cc00.17b4.0000)
  Internet address is

r1(config)#ipv6 unicast-routing
r1(config)#int fa0/0
r1(config-if)#ipv6 address 2001:B00B:1E5:1::/64 eui-64

What will r1’s fao/o IPv6 address be after this configuration is applied?

Click Here For Answer

Yesterday’s Question

 Question Of The Day: 28 March, 2008 

Topic: Route Summarization

You have the following subnets in your network:

Write a single summary route that will encompass all of these routes while being as specific as possible.


Since the first two octets (132.16) are the same we need to look at the third octet.  Since we’re writing a single line we can just use the lowest (2) and highest (181) values:     10000100 00010000 00000010 00000000 10000100 00010000 10110101 00000000

I this case we can see that the first bits that are different the first bits of the 3rd octet.  We can stop right there.  Everything before those bits will be our network address ( and the rest will be our mask (  Our summary will be

Route Summarization

Create a free website or blog at