[c-nsp] NVRAM Size Limitations - Field Experiences?

[Chris Woodfield]

I'll jump on the bandwagon as well - I have yet to see it break.  
Might add a few seconds to the "wr mem" wait time and the initial  
config load at boot, but all in all it's worthwhile.

That said, given the size of your config I'd suggest throwing testing  
this on a lab box if you can and measuring the difference in wr mem  
times before you put it in the field...that way your ops folks won't  
think they've hung the router when they don't get the [OK] right back.

-C

On Feb 14, 2007, at 4:26 PM, Eric Kagan wrote:

>> We are slightly over 50% utilization on one of our router's NVRAM
>> space (128KB on an NPE-300).
>>
>> We like to be pre-emptive way beforehand just so we don't shoot
>> ourselves in the foot when crunch-time comes. So we are wondering
>> whether to consider the 'service compress-config' feature to keep
>> this router's running configuration manageable, or to upgrade to
>
> We have the 'service compress-config' working fine on several routers.
>
> Eric
>
>
>
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>