From: Tony Olzak (aolzak@xxxxxxxxxxxxxxxxxxx)
Date: Sat Dec 02 2000 - 20:47:48 GMT-3
Actually, that IS something that is VERY helpful in the lab. Clearing
IP/IPX/BGP is one of the best ways to "kick" your routers. I configure
aliases for all protocols for clearing necessary info quickly.
alias exec cb clear ip bgp *
alias exec ci clear ip route *
alias exec cx clear ipx route *
alias exec i show ip route
alias exec ix show ipx route
Those are some of the aliases I use. Just put them into notepad and paste
them into all routers before with your general base configs for all routers.
Tony
----- Original Message -----
From: "Tracy Blackmore" <TracyB@TSLAD.com>
To: "'Kevin Baumgartner '" <kbaumgar@cisco.com>; "Tracy Blackmore"
<TracyB@TSLAD.com>; "Tracy Blackmore" <TracyB@TSLAD.com>;
<ccielab@groupstudy.com>
Sent: Friday, December 01, 2000 3:09 PM
Subject: RE: Pitfalls
> Happy is the man who learns from his mistakes. Wise (or cheep in my case)
> is the man who learns from others.
>
> Let me start this.
>
> While working on an OSPF issue between three routers, I found that even
> though all was coded correctly, I had to clear the route table on the
center
> router before it would pick up the third routers routes. Nothing more,
just
> clear the route. Well... I had been looking at the configs for 30
minutes
> before I just tried clearing the route table. It worked! Now... That 30
> minutes can burn up pretty quickly while any of us are in the actual lab.
>
> Since this is a help-each-other-out kinda list, I thought that if we all
> added some of the more common "pitfalls" to a central list, maybe someone
> won't have to burn 30 minutes (or longer God forbid) on something that is
> common but we just haven't seen before.
>
> -----Original Message-----
> From: Kevin Baumgartner
> To: Tracy Blackmore; Tracy Blackmore; ''ccielab@groupstudy.com' '
> Sent: 12/1/00 12:49 PM
> Subject: RE: Pitfalls
>
> Well my experience is that just reading from other persons experience
> won't get
> you there to passing the lab. You need hands on practice on the routers.
> And the more practice the better. The best approach that I have seen is
> to
> built your own home lab. And as a lot of members have mentioned they
> have
> sold the routers when done.
>
> Kevin
>
>
> At 12:26 PM 12/1/00 -0700, Tracy Blackmore wrote:
> >I would have to say the bootcamp labs would be a great example. They
> are
> >designed with several things to look out for (pitfalls.) I was just
> looking
> >for getting the common ones in one place.
> >
> >Some of us don't have the money to buy days (or weeks) of time on their
> labs
> >nor the money to build a nine router lab at home. On the job
> experience is
> >great but how often do you have to build a network with all of the
> items
> >required for the CCIE and do it in two days (or even two months?)
> >
> >-----Original Message-----
> >From: Kevin Baumgartner
> >To: Tracy Blackmore; 'ccielab@groupstudy.com'
> >Sent: 12/1/00 12:19 PM
> >Subject: Re: Pitfalls
> >
> >I don't see how anyone that has already taken the lab can talk about
> >general
> >lab scenarios. Even if reworded. Still seems like NDA.
> >
> > So what exactly are "general" labs?
> >
> > Kevin
> >
> >At 10:46 AM 12/1/00 -0700, Tracy Blackmore wrote:
> > >Group;
> > >
> > > I have read many briefs from people who have been to the lab,
> >passed or
> > >not. One thing that I would like to see/ask is...
> > >
> > >What are some of the major pitfalls to look for in general lab
> >scenarios?
> > >
> > >I can gather several of them by reviewing the questions posted but it
> >would
> > >be nice to have a compilation of all of the major ones so that as we
> >study,
> > >we'll have an idea of pitfalls to look for.
> > >
> > >Thanks for any help you guys can provide!
> > >
> > >P.S. So as not to break the NDA, I have worded my question so as to
> >gain
> > >information on "general" labs. Please do not give exact problems
> faced
> >in
> > >the CCIE Lab.
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:57 GMT-3