Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!ncar!boulder!daemon
From: lougheed@cisco.com
Newsgroups: comp.dcom.sys.cisco
Subject: Re: Static Subnet Defaults..
Message-ID: <27486@boulder.Colorado.EDU>
Date: 3 Oct 90 22:22:51 GMT
Sender: news@boulder.Colorado.EDU
Lines: 28

When you do a "show configuration" you do indeed see the entire contents of
NVRAM, except for a "magic number" indicating the memory was written, a byte
count, and a checksum.  We store the configuration commands in NVRAM as
ASCII text.

To avoid consuming too much memory, only the non-default configuration
settings are entered into the NVRAM when you do a "write" command.

In the case you mention, I suspect entering the command "ip route-cache"
would have done the trick.

Kirk Lougheed
cisco


>> 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.