From: Scott Morris (swm@emanon.com)
Date: Fri Aug 19 2005 - 10:13:43 GMT-3
When you're working in the lab, you should take the time to make your own
copy of the lab layout (diagram).
It doesn't have to be pretty, but functional. This allows you to jot notes
down about ACLs (in/out), protocols, filters, map-classes and all sorts of
stuff.
What you highlight here is a common mistake where you don't remember
everything you did earlier in the lab. That's why good notes/documentation
are critical. This should be a lesson for real life as well, but the
immediate importance is the lab!
HTH,
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccie2be
Sent: Friday, August 19, 2005 8:59 AM
To: Group Study
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