AW: Advice on reading the whole lab before starting?

I fully agree with Piotr. You do not have to read each detail but after your
proper LAB preparation you know what you have to look for while reading
through the tasks.

For example: As you know, you have to take care about your OSPF network type
setup in regards to the frame-relay config or for example if you configure
HSRP and afterwards you have a task which tells you that you have to
configure port security on your switches.

All these things have dependencies and it is much easier if you discover
them in advance which might prevent you from doing unnecessary changes or
corrections during your lab.

At the end it is up to you and a question of "personal strategy".

Good Luck!

Roger #24543

-----Urspr|ngliche Nachricht-----
Von: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] Im Auftrag von
Piotr Kaluzny
Gesendet: Donnerstag, 4. Mdrz 2010 14:16
An: groupstudy_at_nyms.net
Cc: ccielab_at_groupstudy.com
Betreff: Re: Advice on reading the whole lab before starting?

The point in reading the whole lab prior to start is to identify potential
dependencies between the tasks. For example, some later questions may impose
particular requirements on the L2 topology. Initially it may look like there
are few choices to build it, but finally it turns out that only one option
was valid. Other than that, there may be tasks that you have to do early in
the lab or otherwise you will not be able to proceed with some others.

Regards,

-- 
Piotr Kaluzny
CCIE #25665 (Security), CCSP, CCNP
Sr. Support Engineer - IPexpert, Inc.
URL: http://www.IPexpert.com
On Thu, Mar 4, 2010 at 1:46 PM, <groupstudy_at_nyms.net> wrote:
> Not sure if anyone commenting on here has passed v4, but I've tried and
> time is definitely of the essence.
>
> So I'm wondering - for all you guys who've passed v3 or v4, did you read
> the whole task list through first? I know INE recommend to read it (and if
> it's good enough to read once, it's good enough to read twice). Problem is
-
> when I do this, it takes at least 30 minutes to read through just once.
You
> read the task, have a preliminary look at the routers involved on the
> diagram and make some notes (which often just regurgitate the task).
>
> If I read through, I spend time on each task familiarising with the
> topology and state of the part of the network relevant to the task. Then I
> move onto the next task and by the time I go through the whole task list,
> the first bits are largely forgotten.
>
> So I'm wondering, would it be SO dangerous to just do the tasks in a
linear
> fashion, reading a task through, then completing it before doing the next
> task? I figure I can gain an extra 45 minutes odd doing this, and the
tasks
> are designed to be linear anyway.
>
> Or am I just being too detailed in the task reading? Is the point in this
> to get a general idea of what's coming without assessing the finer points
of
> the topology on each task?
>
> Very keen to hear the strategy of passers, especially recent ones...
> THANKS!
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net