Re: OT: Secure the startup config?

Doh, never thought about that.

On 18 March 2010 15:30, Group Study <gs_at_netengineer.org> wrote:

> But then couldn't someone just edit the EEM script to re-enable it?
> and then write to startup...
>
> or even delete the EEM script...
>
> I pretty much want the user to go nuts on the router and test whatever
> they want but at the end of the day, be able to revert to a baseline
> config...
>
> I was thinking of tftping an startup config to it bu then I get the
> problem of well, if i do a write erase how am I going to get
> connectivity to tftp a start up config :)
>
> Also, I'm trying to do it without console access.
>
>
>
>
> On Thu, Mar 18, 2010 at 11:24 AM, Muzammil Malick <malickmuz_at_gmail.com>
> wrote:
> > You could always disable write mem etc. with an EEM script.
> >
> > On 18 March 2010 15:19, Group Study <gs_at_netengineer.org> wrote:
> >>
> >> Off topic...
> >>
> >> I want to keep an intial config on some lab routers and let others go
> >> nuts when they're using the routers... is there a way to keep a start
> >> up config, untouched, so that let say someone decides to write erase
> >> everything and shut down all the interfaces etc... that I can power
> >> cycle the router and keep back to an initial state?
> >>
> >> Almost like disabling write mem or copy run start...
> >>
> >> thanks
> >>
> >>
> >> 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 Thu Mar 18 2010 - 16:09:06 ART