Your configuration file has become larger than the router's available NVRAM.
You can compress your router's configuration file before saving it to NVRAM to allow you to save more configuration information. The command service compress-config will compress the configuration information when the router saves the file, and uncompress it when it is required:
Router1#configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router1(config)#service compress-config Router1(config)#end Router1#
Cisco generally ships its routers with more than enough NVRAM to store an average configuration file. However, there are times when configuration files exceed the available NVRAM. For instance, some routers contain large access lists that are hundreds of lines in length. When configuration files grow beyond the finite amount of NVRAM you will begin to have problems.
The first sign of serious problems with an overly large configuration file is usually when the router refuses to save its configuration because of size. This is a dangerous situation because the router can no longer keep a copy of the whole running-configuration file in its NVRAM storage, and it is difficult to predict how much of your configuration will be lost if you were to reload the router.
Turning on compression roughly doubles the size of the configuration file you can store. You must put the command service compress-config into the configuration with a configure terminal. Then, for this command to take effect, you need to copy the running configuration file to NVRAM:
Router1#copy running-config startup-config Destination filename [startup-config]? <enter> Building configuration... Compressed configuration from 9664 bytes to 4903 bytes[OK] Router1#
In this case, you can see that the compression reduced the configuration file to less than half of its original size. This compression algorithm will not attempt to compress a file that is three times larger than the available NVRAM space. Although this limit exists, we have never seen a router approach a 3 to 1 ratio in practice.
The actual amount of available NVRAM storage varies between different router models. You can see how much total NVRAM storage is available on a particular router with the show version command:
Router1#show version Cisco Internetwork Operating System Software IOS (tm) C2600 Software (C2600-IK9O3S-M), Version 12.2(12a), RELEASE SOFTWARE (fc1) Copyright (c) 1986-2002 by cisco Systems, Inc. Compiled Tue 24-Sep-02 02:05 by pwade Image text-base: 0x8000808C, data-base: 0x8127FF40 ROM: System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1) Router1 uptime is 12 hours, 15 minutes System returned to ROM by reload System restarted at 23:18:45 EST Fri Jan 10 2003 System image file is "flash:c2600-ik9o3s-mz.122-12a.bin" cisco 2621 (MPC860) processor (revision 0x102) with 45056K/4096K bytes of memory. Processor board ID JAB04130B2Q (1293133440) M860 processor: part number 0, mask 49 Bridging software. X.25 software, Version 3.0.0. 2 FastEthernet/IEEE 802.3 interface(s) 2 Serial network interface(s) 32K bytes of non-volatile configuration memory. 16384K bytes of processor board System flash (Read/Write) Configuration register is 0x2102 Router1#
This router contains 32Kb of NVRAM in which to store configuration files. The top of the output from the show startup-config command shows how much NVRAM storage is available, and how much this particular configuration file requires. If you enable compression, it will also show the compressed and uncompressed sizes:
Router1#show startup-config Using 5068 out of 29688 bytes, uncompressed size = 9969 bytes Uncompressed configuration from 5068 bytes to 9969 bytes ! ! Last configuration change at 12:36:22 EST Sat Jan 11 2003 by ijbrown ! NVRAM config last updated at 13:34:57 EST Sat Jan 11 2003 by ijbrown ! version 12.2 <removed for brevity>
In this case we have used about 5Kb of the available 29Kb for this router's configuration file. However, the show version output indicates a total of 32Kb NVRAM, leaving 3Kb unaccounted for. The router's NVRAM used to contain the startup configuration file only, but this is no longer strictly the case. Recent IOS releases also use the same NVRAM space to store information such as private keys for SSH or IPSec, and interface numbers for SNMP. You can see information about all of these files with the dir nvram: command:
Router1#dir nvram:
Directory of nvram:/
20 -rw- 5068 <no date> startup-config
21 ---- 2302 <no date> private-config
1 ---- 0 <no date> persistent-data
2 -rw- 133 <no date> ifIndex-table
29688 bytes total (20218 bytes free)
Router1#
Note that the second column from the left in this output contains file attributes similar to those used by the Unix ls command. In this case, both the startup-config and ifIndex-table files are readable and writable. For example, you could look at your router's startup-config file using the following command:
Router1#more nvram:/startup-config
You can view any file that has an "r", and you can modify any file that has a "w". The two files in this router's NVRAM that have neither "r" nor "w" can't be displayed, modified, or deleted. Note that although the ifIndex-table is readable, it is in a binary format that isn't very meaningful when displayed with the more command.
|
|
|
| Top |