Re: lab step 1: write erase / reload?

Hi Charles,

You may try the following to speed things up: for example you have few
configs which you may want to keep such as:

no ip domain-lookup
logg console
line con 0
privi lev 15
exec-timout 0 0
logg syn

ip address for the loopback, etc..... If this is the case just start
with a clean config add all the configs and save them to the flash as
a file eg copy run flash:fresh

On reload just copy flash:fresh startup reload.... and you should
have the clean configs ready to start the next lab.

HTH, Dan

On Mon, Jun 1, 2009 at 10:45 AM, <Charles.Henson_at_regions.com> wrote:
> All,
> I'm a few months out and am trying to focus on strategy. One thing
> I've notice in many of the lab from various vendors and discussed in the
> real lab is initial configs with errors. Does anyone have an opinion on
> just erasing and reloading VS hunting for potential problems in advance? I
> have thought of reloading, then reading my lab and drawing it out while the
> routers reload. Has anyone thought of this or tried this or am I way off my
> rocker in terms of good testing methodology.
>
> Charles
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Mon Jun 01 2009 - 14:01:35 ART