RE: Lab Problems (Was: RE: Interfaces are all pingable)

From: Brian Dennis (brian@labforge.com)
Date: Wed Feb 26 2003 - 12:38:58 GMT-3


Yes, changing one simple word can change the whole solution. How you
interpret a single sentence in a section can change the solution. When I
did my Security CCIE I finished around lunch but spent over an hour
reviewing one section due to the "poor" wording of a single sentence in
that section.

Brian Dennis, CCIE #2210 (R&S/ISP Dial/Security)
brian@labforge.com
http://www.labforge.com

-----Original Message-----
From: p729@cox.net [mailto:p729@cox.net]
Sent: Wednesday, February 26, 2003 6:18 AM
To: Brian Dennis; ccielab@groupstudy.com
Subject: Re: Lab Problems (Was: RE: Interfaces are all pingable)

"Another pitfall could be something as simple as addressing an interface
with the most efficient subnet possible that allows for 6 PC's to be
attached. The answer isn't a /29 it's a /28."

...and substitute "PC's" with "hosts" and it may change the answer--is
the router's interface considered a "host"? By definition, yes. Should
you ask the proctor for a ruling? I'll leave that for the reader to
decide ;)

Regards,

Mas Kato
http://ecardfile.com/mkato

============================================================
From: "Brian Dennis" <brian@labforge.com>
Date: 2003/02/26 Wed AM 02:27:31 EST
To: <ray_gan74@hotmail.com>, <ccielab@groupstudy.com>
Subject: Lab Problems (Was: RE: Interfaces are all pingable)

First off let me say this. When I teach my CCIE prep course I categorize
problems you could run into in the CCIE lab mainly in three ways. The
first being what I call a "show stopper". These are the problems you run
into that you definitely know is a problem. Example:

Give all class "A" networks received via RIP from BB3 an additional hop
count of 2 with the exception of the 2.0.0.0/8 route. Use a maximum of 2
access-list statements for this task.

This kind of task doesn't have a lot of possible solutions and if you
can't make it work with just the two ACL statements it's a "show
stopper". This is a clear and easy to see problem.

The second is where a solution for one task conflicts with the solution
for another task. Sometimes these are easy to spot and sometimes they
aren't. Example:

Earlier in the lab you figured out through the wording they gave you
that they wanted you to use HSRP between two routers. **Please remember
that Cisco isn't going to just come out and ask for something like HSRP.
They are going give you a task that has HSRP as the solution but they
may never mention HSRP** Okay so we configured HSRP and no big deal. Now
towards the end of the lab you are given a task where you need to put an
ACL on one of the router's interfaces that you are running HSRP on. Now
you put the ACL on and met the requirements of this task but don't allow
for UDP port 1985 (HSRP) so you've broken HSRP and you'll lose points
for the earlier task.

The last one is a pitfall. These are the nastiest of problems. A
"pitfall" is a task that has multiple solutions but only one is truly
the correct solution. These tasks may "trick" you into configuring an
incorrect solution due to the wording of the task.

A very simple one would be like asking you to "backup" a frame-relay
interface when you're not using sub-interfaces. If you use the backup
interface command you won't get the points for the task. The backup
interface command shouldn't be used if you only have a physical
frame-relay interface to work with. The task is worded as "backup" but
wants you to use dialer watch.

Another pitfall could be something as simple as addressing an interface
with the most efficient subnet possible that allows for 6 PC's to be
attached. The answer isn't a /29 it's a /28.

Of course these should be very simple for us to catch but when you get a
full day of them plus more complex ones, it can lead to a long 8 hours
;-)
 

Good luck on your lab.

Brian Dennis, CCIE #2210 (R&S/ISP Dial/Security)
brian@labforge.com
http://www.labforge.com
 

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ray_gan74@hotmail.com
Sent: Tuesday, February 25, 2003 9:30 PM
To: ccielab@groupstudy.com
Subject: Re: Interfaces are all pingable

This thread has got me scared. I have my first lab attempt next Monday
and
hearing this kind of stuff make me worry. Without violating the NDA,
what
are some examples of pitfalls? I guess the best sound advice would be
to
know how to do things several ways and ask the proctor or fish it out of
him
which way is the one they want?

Ray

----- Original Message -----
From: "Gery Pang" <pang_gery@yahoo.com.hk>
To: <ccielab@groupstudy.com>
Sent: Tuesday, February 25, 2003 8:14 PM
Subject: Re: Interfaces are all pingable

> Hello,
>
> Could you give one example about the pitfall?
>
> Thank you.
>
> Gery
>
> >>> "Brian Dennis" <brian@labforge.com> 02/26 11:28 am >>>
> You may have run into what I like to call a "lab pitfall". This is a
> task that has multiple solutions but only one is truly the correct
> solution. These tasks "trick" you into configuring an incorrect
solution
> due to the wording of the task. Just because you have full
connectivity
> doesn't mean you fulfilled all the requirements of the task.
>
> I like putting these "lab pitfalls" in my CCIE prep class because it
> really opens student's eyes as to what they can expect in the real
CCIE
> lab.
>
> Brian Dennis, CCIE #2210 (R&S/ISP Dial/Security)
> brian@labforge.com
> http://www.labforge.com
>
>
>
> Best regards.
>
> Gery Pang
> pang_gery@yahoo.com.hk
> 2003-02-26
>
>
> _________________________________________________________
> 'Z*:E:6F(.e/*(`)!A%*>F%k(=('u'J6T)!A'A3L,u(Twins)...
> 9L$d-:$b>w9aAn BIRing3#1o
> http://ringtone.yahoo.com.hk
============================================================



This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:36 GMT-3