One of my new books that I've been using is Satterlee & Hutnik's "CCIE Lab
Practice Kit," (007212766X - *mucho* mistakes, but not crippling and they
actually make the labs more challenging) and they claim it's "As Close As
You Can Get" - Satterlee's a CCIE (3980). Now, I've worked through the
first lab (on BGP), and it's basically a 56-step procedure. They give you a
topology diagram, a few general rules (no static routes, can't use "ip ospf
network point-to-multipoint," etc.), then cut you loose.
Now, my question is, is the CCIE Lab equivalent to just one of these labs,
or two, or more? I also shot an email off to the "CCIE team" from CCO
regarding the use of Notepad in the Lab - I've been relying on it quite
heavily, but from what I understand, nothing can be saved to the hard drive
during the Lab. I'd hate to see an untimely PC crash wipe out all my
work....
----- Original Message -----
From: NetEng Phx
To: [EMAIL PROTECTED]
Sent: Wednesday, June 13, 2001 1:14 PM
Subject: What is the Lab 'like'? [7:8366]
All,
I am looking forward to a run at my CCIE next year and I am trying to
visualize what the Lab test will be 'like'. I have read Cisco's material
and searched around a bit, but that info falls short of what I am looking
for here.
I understand the lab consist of essentially two parts; build out and
troubleshooting. How are the Problems/requirements presented?
For example, are you given very high level requirements such as "build a
scalable network" and you make all the design decisions, or are you likely
to get more specific requirements such as; "plan and addressing scheme to
conserve IP space and router resources", or even more specific like:
"select and OSPF network type to use in your network"?
In the troubleshooting section, do they insert faults that you have to
discover, or do they provide you with at least some clue of which high level
functionality may or may not be working? Real world troubleshooting is
usually in response to observed problem, or issue. Is it fair game to have
something tweaked in the configs that is not expressed in any level of
functionality, or lack there-of, on the test pod?
Are the problems presented in writing, orally by the proctor, or both?
Do you deliver to the proctor diagrams, and notes, or just the configs and
cableing on the routers.
Are you required to orally defend your design?
I am not interested in info that violates the agreement with Cisco, just any
input that can help me visualize what it will be like.
Thanks!
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=8434&t=8366
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
