From: Vijay Ramcharan (vramcharan@thedeal.com)
Date: Fri Aug 19 2005 - 11:10:32 GMT-3
I'm a relatively new CCIE so I can easily recall some important (to me
anyway) lab tips. Scott is correct about creating your own lab diagram.
I took about 10 minutes or so recreating my own copy. I find it helpful
to draw colored lines indicating neighbor relationships for routing
protocols between routers. E.g. brown for BGP, blue for EIGRP, orange
for OSPF, red for RIP etc. I also like to indicate which protocol is
advertising loopbacks, so next to each router I note that. I also note
what is being redistributed on each router. So if doing mutual
redistribution between RIP and OSPF for example, I'd note RIP <--> OSPF
next to the router doing that.
It's also important to be as comfortable as possible with your Windows
desktop layout. For example, I took another 5 minutes or so customizing
my terminal app windows to match what I was used to in my practice labs.
I adjusted font size and type, scrollback buffer etc. At the end of my
prep time, I was satisfied that I had a fairly close approximation of my
practice lab environment after which I began reading the questions.
Another tip I find helpful is when I create ACLs or route or class maps
I usually name it (if possible within the confines of the question) for
the first question that prompted me to create it. That way I know that
if I need to change it, I know which question to refer back to so that I
don't break a previous requirement.
I think it's little (big?) things like that which help in minimizing
errors.
Vijay Ramcharan, CCIE #14824, CCDP, MCSE
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Scott Morris
Sent: 19 August, 2005 09:14
To: 'ccie2be'; 'Group Study'
Subject: RE: show map-class - avoiding dumb, time costly mistakes
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