Newsgroups: comp.dcom.sys.cisco
Path: utzoo!utgpu!cunews!bnrgate!bwdls61.bnr.ca!bwdls56!fortinp
From: fortinp@bwdls56.bnr.ca (Pierre Fortin)
Subject: Re: replace config
Message-ID: <1990Nov28.235243.29967@bwdls61.bnr.ca>
Sender: usenet@bwdls61.bnr.ca (Use Net)
Organization: Bell-Northern Research, Ottawa, Canada
References: <1990Nov19.205855.18509@arcturus.uucp> <12641311988012@heap.cisco.com>
Date: Wed, 28 Nov 90 23:52:43 GMT

In article <12641311988012@heap.cisco.com>, JOHN@heap.cisco.com (John Wright) writes:
> There are three configuration files that one could have:
> 
> The contents of non-volatile battery backup up memory.
> The active running RAM configuration information.
> The file on a local TFTP server.

[...stuff deleted...]

> in that file.  The contents of the active configuration file in RAM
> are written to NVM with the write memory command.

...and the NVRAM can be erased with (at least the following commands):

       write erase          ! obvious
       test memory          ! SURPRISE!!  Gotcha!

> 
> John Wright
> Customer Engineering
> cisco Systems, Inc.


Pierre Fortin       Bell-Northern Research     I know, my postings are
Internet Systems    P.O.Box 3511, Stn C        terse and humourless. So?
(613)763-2598       Ottawa, Ontario            RIP: aptly named protocol
fortinp@bnr.ca      Canada    K1Y 4H7          AppleTalk: Adam&Eve's design