|
|
This chapter provides detailed descriptions of the commands used to load and copy configuration files. Configuration files contain commands entered to customize the function of the Cisco IOS software.
| Old Command | New Command |
|---|---|
| configure network | copy rcp running-config (for an rcp server)
copy tftp running-config (for a TFTP server) |
| configure overwrite-network | copy rcp startup-config (for an rcp server)
copy tftp startup-config (for a TFTP server) |
| show configuration | show startup-config |
| write erase | erase startup-config |
| write memory | copy running-config startup-config |
| write network | copy running-config rcp (for an rcp server)
copy running-config tftp (for a TFTP server) |
| write terminal | show running-config |
For configuration information and examples, refer to the "Modifying, Downloading, and Maintaining Configuration Files" chapter in the Configuration Fundamentals Configuration Guide.
To modify the buffer size used to load configuration files, use the boot buffersize global configuration command. Use the no form of this command to return to the default setting.
boot buffersize bytes| bytes | Specifies the size of the buffer to be used. There is no minimum or maximum size that can be specified. |
Buffer size of the NVRAM
Global configuration
This command first appeared in Cisco IOS Release 10.0.
Normally, the Cisco IOS software uses a buffer the size of the system NVRAM to hold configuration commands read from the network. You can increase this size if you have a very complex configuration.
The following example sets the buffer size to 64000 bytes:
boot buffersize 64000
On the Cisco 7000 family, to specify the device and filename of the configuration file from which the router configures itself during initialization (startup), use the boot config global configuration command. Use the no form of the command to remove this specification.
boot config device:filename| device: | Device containing the configuration file. The colon (:) is required. Valid devices are as follows:
· bootflash--Internal Flash memory. · nvram--Nonvolatile random-access memory (NVRAM). If you specify NVRAM, omit the filename. · slot0--First PCMCIA slot. · slot1--Second PCMCIA slot. |
| filename | Name of the configuration file. The configuration file must be an ASCII file. The maximum filename length is 63 characters. |
NVRAM (nvram:)
Global configuration
This command first appeared in Cisco IOS Release 11.0.
Use this command only with the Cisco 7000 family. You set the CONFIG_FILE environment variable in the current running memory when you use the boot config command. This variable specifies the configuration file used for initialization (startup).
If you specify nvram: as the device, and it contains only a distilled version of the configuration, the Cisco IOS software displays an error message and does not update the CONFIG_FILE environment variable. (A distilled configuration is one that does not contain access lists.) If you specify a configuration file in the filename argument that does not exist or is not valid, the software displays an error message and does not update the CONFIG_FILE environment variable.
The router uses the NVRAM configuration during initialization when the CONFIG_FILE environment variable does not exist or when it is null (such as at first-time startup). If the software detects a problem with NVRAM or the configuration it contains, the device enters setup mode. Refer to the "Setup Command" chapter in this publication for more information on the setup command facility.
When you use the no form of this command, the router returns to using the NVRAM configuration as the startup configuration.
In the following example, the first line specifies that a Cisco 7000 series router should use the configuration file router-config located in internal Flash memory to configure itself during initialization. The second line copies the specification to the startup configuration, ensuring that this specification will take effect upon the next reload:
Router (config)#boot config flash:router-configRouter (config)# end Router#copy running-config startup-config
The following example instructs a Cisco 7500 series router to use the configuration file router-config located on the Flash memory card inserted in the second PCMCIA slot of the RSP card during initialization. The second line copies the specification to the startup configuration, ensuring that this specification will take effect upon the next reload:
Router (config)#boot config slot1:router-configRouter (config)# end Router#copy running-config startup-config
You can use the master indexes or search online to find documentation of related commands.
copy running-config startup-config
show boot
show flash
To change the default name of the host configuration filename from which you want to load configuration commands, use the boot host global configuration command. Use the no form of this command to restore the host configuration filename to the default.
boot host mop filename [mac-address] [interface]| mop | Configures the router from a configuration file stored on a DEC MOP server. |
| filename | Name of the file from which you want to load configuration commands. |
| mac-address | (Optional) MAC address of the MOP server on which the file resides. If the MAC address argument is not included, a broadcast message is sent to all MOP boot servers. The first MOP server to indicate that it has the file is the server from which the router gets the boot image. |
| interface | (Optional) Interface out which the router should send MOP requests to reach the MOP server. The interface options are async, dialer, ethernet, serial, and tunnel. If the interface argument is not specified, a request is sent on all interfaces that have MOP enabled. The interface from which the first response is received is the interface used to load the software. |
| tftp | (Optional) Configures the router from a configuration file stored on a TFTP server. |
| rcp | (Optional) Configures the router from a configuration file stored on an rcp server. |
| ip-address | (Optional) IP address of the TFTP server on which the file resides. If omitted, this value defaults to the IP broadcast address of 255.255.255.255. |
The router uses its host name to form a host configuration filename. To form this name, the router converts its name to all lowercase letters, removes all domain information, and appends -confg.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
Use the service config command to enable the loading of the specified configuration file at reboot time. Without this command, the router ignores the boot host command and uses the configuration information in NVRAM. If the configuration information in NVRAM is invalid or missing, the service config command is enabled automatically.
The network server will attempt to load two configuration files from remote hosts. The first is the network configuration file containing commands that apply to all network servers on a network. The second is the host configuration file containing commands that apply to one network server in particular.
The following example sets the host filename to wilma-confg at address 192.168.7.19:
boot host /usr/local/tftpdir/wilma-confg 192.168.7.19
You can use the master indexes or search online to find documentation of related commands.
To change the default name of the network configuration file from which you want to load configuration commands, use the boot network global configuration command. Use the no form of this command to restore the network configuration filename to the default.
boot network mop filename [mac-address] [interface]| mop | Configures the router to download the configuration file from a network server using the Digital Maintenance Operation Protocol (MOP) protocol. |
| filename | Name of the file from which you want to load configuration commands. The default filename is network-config. |
| mac-address | (Optional) If mop is specified, the MAC address of the network server on which the file resides. If the MAC address argument is not included, a broadcast message is sent to all MOP boot servers. The first server to indicate that it has the file is the server from which the router gets the boot image. |
| interface | (Optional) If mop is specified, the interface out which the router should send MOP requests to reach the server. The interface options are async, dialer, ethernet, serial, and tunnel. If the interface argument is not specified, a request will be sent on all interfaces that have MOP enabled, and the interface from which the first response is received will be used to load the software. |
| tftp | (Optional) Configures the router to download the configuration file from a network server using TFTP. If omitted and rcp is not specified, defaults to tftp. |
| rcp | (Optional) Configures the router to download the configuration file from a network server using rcp. If omitted, defaults to tftp. |
| ip-address | (Optional) If rcp or tftp is specified, the IP address of the network server on which the compressed image file resides. If the IP address is omitted, this value defaults to the IP broadcast address of 255.255.255.255. |
The default filename is network-config. The default transfer protocol type is TFTP, if neither tftp nor rcp is specified.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
When booting from a network server, routers ignore routing information, static IP routes, and bridging information. As a result, intermediate routers are responsible for handling rcp or TFTP requests. Before booting from a network server, verify that a server is available by using the ping command.
Use the service config command to enable the loading of the specified configuration file at reboot time. Without this command, the router ignores the boot network command and uses the configuration information in NVRAM. If the configuration information in NVRAM is invalid or missing, the service config command is enabled automatically.
The network server will attempt to load two configuration files from remote hosts. The first is the network configuration file containing commands that apply to all network servers on a network. Use the boot network command to identify the network configuration file.
The rcp software requires that a client send the remote username on each rcp request to the network server. When the boot network rcp command is executed, the Cisco IOS software sends the host name as the both the remote and local usernames. The rcp implementation searches for the configuration files to be used relative to the account directory of the remote username on the network server, if the server has a directory structure, for example, as do UNIX systems.
If you copy the system image to a personal computer used as a file server, the remote host computer must support the remote shell (rsh) protocol.
The following example changes the network configuration filename to bridge_9.1 and uses the default broadcast address:
boot network bridge_9.1 service config
The following example changes the network configuration filename to bridge_9.1, specifies that rcp is to be used as the transport mechanism, and gives 172.16.1.111 as the IP address of the server on which the network configuration file resides:
boot network rcp bridge_9.1 172.16.1.111 service config
You can use the master indexes or search online to find documentation of related commands.
To enter global configuration mode, use the configure privileged EXEC command. You must be in global configuration mode to enter global configuration commands.
configure {terminal | memory | network}| terminal | Executes configuration commands from the terminal. |
| memory | For all platforms except the Cisco 7000 family, executes the commands stored in NVRAM.
For the Cisco 7000 family, executes the configuration specified by the CONFIG_FILE environment variable. |
| network | The copy rcp running-config or copy tftp running-config command replaces the configure network command. If you use rcp, see the copy rcp command for more information on copy rcp running-config. If you use TFTP, see the copy tftp command for more information on copy tftp running-config. |
For all platforms except the Cisco 7000 family, there is no default.
For the Cisco 7000 family, the router uses the NVRAM configuration (if valid) when the CONFIG_FILE environment variable does not exist or is null (such as at first-time startup).
Privileged EXEC
This command first appeared in Cisco IOS Release 10.0.
If you do not specify terminal or memory, the Cisco IOS software prompts you for the source of configuration commands. If you specify terminal, the software executes the commands you enter at the system prompts.
On all platforms except the Cisco 7000 family, if you specify memory, the software executes the commands located in NVRAM. On the Cisco 7000 family, if you specify memory, the router executes the commands pointed to by the CONFIG_FILE environment variable. The CONFIG_FILE environment variable specifies the device and filename of the configuration file that the router uses to configure itself during initialization. Possible devices are as follows:
When the CONFIG_FILE environment variable specifies NVRAM, the router executes the NVRAM configuration only if it is an entire configuration, not a distilled version. A distilled configuration is one that does not contain access lists.
To view the contents of the CONFIG_FILE environment variable, use the show boot command. To modify the CONFIG_FILE environment variable, use the boot config command and then save your changes by issuing the copy running-config startup-config command.
After you enter the configure command, the system prompt changes from
In the following example, a router is configured from the terminal:
Router#configureConfiguring from terminal, memory, or network [terminal]? Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
In the following example, a Cisco 7000 family router executes the commands pointed to by the CONFIG_FILE environment variable:
configure memory
You can use the master indexes or search online to find documentation of related commands.
boot config
copy running-config startup-config
show boot
show running-config
show startup-config
The copy rcp startup-config or copy tftp startup-config command replaces the configure overwrite-network command. See the copy command in the "Router Memory Commands" chapter of the Configuration Fundamentals Command Reference for more information on copy rcp startup-config and copy tftp startup-config.
To erase a saved configuration, use the erase startup-config EXEC command. The erase startup-config command replaces the write erase command.
erase startup-configThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.0.
On all platforms except the Cisco 7000 family, this command erases the startup configuration in NVRAM.
When you use the erase startup-config command on the Cisco 7000 family, the router erases or deletes the configuration pointed to by CONFIG_FILE environment variable. The CONFIG_FILE environment variable specifies the configuration file used for initialization. If the CONFIG_FILE environment variable points to NVRAM, the router erases NVRAM. If the CONFIG_FILE environment variable specifies a Flash memory device and configuration filename, the Cisco IOS software deletes the configuration file. That is, the software marks the file as "deleted."
The following example erases the configuration located in NVRAM or specified by the CONFIG_FILE environment variable:
erase startup-config
You can use the master indexes or search online to find documentation of related commands.
boot config
delete
show boot
show startup-config
undelete
To compress configuration files, use the service compress-config global configuration command. To disable compression, use the no form of this command.
service compress-configThis command has no arguments or keywords.
Disabled
Global configuration
This command first appeared in Cisco IOS Release 10.0.
If the file compression completes successfully, the following message is displayed:
Compressing configuration fromconfiguration-sizetocompressed-size[OK]
If the boot ROMs do not recognize a compressed configuration, the following message is displayed:
Boot ROMs do not support NVRAM compression Config NOT written to NVRAM
If the file compression fails, the following message is displayed:
Error trying to compress nvram
One way to determine whether a configuration file will compress enough to fit into NVRAM is to use a text editor to enter the configuration, then use the UNIX compress command to check the compressed size. To get a closer approximation of the compression ratio, use the UNIX command compress -b12.
Once the configuration file has been compressed, the router functions normally. A show startup-config command would uncompress the configuration before displaying it. At boot time, the system would recognize that the configuration file was compressed, uncompress it, and proceed normally.
To disable compression of the configuration file, enter configuration mode and specify the no service compress-config command. Then enter the copy running-config startup-config command. The router displays an OK message if it is able to successfully write the uncompressed configuration to NVRAM. Otherwise, the router displays an error message indicating that the configuration is too large to store. If the configuration file is larger than the physical NVRAM, the following message is displayed:
##Configuration too large to fit uncompressed in NVRAM Truncate configuration? [confirm]
To truncate and save the configuration, type Y. To not truncate and not save the configuration, type N.
In the following example, the configuration file is compressed:
service compress-config
You can use the master indexes or search online to find documentation of related commands.
To enable autoloading of configuration files from a network server, use the service config global configuration command. Use the no form of this command to restore the default.
service configThis command has no arguments or keywords.
Disabled, except on systems without NVRAM or with invalid or incomplete information in NVRAM. In these cases, autoloading of configuration files from a network server is enabled automatically.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
Usually, the service config command is used in conjunction with the boot host or boot network command. You must enter the service config command to enable the router to automatically configure the system from the file specified by the boot host or boot network command.
The service config command can also be used without the boot host or boot network command. If you do not specify host or network configuration filenames, the router uses the default configuration files. The default network configuration file is network-confg. The default host configuration file is host-confg, where host is the host name of the router. If the Cisco IOS software cannot resolve its host name, the default host configuration file is router-confg.
In the following example, a router is configured to autoload the default host configuration file:
service config
You can use the master indexes or search online to find documentation of related commands.
The show startup-config command replaces this command. Refer to the description of the
show startup-config command for more information.
To display the configuration stored in a specified file on the Cisco 7000 family, use the show file EXEC command.
show file [device:] filename| device: | (Optional) Device containing the configuration file. The colon (:) is required. Valid devices are as follows:
· bootflash--Internal Flash memory. · slot0--First PCMCIA slot. This device is the initial default device. · slot1--Second PCMCIA slot. · nvram--Router's NVRAM. If you specify NVRAM, omit the filename. The colon (:) is required. · slavebootflash--Internal Flash memory on the slave RSP card of a Cisco 7507 or Cisco 7513 configured for HSA. · slaveslot0--First PCMCIA slot of the slave RSP card on a Cisco 7507 or Cisco 7513 configured for HSA. · slaveslot1--Second PCMCIA slot of the slave RSP card on a Cisco 7507 or Cisco 7513 configured for HSA. · slavenvram--NVRAM of the slave RSP card on a Cisco 7507 or Cisco 7513 configured for HSA. If you specify the slave NVRAM, omit the filename. If you omit the device: argument, the system uses the default device specified by the cd command. |
| filename | Name of the file. The file can be of any type. The maximum filename length is 63 characters. |
EXEC
This command first appeared in Cisco IOS Release 11.0.
Use this command for the Cisco 7000 family. When showing the configuration, the Cisco IOS software informs you whether the displayed configuration is a complete configuration or a distilled version. A distilled configuration is one that does not contain access lists.
The following is sample output from the show file command:
Router# show file slot0:router-config
Using 534 out of 129016 bytes
!
version 10.3
!
hostname Cyclops
!
enable-password xxxx
service pad
!
boot system dross-system 172.16.13.111
boot system dross-system 172.16.1.111
!
exception dump 172.16.13.111
!
no ip ipname-lookup
!
decnet routing 13.1
decnet node-type area
decnet max-address 1023
!
interface Ethernet 0
ip address 172.16.1.1 255.255.255.0
ip helper-address 172.31.1.0
ip accounting
ip gdp
decnet cost 3
!
ip domain-name CISCO.COM
ip name-server 255.255.255.255
!
end
You can use the master indexes or search online to find documentation of related commands.
To display the configuration information currently running on the terminal, use the show running-config EXEC command. This command replaces the write terminal command.
show running-configThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.0.
Use this command in conjunction with the show startup-config command to compare the information in running memory to the information stored in NVRAM or in a location specified by the CONFIG_FILE environment variable. On the Cisco 7000 family, this variable specifies the configuration file used for initialization (startup). Use the boot config command in conjunction with the copy running-config startup-config command to set the CONFIG_FILE environment variable.
The following partial sample output displays the running configuration:
Router2# show running-config Building configuration... Current configuration: ! version 11.2 no service udp-small-servers no service tcp-small-servers ! hostname Router2 ! ... ! end
You can use the master indexes or search online to find documentation of related commands.
boot config
configure
copy running-config startup-config
show startup-config
To display the contents of NVRAM (if present and valid) or to show the configuration file pointed to by the CONFIG_FILE environment variable, use the show startup-config EXEC command. This command replaces the show configuration command.
show startup-configThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.0.
NVRAM stores the configuration information on the network server in text form as configuration commands. For all platforms except the Cisco 7000 family, the show startup-config command shows the version number of the software used when you last executed the copy running-config startup-config command.
For the Cisco 7000 family, the show startup-config command shows the configuration file specified by the CONFIG_FILE environment variable. The Cisco IOS software informs you whether the displayed configuration is a complete configuration or a distilled version. A distilled configuration is one that does not contain access lists. If the CONFIG_FILE environment variable does not exist or is not valid, the software displays the NVRAM configuration (if it is a valid, complete configuration).
The following sample output from the show startup-config command displays the contents of NVRAM:
Router# show startup-config
Using 5057 out of 32768 bytes
!
version 10.3
!
enable-password xxxx
service pad
!
boot system dross-system 172.16.13.111
boot system dross-system 172.16.1.111
!
exception dump 172.16.13.111
!
no ip ipname-lookup
!
decnet routing 13.1
decnet node-type area
decnet max-address 1023
!
interface Ethernet 0
ip address 172.16.1.1 255.255.255.0
ip helper-address 172.30.1.0
ip accounting
ip gdp
decnet cost 3
!
ip domain-name CISCO.COM
ip name-server 255.255.255.255
!
end
The following is partial sample output from the show startup-config command when the configuration file has been compressed:
Router# show startup-config
Using 21542 out of 65536 bytes, uncompressed size = 142085 bytes
!
version 9.22
service compress-config
!
hostname rose
!
boot system flash gs7-k.sthormod_clean
boot system rom
You can use the master indexes or search online to find documentation of related commands.
configure
copy running-config startup-config
description
service compress-config
show boot
show running-config
The erase startup-config command replaces this command. Refer to the description of the erase startup-config command for more information.
The copy running-config startup-config command replaces this command. Refer to the description of the copy command in the "Router Memory Commands" chapter in the Configuration Fundamentals Command Reference for more information on copy running-config startup-config.
The copy running-config rcp or copy running-config tftp command replaces this command. Refer to the description of the copy command in the "Router Memory Commands" chapter in the Configuration Fundamentals Command Reference for more information on copy running-config rcp or copy running-config tftp.
The show running-config command replaces this command. Refer to the description of
show running-config for more information.
|
|