Read um and Weep Here’s the short list of books I would recommend to read (at a minimum) during your lab PReparation. Find yourself a shady spot outside, and crack the spine of each of these page-turners; it’s the only chance you’ll have to see the sun for a few months:
Cisco Certification: Bridges, Routers and Switches for CCIEs, Second Edition by Andrew BrUCe Caslow
Internet Routing Architectures, Second Edition by Bassam Halabi
CCIE Prof. Development Routing TCP/ip Volumes I & II, Jeff Doyle
Cisco LAN Switching (CCIE professional development)
Cisco Catalyst LAN Switching by Louis R Rossi, Louis D. Rossi, Thomas Rossi
Configuring Cisco Routers for bridging, DLSW+, & Desktop Protocols by Tan Nam-Kee
My own lab prep book, once I finish writing it (look for it sometime in 2003)… J
Building your own Pod:
One of the most important elements of your CCIE lab preparation is having equipment to practice on. My advice would be put together a home pod watching every dollar very carefully, and then sell it on ebay when you’re done. If you do everything right, your practice time should only cost you the interest on your credit card, and the depreciation in the value of the equipment. What follows is a list of what I think has the makings of a great CCIE Lab practice pod:
· One Cisco 2511 router to use as a terminal server. A 2509 would work fine if you have one, but trust me, before long you’ll need the extra ports.
· A router with multiple Serial ports to use as a Frame Relay switch. Cisco 2522’s are popular for this, although in my own lab I use a 2610 with an 8-port serial module.
· Two Cisco 2503’s.
· One Cisco 2504 (for the FatKid labs).
· Four or five more Cisco 2500 series routers with a selection of Serial, Ethernet and Token Ring ports, (I love 2513’s, because they have all three).
· One ISDN emulator.
· Two 3550 switches loaded with Enterprise software.
· One Cisco 3620 or 2620 with at least one Fast Ethernet port and a pair of FXS ports for VoIP.
· Two CAB-OCTAL-ASYNC. These 8-lead octal cables (68 pin to 8 male RJ-45s) are used with the terminal server
· One MAU.
· Lots of DTE/DCE serial cables, AUI adapters, patch cables, and crossover cables.
* Please note that all 2500 series routers should have 16 Megs of memory, 16 Megs of Flash and be loaded with an Enterprise Version of 12.1 IOS appropriate to its physical configuration.
The only things missing from the list above is ATM and a Token Ring switch. I consider ATM just too darn eXPensive for a home pod, and a 3920 is hard to get, expensive, and easy to configure. For both these technologies, I would recommend renting some on-line lab time.
OK, The Equipment Looks Good on the Rack, Now What?
You’ll also need practice labs to run on your routers. Here’s a list of lab materials I think are useful, in order of complexity (easiest to hardest):
· Cisco CCIE Lab Study Guide, Second Edition by Stephen Hutnik and Michael Satterlee
· CCIE Practical Studies Volume #1 by Karl Solie (Cisco Press)
· www.FatKid.com (these have the added advantage of being free)
· www.solutionlabs.com
· www.IPExpert.net
· www.boson.com
· www.CCBootcamp.com
Advice on Preparation:
Know the CD. When you’re in the lab, this will be one of your few friends. Know where the command reference are, and most importantly, know where the sample configurations are. Think how much time you can save if you cut-and-paste samples from the CD into your configurations.
Print out and keep posted on the wall a copy of the exam blueprint. This should be a constant reminder of what you know, and what’s left to figure out.
Avoid first time pressure. Only a small percentage of people pass on the first attempt, and your four digit number is not de-valued if you make several attempts. Prepare for what you expect the exam to be, but be ready to accept the first attempt as exploratory expedition; a chance to map the terrain for future trips. Who knows; the extra calm of reduced expectations may actually help you pass.
Watch the news feeds at www.groupstudy.com, these are Excellent free resources. People are always posting problems, and working out how to help them not only builds goodwill, but also helps develop your own understanding of these technologies.
Focus on the core technologies; ISDN, Frame Relay, bridging, routing protocols, redistribution, etc. These will represent the bulk of the points in the lab, and you MUST have a very firm understanding of them to have any chance at all.
Have a bucket of tools at your disposal. You should have a good grasp of IP Tunneling, Bridging, NAT, IRB, CRB, route filters, passive interfaces, adjusting Administrative Distances, as well as summary, default and static routes. You never know when these will come in useful.
Search on-line for resources that might be useful sources of equipment, practice labs, advice, configurations, etc. Remember the old standards: www.groupstudy.com, www.ccbootcamp.com, www.fatkid.com and, of course, www.cisco.com.
Budget your time like you would budget your money, conservatively. Once you’ve got a lab date, review the exam blueprint and figure out how much time to spend on each technology, leaving at least 30% of your available time for performing multi-technology labs, like the ones from CCBootCamp.
formalize your notes. When you force yourself to write something for others, it forces you to really understand what you’re talking about.
Don’t exclude your spouse, children, friends and significant others. While the CCIE is a valuable certification, its meaningless without having people around who can help you spend the money once you get it. I know one fellow who taught his wife the basics of IOS so she could introduce problems into a finished configuration to help him practice troubleshooting (not a formal part of the exam any longer, but still something you better know on lab day).
Enjoying the actual Lab experience:
Don’t start entering configuration commands until your initial network design is complete, carefully detailing IP addresses, masks, routing areas, links, tunnels, etc.
Use a list of well practiced alias commands. These will save keystrokes and the frustration of mis-keyed commands.
Make sure you know how to disable DNS lookups and prevent messages appearing on the screen while you’re working.
Type up templates of common configuration elements in notepad to facilitate cut-and-pasting. I have a standard router config that includes all my aliases, loopback interfaces, line configurations, etc. Whenever I’m starting a practice lab I type it up in notepad and paste into each routers. Cutting and pasting is a lot faster and more accurate then typing things over and over again.
Cut-and-paste addresses and other lengthy information from show commands to prevent mistakes.
The best time to save your configurations is when you’re getting ready to change routers. Get use to doing a “wr” just before you move from one router to another. This will make sure you save often, and avoid the long delay of watching a configuration get saved.
Create ping scripts; a set of ping commands stored in text format that can be pasted into a config to test connectivity to all devices on the net.
When talking to the proctor, always be respectful; keep your questions to the “yes” and “no” varieties, and notify them as quickly as possible if you suspect an equipment failure. Above all, don’t create a hostile relationship with the proctor, and if they create one with you, swallow your pride and do what you need to do to keep the channels of coOperation open. Consider it good practice for the real world later.
Conclusions:
I hope this document gives you a place to start your CCIE Lab preparations. I expect we’ll be seeing each other in the CCIELAB Groupstudy e-mail feed, but please feel free to contact me directly if you feel you have any hints to add to this document, want me review your notes for accuracy, or just to brag when you pass…
