|
|
This chapter describes how to load system images, microcode images, and configuration files. The system images contain the system software, and the configuration files contain commands entered to customize the function of the router. Microcode images contain microcode to be downloaded to various hardware devices. The instructions in this chapter describe how to copy system images from routers to network servers (and vice versa), display and compare different configuration files, and list the system software version running on the router.
This chapter also describes the AutoInstall procedure, which you can use to automatically configure and enable a new router upon startup.
For a complete description of the commands mentioned in this chapter, refer to the "System Image, Microcode Image, and Configuration File Load Commands" chapter in the Router Products Command Reference publication.
You can perform the tasks in the following sections to load system images, microcode images, and configuration files.
This section provides information about AutoInstall, a procedure that enables you to configure a new router automatically and dynamically. The AutoInstall procedure involves connecting a new router to a network on which there is an existing preconfigured router, turning on the new router, and having it immediately enabled with a configuration file that is automatically downloaded from a TFTP server.
The following sections provide the requirements for AutoInstall and present an overview of how the procedure works. To start the procedure, go to "Perform the AutoInstall Procedure" later in this section.
For the AutoInstall procedure to work, your system must meet the following requirements:
Once the requirements for using AutoInstall are met, the dynamic configuration of the new router occurs in the following order:
The new router (newrouter) resolves its interface's IP addresses by one of the following means:
The existing router (existing) responds in one of the following ways depending upon the request type:
As of Software Release 9.21, routers can be configured to act as RARP servers.
As soon as one interface resolves its IP address, the router will move on to resolve its host name. Therefore, only one IP address needs to be set up using either SLARP, BootP, or RARP.
The new router resolves its IP address-to-host name mapping by sending a TFTP broadcast requesting the file network-confg, as shown in Figure 3-3.
The network-confg file is a configuration file generally shared by several routers. In this case, it is used to map the IP address the new router just obtained dynamically to the name of the new router. The file network-confg must reside on a reachable TFTP server and must be globally readable.
The following is an example of a minimal network-confg file that maps the IP address of the new router (131.108.10.2) to the name newrouter. The address of the new router was learned via SLARP and is based on existing's IP address of 131.108.10.1.
ip host newrouter 131.108.10.2
If newrouter does not receive a network-confg file, or if the IP address-to-host name mapping does not match the newly acquired IP address, newrouter sends a DNS broadcast. If DNS is configured and has an entry that maps newrouter's SLARP, BootP, or RARP-acquired IP address to its name, newrouter successfully resolves its name.
If DNS does not have an entry mapping newrouter's SLARP, BootP, or RARP-acquired address to its name, the new router cannot resolve its host name. The new router attempts to download a default configuration file as described in the next section, and failing that, enters setup mode.
After the router successfully resolves its host name, newrouter sends a TFTP broadcast requesting the file newrouter-confg. The name newrouter-confg must be in all lowercase, even if the true host name is not. If newrouter cannot resolve its host name, it sends a TFTP broadcast requesting the default host configuration file router-confg. The file is downloaded to newrouter where the configuration commands take effect immediately.
If the host configuration file contains only the minimal information, the administrator must Telnet into existing, from there Telnet to newrouter, and then run the setup command to configure newrouter. Refer to the Router Products Getting Started Guide for details on the setup command.
If the host configuration file is complete, newrouter should be fully operational. You can enter the enable command (with the system administrator password) at the system prompt on newrouter, and then issue the write memory command to save the information in the recently obtained configuration file into NVRAM. If a reload occurs, newrouter simply loads its configuration file from NVRAM.
If the TFTP request fails, or if newrouter still has not obtained the IP addresses of all its interfaces, and those addresses are not contained in the host configuration file, then newrouter enters setup mode automatically. Setup mode prompts for manual configuration of the router via the console. The new router continues to issue broadcasts to attempt to learn its host name and obtain any unresolved interface addresses. The broadcast frequency will dwindle to every ten minutes after several attempts. Refer to the Router Products Getting Started Guide for details on the setup command.
To dynamically configure a new router using AutoInstall, complete the following tasks. Steps 1, 2, and 3 are completed by the central administrator. Step 4 is completed by the person at the remote site.
Step 1 Modify the existing router's configuration to support the AutoInstall procedure.
Step 2 Set up the TFTP server to support the AutoInstall procedure.
Step 3 Set up BootP or RARP server if needed (required for AutoInstall using an Ethernet, Token Ring, or FDDI interface; not required for AutoInstall using an HDLC-encapsulated serial interface).
Step 4 Connect the new router to the network.
You can use either of the following types of interface:
To set up AutoInstall via a serial line with HDLC encapsulation (the default), complete the following tasks to configure the existing router:
| Task | Command |
|---|---|
| Step 1 Enter configuration mode. | configure terminal |
| Step 2 Configure the serial interface that connects to the new router with HDLC encapsulation (the default). | interface serial interface-number1 |
| Step 3 Enter an IP address for the interface The host portion of the address must have a value of 1 or 2. | ip address address mask2 |
| Step 4 Configure a helper address for the serial interface to forward broadcasts associated with the TFTP, BootP, and DNS requests. | ip helper-address address |
| Step 5 Optionally, configure a DCE clock rate for the serial line, unless an external clock is being used. This step is needed only for DCE appliques. | clockrate bits per second |
| Step 6 Exit configuration mode. | Ctrl-Z |
| Step 7 Save the configuration changes to NVRAM. | write memory |
A DTE interface must be used on the new router because there is no default clock rate for a DCE interface.
In the following example, the existing router's configuration file contains the commands needed to configure the router for AutoInstall on a serial line:
Router1# configure terminal
Router1(config)# interface serial 0
Router1(config)# ip address 131.108.10.1 255.255.255.0
Router1(config)# ip helper-address 131.108.20.5
Ctrl-Z
Router1# write memory
To set up AutoInstall using an Ethernet, Token Ring, or FDDI interface, complete the following tasks as needed to modify the configuration of the existing router. Typically, the local area network (LAN) interface and IP address are already configured on the existing router. You might need to configure an IP helper address if the TFTP server is not on the same network as the new router.
| Task | Command |
|---|---|
| Step 1 Enter configuration mode. | configure terminal |
| Step 2 Configure a LAN interface. | interface {ethernet | tokenring | fddi} interface-number1 |
| Step 3 Enter an IP address for the interface. | ip address address mask2 |
| Step 4 Optionally, configure a helper address to forward broadcasts associated with the TFTP, BootP, and DNS requests. | ip helper-address address |
| Step 5 Exit configuration mode. | Ctrl-Z |
| Step 6 Save the configuration changes to NVRAM. | write memory |
In the following example, the existing router's configuration file contains the commands needed to configure the router for AutoInstall on an Ethernet interface:
Router1# configure terminal
Router1(config)# interface Ethernet 0
Router1(config-if)# ip address 131.108.10.1 255.255.255.0
Router1(config-if)# ip helper-address 131.108.20.5
Ctrl-Z
Router1# write memory
For AutoInstall to work correctly, the new router must be able to resolve its host name and then download a name-confg file from a TFTP server. The new router can resolve its host name by using a network-confg file downloaded from a TFTP server or by using the DNS.
To set up a TFTP server to support AutoInstall, complete the following tasks. Steps 2 and 3 are different ways to resolve the new router's host name. Perform step 2 if you want to use a network-config file to resolve the new router's host name. Perform step 3 if you want to use the DNS to resolve the new router's host name.
| Task | Command |
|---|---|
| Step 1 Enable TFTP on a server. | Consult your host vendor's TFTP Server documentation and RFCs 906 and 783. |
| Step 2 If you want to use a network-confg file to resolve the new router's name, create the file network-confg containing an IP address-to-host name mapping for the new router. Enter the ip host command into the TFTP config file, not into the router. The IP address must match the IP address that is to be dynamically obtained by the new router.
or Step 3 If you want to use the DNS to resolve the new router's name, create an address-to-name mapping entry for the new router in the DNS database. The IP address must match the IP address that is to be dynamically obtained by the new router. | ip host hostname address1
Contact the DNS administrator or refer to RFCs 1101 and 1183.
|
| Step 4 Create the file name-confg, which should reside in the tftpboot directory on the tftp server. The <name> part of name-confg must match the host name you assigned for the new router in the previous step. Enter into this file configuration commands for the new router. | See the appropriate chapter in this guide for specific commands. |
The name-confg file can contain either the new router's full configuration or a minimal configuration.
The minimal configuration file consists of a virtual terminal password and an enable password. It allows an administrator to Telnet into the new router to configure it. If you are using BootP or RARP to resolve the address of the new router, the minimal configuration file must also include the IP address to be obtained dynamically using BootP or RARP.
You can use the write network command to help you generate the configuration file that you will download during the Autoinstall process.
You can save a minimal configuration under a generic newrouter-confg file. Use the ip host command in the network.confg file to specify newrouter as the host name with the address you will be dynamically resolving. The new router should then resolve its IP address, host name and minimal configuration automatically. Use Telnet to connect to the new router from the existing router and use the setup facility to configure the rest of the interfaces. For example, the line in the network-confg file could be similar to the following:
ip host newrouter 131.108.170.1
The following host configuration file contains the minimal set of commands needed for AutoInstall using SLARP or BootP:
enable-password letmein
!
line vty 0
password letmein
!
end
The preceding example shows a minimal configuration for connecting from a router one hop away. From this configuration, use the setup facility to configure the rest of the interfaces. If the router is more than one hop away, you also must include routing information in the minimal configuration.
The following minimal network configuration file maps the new router's IP address, 131.108.10.2, to the host name newrouter. The new router's address was learned via SLARP and is based on existing router's IP address of 131.108.10.1.
ip host newrouter 131.108.10.2
If the new router is connected to the existing router using an Ethernet, Token Ring, or FDDI interface, you must configure a BootP or RARP server to map the new router's MAC address to its IP address. If the new router is connected to the existing router using a serial line with HDLC encapsulation, the steps in this section are not required.
To configure a BootP or RARP server, complete one of the following tasks:
| Task | Command |
|---|---|
| If BootP is to be used to resolve the new router's IP address, configure your BootP server. | Refer to your host vendor's manual pages and to RFCs 951 and 1395 |
| If RARP is to be used to resolve the new router's IP address, configure your RARP server. | Refer to your host vendor's manual pages and to RFC 903 |
The following host configuration file contains the minimal set of commands needed for AutoInstall using RARP. It includes the IP address that will be obtained dynamically via BootP or RARP during the AutoInstall process. When RARP is used, this extra information is needed to specify the proper netmask for the interface.
interface ethernet 0
ip address 131.108.10.2 255.255.255.0
enable-password letmein
!
line vty 0
password letmein
!
end
Connect the new router to the network using either an HDLC-encapsulated serial interface or an Ethernet, Token Ring, or FDDI interface. After the router successfully resolves its host name, newrouter sends a TFTP broadcast requesting the file name-confg. The router name must be in all lowercase, even if the true host name is not. The file is downloaded to the new router where the configuration commands take effect immediately. If the configuration file is complete, the new router should be fully operational. To save the complete configuration to NVRAM, complete the following steps:
| Task | Command |
|---|---|
| Step 1 Enter privileged mode at the system prompt on the new router. | enable 1 password |
| Step 2 Save the information from the name-config file into NVRAM. | write memory |
 | Caution Verify that the existing and new routers are connected before entering the write memory EXEC command to save these configuration changes. Use the ping EXEC command to verify connectivity. If an incorrect configuration file is downloaded, the new router will load NVRAM configuration information before it can enter AutoInstall mode. |
If the configuration file is a minimal configuration file, the new router comes up, but with only one interface operational. Complete the following steps to connect to the new router and configure it:
| Task | Command |
|---|---|
| Step 1 Establish a Telnet connection to the existing router. | telnet existing1 |
| Step 2 From the existing router, establish a Telnet connection to the new router | telnet newrouter |
| Step 3 Enter privileged EXEC mode. | enable password |
| Step 4 Enter setup mode to configure the new router. | setup2 |
To enter configuration mode, enter the EXEC command configure at the privileged-level EXEC prompt. The router responds with the following prompt asking you to specify the terminal, nonvolatile memory (NVRAM), or a file stored on a network server as the source of configuration commands:
Configuring from terminal, memory, or network [terminal]?
Each of these three methods is described in the next three sections.
The router accepts one configuration command per line. You can enter as many configuration commands as you want.
You can add comments to a configuration file describing the commands you have entered. Precede a comment with an exclamation point (!). Comments are not stored in NVRAM or in the active copy of the configuration file. In other words, comments do not show up when you list the active configuration with the write terminal EXEC command or list the configuration in NVRAM with the show configuration EXEC command. Comments are stripped out of the configuration file when it is loaded to the router. However, you can list the comments in configuration files stored on a TFTP or MOP server.
To configure the router from the terminal, complete the following tasks:
In the following example, the router is configured from the terminal. The comment "The following command provides the router host name" identifies the purpose of the next command line. The hostname command changes the router name from router1 to router2. By pressing Ctrl-Z, the user quits configuration mode. The command write memory loads the configuration changes into NVRAM.
Router1# configure terminal
Router1(config)# !The following command provides the router host name.
Router1(config)# hostname router2
Ctrl-Z
Router2# write memory
Nonvolatile memory stores the current configuration information in text format as configuration commands, recording only nondefault settings. The memory is checksummed to guard against corrupted data.
As part of its startup sequence, the router startup software always checks for configuration information in NVRAM. If NVRAM holds valid configuration commands, the router executes the commands automatically at startup. If the router detects a problem with the nonvolatile memory or the configuration it contains, it enters setup mode and prompts for configuration. Problems can include a bad checksum for the information in NVRAM or the absence of critical configuration information. See the publication Troubleshooting Internetworking Systems for troubleshooting procedures. See the Router Products Getting Started Guide for details on setup information.
You can configure the router from NVRAM by reexecuting the configuration commands stored in NVRAM. To do so, complete the following task in EXEC mode:
| Task | Command |
|---|---|
| Configure the router from NVRAM. | configure memory |
You can configure the router by retrieving and adding to the configuration file stored on one of your network servers. To do so, complete the following tasks:
In the following example, the router is configured from the file tokyo-config at IP address 131.108.2.155:
Router1# configure network
Host or network configuration file [host]?
IP address of remote host [255.255.255.255]? 131.108.2.155
Name of configuration file [tokyo-confg]?
Configure using tokyo-confg from 131.108.2.155? [confirm] y
Booting tokyo-confg from 131.108.2.155:!! [OK - 874/16000 bytes]
The order in which the router looks for configuration information depends upon the boot field setting in the configuration register. The configuration register is a 16-bit register. The lowest four bits of the configuration register (bits 3, 2, 1, and 0) form the boot field. To change the boot field and leave all other bits set to their default values, follow these guidelines:
For the Cisco 2000, Cisco 3000, Cisco 4000, or Cisco 7000 series running Software Release 9.1 or later, you can change the configuration register by completing the following tasks:
| Task | Command |
|---|---|
| Step 1 Enter configuration mode, selecting the terminal option. | configure terminal |
| Step 2 Modify the default configuration register setting. | config-register <value>1 |
| Step 3 Exit configuration mode. | Ctrl-Z |
For routers other than the Cisco 2000, Cisco 3000, Cisco 4000, or Cisco 7000 series running Software Release 9.1 or later, the configuration register can only be changed on the processor card or with DIP switches located at the back of the router. See the appropriate hardware installation guide for details.
Use the show version EXEC command to list the current configuration register setting and the new configuration register setting, if any, that will be used the next time the router is reloaded. In ROM monitor mode, use the o command to list the value of the boot field in the configuration register.
In the following example, the configuration register is set so that the router will boot automatically from the Flash memory default file. The last line of the output of the show version command indicates that a new configuration register setting (0x10F) will be used the next time the router is reloaded.
Router1# configure terminal
Router1(config)# config-register 0x10F
Ctrl-Z
Router1# show version
GS Software, Version 9.0(1)
Copyright (c) 1986-1992 by cisco Systems, Inc.
Compiled Fri 14-Feb-92 12:37
System Bootstrap, Version 4.3
Router1 uptime is 2 days, 10 hours, 0 minutes
System restarted by reload
System image file is unknown, booted via tftp from 131.108.13.111
Host configuration file is "thor-boots", booted via tftp from 131.108.13.111
Network configuration file is "network-confg", booted via tftp from
131.108.13.111
CSC3 (68020) processor with 4096K bytes of memory.
X.25 software.
Bridging software.
1 MCI controller (2 Ethernet, 2 Serial).
2 Ethernet/IEEE 802.3 interface.
2 Serial network interface.
32K bytes of non-volatile configuration memory.
Configuration register is 0x0 (will be 0x10F at next reload)
Router1# reload
You can enter multiple boot commands in NVRAM configuration to provide backup methods for loading a system image onto the router. There are three ways to load a system image:
You can enter the different types of boot commands in any order in NVRAM configuration. If you enter multiple boot commands, the router tries them in the order they are entered.
Flash memory is available for the AGS+, AGS, MGS, CGS, Cisco 2000, Cisco 3000, Cisco 4000, and Cisco 7000 platforms. Depending on the hardware platform, Flash memory might be available as EPROMs, SIMMs, or memory cards. Check the appropriate hardware installation and maintenance guide for information about types of Flash memory available on a specific platform.
Flash memory is located on the route processor (RP) in the Cisco 7000. Software images can be stored, booted, and rewritten into Flash memory as necessary. Flash memory can reduce the effects of network failure by reducing dependency on files that can only be accessed over the network.
Flash memory allows you to do the following:
Flash memory features include the following:
Note the following when loading from Flash memory:
The following list is an overview of how to configure your Cisco 7000 series system to boot from Flash memory. It is not a step-by-step set of instructions; rather, it is an overview of the process of using the Flash capability. Refer to the Cisco 7000 Hardware Installation and Maintenance publication for complete instructions for installing the hardware and netbooting, and in particular, for the jumper settings required for your configuration.
Once you have successfully configured Flash memory, you might want to configure the system with the no boot system flash command to revert back to booting from ROM.
Configure the router to automatically boot from an image in Flash memory by completing the following tasks:
| Task | Command |
|---|---|
| Step 1 Enter configuration mode from the terminal. | configure terminal |
| Step 2 Enter the filename of an image stored in Flash memory. | boot system flash [filename] |
| Step 3 Set the configuration register to enable loading of the system image from Flash memory. | config-register value1
|
| Step 4 Exit configuration mode. | Ctrl-Z |
| Step 5 Save the configuration information to NVRAM. | write memory |
Automatically booting from Flash memory requires changing the processor's configuration register. See the section entitled "Modify the Configuration Register Boot Field" earlier in this chapter. Use the show version command to list the current configuration register setting.
If you enter more than one image filename, the router tries them in the order entered.
If a filename already appears in the configuration file and you want to specify a new filename, remove the existing filename with the no boot system flash filename command.
To actually boot the system, perform the following task in EXEC mode:
| Task | Command |
|---|---|
| Boot the system. | reload |
The following example shows how to configure the router to automatically boot from an image in Flash memory:
Router# configure terminal
Router (config)# boot system flash gsnew-image
Ctrl-Z
Router# write memory
[ok]
Router# reload
[confirm]
%SYS-5-RELOAD: Reload requested
System Bootstrap, Version 4.6(0.16), BETA SOFTWARE
Copyright (c) 1986-1994 by cisco Systems
RP1 processor with 16384 Kbytes of memory
F3: 1871404+45476+167028 at 0x1000
Booting gsnew-image from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR [OK - 1916912/13767448 bytes]
F3: 1871404+45476+167028 at 0x1000
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
1525 O'Brien Drive
Menlo Park, California 94025
GS Software (GS7), Version 9.17(0.3), BETA SOFTWARE
Copyright (c) 1986-1992 by cisco Systems, Inc.
Compiled Thu 05-Nov-92 14:16 by mlw
Complete the following tasks to specify the loading of a system image from a network server. This process is called netbooting.
| Task | Command |
|---|---|
| Step 1 Enter configuration mode from the terminal. | configure terminal |
| Step 2 Specify the system image file to be netbooted from a TFTP or MOP server. | boot system [tftp] filename [ip-address] boot system mop filename [mac-address] [interface] |
| Step 3 Set the configuration register to enable loading of the system image from a network server. | config-register value1 |
| Step 4 Exit configuration mode. | Ctrl-Z |
| Step 5 Write the configuration information to NVRAM. | write memory |
The configuration register boot field must be set to the correct value. See "Modify the Configuration Register Boot Field" earlier in this chapter. Use the show version command to list the current configuration register setting.
You can also netboot from a compressed image. One reason to use a compressed image is to ensure that there is enough memory available to boot the router. On routers that do not contain a run from ROM image in EPROM, when the router netboots software, the image being booted and the running image both must fit into memory. If the running image is large, there might not be room in memory for the image being netbooted.
If there is not enough room in memory to netboot a regular image, you can produce a compressed software image on any UNIX platform using the compress program. Refer to your UNIX platform's documentation for the exact usage of the compress program.
In the following example, the router is configured to netboot from the testme5.tester system image file at IP address 131.108.13.111:
Router1# configure terminal
Router1(config)# boot system testme5.tester 131.108.13.111
Ctrl-Z
Router1# write memory
To specify the use of the ROM system image as a backup to other boot instructions in the configuration file, complete the following tasks:
| Task | Command |
|---|---|
| Step 1 Enter configuration mode from the terminal. | configure terminal |
| Step 2 Specify use of the ROM system image as a backup image. | boot system rom |
| Step 3 Set the configuration register to enable loading of the system image from ROM. | config-register value1 |
| Step 4 Exit configuration mode. | Ctrl-Z |
| Step 5 Save the configuration information to NVRAM. | write memory |
In the following example, the router is configured to boot a Flash image called image1 first. Should that image fail, the router will boot the configuration file backup1 from a network server. If that method should fail, then the system will boot from ROM.
Router1# configure terminal
Router1(config)# boot system flash image1
Router1(config)# boot system backup1 131.108.20.4
Router1(config)# boot system rom
Ctrl-Z
Router1# write memory
Occasionally network failures make netbooting impossible. To lessen the effects of network failure, consider the following boot strategy. After Flash is installed and configured, you may want to configure the router to boot in the following order:
This boot order provides the most fault-tolerant alternative in the netbooting environment. Use the following commands in your configuration to allow you to boot first from Flash, then from a system file, and finally from ROM:
| Task | Command |
|---|---|
| Step 1 Enter configuration mode from the terminal | configure terminal |
| Step 2 Configure the router to boot from Flash memory. | boot system flash [filename]
|
| Step 3 Configure the router to boot from a system filename. | boot system filename [ip-address]
|
| Step 4 Configure the router to boot from ROM. | |
| Step 5 Set the configuration register to enable loading of the system image from a network server or Flash | config-register value1 |
| Step 6 Exit configuration mode. | Ctrl-Z |
| Step 7 Save the configuration information to NVRAM. | write memory |
The order of the commands needed to implement this strategy is shown in the following example:
Router# configure terminal
Router(config)# boot system flash gsxx
Router(config)# boot system gsxx 131.131.101.101
Router(config)# boot system rom
Ctrl-Z
Router# write memory
[ok]
Router#
Using this strategy, a router used primarily in a netbooting environment would have three alternative sources from which to boot. These alternative sources would help cushion the negative effects of a failure with the TFTP file server and of the network in general.
Configuration files can be stored on network servers. You can configure the router to automatically request and receive two configuration files from the network server:
The first file the server attempts to load is the network configuration file. The network configuration file contains information that is shared among several routers. For example, it can be used to provide mapping between IP addresses and host names.
The second file is the host configuration file, which contains commands that apply to one router in particular. Both the network and host configuration files must reside on a reachable TFTP server and be readable.
You can specify an ordered list of network configuration filenames and host configuration filenames. The router scans this list until it successfully loads the appropriate network or host configuration file.
To configure the router to download a network configuration file from a server upon restart, complete the following tasks. Step 2 is optional. If you do not specify a network configuration filename, the router uses the default filename network-confg.
You can specify more than one network configuration file. The router tries them in order until it loads one successfully. This procedure can be useful for keeping files with different configuration information loaded on a network server.
To configure the router to download a host configuration file from a server upon restart, complete the following tasks. Step 2 is optional. If you do not specify a host configuration filename, the router uses its own name to form a host configuration filename by converting the router name to all lowercase letters, removing all domain information, and appending -confg. If no host name information is available, the router uses the default host configuration filename router-confg.
You can specify more than one host configuration file. The router tries them in order until it loads one successfully. This procedure can be useful for keeping files with different configuration information loaded on a network server.
In the following example, the router is configured to boot from the host configuration file hostfile1 and from the network configuration file networkfile1:
Router1# configure terminal
Router1(config)# boot host hostfile1
Router1(config)# boot network networkfile1
Router1(config)# service config
Ctrl-Z
Router1# write memory
If the network server fails to load a configuration file during startup, it tries again every ten minutes (default setting) until a host provides the requested files. With each failed attempt, the network server displays a message on the console terminal. If the network server is unable to load the specified file, it displays the following message:
Booting host-confg... [timed out]
Refer to the Troubleshooting Internetworking Systems publication for troubleshooting procedures. If there are any problems with the configuration file pointed to in NVRAM, or the configuration register is set to ignore NVRAM, the router will enter the setup command facility. See the Router Products Getting Started Guide for details on the setup command.
The buffer that holds the configuration commands is generally the size of nonvolatile memory. Complex configurations may need a larger configuration file buffer size. To change the buffer size, complete the following tasks:
In the following example, the buffer size is set to 50000 bytes:
Router1# configure terminal
Router1(config)# boot buffersize 50000
Ctrl-Z
Router1# write memory
On the Cisco 7000 series, Cisco 4000, Cisco 3000, and AGS+ routers that have NVRAM, you can compress configuration files. To compress configuration files, perform the following tasks:
Installing new ROMs is a one-time operation, and is only necessary if you do not already have IOS Release 10 in ROM. Before you can load a large (that is, larger than the size of NVRAM) configuration, you must issue the service compress-config command. The configure terminal command works only if you have IOS Release 10 boot ROMs. It does not work with 9.17 ROMs.
If your router does not find a valid system image, or if its configuration file is corrupted at startup, and the configuration register is set to enter ROM monitor mode, the system might enter read-only memory (ROM) monitor mode. From this mode, you can manually load a system image from Flash, from a network server file, or from ROM.
You can also enter ROM monitor mode by restarting the router and then pressing the Break key during the first 60 seconds of startup.
To manually boot from Flash memory, complete the following tasks:
| Task | Command |
| Step 1 Restart the router. | reload |
| Step 2 Press the Break key during the first 60 seconds while the system is starting up. | Break1 |
| Step 3 Manually boot the router. | b flash [filename] |
In the following example, the router is manually booted from Flash memory. Since the optional filename argument is absent, the first file in Flash memory will be loaded.
> b flash
F3: 1858656+45204+166896 at 0x1000
Booting gs7-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR [OK -
1903912/13765276 bytes]
F3: 1858676+45204+166896 at 0x1000
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
In the following example, the boot flash command is used with the filename gs7-k. That is the file that will be loaded.
> b flash gs7-k
F3: 1858656+45204+166896 at 0x1000
Booting gs7-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRR [OK - 1903912/13765276 bytes]
F3: 1858676+45204+166896 at 0x1000
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
System Bootstrap, Version 4.6(1012) [mlw 99], INTERIM SOFTWARE
Copyright (c) 1986-1992 by cisco Systems
RP1 processor with 16384 Kbytes of memory
To manually boot from a network file, complete the following tasks in EXEC mode:
| Task | Command |
| Step 1 Restart the router. | reload |
| Step 2 Press the Break key during the first 60 seconds while the system is starting up. | Break1 |
| Step 3 Manually boot the router. | b filename [ip-address] |
In the following example, the router is manually booted from the network file network1:
>b network1
To manually boot the router from ROM, complete the following steps in EXEC mode:
| Task | Command |
| Step 1 Restart the router. | reload |
| Step 2 Press the Break key during the first 60 seconds while the system is starting up. | Break1 |
| Step 3 Manually boot the router from ROM. | b |
In the following example, the router is manually booted from ROM:
>b
As a TFTP server host, the router responds to TFTP Read Request messages by sending a copy of the system image contained in ROM or one of the system images contained in Flash to the requesting host. The TFTP Read Request message must use one of the filenames that are specified in the router's configuration.
The following algorithm is used when deciding whether to send the ROM or Flash image:
To specify TFTP server operation for a router, complete the following tasks:
The TFTP session can sometimes fail. To help determine why a TFTP session failed, TFTP generates an "E" character if it receives an erroneous packet, and an "O" character if it receives an out-of-sequence packet. A period (.) indicates a timeout. The transfer session may still succeed even if TFTP generates these characters, but the output is useful for diagnosing the transfer failure. For troubleshooting procedures, refer to the Troubleshooting Internetworking Systems publication.
In the following example, the router is configured to send, via TFTP, a copy of the ROM software when it receives a TFTP read request for the file version 9.0. The requesting host is checked against access list 22.
tftp-server system version-9.0 22
You can configure the router as a RARP server. With this feature, RARP requests can be answered by the router, thereby allowing the router to make possible diskless booting of various systems, such as Sun workstations or PCs, on networks where the client and server are on separate subnets.
To configure the router as a RARP server, perform the following task in interface configuration mode:
| Task | Command |
|---|---|
| Configure the router as a RARP server. | ip rarp-server ip-address |
In the following example, the router is configured to act as a RARP server. Figure 3-4 illustrates the network configuration.
! Allow the router to forward broadcast portmapper requests
ip forward-protocol udp 111
! Provide the router with the IP address of the diskless sun
arp 128.105.2.5 0800.2002.ff5b arpa
interface ethernet 0
! Configure the router to act as a RARP server, using the Sun Server's IP
! address in the RARP response packet.
ip rarp-server 128.105.3.100
! Portmapper broadcasts from this interface are sent to the Sun Server.
ip helper-address 128.105.3.100
The Sun client and server machine's IP addresses must use the same major network number due to a limitation of the current SunOS rpc.BootParamd daemon.
The Boot Protocol (BootP) server for SLIP supports the extended BootP requests specified in RFC 1084. The following command is useful in conjunction with using the auxiliary port as an asynchronous interface. To configure extended BootP requests for SLIP, perform the following task in global configuration mode:
| Task | Command |
|---|---|
| Configure extended BootP requests for SLIP. | async-bootp tag [:hostname] data1 |
You can display the extended BootP requests by performing the following task in EXEC mode:
| Task | Command |
|---|---|
| Show parameters for BootP requests. | show async-bootp1 |
To change the router's parameters for retransmitting boot requests to a MOP server, complete the following tasks:
By default, when the router transmits a request that requires a response from a MOP boot server and the server does not respond, the message will be retransmitted after four seconds. If the MOP boot server and router are separated by a slow serial link, it may take longer than four seconds for the router to receive a response to its message. Therefore, you might want to configure the router to wait longer than four seconds before retransmitting the message if you are using such a link.
In the following example, if the MOP boot server does not respond within 10 seconds after the router sends a message, the router will retransmit the message:
mop retransmit-timer 10
You can copy a system image from a TFTP server to Flash memory by completing the following tasks:
| Task | Command |
|---|---|
| Step 1 Make a backup copy of the current system software image. | See the instructions in the section "Copy System Images from Flash Memory to a Network Server" later in this chapter. |
| Step 2 Copy a system image to Flash memory. | copy tftp flash |
| Step 3 When prompted, enter the IP address or domain name of the server. | ip-address or name |
| Step 4 When prompted, enter the filename of the server system image. | filename |
buffer overflow - xxxx/xxxx, will appear, where xxxx/xxxx is the number of bytes read in/number of bytes available.
The server system image copied to the Flash memories for the AGS+, AGS, MGS, and CGS must be at least Software Version 9.0 or above. For Cisco 2000, Cisco 3000, Cisco 4000, and Cisco 7000 series, the server system image must be at least Software Version 9.1 or above.
Once you give the copy tftp flash command, the system prompts you for the IP address (or domain name) of the TFTP server. This can be another router serving ROM or Flash system software images. You are then prompted for the filename of the software image and when there is free space available in Flash memory, you are given the option of erasing the existing Flash memory before writing onto it. If no free Flash memory space is available, or if the Flash memory has never been written to, the erase routine is required before new files can be copied. The system will inform you of these conditions and prompt you for a response. Note that the Flash memory is erased at the factory before shipment.
If you attempt to copy a file into Flash memory that is already there, a prompt will tell you that a file with the same name already exists. This file is "deleted" when you copy the new file into Flash. The first copy of the file still resides within Flash memory, but is rendered unusable in favor of the newest version, and will be listed with the [deleted] tag when you use the show flash command. If you abort the copy process, the newer file will be marked [deleted] because the entire file was not copied and is, therefore, not valid. In this case, the original file in Flash memory is valid and available to the system.
Following is sample output (copying a system image named gs7-k) of the prompt you will see when using the copy tftp flash command when Flash memory is too full to copy the file. The filename gs7-k can be in either lowercase or uppercase; the system will see GS7-K as gs7-k. If more than one file of the same name is copied to Flash, regardless of case, the last file copied will become the valid file.
env-chassis# copy tftp flash
IP address or name of remote host [255.255.255.255]? dirt
Translating "DIRT"...domain server (255.255.255.255) [OK]
Name of file to copy ? gs7-k
Copy gs7-k from 131.108.13.111 into flash memory? [confirm]
Flash is filled to capacity.
Erasure is needed before flash may be written.
Erase flash before writing? [confirm]
Erasing flash EPROMs bank 0
Zeroing bank...zzzzzzzzzzzzzzzz
Verify zeroed...vvvvvvvvvvvvvvvv
Erasing bank...eeeeeeeeeeeeeeee
Erasing flash EPROMs bank 1
Zeroing bank...zzzzzzzzzzzzzzzz
Verify zeroed...vvvvvvvvvvvvvvvv
Erasing bank...eeeeeeeeeeeeeeee
Erasing flash EPROMs bank 2
Zeroing bank...zzzzzzzzzzzzzzzz
Verify zeroed...vvvvvvvvvvvvvvvv
Erasing bank...eeeeeeeeeeeeeeee
Erasing flash EPROMs bank 3
Zeroing bank...zzzzzzzzzzzzzzzz
Verify zeroed...vvvvvvvvvvvvvvvv
Erasing bank...eeeeeeeeeeeeeeee
Loading from 131.108.1.111: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 1906676/4194240 bytes]
Verifying via checksum...
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvv
Flash verification successful. Length = 1906676, checksum = 0x12AD
Following is sample output from copying a system image named gs7-k into the current Flash configuration, in which a file of the name gs7-k already exists:
env-chassis# copy tftp flash
IP address or name of remote host [131.108.13.111]?
Name of file to copy ? gs7-k
File gs7-k already exists; it will be invalidated!
Copy gs7-k from 131.108.13.111 into flash memory? [confirm]
2287500 bytes available for writing without erasure.
Erase flash before writing? [confirm]n
Loading from 131.108.1.111: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 1906676/2287500 bytes]
Verifying via checksum...
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvv
Flash verification successful. Length = 1902192, checksum = 0x12AD
In the following example, the Flash security jumper is not installed, so you cannot write files to Flash memory.
Everest# copy tftp flash
Flash: embedded flash security jumper(12V)
must be strapped to modify flash memory
You can copy normal or compressed images to Flash memory. You can produce a compressed system image on any UNIX platform using the compress command. Refer to your UNIX platform's documentation for the exact usage of the compress command.
The following example shows sample output from copying a system image named IJ09140Z into the current Flash configuration.
Router# copy tftp flash
IP address or name of remote host [255.255.255.255]? server1
Name of tftp filename to copy into flash []? IJ09140Z
copy IJ09140Z from 131.131.101.101 into flash memory? [confirm] <Return>
xxxxxxxx bytes available for writing without erasure.
erase flash before writing? [confirm] <Return>
Clearing and initializing flash memory (please wait)####...
Loading from 101.2.13.110: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!... [OK - 324572/524212 bytes]
Verifying checksum...
VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV...
Flash verification successful. Length = 1204637, checksum = 0x95D9
The series of pound signs (#) indicates that each Flash device is being cleared and initialized; one per device. Different router platforms use different ways of indicating that Flash is being cleared. The exclamation points (!) indicate the copy process. The series of Vs indicates that a checksum is calculated. An O would have indicated an out-of-order packet. A period (.) would have indicated a timeout. The last line in the sample configuration indicates that the copy is successful.
Flash load helperis a software option available to users who want to upgrade their system software on run-from-Flash systems. Flash load helper simplifies the upgrade procedure without requiring additional hardware; however, it does require some brief network downtime. A system image running from Flash can use Flash load helper only if the boot ROMs support Flash load helper. If the boot ROMs do not support Flash load helper, you must perform the Flash upgrade manually.
Flash load helper involves an automated procedure that reloads from the current running image to the ROM-based bootstrap image, downloads to Flash memory, and reboots to the system image in Flash memory. Flash load helper performs checks and validations to maximize the success of a Flash upgrade and minimize the chance of leaving Flash memory in either an erased state or with a file that cannot boot.
In run-from-Flash systems, the software image in the router is stored in the Flash EPROM and executed from there (as opposed to being executed from RAM), thereby reducing memory cost. A run- from-Flash system requires enough Flash EPROM to hold the image and enough main system RAM to hold the routing tables and data structures. The system does not need the same amount of main system RAM as a run-from-RAM system because the full image does not reside in RAM. Run-from-Flash systems include the Cisco 2500 series.
Flash load helper includes the following features:
To download a new file to Flash memory, enter the copy tftp flash EXEC command. Use the show flh-log EXEC command to view the system console output generated during the Flash load helper operation. Because remote Telnet users might perform the Flash upgrade without a console connection, this command allows them to retrieve console output when their Telnet connection has terminated due to the switch to the ROM image.
Flash load helper also supports the copy mop flash command. However, the copy mop flash command does not provide all the enhanced features available in the copy tftp flash command. Specifically, it does not provide the access check for the file on the MOP server, the size check to ensure that the file will fit into Flash memory, or warnings if the file is not appropriate for the system. Another difference between the copy tftp flash command and the copy mop flash command is that there is no prompt for the MOP server address (similar to the TFTP server address prompt), because the MOP server is automatically solicited. Other enhanced features of the copy mop flash command are identical to the copy tftp flash command enhanced features.
To upgrade system software using Flash load helper, perform one of the following tasks in privileged EXEC mode:
| Task | Command |
|---|---|
| Begin to download a file from a TFTP server to Flash memory. | copy tftp flash |
| Begin to download a file from a MOP server to Flash memory. | copy mop flash |
As long as the boot ROMs support Flash load helper, executing the copy tftp flash command automatically invokes Flash load helper.
You can always invoke Flash load helper from a console terminal. You can also invoke Flash load helper from a virtual terminal (for example, a Telnet session) if the system is configured for auto-booting. This means that the boot bits in the system configuration register must be nonzero. Refer to the appropriate hardware installation manual for information about setting the boot bits.
The following error message appears if you are in a Telnet session and the system is set for manual booting (the boot bits in the configuration register are zero).
Router# copy tftp flash
ERR: Config register boot bits set for manual booting
This helps minimize the chance of having the system go down to the ROM monitor prompt (and taken out of the remote Telnet user's control) in case of any catastrophic failure in the Flash upgrade. The system would try to bring up at least the boot ROM image if it cannot boot an image from Flash. You must go into global configuration mode and change the configuration register value (using the config-register command) so that the boot bits are nonzero before reinitiating the copy tftp flash command.
The copy tftp flash command initiates a dialog similar to the following:
Router# copy tftp flash
*************************** NOTICE *******************************
Flash load helper v1.0
This process will accept the TFTP copy options and then terminate the current system image to use the ROM based image for the copy. Router functionality will not be available during that time. If you are logged in via telnet, this connection will terminate. Users with console access can see the results of the copy operation.
******************************************************************
If any terminals other than the one on which this command is being executed are active, the following message appears:
There are active users logged into the system.
Proceed? [confirm] y
System flash directory:
File Length Name/status
1 2251320 abc/igs-kf.914
[2251384 bytes used, 1942920 available, 4194304 total]
Enter the IP address or name of the remote host you are copying from:
Address or name of remote host [255.255.255.255]? 131.108.1.111
Enter the name of the file you want to copy:
Source file name? abc/igs-kf.914
Enter the name of the destination file:
Destination file name [default = source name]? <Return>
Accessing file 'abc/igs-kf.914' on 131.108.1.111....
Loading from 131.108.13.111:
Erase flash device before writing? [confirm] <Return>
If you choose to erase Flash memory, the dialog continues as follows. The copy tftp flash operation verifies the request from the running image by trying to TFTP a single block from the remote TFTP server. Then the Flash load helper is executed, causing the system to reload to the ROM-based system image.
Erase flash device before writing? [confirm] y
Flash contains files. Are you sure? [confirm] y
If the file does not seem to be a valid image for the system, a warning is displayed and a separate confirmation is sought from the user.
Copy 'abc/igs-kf.914' from TFTP server
as 'abc/igs-kf.914' into Flash WITH erase? y
%SYS-5-RELOAD: Reload requested
%FLH: rxboot/igs-kf.914r from 131.108.1.111 to flash ...
If you choose not to erase Flash memory and there is no file duplication, the dialog would have continued as follows:
Erase flash device before writing? [confirm] n
Copy 'abc/igs-kf.914' from TFTP server
as 'abc/igs-kf.914' into Flash WITHOUT erase? y
If you choose not toerase Flash memory, and there was file duplication, the dialog would have continued as follows:
Erase flash device before writing? [confirm] n
File 'abc/igs-kf.914' already exists; it will be invalidated!
Invalidate existing copy of 'abc/igs-kf' in flash memory? [confirm] y
Copy 'abc/igs-kf.914' from TFTP server
as 'abc/igs-kf.914' into Flash WITHOUT erase? y
If the configuration has been modified but not yet saved, you are prompted to save the configuration:
System configuration has been modified. Save? [confirm]
If you confirm to save the configuration, you might also receive the following message:
Warning: Attempting to overwrite an NVRAM configuration previously written by a different version of the system image. Overwrite the previous NVRAM configuration? [confirm]
If you have an open Telnet connection, you are notified of the system reload, as follows:
**System going down for Flash upgrade**
In case of TFTP failures, the copy operation is retried up to three times. If the failure happens in the middle of a copy (part of the file has been written to Flash memory), the retry does not erase Flash unless you specified an erase. The partly written file is marked as deleted and a new file is opened with the same name. If Flash memory runs out of free space in this process, the copy is terminated.
After the Flash load helper finishes its copy (whether successful or not), it automatically attempts an auto boot or a manual boot, depending on the value of the boot bits in the configuration register. If the boot bits are zero, the system attempts a default boot from Flash memory (equivalent to a manual b flash command at the ROM monitor prompt) to load up the first bootable file in Flash.
If the boot bits are nonzero, the system attempts to boot based on the boot configuration commands. If no boot configuration commands exist, the system attempts a default boot from Flash (load the first bootable file in Flash memory).
Because you may be a remote Telnet user performing the Flash upgrade without a console connection, you can retrieve console output when your Telnet connection has terminated due to the switch to the ROM image. The output indicates what happened during the download, and is particularly useful if the download fails.
To view the system console output generated during the Flash load helper operation, perform the following task in EXEC mode:
| Task | Command |
|---|---|
| Display console output generated by Flash load helper. | show flh-log |
In addition to Flash load helper, Release 9.14(8) rxboot adds Flash enhancements for the Cisco 4000 and the Cisco 3000 platforms which are not run-from-Flash systems. To have these enhancements, you must update the rxboot ROM to version 9.14(8). These enhancements cover Flash upgrades, automatic booting, and reloads. The improvements are as follows:
Before booting from Flash memory, verify that the checksum of the image in Flash memory matches the checksum listed in the README file that was distributed with the system software image. The checksum of the image in Flash memory is displayed at the bottom of the screen when you issue the copy tftp flash command. The README file was copied to the TFTP server automatically when you installed the system software image on the TFTP server.
| Caution If the checksum value is not correct according to the value in the README file, do not reboot the router. Issue the copy tftp flash command and compare the checksums again. If the checksum is repeatedly wrong, copy the original system software image back into Flash memory before you reboot the router from Flash memory. If you have a bad image in Flash memory and try to boot from Flash, the router will start the system image contained in ROM (assuming netbooting is not configured). If ROM does not contain a fully functional system image, the router will not function and will have to be reconfigured through a direct console port connection. |
This section describes the dual Flash bank feature. Dual Flash bank allows you to partition a Flash device to maintain two separate files systems in one Flash memory device.
Dual Flash bank is a software feature available in IOS Release 10.0(6) and later on low-end systems that have at least two banks of Flash memory. It allows you to partition these banks into two separate, logical devices so that each logical device has its own file system. Low-end systems supported are the AccessPro PC card, Cisco 2500 series, Cisco 3000 series, and Cisco 4000 series.
There must be at least two banks of Flash and one bank is a set of 4 chips. The minimum partition size is the size of a bank.
Since the boot ROMs must be capable of accessing files in any file system, boot ROMS must be one of the following versions:
There are several benefits to partitioning Flash memory:
You might use Flash load helper rather than dual Flash bank for one of the following reasons:
Partitioning requires that run-from-Flash images be loaded into different Flash memory banks at different physical addresses. This means that images must be relocatable. A relocatable image is an image that contains special relocation information that allows the following:
Run-from-Flash systems (the Cisco 2500 series and Cisco 3000 series) execute images that need to be stored in Flash memory at a specific address. This means storing the image as the first file in Flash. If the image is stored at any other location in Flash, it cannot be executed, nor can the image be executed from RAM. The relocatable image is necessary to overcome this limitation.
With Flash partitioning, the run-from-Flash images will not work unless loaded into the first device as the first file. This requirement defeats the purpose of partitioning. However, relocatable images can be loaded into any Flash partition (and not necessarily as the first file within the partition) and executed in place.
Note that unless downloaded as the first file in the first partition, this download must be done by an image that recognizes relocatable images.
A relocatable image is an image that is IOS Release 10.0(6) or later. A nonrelocatable image is an image that was created before the relocatable image era (and hence does not recognize relocatable images). The following are nonrelocatable images:
You can identify a relocatable image by its name. The naming convention for image names for storage on a UNIX system is as follows:
platform-capabilities-type
The letter "l" in the type field indicates a relocatable image. The following are examples of some relocatable image names:
Only the "igs" prefix images used by the Cisco 3000 series and Cisco 2500 series are available as relocatable images. Images distributed on floppy diskettes might have different naming conventions.
For backward compatibility, the relocatable images have been linked to execute as the first file in the first Flash memory bank. This makes the images similar to previous Flash images. Thus, if you download a relocatable image into a nonrelocatable image system, the image will run correctly from Flash memory.
If you upgrade to IOS Release 10.0(6) from a previous software release, you need to erase Flash when you are prompted during the download. This is to ensure that the image is downloaded as the first file in Flash memory.
To partition Flash memory, perform the following task in global configuration mode:
| Task | Command |
|---|---|
| Partition Flash memory. | partition flash partitions [size1 size2] |
Tis command will succeed only if the system has at least two banks of Flash and the partitioning does not cause an existing file in Flash to be split across the two partitions.
To download a file into a Flash partition, perform one of the following tasks in EXEC mode:
| Task | Command |
|---|---|
| Download a file from a TFTP server into a Flash partition. | copy tftp flash |
| Download a file from a MOP server into a Flash partition. | copy mop flash |
The prompts displayed after you execute the copy tftp flash or copy mop flash commands indicate the method by which the download can be done into each partition. The possible methods are:
If the image can be downloaded can be done into more than one partition, you are prompted for the partition number. Enter the following at the partition number prompt to obtain help:
To manually boot the router from Flash memory, perform one of the following tasks in ROM monitor mode:
The result of booting a relocatable image from Flash memory depends on where and how the image was downloaded into Flash memory. For a definition of relocatable and nonrelocatable images, see the section "Relocatable Images" provided earlier. Table 3-1 describes various means by which an image could be downloaded and the corresponding result of booting from Flash.
| How Downloaded | Result of Booting From Flash |
|---|---|
| The image was downloaded as the first file by a nonrelocatable image. | The image will execute in place from Flash, just like a run-from-Flash image. |
| The image was downloaded not as the first file by a nonrelocatable image. | The nonrelocatable image would not have relocated the image before storage in Flash. This image will not be booted. |
| The image was downloaded as the first file by a relocatable image. | The image will execute in place from Flash, just like a run-from-Flash image. |
| The image was downloaded not as the first file by a relocatable image (including download into the second partition). | The relocatable image relocates the image before storage in Flash. Hence, the image will execute in place from Flash, just like any other run-from-Flash image. |
To configure the router to boot automatically from Flash, perform one of the following tasks in global configuration mode:
The result of booting a relocatable image from Flash depends on where and how the image was downloaded into Flash. Table 1 shown earlier describes various means by which an image could be downloaded and the corresponding result of booting from Flash.
To configure a Flash partition as a TFTP server, perform one of the following tasks in global configuration mode:
Once you have specified TFTP server operation, exit configuration mode and save the configuration information to nonvolatile memory.
You can copy a system image back to a network server. This copy of the system image can serve as a backup copy and also can be used to verify that the copy in Flash is the same as on the original file on disk. To copy the system image to a network server, perform the following task:
The following example uses the show flash all command to learn the name of the system image file and the copy flash tftp command to copy the system image to a TFTP server. The name of the system image file (xk09140z) is listed near the end of the show flash all output.
Router# show flash all
2048K bytes of flash memory on embedded flash (in XX).
ROM socket code bytes name
0 U42 89BD 0x40000 INTEL 28F020
1 U44 89BD 0x40000 INTEL 28F020
2 U46 89BD 0x40000 INTEL 28F020
3 U48 89BD 0x40000 INTEL 28F020
4 U41 89BD 0x40000 INTEL 28F020
5 U43 89BD 0x40000 INTEL 28F020
6 U45 89BD 0x40000 INTEL 28F020
7 U47 89BD 0x40000 INTEL 28F020
security jumper(12V) is installed,
flash memory is programmable.
file offset length name
0 0x40 1204637 xk09140z
[903848/2097152 bytes free]
Router# copy flash tftp
IP address of remote host [255.255.255.255]? 101.2.13.110
filename to write on tftp host? xk09140z
writing xk09140z !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
successful tftp write.
Router#
To stop the copy process, press Ctrl-^. Refer to the Troubleshooting Internetworking Systems publication for procedures on how to resolve Flash memory problems.
Once you have configured Flash memory, you might want to configure the system (using the configure terminal command) with the no boot system flash configuration command to revert to booting from ROM (for example, if you do not yet need this functionality, if you choose to netboot, or if you do not have the proper image in Flash memory). After you enter the no boot system flash command, use the write memory command to save the new configuration command to NVRAM.
This procedure on the Cisco 7000 series also requires changing the jumper on the processor's configuration register. Refer to the appropriate hardware installation and maintenance manual for instructions.
You can copy a configuration file from the router to a network server. The configuration file that you copy to usually must already exist on the TFTP server and be globally writable before the TFTP server allows you to write to it.
To store configuration information on a network server, complete the following tasks in the EXEC mode:
The command prompts you for the destination host's address and a filename, as the following example illustrates.
The following example copies a configuration file from a router to a server:
Tokyo# write network
Remote host [131.108.2.155]?
Name of configuration file to write [tokyo-confg]?
Write file tokyo-confg on host 131.108.2.155? [confirm] y
#
Writing tokyo-confg !! [OK]
Perform the following tasks in EXEC mode to display information about system software, system image files, and configuration files:
You can also use the o command in ROM monitor mode to list the configuration register settings on some models.
The Flash content listing does not include the checksum of individual files. To recompute and verify the image checksum after the image is copied into Flash memory, complete the following task in EXEC mode:
| Task | Command |
|---|---|
| Recompute and verify the image checksum after the image is copied into Flash memory | copy verify |
When you enter this command, the screen prompts you for the filename to verify. By default, it prompts for the last (most recent) file in Flash. Press Return to recompute the default file checksum or enter the filename of a different file at the prompt. Note that the checksum for microcode images is always 0x0000.
To clear the contents of nonvolatile memory, perform the following task in EXEC mode:
| Task | Command |
|---|---|
| Clear the contents of NVRAM. | write erase |
To reexecute the configuration commands in nonvolatile memory, perform the following task in EXEC mode:
| Task | Command |
|---|---|
| Reexecute the configuration commands in NVRAM. | configure memory |
Flash memory can be used as a TFTP file server for other routers on the network. This feature allows you to boot a remote router with an image that resides in the Flash server memory.
In the description that follows, one Cisco 7000 router is referred to as the Flash server, and all other routers are referred to as client routers. Example configurations for the Flash server and client routers include commands as necessary.
The Flash server and client router must be able to reach one another before the TFTP function can be implemented. Verify this connection by pinging between the Flash server and client router (in either direction) using the ping command.
An example use of the ping command is as follows:
Router# ping 131.131.101.101 <Return>
In this example, the Internet Protocol (IP) address of 131.131.101.101 belongs to the client router. Connectivity is indicated by !!!!!, while ... [timed out] or [failed] indicates no connection. If the connection fails, reconfigure the interface, check the physical connection between the Flash server and client router, and ping again.
After you verify the connection, ensure that a TFTP-bootable image is present in Flash memory. This is the system software image the client router will boot. Note the name of this software image so you can verify it after the first client boot.
| Caution For full functionality, the software residing in the Flash memory must be the same type as the ROM software installed on the client router. For example, if the server has X.25 software, and the client does not have X.25 software in ROM, the client will not have X.25 capabilities after booting from the server's Flash memory. |
Perform the following task in EXEC mode to configure the Flash server by adding the tftp-server system command to the configuration memory:
| Task | Command |
|---|---|
| Enter configuration mode from the terminal. | configure terminal |
| Specify TFTP server operation for a router. | tftp-server system filename [ip-access-list] |
The following example shows the use of configure terminal command to get into configuration mode and configure the Flash server:
Server# configure terminal
Enter configuration commands, one per line.
Edit with DELETE, CRTL/W, and CRTL/U; end with CTRL/Z
Server# tftp-server system gs7-k.9.17 1
Server# access-list 1 permit 131.131.101.0 0.0.0.255
Ctrl-Z
Server# write memory <Return>
[ok]
Server#
This example gives the filename of the software image in the Flash server and one access list (labeled 1). The access list must include the network where the client router resides. Thus, in the example, the network 131.131.101.0 and any client routers on it are permitted access to the Flash server filename gs7-k.9.17.
Configure the client router using the boot system rom command. Use the configure terminal command to enter this commands into the client router's memory configuration. Using these commands on the Cisco 7000 requires changing the jumper on the configuration register of the processor to the pattern 0-0-1-0 (Position 1). For this exercise, the IP address of the Flash server is 131.131.111.111.
| Task | Command |
|---|---|
| Enter configuration mode from the terminal. | configure terminal |
| Boot the router from ROM. | boot system rom |
| Caution Using the no boot system command in the following example will invalidate all other boot system commands currently in the client router system configuration. Before proceeding, determine whether the system configuration stored in the client router should first be saved (uploaded) to a TFTP file server so you have a backup copy. |
Following is an example of the use of these commands:
Client# configure terminal
Enter configuration commands, one per line.
Edit with DELETE, CRTL/W, and CRTL/U; end with CTRL/Z
Client# no boot system
Client# boot system gs7-k.9.17 131.131.111.111
Client# boot system rom
Ctrl-Z
Client# write memory <Return>
[ok]
Server# reload
In this example, the no boot system command invalidates all other boot system commands currently in the configuration memory, and any boot system commands entered after this command will be executed first. The second command, boot system filename address, tells the client router to look for the file gs7-k.9.17 in the (Flash) server with an IP address of 131.131.111.111. Failing this, the client router will boot from its system ROM upon the boot system rom command, which is included as a backup in case of a network problem. The write memory command copies the configuration to memory, and the reload command boots the system.
| Caution The system software (gs7-k.9.17) to be booted from the Flash server (131.131.111.111) must reside in Flash memory on the server. If it is not in Flash memory, the client router will boot the Flash server's system ROM. |
Use the show version command on the client router to verify that the software image booted from the Flash server is the image present in Flash memory.
Following is sample output of the show version command:
env-chassis> show version
GS Software (GS7), Version 9.1.17
Copyright (c) 1986-1992 by cisco Systems, Inc.
Compiled Wed 21-Oct-92 22:49
System Bootstrap, Version 4.6(0.15)
Current date and time is Thu 10-22-1992 13:15:03
Boot date and time is Thu 10-22-1992 13:06:55
env-chassis uptime is 9 minutes
System restarted by power-on
System image file is "gs7-k.9.17", booted via tftp from 131.131.111.111
RP1 (68040) processor with 16384K bytes of memory.
X.25 software.
Bridging software.
1 Switch Processor.
1 EIP controller (6 Ethernet).
6 Ethernet/IEEE 802.3 interface.
128K bytes of non-volatile configuration memory.
4096K bytes of flash memory on embedded flash (in RP1).
Configuration register is 0x0
The important information in this example is contained in the first line (GS Software...) and in the line that begins with "System image file...." The two software types and versions shown indicate the software currently running in RAM in the client router (first line) and the software booted from the Flash server (last line). These two types and versions must be the same.
Verify that the software shown in the first line of the previous example is the software residing in the Flash server memory.
Cisco 7000 interface processors and the switch processor (SP) each have a writable control store (WCS). The WCS stores microcode. You can load updated microcode onto the WCS from the onboard ROM or from Flash memory on the route processor (RP) card. With this feature, you can update microcode without having physical access to the router, and you can load new microcode without rebooting the system.
The default is to load from the microcode bundled in the system image.
To load microcode from Flash, complete the following task:
| Task | Command |
|---|---|
| Step 1 Copy microcode files into Flash. | copy tftp flash
See the section "Copy System Images from a Network Server to Flash Memory" earlier in this chapter for more information about how to copy TFTP images to Flash memory. |
| Step 2 Load microcode from Flash memory into the WCS. | microcode interface [flash | rom] [filename] |
| Step 3 Retain new configuration information when the system is rebooted | write memory |
If an error occurs when you are attempting to download microcode, the onboard ROM microcode will be loaded and the interface will remain operational.
These configuration commands are implemented following one of three events:
After you have entered a microcode configuration command and one of these events has taken place, all of the cards are reset, loaded with microcode from the appropriate sources, tested, and enabled for operation.
To signal to the system that all microcode configuration commands have been entered and the processor cards should be reloaded, complete the following task in interface configuration mode:
| Task | Command |
|---|---|
| Notify the system that all microcode configuration commands have been entered and the processor cards should be reloaded. | microcode reload |
If Flash memory is busy because a card is being removed or inserted, or a microcode reload command is executed while Flash is locked, the files will not be available and the onboard ROM microcode will be loaded. Issue another microcode reload command when Flash memory is available, and the proper microcode will be loaded. The show flash command will show if another user or process has locked Flash memory. The microcode reload command should not be used while Flash is in use (for example, do not use this command when a copy tftp flash or show flash command is active).
The microcode reload command is automatically added to your running configuration when you issue a microcode command that changes the system's default behavior of loading all processors from ROM.
To display microcode information, perform the following task in EXEC mode:
| Task | Command |
|---|---|
| Display microcode information. | show microcode |
|
|