Path: utzoo!attcan!uunet!wuarchive!cs.utexas.edu!news-server.csri.toronto.edu!utgpu!cunews!bnrgate!bwdls56!fortinp
From: fortinp@bwdls56.bnr.ca (Pierre Fortin)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: Static Subnet Defaults..
Message-ID: <1990Oct2.191648.8570@bnrgate.bnr.ca>
Date: 2 Oct 90 19:16:48 GMT
References: <27385@boulder.Colorado.EDU>
Sender: news@bnrgate.bnr.ca (USENET News System)
Organization: Bell-Northern Research, Ltd. Ottawa Ontario CANADA
Lines: 36

In article <27385@boulder.Colorado.EDU>, cja@flamingo.nersc.gov (Cathy Aronson) writes:

[stuff deleted]

>                          I can reproduce this problem over and over
> whenever I want.  There is no difference between what is in the
> volitile mem, and what is in non-volitile memory at the time 
> that I config it from memory.  
> 
We've also run across a problem related to non-volatile memory (my coleague
should have reported it directly to cisco by now).  At any rate, my 
conclusion was that the NV memory actually contained lots of stuff which 
is *not* displayed with "show config".
 
To cisco (avoided using caps... :^) ):  Can you provide an optional 
parameter to allow showing *all* contents of the NV memory?
Something like "show config all"; and why not "write term all" while you're
at it?

In our case, a "write erase" quickly followed by "write memory" was required
to get rid of a persistent "no ip route-cache" statement which would 
disappear with "no ip address" and reappear when an IP address was coded.

> 
> 	Cathy Aronson
>         National Energy Research Supercomputer Center
>         Lawrence Livermore National Laboratory
>         cja@marmot.nersc.gov
> 	415-422-4016

Cheers,
Pierre
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
                    Canada    K1Y 4H7          AppleTalk: Adam&Eve's design