Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Support

Upgrading SW and Microcode in Cisco 7000 Series Routers

Downloads

Table Of Contents

Upgrading Software and Microcode in Cisco 7000 Series Routers

Table of Contents

Overview of Image Distribution and Upgrade Methods

Upgrading from Floppy Disks or TFTP Servers

Prerequisites and Caveats

Prerequisites

Caveats

Procedural Overview

Installing the New Image onto Your TFTP Server

Installing New Images onto a DOS-Based PC

Installing New Images onto a Sun Workstation

Making Network Connections

Testing the TCP/IP Software

Establishing a TFTP Session

Setting Up TFTP on a Sun Workstation

Enabling the TFTP Daemon

Creating a tftpboot Directory

Establishing a Telnet Session

Loading the New Image

Backing Up the Current Contents of Flash Memory

Learning the Image Names

Copying the Image from Flash Memory to the TFTP Server

Copying the Image from a TFTP Server to Flash Memory

Recovering from a Flash Memory Failure

Verifying the New Image in Flash Memory

Using Additional Flash Memory Commands

Changing the Boot Instructions

Automatically Booting from Flash Memory

Manually Booting from Flash Memory

Configuring Microcode

Changing Microcode Boot Instructions

Listing the Bundled Microcode Versions

Repeating the Installation Process

Upgrading Software and Microcode with Replacement ROMs

Procedural Overview

Tools and Equipment

Preventing Electrostatic Discharge (ESD) Damage

Removing and Replacing the RP, SP, SSP, and Interface Processors

Replacing the RP, SP, SSP, or Interface Processors

Upgrading the System Software ROMs

Replacing the ROMs

Checking the Installation

Changing the Boot Field Jumper

Setting the Flash Write-Protect Jumper

Upgrading Microcode ROMs

Replacing the ROM

Verifying the Microcode Version

If You Need More Information

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone


Upgrading Software and Microcode in Cisco 7000 Series Routers

Note This document once contained information for upgrading software and microcode for Cisco 7500 series routers. For information on upgrading software and microcode in Cisco 7500 series routers, see the Cisco IOS Configuration Fundamentals Configuration Guides for the mainline software release that you are running.
The Cisco IOS Configuration Fundamentals Configuration Guides are not platform-specific; however, the information in these books also pertains to the Cisco 7500 series.
In most cases, the Cisco IOS Configuration Fundamentals Configuration Guide can be retrieved by clicking the following Cisco.com path:
Technical Documents (under Service & Support): Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release (release number): Configuration Guides and Command References: Configuration Fundamentals Configuration Guide

Cisco 7000 series routers support downloadable software and microcode for most new images; however, some exceptions require read-only memory (ROM) replacement in order for the router to boot and operate properly. This document provides instructions for upgrading with both types of media—floppy disk and ROM.

This publication describes the following tasks:

•Floppy disk or Trivial File Transfer Protocol (TFTP) server distribution—Procedures for upgrading the existing system software or microcode with new images that are distributed on floppy disk or made available for downloading from a network server using TFTP.

–How to install a microcode upgrade or a software upgrade from 3.5-inch PC-DOS-formatted floppy disks to a personal computer (PC) or UNIX workstation configured as a TFTP server.

–How to use TFTP to transfer a new system software image bundled (or unbundled) with microcode to Flash memory.

Note We strongly recommend that the microcode bundled with the system software be used as a package. Overriding the bundle could possibly result in incompatibility between the various interface processors in the system. The exception to this is CIP microcode, which, as of Cisco IOS Release 11.1(1), is unbundled from the Cisco IOS bundle and shipped as a separate package on floppy disks, Flash memory cards, or is available via Cisco.com.

–How to boot the router manually or automatically from a system software image stored in Flash memory.

•ROM distribution—Upgrading the existing system software or microcode with new images that are distributed on replacement ROM components.

–How to replace the eight system software ROMs on the Route Processor (RP).

–How to replace the single microcode ROM on the Switch Processor (SP), Silicon Switch Processor (SSP), or any interface processor.

Routers also can netboot from a TFTP file server directly to central processing unit (CPU)-local random-access memory (RAM) regardless of whether it has Flash memory. For procedures, refer to the appropriate software configuration documentation listed in the "If You Need More Information" section. Instructions for contacting technical assistance are provided at the end of this document, in the section "Obtaining Documentation."

Caution SP Microcode Version 1.4 must reside in ROM; it cannot be loaded from Flash memory. During the boot process, the system accesses the SP microcode. If the SP microcode ROM contains a version earlier than 1.4 and the router contains an FSIP, the system may fail to boot properly.

Table of Contents

The information in this publication is organized within the following sections:

•Overview of Image Distribution and Upgrade Methods, page 4

•Upgrading from Floppy Disks or TFTP Servers, page 5

–Prerequisites and Caveats, page 5

–Procedural Overview, page 7

–Installing the New Image onto Your TFTP Server, page 8

–Making Network Connections, page 12

–Loading the New Image, page 15

–Changing the Boot Instructions, page 22

–Configuring Microcode, page 26

–Repeating the Installation Process, page 29

•Upgrading Software and Microcode with Replacement ROMs, page 29

–Procedural Overview, page 29

–Tools and Equipment, page 30

–Removing and Replacing the RP, SP, SSP, and Interface Processors, page 31

–Upgrading the System Software ROMs, page 39

–Upgrading Microcode ROMs, page 46

•If You Need More Information, page 52

•Obtaining Documentation, page 53

–World Wide Web

–Documentation CD-ROM

–Ordering Documentation

–Documentation Feedback

•Obtaining Technical Assistance, page 54

–Cisco.com

–Technical Assistance Center

Note As of Cisco IOS Release 11.0, command syntax has been updated for certain commands. Wherever command syntax appears throughout this document and the newer command syntax applies, the newer command syntax is shown in parentheses after the command.

Overview of Image Distribution and Upgrade Methods

Cisco 7000 series routers feature downloadable software and microcode for most new images. Also, microcode images are bundled with the system code, so individual microcode upgrades are no longer necessary.

Note We strongly recommend that the microcode bundled with the system software be used as a package. Overriding the bundle could possibly result in incompatibility between the various interface processors in the system. The exception to this is CIP microcode, which, as of Cisco IOS Release 11.1(1), is unbundled and shipped as a separate package on floppy disks, Flash memory cards, or is available via Cisco.com.

Downloadable microcode allows you to download new images over the network, store the images in the router's Flash memory, and load images from Flash memory at system startup without having to physically access the router. Although for most upgrades you can configure the system to load newer images from Flash memory files to override the default ROM images, some exceptions require ROM replacement to ensure proper startup and operation.

All Cisco 7000 series software and microcode upgrades that were released prior to SP Microcode Version 1.4 (in September 1993) were distributed on floppy disk and could be stored in, and loaded from, Flash memory. SP Microcode Version 1.4 was the first microcode upgrade to be distributed on ROM. (Because the system software accesses the SP microcode during the boot process, SP  Microcode Version 1.4 must reside in ROM; it cannot be stored and loaded from a Flash file.)

Bundled images include the latest system software image and the latest available microcode image for the following processor types: Asynchronous Transfer Mode (ATM) Interface Processor (AIP), Channel Interface Processor (CIP), Ethernet Interface Processor (EIP), Fiber Distributed Data Interface (FDDI) Interface Processor (FIP), Fast Ethernet Interface Processor (FEIP), Fast Serial Interface Processor (FSIP), High-Speed Serial Interface (HSSI) Interface Processor (HIP), Multichannel Interface Processor (MIP), SP, SSP, and Token Ring Interface Processor (TRIP).

The upgrade procedure for bundled images is the same as that for previous upgrades; bundled images reside either in Flash memory or in ROM. When the system boots from a bundled image, a utility scans the installed processors to determine compatibility with the new microcode, and (if there are no conflicts) loads the microcode images automatically. A new command, show microcode, lists all of the microcode images that are bundled with the system software image. (For a brief description of the show microcode command, refer to "Listing the Bundled Microcode Versions" on page 28; for a complete description, refer to the show microcode command reference or the appropriate chapter [in most cases, the chapter is Loading and Maintaining Software Images and Microcode] of the Cisco IOS Configuration Fundamentals Guide).

Depending upon the type of media in your upgrade kit, proceed as follows:

•If you received an upgrade on floppy disk, proceed to the following section, "Upgrading from Floppy Disks or TFTP Servers."

•If you received an upgrade on one or more replacement ROMs, proceed to "Upgrading Software and Microcode with Replacement ROMs" on page 29.

Review the entire section before beginning either of these procedures to ensure that you are aware of any safety considerations or system prerequisites.

Caution SP Microcode Version 1.4 must reside in ROM; it cannot be loaded from Flash memory. During the boot process, the system accesses the SP microcode. If the SP microcode ROM contains a version earlier than 1.4 and the router contains an FSIP, the system may fail to boot properly.

Upgrading from Floppy Disks or TFTP Servers

This section describes the procedures for upgrading system software or microcode from a floppy disk by copying the new image to a TFTP server, then loading the new image from the TFTP server to the Flash memory on one or more routers. When ROM replacement is not required, this procedure allows you to upgrade all of the routers in your network remotely, without having to physically access the router to replace components.

Cisco 7000 series routers also can netboot from a TFTP file server directly to CPU-local RAM, which does not require storing the image in Flash memory. The procedure is described in the appropriate router software configuration documentation. If you received an upgrade kit with replacement ROMs for the system software or microcode, refer to "Upgrading Software and Microcode with Replacement ROMs" on page 29 for instructions.

Prerequisites and Caveats

To successfully upgrade the system software or microcode, you should observe the following prerequisites and caveats.

Prerequisites

•You must have Internet Protocol (IP) running to the devices you plan to upgrade on the network.

•You must have a terminal connection that enables you to issue commands to each router on the network you want to upgrade. If you do not have a direct terminal connection, you must set up a Telnet session on a device attached to the router to be upgraded.

–If you are using TCP/IP software that permits concurrent Telnet and TFTP server connections, your terminal connection and TFTP session can be from the same PC.

–If you are using TCP/IP software that permits only the TFTP server to run (such as PC/TCP from FTP Software, Inc.), you need two machines. Set up one for your terminal connection and the other for your TFTP server.

•A TFTP file server must be active and accessible to the router. You must copy the system software or microcode image into the TFTP server directory to download it to the router.

If the TFTP server is a PC, it must have the following minimum configuration:

–The server must be a PC or a desktop SPARC station with a 1.44-MB 3.5-inch floppy drive.

–The configuration of the computer must meet the requirements established by the TFTP software vendor. Cisco has tested the following software running on an Everex 386/33 running under DOS 5.0 (in both Ethernet and Token Ring environments):

PC/TCP from FTP Software, Inc., Version 2.0 and greater. The toll-free number for FTP Software, Inc. is 800 282-4387. The address for FTP Software, Inc. is 2 High Street, North Andover, MA 01845-2620 or 100 Brickstone Square, Andover, MA 01810.

Chameleon TCP/IP for Windows from NetManage, Inc. To contact NetManage, Inc., call (408) 973-7171 or fax 408 257-6405. The address is 10725 North DeAnza Boulevard, Cupertino, CA 95014, USA.

Cisco has also tested the TFTP server provided by SunOS 4.1.x on SPARCstation platforms.

•The keywords flash and rom are reserved for the boot system and microcode configuration commands and indicate that the Flash memory or system ROMs, respectively, are to be used for booting system images. Do not use these reserved keywords for other files you might create.

•Total Flash memory capacity is 4 MB, and you cannot selectively delete files from Flash memory. If there is not sufficient free space in Flash memory to add a new image, you will have to erase the entire contents of Flash memory before you can add a new image. If there are files stored in Flash memory that you want to save, copy the files to a TFTP server before performing the upgrade. After you install the upgrade (and Flash memory is cleared of all but the new image), selectively copy the saved files back into Flash memory. (Refer to "Backing Up the Current Contents of Flash Memory" on page 15.)

•Jumper J2 on the RP is the Flash write-protect jumper. The jumper installed on J2 (the factory default) enables writing to Flash memory. Removing the jumper disables writing to Flash memory and protects the contents. You can store new images in Flash memory only if jumper J2 is installed. (For instructions, refer to "Setting the Flash Write-Protect Jumper" on page 46).

•Cisco 7000 series routers, which use the Route Processor (RP), ship with the hardware configuration register boot field jumper set to boot from ROM. If you have not yet changed this setting (if you have not installed and booted from an image in Flash), you will have to change the jumper setting. (If you are running Cisco IOS Release 10.0 or later and you have Cisco IOS Release 10.0 [or later] boot ROMs installed in the RP, special circumstances apply, refer to "Changing the Boot Field Jumper" on page 43.)

Note Cisco 7000 series routers that have the 7000 Series Route Switch Processor (RSP7000) installed use the software configuration register feature exclusively. The RSP-based processor modules have no user-configurable jumpers.

Caveats

•If you have not yet installed your TCP/IP software, be aware of the following issues when installing it:

–Use the proper driver for your network interface card and system configuration.

–Know whether your TFTP server is using a DMA channel.

–Some network interface cards require that you manually set the interrupt request (IRQ) value; if your network interface card requires an IRQ value, make sure it does not conflict with a value used by another PC card.

–Some network interface cards require that you specify the card's I/O address.

–Obtain an IP address for the PC and identify the number of subnet bits to assign.

•If you are using Chameleon TCP/IP for Windows, make sure you click the Server On checkbox in the Server Settings dialog box before you use TFTP to transfer the system software image.

•Chameleon TCP/IP for Windows from NetManage, Inc., does not support DR DOS.

•If your PC is using a Western Digital card that was resold by SMC, you might need to use a different driver than the one supplied by NetManage.

•When you install a new image onto your TFTP server, make sure the server has at least 2 MB of disk (storage) space available. If it does not, the existing space will be filled up with an incomplete image that will not function on your routers.

•When copying a file to Flash memory, a prompt asks whether you want to erase the contents of Flash memory. Answering yes, or pressing the Return key without entering yes or no, erases the entire contents. (The default is to confirm the erasing process). Before starting the copy process, copy any files that you do not want erased to a TFTP server so that you can retrieve them later.

•If you download Cisco IOS Release 10.0 or later into Flash memory and wish to use the software configuration register feature, you must install Cisco IOS Release 10.0 or later boot ROM components on the RP card; otherwise, the hardware configuration register (located on the RP card) will be used by default. Refer to the section "Upgrading the System Software ROMs" on page 39.

•We strongly recommend that the microcode bundled with the system software be used as a package. Overriding the bundle could possibly result in incompatibility between the various interface processors in the system.

Procedural Overview

This section lists the general steps required to upgrade from a new image on floppy disk. The sections that follow describe these steps in greater detail.

Step 1 Install the new image from the floppy disk on your PC or UNIX machine into the TFTP server directory.

Step 2 Verify that the router you want to upgrade has access to the TFTP server. Ping from the TFTP server to the router and from the router to the TFTP server.

Step 3 Start the TFTP server if it is not already active.

Step 4 Connect a console terminal or establish a Telnet session with the router you plan to upgrade.

Step 5 Back up any current system software and microcode images that are stored in Flash memory by copying them to the TFTP server.

Step 6 Copy the new image from the TFTP server into Flash memory.

Step 7 Ensure that the checksum listed on the bottom line of the output for the copy tftp command matches the checksum listed in the README file on the upgrade disk. If it does not, you must invoke the copy tftp command again before booting from Flash memory.

Step 8 Make sure your system is configured to boot from the new image in Flash memory.

Step 9 Boot the router from Flash memory. This process writes the images from Flash memory into system RAM.

Step 10 Check all network connections to make sure the router with the upgraded system software is up and functioning properly.

Step 11 Repeat these steps to upgrade additional routers.

Installing the New Image onto Your TFTP Server

This section describes how to use the installation program on the disk to install the new image onto your DOS-based PC or your desktop SPARCstation. Refer to the online README file on the upgrade disk for details about the new image. The README file lists details such as the product number, image types, file sizes, and checksums of the images.

Installing New Images onto a DOS-Based PC

To copy the new image into the appropriate directory on the PC you plan to use as the TFTP server, follow this procedure. Allow five minutes to complete this procedure.

Caution Do not install the system software or microcode image to the TFTP server and then install it a second time. If you do, the system appends the second image to the first image rather than writing over it, and the altered image will not function in your routers. If you want to install the image a second time, first delete the image from the destination directory on the TFTP server and then reinstall it.

Note It is good practice to make a backup copy of the master upgrade disk (containing the new bundled image) and work from the backup copy. Archive the master disk.

Following is the procedure for installing new images onto a DOS-based personal computer (PC):

Step 1 Insert the master upgrade disk into your 3.5-inch disk drive.

Step 2 Type the following command and press Enter. 

C:\> a:install

where a is the drive in which you inserted the source disk. The drive letter can be either a or b.

A screen similar to the following appears. This screen is for a 10.3(9) software image. If you are upgrading to a release other than 10.3(9), the information in the header fields (the first four lines) will be different. 

********************** 7K1000390Z.DOC **********************************


    PRODUCT NO. SW-G7-10.3.9=   

    System Software Image 7K91770Z, GS7-K Version 10.3(9)

    Compressed size = 1610960 bytes; Checksum=0xa0df

    Copyright (c) 1995 Cisco Systems, Inc.


File 7K10390Z supports all software capabilities for the Cisco 7000.


To install this software in a PCDOS environment enter:

    A:install          (or use the appropriate drive letter)

To install this software in a UNIX environment enter:

    #mount -rt pcfs /dev/fd0 /pcfs

    #/pcfs/install.unx    (where the user has root privileges)


To install this software onto a router, follow the procedures in 

the accompanying publication, "Upgrading System Software and 

Microcode in the Cisco 7000." 


**********************************************************************

Step 3 A prompt appears asking if you want to continue with the installation. Press the Y key (or Enter) to continue, or the N key to abort.

Step 4 A prompt appears asking where the files will be installed. The default directory is C:\TFTPBOOT. To accept this directory, press Enter. To specify a different directory, type the full pathname, then press Enter.

If the nondefault directory you specify does not already exist, a message appears asking if you want to create the directory.

Step 5 To create the directory, press the Y key. If you do not want to create a new directory on your PC and want to abort this process, press the N key.

The software displays a set of messages indicating the status of the installation. The copy process takes about one minute.

Step 6 If you have multiple floppy disks, the system prompts you to insert the second disk and press Enter.

When the process is complete, a message appears. The following example shows the 10.3(9) image—7K10000390Z. 

Installation for 7K10390Z complete!

Step 7 Eject the disk from the disk drive and keep it in a safe place.

Step 8 Change to the directory in which you installed the 10.3 image. For example, if you installed it in the default directory, type the following command and press Enter: 

C:\> cd \tftpboot

Step 9 List the contents of the image in this directory. For example, if you installed the System Software Release 10.3(9), type the following command and press Enter: 

C:\> dir 7K10390Z.*

The following two files should appear:

•7K10390Z

•7K10390Z.DOC (the README file that appears when you install the image on the server)

Proceed to "Establishing a TFTP Session" on page 12.

Installing New Images onto a Sun Workstation

The following procedure describes how to install the new image onto a desktop SPARCstation with SunOS 4.1.x. The workstation must have a 3.5-inch, 1.44-MB floppy disk drive. Allow ten minutes to complete this procedure.

You must have superuser access to install the new image on a UNIX system.

Note If you have a different UNIX-based system, refer to your system's documentation for instructions on how to load a PC-DOS formatted floppy disk and how to configure the system as a TFTP server.

Caution Do not reinstall the new image on the TFTP server after installing it a first time. If you do, the system appends the second image to the first image rather than writing over it, and the altered image will not function in your routers. If you want to install the image a second time, first delete the image from the destination directory on the TFTP server and then reinstall it.

Use the following procedure to create a mount point and install the new image on your TFTP server. Note that filenames are case sensitive.

Step 1 Create a directory named pcfs as follows (you must have superuser capability to execute this instruction): 

hostname# mkdir /pcfs

Step 2 Insert the disk containing the upgrade into your 3.5-inch floppy disk drive.

Step 3 Mount the floppy disk drive as a device by entering the following command: 

hostname# mount -t pcfs /dev/fd0 /pcfs

If the disk is write-protected, enter the following command: 

hostname# mount -rt pcfs /dev/fd0 /pcfs

The floppy is now set up as the device /pcfs.

Step 4 Copy the new image to your TFTP directory. To copy it to the default (/tftpboot) directory, enter the following command: 

hostname# /pcfs/install.unx

Step 5 A message appears prompting you to specify the device from which the new image is being installed. The default is /dev/fd0. To accept the default, press Return. To specify a different directory, type the name of the built-in floppy drive on the SPARCstation.

Step 6 A prompt asks you to specify the path from the mounted floppy drive. The default is /pcfs. To accept the default, press Return. To specify a different path, type the full path name.

A screen similar to the following appears. The following screen is for a 10.3(9) system software image. If you are upgrading to a release other than 10.3(9), the header fields (the first four lines of the display) will be different. 

********************** 7K10390Z.DOC **********************************

    PRODUCT NO. SW-G7-10.3.9=   

    System Software Image 7K10390Z, GS7-K Version 10.3(9)

    Compressed size = 1610960 bytes; Checksum=0xa0df

    Copyright (c) 1995 Cisco Systems, Inc.


File 7K100390Z supports all software capabilities for the Cisco 7000.

To install this software in a PCDOS environment enter:

    A:install          (or use the appropriate drive letter)

To install this software in a UNIX environment enter:

    #mount -rt pcfs /dev/fd0 /pcfs

    #/pcfs/install.unx    (where the user has root privileges)


To install this software onto a router, follow the procedures in the

accompanying publication, "Upgrading Software and Microcode in  
Cisco 7000 Family Routers." 


**********************************************************************

Step 7 A prompt appears asking if you want to continue with the installation. Press the Y key (or Enter) to continue, or the N key to abort. The screen displays a set of messages indicating the status of the installation. The copy process takes about five minutes.

Step 8 If you have multiple floppy disks, the system prompts you to insert the subsequent disks and press Enter.

After the image is installed on your TFTP server, the disk is automatically ejected and the disk drive is automatically unmounted. When the copy process is complete, a message appears. The following example shows the 10.3(9) image 7k10390Z. 

Installation for 7k10390Z complete!

Step 9 Eject the disk from the disk drive and keep it in a safe place.

Step 10 Change to the directory in which you installed the system software or microcode image. For example, if you installed it in the default directory, type: 

hostname# cd /tftpboot

Step 11 List the contents of the image in this directory. For example, for a 10.3(9) system software image, enter the following command: 

hostname# ls -l 7k100390z*

The following two files should appear (for the 10.3[9] image; other images would be different, such as 7k11110z for the 911.1[1] image):

•7k10390z

•7k10390z.doc (the README file that appears when you install the software image on the server)

Proceed to the next section, "Making Network Connections."

Making Network Connections

This section describes the following topics:

•Testing the TCP/IP software

•Establishing a TFTP session (to the router)

•Establishing a Telnet session (from the router to the TFTP server)

Testing the TCP/IP Software

After installing the TCP/IP software you will use to copy the new image to the routers on your network, make sure it functions properly by following this procedure:

Step 1 Make sure a router with which you plan to communicate is up and running by pinging from that router to the TFTP network server. Use the following syntax for the ping command: 

Router# ping ip-address

If the router is appropriately connected, you see a series of exclamation points (!!!!!). However, the following messages indicate that you have no connection:

•[timed out]

•[failed]

Step 2 Verify the connection to the TFTP file server by transmitting a ping from the TFTP file server to the router.

If the connection fails, make sure you reconfigure the interface, check the physical connection to the TFTP file server, and retransmit the ping.

If you are using PC/TCP Network Software for DOS from FTP Software, Inc., you can verify the appropriate driver and IP address by entering the following command: 

C:\> ifconfig drivers\drivername show

You can verify your IP configuration by entering the following command: 

C:\> ipconfig ftp_3c\ipcust.sys show

If you are using Chameleon TCP/IP for Windows from NetManage, Inc., run its setup program to verify that you are using the appropriate driver and have configured the TCP/IP software properly.

Establishing a TFTP Session

This section describes how to set up your UNIX system or PC as a TFTP server and start a TFTP session with the router you want to upgrade remotely.

If you are using a PC and do not already have TFTP software, we recommend the following two TCP/IP software packages:

•PC/TCP Network Software for DOS from FTP Software, Inc. (character-based TFTP software capability)

•Chameleon TCP/IP for Windows software from NetManage, Inc. (a Windows-based TFTP server)

The "Prerequisites and Caveats" section lists some issues to keep in mind while installing the software.

Setting Up TFTP on a Sun Workstation

To set up the Sun system as a TFTP server, you must verify that the TFTP daemon is enabled, the TFTP environment variable is set correctly, and a tftpboot directory exists. To see if TFTP is enabled, enter the following command: 

hostname# netstat -a | grep tftp

If the TFTP daemon is already enabled, proceed to "Creating a tftpboot Directory" on page 14.

Enabling the TFTP Daemon

The TFTP daemon (tftpd) permits the system to be a TFTP server. If you are using the standard Sun software, verify that tftpd is enabled by completing the following steps:

Step 1 Log in as a superuser.

Step 2 Using a text editor such as vi, edit the /etc/inetd.conf file.

Step 3 Look in the /etc/inetd.conf file for the line that invokes tftpd. If the line is commented out (starts with a pound sign [#]), remove the pound sign with an editor. This example shows sample output for the /etc/inetd.conf file. 

# tftp dgram udp wait root /user/etc/in.tftpd  
in.tftpd -s /tftpboot

Step 4 Save the changes in the edited file and exit.

Step 5 At the UNIX prompt, enter the following command to display the process ID number for the inetd configuration: 

hostname# ps -ax | grep -v grep | grep inetd

The system response is similar to the following: 

119 ?   S   0:05 inetd

The first number in the output is the process ID of the inetd process. You must kill this inetd process by entering the following command: 

hostname# kill -HUP 119

Step 6 Verify that TFTP is enabled by entering the following command: 

hostname# netstat -a | grep tftp

The output should be similar to the following: 

udp     0       0   *.tftp        *.*

If there is no output, tftpd is not enabled. For additional information about TFTP, refer to the UNIX manual pages about tftp and tftpd.

Creating a tftpboot Directory

The tftpboot directory can be used to save and store configuration files that are loaded to a device. Device configuration files can be saved as TFTP boot files.

Note The tftpboot directory is accessible by all users. To protect the security of your system, do not leave sensitive files in this directory.

Creating a tftpboot Directory on a Sun Workstation

You must have superuser access to perform the following steps. These steps describe how to create a tftpboot directory.

Step 1 If the tftpboot directory does not exist, use the following command to create it: 

hostname# mkdir /tftpboot

Step 2 The /tftpboot directory must have the appropriate permissions. Modify the permissions with the following command: 

hostname# chmod 777 /tftpboot

As a result, all users accessing this directory will have read, write, and execute permissions.

Creating a tftpboot Directory on a PC

To create a new directory on a PC, enter the following command: 

C:> MKDIR \TFTPBOOT

After completing all the preparations required to set up your Sun workstation or PC as a TFTP server, refer to "Testing the TCP/IP Software" on page 12.

Establishing a Telnet Session

You must be able to issue commands to the router you plan to upgrade. For example, this publication tells you to issue a command to download an image from the TFTP server to the router. If you have a console port connection to the router, you need not invoke a Telnet session.

If you do not have a console port connection to the router, you must establish a Telnet session with it so that you can issue commands.

You can set up a Telnet session from a Sun workstation or from a PC.

•If you are using a Sun workstation as a TFTP server, you can also establish a Telnet session from the workstation to the router in addition to the TFTP session.

•If you are running TCP/IP software on a PC, is the software character-based or Windows-based?

–If character-based, you need a second PC from which you can establish a Telnet session.

–If Windows-based, you can open one window for the TFTP session and one window for the Telnet session.

Loading the New Image

This section presents the following topics:

•Backing up any current system software and microcode images that are stored in Flash memory, including learning the image names and copying the images from Flash memory to the TFTP server (this is not necessary to back up images stored in ROM)

•Copying the new image from a TFTP server to Flash memory

•Modifying the configuration file with instructions to load the new image at startup, and to disable any existing instructions to load system software or microcode images from ROM or Flash files

•Reloading the software

•Verifying the new image in Flash memory

Backing Up the Current Contents of Flash Memory

If your system is currently running from a system software image stored in Flash memory and you do not already have the image backed up on a TFTP server, make sure you back up this image before installing the new image. You can also use this procedure to back up other files you have stored in Flash memory.

Also back up any microcode images stored in Flash memory that you want to keep. Microcode upgrades for most Cisco 7000 series interface processors have been released, and all except SP Microcode Version 1.4 were distributed on floppy disk. Because microcode is now bundled with system software images, you no longer need to save the individual microcode images. However, until you verify that the new bundled image is loaded and running successfully, we recommend that you back up all working files that are currently stored in Flash memory. You can delete the backups after you install and verify the new image.

Learning the Image Names

First, you must know the exact spelling of the name of each image that you will back up. To learn the image name, issue the show flash all command. The following sample output shows one system software image (7k91720z) and one microcode image (fip1-1). 

Router# show flash all

4096K bytes of flash memory on embedded flash (in RP1).

   ROM     socket   code    bytes     name

     0      U63     012A   0x40000 AMD 28F020

     1      U62     012A   0x40000 AMD 28F020

     2      U61     012A   0x40000 AMD 28F020

     (display text omitted)

    11      U27     012A   0x40000 AMD 28F020

    12      U17     012A   0x40000 AMD 28F020

    13      U16     012A   0x40000 AMD 28F020

    14      U15     012A   0x40000 AMD 28F020

    15      U14     012A   0x40000 AMD 28F020

  security jumper(12V) is installed,

  flash memory is programmable.


file     offset     length        name

  0     0x80        3           test3

  1     0x1E72E8    97200       fip1-1

  2     0x13EDE0    1305820     7k91720z

  [1582404/4194304 bytes free]

Router#

When you back up the image, use the exact filename from the show flash all command screen.

Copying the Image from Flash Memory to the TFTP Server

To copy an image from Flash memory to a TFTP server, use the copy flash tftp command: 

Router# copy flash tftp filename

The router prompts you for the IP address of the TFTP server and the name of the image file you are copying to the server. A sample of the output for this command using IP address 131.108.10.6 and filename 7k91720z follows: 

IP address of remote host [255.255.255.255]? 1.1.1.6

Name of file to copy []? 7k10390z <Return>

writing 7k91720z!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Router#

Use the image you backed up to the TFTP server in case the upgrade image becomes damaged.

Copying the Image from a TFTP Server to Flash Memory

The copy tftp flash command retrieves an image from a TFTP server and copies (writes) the image into the router's Flash memory. The TFTP server can be another Cisco router serving ROM or Flash system software images, or a PC or UNIX workstation set up as a server for remotely downloading new images to routers on the network. If you have already established a connection with the remote server, proceed to "Downloading the New Image" on page 18.

Note Before you can copy an image to Flash memory, the write-protection jumper (J2) on the RP card must be installed. (See Figure 7). If this jumper is removed, Flash memory is write protected and cannot be overwritten. The RP is shipped with this jumper installed; therefore, Flash memory can be overwritten by default.

In some cases, primarily outside of North America, Cisco Systems distributors may choose not to distribute the new image on floppy disk. Instead, they can place the new image on TFTP servers and provide their customers with the information they will need to access and download the new image. If you are downloading a new image from your distributor with this process, ensure that your distributor has provided you with all of the following information:

•IP address of the TFTP server that contains the new image

•Exact image name

•Image size (length in bytes)

•Checksum

You must have all of this information from your distributor before you can complete the upgrade. Proceed to the following section, "Verifying the Connection."

Verifying the Connection

Verify the connection between your router and the remote server by pinging the server using the IP address (this may be provided by your distributor). Following is an example of a successful ping command to a remote server with the address 1.1.1.101: 

Router# ping 1.1.1.101 <Return>

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echoes to 1.1.1.101, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/15/64 ms

Router#

The console displays a series of exclamation points (!!!!!) to indicate a good connection between your router and the server, or a series of periods (.....) or the messages [timed out] or [failed] to indicate that the connection failed. If the connection fails, verify that you have the correct IP address for the server and that the server is active (powered on), and repeat the ping command.

Verifying Flash Capacity and Configuration

Before copying the new image to Flash memory, use the show flash all (or dir [ bootflash | slot0 | slot1 ]) command to verify that Flash memory is not write-protected and that there is sufficient space remaining for the new image. The following example shows that writing to Flash memory is enabled (the write-protection [security] jumper [J2] is installed on the RP) and that Flash memory has approximately 1.7 MB of space available for new images (shown as the amount of bytes free in the last line of the display). 

Router# show flash all

4096K bytes of flash memory on embedded flash (in RP1).

   ROM     socket   code    bytes     name

     0      U63     89BD   0x40000 INTEL 28F020

    (displayed text omitted)

    15      U14     89BD   0x40000 INTEL 28F020

  security jumper(12V) is installed,

  flash memory is programmable.


file     offset     length        name

  0     0x80        1995304     gs7-k.103.9.1

  1     0x1E72E8    97200       fip1-1

  (displayed text omitted)

  7     0x2483A4    55418       sp1-2

  [1731676/4194304 bytes free]

Cisco 7000 family routers are shipped with Flash memory enabled for writing. If jumper J2 on the RP has been removed to protect the Flash memory contents, you will not be able to write the new image to Flash memory until you replace the jumper. Refer to "Setting the Flash Write-Protect Jumper" on page 46 for instructions.

Compare the amount of memory available (the bytes free value) with the size of the new image to ensure that there is ample space available in Flash memory. Total Flash memory capacity is 4 MB, and most system software images are close to 2 MB in size. Therefore, you can usually store one system software image and several microcode images. If there is not sufficient space available for the new image, you must erase the entire contents of Flash memory before you can copy in the new image; you cannot selectively delete specific files. You should, however, copy the files you want to keep to a TFTP server and then selectively copy the files back into Flash memory after erasing and installing the new image. Refer to "Backing Up the Current Contents of Flash Memory" on page 15 for instructions.

Note Although you can compress an image and boot the compressed image from Flash memory, this is not recommended. The README file on your master upgrade diskette lists the size and checksum of the uncompressed image. If you compress the image, then load it into Flash memory, you have no way of verifying that the image did not become corrupt during the TFTP process. For more information about verifying that your image is not corrupt, refer to the section "Verifying the New Image in Flash Memory" on page 20.

If you attempt to copy a new image into Flash memory when there is not enough space available, the copy process will begin but the entire image will not copy into Flash memory. A failure message, "Buffer overflow - xxxx/xxxx" will appear, where xxxx/xxxx is the number of bytes read in/number of bytes available. The partial image will remain in Flash memory until it is erased.

Downloading the New Image

When you issue the copy tftp command for the first time, you are prompted for the IP address (or domain name) of the TFTP server. You are then prompted for the filename of the software image and given the option of erasing the contents of embedded (onboard) Flash memory or a Flash memory card. Accepting the default by pressing Y or the Return key clears the entire contents of Flash memory. If other images, such as updated microcode images, are stored in Flash memory, make sure you do not need these images or back them up before copying the new image into Flash memory.

Note Before you can copy an image to Flash memory, the write-protection jumper (J2) on the RP card must be installed. (See Figure 7.) If this jumper is removed, Flash memory is write protected and cannot be overwritten. The RP is shipped with this jumper installed; therefore, Flash memory can be overwritten by default.

The entire copying process takes several minutes, and this time differs from network to network.

Note Do not make any typographical errors while using the copy tftp command in selecting the filename of the image you are copying. If you type a filename that does not exist when using the copy tftp command and then tell the system to erase the current image, the router erases the existing image in Flash memory. If this happens, the router still has a working image in RAM and ROM, so your router will still function. If you think you have tried to load a nonexistent file, do not reboot the router. If you do, your router will not have a functional image in Flash memory. To recover from accidental Flash memory erasure, execute the copy tftp command again to load the appropriate image into Flash memory. If this procedure does not work, set up the router to boot from the ROM image and reboot it.

The filename can be lowercase or uppercase; the router will see the name as lowercase.

Caution If you accept the default for the prompt "erase flash before writing? [confirm]" by pressing either the Y key or Return, the entire contents of Flash memory will be erased. If your Flash memory contains files that you do not want to erase, back them up to a remote host before erasing Flash memory. (See "Backing Up the Current Contents of Flash Memory" on page 15.)

The following example shows an image named new.image being copied into Flash memory: 

Router# copy tftp:new.image slot0:new.image

20575008 bytes available on device slot0, proceed? [confirm]

Address or name of remote host [1.1.1.1]?

Loading new.image from 1.1.1.1 (via Ethernet1/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[OK - 7799951/15599616 bytes]

CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC

CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC

CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC

Router#

Note In the preceding example, the exclamation points (!!!) appear as the file is downloaded, and the "C" characters signify calculation of the checksum, which is a verification that the file has been correctly downloaded to the Flash memory card.

The series of exclamation points (!!!!) in the preceding sample output indicates that the copying process is taking place. The series of Cs indicates that a checksum is being calculated. The last line in the sample configuration indicates that the file transfer is complete.

If the process was successful, proceed to "Verifying the New Image in Flash Memory" on page 20. If it was not successful, refer to the next section, "Recovering from a Flash Memory Failure."

Note To abort the copy process, simultaneously press Control, Shift, and 6. The process will abort; however, the partial file copied before the abort was issued will remain until the entire contents of Flash memory is erased.

Recovering from a Flash Memory Failure

If the image fails to load properly into Flash memory, the following error message appears: 

Error programming flash memory

If three or more attempts to load the image fail and result with this message, contact a technical support immediately. (Refer to the section "Obtaining Technical Assistance" on page 54.)

In an attempt to recover from the error, you also can erase the Flash memory and try to download the file again. You can repeat this procedure. To erase the Flash memory, issue the copy tftp command and press Return or the Y key at the following prompt: 

erase flash before writing? [confirm] <Return>

Having successfully copied an image into Flash memory, you can display the image name by issuing the show flash all command. 

Router# show flash all

4096K bytes of flash memory on embedded flash (in RP1).

   ROM     socket   code    bytes     name

     0      U63     012A   0x40000 AMD 28F020

     1      U62     012A   0x40000 AMD 28F020

(display text omitted)

  security jumper(12V) is installed,

  flash memory is programmable.


file     offset     length        name

  0     0x80        3           test3

  1     0xC4        1305820     gs7-k.917-2.Z

  2     0x13EDE0    1305820     7k91720z

  [1582404/4194304 bytes free]

Verifying the New Image in Flash Memory

Before booting from Flash memory, verify that the checksum of the bundled image (shown at the bottom of the screen after you issue the copy tftp command) matches the checksum listed in the README file on the master upgrade disk. If the checksum values do not match, enter the copy tftp command and compare the checksums again.

You can also verify the presence and file size of the new image by displaying the contents of Flash memory with the show flash command. The Flash memory 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, use the copy verify command. When you issue the command, the screen prompts you for the filename to verify. By default, it prompts for the last file in Flash memory (most recent). Press Return to recompute the default file checksum or enter the exact filename of a different file at the prompt.

Following are examples of the show flash and copy verify commands: 

Router# show flash

4096K bytes of flash memory on embedded flash (in RP1).


file    offset      length      name

  0     0x80        2060240     gs7-k.103-8

  1     0x2577F0    98162       flip1-2

[1656560/4194304 bytes free]


Router# copy verify

Name of file to verify [flip1-2]? gs7-k.103-8

Verifying via checksum...

vvvvvvvvvvv

Flash verification successful.  Length = 2060240, checksum = 0x0a42

Router#

After you verify that the checksum of the new image in Flash memory matches that listed in the README file on the upgrade disk, proceed to the next section to instruct the system to load the new file when you restart the router.

If the copy tftp and the copy verify commands result in a checksum that repeatedly does not match the checksum listed in the README file, do not reload or restart the router. Copy the original working image (or images) back into Flash memory, and contact a service representative for assistance. (Refer to the section "Obtaining Technical Assistance" on page 54.)

Caution If you have a bad image in Flash memory and try to boot from Flash memory, the router will not function and must be reconfigured through a direct console port connection.

Using Additional Flash Memory Commands

Following are additional commands related to the Flash memory in the single in-line memory module (SIMM) on the RSP (called bootflash) and in PCMCIA cards. (The following example assumes you are currently accessing a Flash memory card in PCMCIA Slot 0.) You can determine which PCMCIA slot you are accessing using the pwd command as follows: 

Router# pwd

slot0

You can move between Flash memory media using the cd [ bootflash | slot0 | slot1 ] command as follows: 

Router# cd slot0

slot0

Router# cd slot1

Router# pwd

slot1

You can list the directory of any Flash memory media using the dir [ bootflash | slot0 | slot1 ] command as follows: 

Router# dir

-#- -length- -----date/time------ name

1   4601977  May 19 1994 09:42:19 myfile1

6   679      May 19 1994 05:43:56 todays-config

7   1        May 19 1994 09:54:53 fun1

You can delete a file from any Flash memory media using the delete command as follows: 

Router# delete slot0:fun1

Router# dir

-#- -length- -----date/time------ name

1   4601977  May 19 1994 09:42:19 myfile1

6   679      May 19 1994 05:43:56 todays-config

To verify that the delete command was successful, use the dir/all/long command.

Note Files that are deleted are simply marked as deleted, but still occupy space in Flash memory. To remove them, use the squeeze command.

The squeeze command permanently removes files, which are marked as deleted, and pushes all other undeleted files together to eliminate spaces between them.

Following is the syntax of the squeeze command: 

Router# squeeze slot0:

All deleted files will be removed, proceed? [confirm]

Squeeze operation may take a while, proceed? [confirm]

ebESZ

To prevent loss of data due to sudden power loss, the "squeezed" data is temporarily saved to another location of Flash memory, which is specially used by the system.

In the previous command display output, the character "e" means this special location has been erased (which must be performed before any write operation). The character "b" means that the data that is about to be written to this special location has been temporarily copied. The character "E" signifies that the sector that was temporarily occupied by the data has been erased. The character "S" signifies that the data was written to its permanent location in Flash memory.

Changing the Boot Instructions

Before you reboot with a new image, you must add boot instructions to the configuration file that specify the name and location of the new file (image) to load, and remove any old boot instructions from the configuration file. Otherwise, the system will continue (or attempt) to boot from ROM or from an older image, even though the new image is present in Flash memory. Also, if this is the first time you are upgrading the system software image, you will also need to change the position of a boot field jumper on the configuration register before the router can reboot with the new image in Flash memory. If you are already familiar with the boot field jumper settings and configuration file boot commands, proceed to the following section, "Automatically Booting from Flash Memory."

The hardware configuration register is a 50-pin jumper block on the RP. The boot field jumper position determines the source of the software image that the system loads at startup. The factory default is to boot from ROM. If you have not changed the factory default setting (if you have not previously upgraded the software by loading a new image into Flash memory and your router is still booting from ROM), you will have to reset the boot field jumper before the system will boot from an image in Flash memory. Otherwise, a newer system image can be present in Flash memory, but the router will continue to boot with the older image in ROM. To change the jumper setting, refer to "Changing the Boot Field Jumper" on page 43.

If you are running Cisco IOS Release 10.0 or later and have Cisco IOS Release 10.0 (or later) boot ROMs installed on the RP, you will access the boot field via the software configuration register, which is a feature in IOS Release 10.0 or later. (For complete information on the software configuration register functions, refer to the appropriate software documentation, and to the RP Configuration and Installation document, Document Number 78-1057-05 (or later).

Note The RSP-based processor modules do not have a hardware configuration register, and use the software configuration register feature exclusively.

When the boot field jumper is set to boot from a filename (rather than booting from ROM, which is the factory default, or booting the router manually into the ROM monitor), the system looks in the configuration file for boot instructions. You must add a boot command to the configuration file that specifies the name of the new filename to load (the name of the new image), and the location of the new file (Flash memory). When you add this command to the configuration file, the router will automatically boot from the new image each time the system is restarted or reloaded.

Because the latest microcode images are now bundled and load with the system image, you should also remove any configuration file commands to load individual microcode images from a Flash file. (Earlier microcode images were distributed separately, and needed a line in the configuration file to instruct the system to load the newer microcode image from Flash memory at startup.) With bundled images, the system default is to load the microcode bundled with the system.

Note We strongly recommend that the microcode bundled with the system software be used as a package. Overriding the bundle could possibly result in incompatibility between the various interface processors in the system. The exception to this is CIP microcode, which, as of Cisco IOS Release 11.1(1), is shipped separately on floppy disks, Flash memory cards, or is available via Cisco.com.

If the configuration file contains a line instructing the system to load a microcode image from Flash memory and the microcode image is still present in Flash memory, the command will override the new bundled image and will cause the older image in Flash memory to load instead. Or, if the microcode image was erased from Flash memory when you downloaded the new bundled image, the router will attempt to find and load a nonexistent file. To negate an existing microcode boot command in the configuration file, issue the command no microcode interface-type flash filename. (Refer to "Configuring Microcode" on page 26 for a description of this command.)

When the boot field jumper is set to boot into the ROM monitor, you must boot the router manually by specifying the name and location of the image to boot when you restart the router.

The following sections describe how to boot automatically or manually with the new image stored in Flash memory.

Automatically Booting from Flash Memory

Whenever you add a new image to Flash memory to upgrade