From: James Matrisciano (jmatrisciano@kenttech.com)
Date: Fri Aug 19 2005 - 10:59:02 GMT-3
I have to whole heartedly agree with Joe. Before your fingers hit the
keyboard, pick up a couple pencils and the paper given to you at the
beginning of the lab. Read through the lab, draw it out. I get as far
as to show what links are carying what protocols, DLSW, Multicast,
NTP...everything. I have a good color concept of what the packets are
and how they are traversing your network. Makes it so much better when
starting to creat ACL's. Now you know, "hey, I gotta build an acl for
the NTP and EIGRP between R2 and R3...but later Multicast will be
traversing this..." so make a note or add PIM into the acl.
This will take some time, you need to factor it in. I set forth knowing
that reading through the lab a few times and really writing it all out
is going to be an hour. PLAN ON IT!!! Don't get overwhelmed by other
people typing on their keyboards, who knows, you may pass and they may
fail, because you took your time.
Just my 2 cents of course, I still have yet to pass the damn thing as
well, so take from it what ever you want :)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Joe Rinehart
Sent: Friday, August 19, 2005 9:47 AM
To: ccie2be; Group Study
Subject: Re: show map-class - avoiding dumb, time costly mistakes
What this also does is highlight one of the cardinal rules of the
lab---read it through end to end a few times first. I know that in
practice labs I started catching numerous "gotchas" by doing that...
Joe Rinehart
CCIE #14256, CCNP, CCDP
Data Network Consultant
AT&T Pacific Northwest Enterprise Markets
----- Original Message -----
From: "ccie2be" <ccie2be@nyc.rr.com>
To: "Group Study" <ccielab@groupstudy.com>
Sent: Friday, August 19, 2005 5:59 AM
Subject: show map-class - avoiding dumb, time costly mistakes
> Hi guys,
>
> While doing a practice lab yesterday, I made a dumb mistake and I
suspect
> I'm not the only one who has made this same mistake.
>
> Here's what happened:
>
> Early in the lab, I needed to configure a map-class for frame-relay to
> enable end-to-end keepalives. No problem, it worked fine.
>
> Then, much later the lab, I needed to configure some QoS stuff for the
same
> f/r interfaces. Well. as you probably guessed, I had forgotten about
the
> map-class stuff I had configured much earlier.
>
> I've also made this same type of mistake with acl's. To prevent
making
this
> type of mistake in the future, now I always do a show access-list
before
> ever creating a new acl.
>
> I figure I should use the same technique when it comes to map-classes
but
I
> couldn't find a show map-class command. As a poor alternative, I
could
> always do a
>
> show run int x
>
> But, I wonder what the GS brain trust thinks of that. Is there
something
> better?
>
> TIA, Tim
>
>
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:19 GMT-3