From: Jim Brown (Jim.Brown@caselogic.com)
Date: Mon Sep 16 2002 - 18:58:19 GMT-3
I personally don't think you have enough time for your suggested
approach. Time is SO valuable in the one day lab and there isn't usually
much to spare.
I cruised through the requirements looking for IP addresses and
configuration issues. I made mental notes of what was required for each
protocol and then started banging out the configs.
I totally skipped diagramming on my successful attempt. Cisco provides
diagrams with enough information to save you the time of creating your
own.
Too put it in perspective, I was configuring the hardware 12 minutes
after we got the green light from the proctor.
You are right about the details. They will kill you. Not being thorough
in my checking kept me from passing the lab for a year. Check, check,
and check again. Even when you know it is right, check it again. Use
every single minute they give you.
Different things work for different people, YMMV. I remember reading a
post about a person who passed the lab without any hands on experience.
He just read and memorized configs because he didn't have the money or
access to equipment!
There is no way I could ever imagine passing the monster using
memorization.
-----Original Message-----
From: Joseph Rinehart [mailto:jjrinehart@hotmail.com]
Sent: Monday, September 16, 2002 3:34 PM
To: ccielab@groupstudy.com
Subject: Methodology
New Thread, dealing with strategy.
Personally I feel that I will probably be ok in terms of the technology
and
overall configuration. I am not claiming to be prepared yet, but I am
saying I think that part will end up adequate. My question is about
strategy, because even in my practice sessions and hands on stuff I find
its
stupid little stuff that tends to kill my effectiveness (mistyped
commands,
forgetting to put in something I even had written out, etc.)
My approach is usually to read requirements, read them again, and then
start
by drawing a diagram, and including addressing and other pertinent
information. Next I will write out a configuration and go over it
several
times, and only then start coding the routers.
What do you feel is a reproducible strategy to the lab? What
methodology
helps minimize mistakes and confusion and helps you avoid throwing away
points outr of sheer stuidity?
Joe
This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:54 GMT-3