From: Ron Trunk (rtrunk@xxxxxxxxxxxxx)
Date: Thu Aug 19 1999 - 15:33:06 GMT-3
Dennis,
Here's a copy of a posting I made after my first attempt. It reflects my
experience with the lab and many on this list concur, although some have
taken execption to the last item.
(Apologies in advance to anyone who doesn't want to read this again.)
Hope this helps!
Ron
>1. Know the documentation. Know how it is laid out and where things are.
>For every feature you have studied, know where the information is in the
>documentation. They will ask you to configure odd things that they don't
>expect you to know the syntax off the top of your head. They want to see
>if you can look things up quickly and figure it out. I was asked to adjust
>some obscure cache on the router. I had no idea what the syntax was, but I
>knew exactly where the information was in the manuals. I found it and set
>it up in less than a minute.
>
>2. Know the equipment. Go to the CCIE pages on cisco's web site and look
>at the equipment list. Are you familar with all the equipment and know how
>to do the basic configurations? I had never worked with a token-ring
>switch. Although I got it working, I spent too much time figuring it out.
>Read the configuration guides so you're familiar with them. When you need
>to set it up, you can refer to them as needed (because you know the
>documentation!)
>
>3. Save your configs. Often. Don't forget. I had set up all my BGP
>stuff on one router, then in the next section I did something that caused
>the router to reboot. Goodbye BGP config. Furiously typed it back in and
>got it back up, but in my haste, didn't realize that I had also wiped out
>my ISDN config. Lost a lot of points on that.
>
>
>4. Look over the steps and see which ones depend on earlier steps. Make
>sure you take this into account when doing your design. Take Caslow's
>advice and write down each "issue" for each step.
>
>5. Remember that you need to get points, so plan to do the steps to get as
>many as possible. Don't waste time on a 1 point question that you're not
>sure about when there is a 3 point question that you know how to do. There
>are things you may not know how to do right away. Put them off till last.
>Get all the points you can out of the way.
>
>6. Remember that you need to get points (should I repeat it again?) You
>may be working on something that is easy. You've done it a hundred times.
>It's just a couple of config lines. It's always worked in the past. But
>its not working now. Don't spend all day in frustration. Stop and go on
>to the next problem. Come back if you have time. Don't do extra work.
>If they don't ask you to do it, don't waste your time on it. It won't help
>you pass.
>
>7. Caslow is absolutely right: Work layer by layer.
>
>8. The lab requires you to make a configuration diagram (as if you
>wouldn't otherwise!). They give you paper, pencils, pens, highlighters (I
>had my "nerd-pack" in my pocket - didn't need any of it). You get no
>points for neatness, it simply has to be readable. Some guys brought
>drafting templates and rulers so they could make a very clean diagram. If
>you're the retentive type and that's the only way you can work, OK, but I
>think it wastes a lot of time.
>
>9. The lab proctor is there to help you. That is worth repeating: the
>lab proctor is there to help you. The proctor is not the enemy. The
>proctor is not the judge. The proctor is there to help you pass. Don't
>feel embarrassed about asking stupid questions. If you're not sure about a
>test problem, ASK. If the equipment rack is a little confusing, ASK. If
>you think there is a hardware problem, ASK. If it just turns out to be a
>mis-cabling problem, that's OK. If there's an area that you're not really
>up on, don't let pride stop you from asking for clarification. The proctor
>will not take off points for questions no matter how stupid or trivial.
>
>10. In the San Jose lab, there is a whitebord in the back that has some
>important information on it for setting up your configs. Be sure you read
>it. I started the ISDN section and nothing in the test told me the switch
>type. Was I supposed to guess? Was there some sort of auto-detect command
>that I didn't know about? I went all through the equipment rack to see if
>there were any clues. Finally got it by trial and error. Then I turned
>around and there it was on the whiteboard!
>
>11. My last piece of advice for those of you who are planning to take a
>prep course or a practice lab. In my opinion, your money is better spent
>taking the actual lab. You may not pass, but you will know exactly what is
>expected of you. You will know exactly how you will have to perform and
>what the environment is like. That's the best preparation posible.
>
-----Original Message-----
From: Rogell, Dennis <Dennis_Rogell@milgo.com>
To: 'ccielab@groupstudy.com' <ccielab@groupstudy.com>
Date: Thursday, August 19, 1999 2:19 PM
Subject: ccie lab
>I am new to this list and I am scheduled to take my test on oct.26 I was
>wondering if anyone has any tips on preparing for the test.
>
>Thanks
>
>Dennis Rogell
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:47 GMT-3