|
|
Upgrading System Software in the Cisco 4000 Series
Product Numbers:
| SW-G4-x.x.x= | SW-G4D-x.x.x= | SW-G45BS-x.x.x= |
|---|---|---|
| SW-G4A-x.x.x= | SW-G4DS-x.x.x= | SW-G45C-x.x.x= |
| SW-G4AN-x.x.x= | SW-G4DSN-x.x.x= | SW-G45CS-x.x.x= |
| SW-G4B-x.x.x= | SW-G4P-x.x.x= | SW-G45D-x.x.x= |
| SW-G4BS-x.x.x= | SW-G45A-x.x.x= | SW-G45DS-x.x.x= |
| SW-G4C-x.x.x= | SW-G45AN-x.x.x= | SW-G45DSN-x.x.x= |
| SW-G4CS-x.x.x= | SW-G45B-x.x.x= | BOOT-4000= |
Read this entire document before attempting any of its procedures.
This publication describes the tasks you must follow to upgrade system software in your Cisco 4000, Cisco 4000-M, Cisco 4500, Cisco 4500-M, Cisco 4700, or Cisco 4700-M via floppy disk. These tasks include the following:
If you plan to use an FDDI interface to transfer the system software using TFTP, then you must first install the appropriate boot ROMs. Refer to the section "Upgrading Boot ROMs in the Cisco 4000 and the Cisco 4000-M," then begin the system software upgrade procedure.
Figure 1 shows the front view of a Cisco 4000 series router.
Figure 1 : Cisco 4000 Series Router---Front View
This document contains the following sections:
Overview of Image Distribution and Upgrade Methods
The Cisco 4000 series supports Flash memory downloading for most new images. Downloadable images enable 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.
Depending on the type of media in your upgrade kit, proceed as follows:
Review the entire section before beginning either of these procedures to ensure that you are aware of any safety considerations or system prerequisites.
Upgrading from Floppy Disks or TFTP Servers
This section describes the procedures for upgrading system software 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 enables you to upgrade all of the routers in your network remotely, without having to physically access the router to replace components.
The Cisco 4000 series can also 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.
To successfully upgrade system software and read-only memory on your Cisco 4000 series routers, first read the following prerequisites and caveats.
This section describes the general steps required to upgrade your system software on a Cisco 4000 series router. The sections that follow describe these steps in greater detail.
Installing System Software onto Your TFTP Server
This section describes how to use the installation program on the disk with your software upgrade to install the system software onto your DOS PC or your desktop SPARCstation.
Refer to the online README file on the software upgrade disk for details about the image for the routers to be upgraded. The README file lists details such as product number, image type, file size, and checksum of the compressed image.
Installing System Software onto a DOS PC
To copy your system software upgrade into the appropriate directory on the PC you plan to use as the TFTP server, use the following procedure. Allow five minutes to complete this procedure.
Installing System Software onto a Sun Workstation
The following procedures describe how to install the system software upgrade onto a desktop SPARCstation with Sun OS 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 router system software onto the UNIX system.
Use the following procedure to create a mount point and install the system software image on your TFTP server. Note that filenames are case sensitive.
Proceed to the next section, "Making Your Network Connections."
Making Your Network Connections
This section describes the following topics:
After installing the TCP/IP software you will use to copy the Cisco IOS Release 11.1 software image to the routers on your network, make sure it functions properly by following this procedure:
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:
The section "Prerequisites and Caveats" on page 4 lists some issues to remember when 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.
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:
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.
You must have superuser access to perform the following steps. These steps describe how to create a tftpboot directory.
After completing all the preparations required to set up the Sun system as a TFTP server, refer to "Testing the TCP/IP Software" on page 10.
You must be able to issue commands to the router you plan to upgrade. For example, this document instructs you to issue a command to download the 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.
This section contains the following topics:
Backing Up Your Current System Software Image
If you do not already have the current system software image on your TFTP server, make sure you back up this image before copying the new system software image to Flash memory on your router.
First, you must know the exact spelling of the image name. To learn the image name, issue the show flash all command. The following sample output for a compressed Cisco 4000 image (Cisco IOS Release 11.1(2)) displays an image name of yj11120n near the bottom of the screen.
Use the name near the bottom of your router's show flash all command (in this case, yj11120n) when you back up the image.
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:
The router asks 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 yj11120n follows:
Use the image you backed up to the TFTP server if 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 memory 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 15.
In some cases, primarily outside of North America, Cisco Systems distributors may choose not to distribute the new software 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 the new image from your distributor with this process, ensure that your distributor has provided you with all of the following information:
You must have all of this information from your distributor before you can complete the upgrade. Proceed to the next 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 131.131.101.101:
The console displays either 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 Memory Capacity and Configuration
Before copying the new image to Flash memory, use the show flash all 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 and that Flash memory has approximately 0.75 MB of space available for new images (shown as the amount of bytes free in the last line of the display).
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. 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, then selectively copy the files back into Flash memory after erasing and installing the new image. Refer to "Backing Up Your Current System Software Image" on page 13 for instructions.
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 "Buffer overflow - xxxx/xxxx" failure message 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 flash command for the first time, you are prompted for the IP address (or domain name) of the TFTP server. This can be another Cisco router serving ROM or Flash memory system software images. You are then prompted for the filename of the software image and given the option to erase the existing Flash memory. Type Y. The filename can be lower- or uppercase; the router will see the name as lowercase. The system clears and initializes Flash memory. The entire copying process takes several minutes. This time differs from network to network.
The following sample output shows a system image named The series of exclamation points (!) in the preceding sample output indicates that the copying process is taking place. The series of Vs 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, refer to the next section, "Verifying Software Images in Flash Memory." If it was not successful, refer to the section "Recovering from a Flash Memory Failure" on page 20.
Verifying Software Images in Flash Memory
Before booting from Flash memory, you must verify that the checksum of the compressed image shown at the bottom of the screen after you issue the copy tftp flash command matches the checksum listed in the README file on the software upgrade disk.
If the checksum value is not correct according to the value in the README file on the system upgrade disk, enter 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.
The following sections describe how to boot from Flash memory, both automatically and manually. When you boot a router from Flash memory, the system writes the image from Flash memory into system RAM. Refer to the previous section, "Verifying Software Images in Flash Memory," before you reboot the router.
From the enable-mode prompt on the router, enter the EXEC command write terminal to see whether the boot system flash command line in the configuration file has the filename argument, as follows:
Automatically Booting from Flash Memory
You can configure the router to automatically boot from the image in Flash memory by following this procedure:
Manually Booting from Flash Memory
If you do not have your router set up to automatically boot from Flash memory, as specified in the previous section, you can manually boot from Flash memory by following this procedure:
Recovering from a Flash Memory Failure
If the image fails to load properly into Flash memory, the following error message appears:
If you try loading the image into Flash memory three or more times and repeatedly see this message, contact technical support immediately and inform them of the situation. Refer to the section labeled "Cisco Connection Online."
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 flash command and press Return or Y at the following prompt:
Having successfully copied an image into Flash memory, you can display the image name by issuing the show flash all command.
Repeating the Installation Process
Before repeating the system software upgrade process on subsequent machines, make sure the upgraded router functions properly by performing the following steps:
Only upgrade subsequent routers if the ping and show route commands generate positive results.
Upgrading Boot ROMs in the Cisco 4000 and the Cisco 4000-M
This section contains procedures to replace the boot ROMs used in the Cisco 4000 and in the Cisco 4000-M.
The following tools are required for the boot ROMs' upgrade procedures:
Follow these guidelines to ensure general safety:
Follow these guidelines when working on equipment powered by electricity:
Preventing Electrostatic Discharge Damage
Electrostatic discharge (ESD) can damage equipment and impair electrical circuitry. It occurs when electronic printed circuit cards are improperly handled and can result in complete or intermittent failures.
Always follow ESD prevention procedures when removing and replacing cards. Ensure that the chassis is electrically connected to earth ground. Wear an ESD-preventive wrist strap, ensuring that it makes good skin contact. Connect the clip to an unpainted chassis frame surface to safely channel unwanted ESD voltages to ground. To properly guard against ESD damage and shocks, the wrist strap and cord must operate effectively.
If no wrist strap is available, ground yourself by touching the metal part of the chassis.
To gain access to the boot ROMs, you must remove the component tray.
Some Cisco 4000 series routers have a safety latch tab on the chassis that affects removing the component tray. (See Figure 2 and Figure 3.)
If you have a chassis with a safety latch tab, follow the procedure in the following section "Removing the Component Tray from a Chassis with a Safety Latch".
If you have a chassis without a safety latch tab, follow the procedure in the section "Removing the Component Tray from a Chassis without a Safety Latch" later in this chapter.
Removing the Component Tray from a Chassis with a Safety Latch
Take the following steps to remove the component tray:
Figure 2 : Component Tray Removal for Chassis With a Safety Latch
Removing the Component Tray from a Chassis without a Safety Latch
Take the following steps to remove the component tray:
Proceed to the next section, "Replacing Boot ROMs."
Figure 3 : Component Tray Removal for a Chassis Without a Safety Latch
Figure 4 : Typical Cisco 4000 Series Component Tray -- Cisco 4000 Shown
After the boot ROMs, FW1 and FW2, on the system card are exposed (see Figure 4), follow the procedures in this section to replace the ROMs.
Figure 5 : Cisco 4000 Boot ROMs
Figure 6 : Cisco 4000-M Boot ROMs
Take the following steps to replace the component tray in the chassis shell:
Replacing the Final Connections to the Router
Take the following steps to make the final connections to the router:
Warning After wiring the DC power supply, remove the tape from the circuit breaker switch handle and reinstate power by moving the handle of the circuit breaker to the ON position.
Figure 7 : DC-Input Power Supply Connections
Test your installation by rebooting the system. When you power up a system in which one or more of the boot ROMs has been incorrectly inserted, the system will boot into the ROM monitor or the operating system mode.
If you suspect that your boot ROMs have been inserted incorrectly, reopen the chassis, locate the affected boot ROM and remove it, straighten its pins, and then reinsert the boot ROM and try rebooting again.
If the system boots correctly, follow the procedures in the section "Installing System Software onto Your TFTP Server."
This section describes the Cisco 4000 series ROM monitor, the first software to run when the router is powered-up or reset. The ROM monitor can help you isolate or rule out hardware problems encountered when installing your router. A summary of the ROM monitor diagnostic tests and command options is provided.
Entering the ROM Monitor Program
The ROM monitor diagnostics help initialize the processor hardware and boot the main operating system software. If you set the software configuration register (bits 3, 2, 1, and 0) to zero, you can start the router in the standalone ROM monitor. An example of the ROM monitor prompt follows:
To enable the Break key, and to default to booting at the ROM monitor while running the system software, reset the configuration register to 0x0 by entering configuration mode, and enter the following configuration command:
The new configuration register value, 0x0, takes effect after the router is rebooted with the reload command. If you set the configuration to 0x0, you will have to manually boot the system from the console each time you reload the router.
Available ROM Monitor Commands
At the ROM monitor prompt, enter ? or help at the ROM Monitor Command Conventions
Following are ROM monitor command conventions:
The following case-sensitive ROM monitor commands are among the most useful:
Most of the debugging commands are functional only when the Cisco IOS software has crashed or is aborted. If you enter the debug commands and Cisco IOS crash information is not available, the screen will display the following error message:
Following are the debugging commands:
The Cisco 4000 series configuration register resides in NVRAM. The configuration register is identical in operation to other Cisco routers. Enter confreg for the menudriven system, or enter the new value of the register in hexadecimal.
Cisco Connection Online (CCO), formerly Cisco Information Online (CIO), is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional content and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously---a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, Internet e-mail, and fax download options, and is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact
Copyright 1988-1996 © Cisco Systems Inc.
C:\> a:
install
****************************** yj11120n.DOC ******************************
File Information
----------------
System Software: c4500-j-mz.111-2
Filename: yj11120n
Cisco IOS Version: 11.1(2)
MD5 Authentication Checksum: ab2b45e185c21b9cb6c73d6d4b24f4e6
For a list of features supported in this image and release,
please refer to your Product Catalog which is available
on-line on UniverCD and CIO (http://www.cisco.com).
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)
Copyright (c) 1995 Cisco Systems, Inc.
****************************************************************************
Installation for yj11120n complete!
C:\> cd \tftpboot
C:\>
dir yj11120n.*
hostname#
mkdir /pcfs
hostname#
mount -t pcfs /dev/fd0 /pcfs
hostname#
mount -rt pcfs /dev/fd0 /pcfs
hostname#
/pcfs/install.unx
****************************** yj11120n.DOC ******************************
File Information
----------------
System Software: c4500-j-mz.111-2
Filename: yj11120n
Cisco IOS Version: 11.1(2)
MD5 Authentication Checksum: ab2b45e185c21b9cb6c73d6d4b24f4e6
For a list of features supported in this image and release,
please refer to your Product Catalog which is available
on-line on UniverCD and CIO (http://www.cisco.com).
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)
Copyright (c) 1995 Cisco Systems, Inc.
****************************************************************************
Installation for yj11120n complete!
hostname#
cd /tftpboot
hostname#
ls -l yj11120n.*
router#
ping
ip-address
[timed out]
[failed]
C:\>
ifconfig drivers\drivername show
C:\>
ipconfig ftp_3c\ipcust.sys show
hostname# netstat -a | grep tftp
# tftp dgram udp wait root /user/etc/in.tftpd
in.tftpd -s /tftpboot
hostname#
ps -ax | grep -v grep | grep inetd
119 ? S 0:05 inetd
hostname#
kill -HUP 119
hostname#
netstat -a | grep tftp
udp 0 0 *.tftp *.*
hostname#
mkdir /tftpboot
hostname#
chmod 777 /tftpboot
router# show flash all
System flash directory:
File Length Name/status
addr fcksum ccksum
1 4448508 master/california/i7/bin/c4500-aj-mz.111-1
0x40 0x52C3 0x52C3
[4448572 bytes used, 3940036 available, 8388608 total]
8192K bytes of processor board System flash (Read/Write)
Chip Bank Code Size Name
1 1 89A2 1024KB INTEL 28F008SA
2 1 89A2 1024KB INTEL 28F008SA
3 1 89A2 1024KB INTEL 28F008SA
4 1 89A2 1024KB INTEL 28F008SA
1 2 89A2 1024KB INTEL 28F008SA
2 2 89A2 1024KB INTEL 28F008SA
3 2 89A2 1024KB INTEL 28F008SA
4 2 89A2 1024KB INTEL 28F008SA
router#
router# copy flash tftp filename
IP address of remote host [255.255.255.255]? 131.108.10.6
Name of file to copy []? yj11120n
writing yj11120n !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
router#
router# ping 131.131.101.101 <Return>
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echoes to 131.131.101.101, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/15/64 ms
router#
router# show flash all
System flash directory:
File Length Name/status
addr fcksum ccksum
1 4448508 master/california/i7/bin/c4500-aj-mz.111-1
0x40 0x52C3 0x52C3
[4448572 bytes used, 3940036 available, 8388608 total]
8192K bytes of processor board System flash (Read/Write)
Chip Bank Code Size Name
1 1 89A2 1024KB INTEL 28F008SA
2 1 89A2 1024KB INTEL 28F008SA
3 1 89A2 1024KB INTEL 28F008SA
4 1 89A2 1024KB INTEL 28F008SA
1 2 89A2 1024KB INTEL 28F008SA
2 2 89A2 1024KB INTEL 28F008SA
3 2 89A2 1024KB INTEL 28F008SA
4 2 89A2 1024KB INTEL 28F008SA
router#
yj11120n copied into the current Flash memory configuration:
router# copy tftp flash
File name/status
0 xx-k.111-2
[123816/2097152 bytes free/total]
IP address or name of remote host [255.255.255.255]? 131.108.1.111
Name of file to copy ? yj11120n
Copy yj11120n from 131.108.1.111 into Flash address space ? [confirm] <Return>
123752 bytes available for writing without erasure.
Erase Flash address space before writing? [confirm] <Return>
bank 0...zzzzzzzzzzzzzzzzvvvvvvvvvvvvvvvveeeeeeeeeeeeeeee
bank 1...zzzzzzzzzzzzzzzzvvvvvvvvvvvvvvvveeeeeeeeeeeeeeee
Loading from 131.108.1.111: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK - 1337256/2097088 bytes]
Verify checksum...vvvvvvvvvvvvvvvvvvvv
Verification successful: Length = 1337256, checksum = 0x5A1C
router> enable
Password:
router# wr term
Current configuration:
!
(text deleted)
boot system flash
(text deleted)
router#
configure terminal
no boot system flash xk11110z
(Removes old filename)
boot system flash yj11120n
(Tells the system to boot new filename)
^Z
router#
write memory
[ok]
router#
router#
reload
[confirm]
%SYS-5-RELOAD: Reload requested
System Bootstrap, Version 5.1(1) [daveu 1], RELEASE SOFTWARE (fc1)
Copyright (c) 1994 by cisco Systems, Inc.
C4500 processor with 32768 Kbytes of main memory
>
>
i
System Bootstrap, Version 5.1(1) [daveu 1], RELEASE SOFTWARE (fc1)
Copyright (c) 1994 by cisco Systems, Inc.
C4500 processor with 32768 Kbytes of main memory
>
b
flash
Checking Link Status...OK
Booting yj11120n from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
[OK - 1337256/3532618 bytes]
#########################################################################
#########################################################################
#########################################################################
##############################################################
F3: 1926336+46904+183152 at 0x12000
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.
170 West Tasman Drive
San Jose, California 94134-1706
Cisco Internetwork Operating System Software
IOS (tm) 4500 Software (C4500-AJ-M), Version 11.1(2)
Copyright (c) 1986-1996 by cisco Systems, Inc.
Compiled Mon 24-May-96 22:46 [mikehub 107]
cisco 4500 (R4K) processor (revision 0x00) with 32768K/4096K bytes of memory.
Processor ID 01242622
R4600 processor, Implementation 32, Revision 1.0
G.703/E1 software, Version 1.0
Bridging software.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
TN3270 Emulation software (copyright 1994 by TGV Inc.).
2 Ethernet/IEEE 802.3 interfaces.
2 Token Ring/IEEE 802.5 interfaces.
4 ISDN Basic Rate interfaces.
2 Serial network interfaces.
128K bytes of non-volatile configuration memory.
8192K bytes of processor board System Flash (Read/Write)
4096K bytes of processor board Boot Flash (Read/Write)
Press RETURN to get started!
router#
Error programming flash memory
erase flash before writing? [confirm]
router# show flash all
System flash directory:
File Length Name/status
addr fcksum ccksum
1 4448508 master/california/i7/bin/c4500-aj-mz.111-1
0x40 0x52C3 0x52C3
[4448572 bytes used, 3940036 available, 8388608 total]
8192K bytes of processor board System flash (Read/Write)
Chip Bank Code Size Name
1 1 89A2 1024KB INTEL 28F008SA
2 1 89A2 1024KB INTEL 28F008SA
3 1 89A2 1024KB INTEL 28F008SA
4 1 89A2 1024KB INTEL 28F008SA
1 2 89A2 1024KB INTEL 28F008SA
2 2 89A2 1024KB INTEL 28F008SA
3 2 89A2 1024KB INTEL 28F008SA
4 2 89A2 1024KB INTEL 28F008SA
router#
show protocol route network.
rommon 1 >
rommon 1 >
prompt to display a list of available commands and options, as follows:
rommon 1 > ?
help monitor builtin command help
boot boot up an external process
dir list files in file system
dev list the device table
confreg configuration register utility
reset system reset
stack produce a stack trace
context display the context of a loaded image
frame print out a selected stack frame
sysret print out info from last system return
meminfo main memory information
rommon 2 >
rommon 10 > dev
Devices in device table:
id name
flash: flash
bootflash: boot flash
eprom: eprom
rommon 11 > dir flash:
File size Checksum filename
2229799 bytes (0x220627) 0x469e C4500-k
"xxx: kernel context state is invalid, can not proceed."
rommon 8 > sysret
System Return Info:
count: 19, reason: user break
pc:0x60043754, error address: 0x0
Stack Trace:
FP: 0x80007e78, PC: 0x60043754
FP: 0x80007ed8, PC: 0x6001540c
FP: 0x80007ef8, PC: 0x600087f0
FP: 0x80007f18, PC: 0x80008734
rommon 9 > meminfo
Main memory size: 8 MB. Packet memory size: 4 MB
Available main memory starts at 0xa000e001, size 0x7f1fff
Packet memory starts at 0xa8000000
NVRAM size: 0x20000
rommon 7 > confreg
Configuration Summary
enabled are:
console baud: 9600
boot: the ROM Monitor
do you wish to change the configuration? y/n [n]: y
enable "diagnostic mode"? y/n [n]: y
enable "use net in IP bcast address"? y/n [n]:
enable "load rom after netboot fails"? y/n [n]:
enable "use all zero broadcast"? y/n [n]:
enable "break/abort has effect"? y/n [n]:
enable "ignore system config info"? y/n [n]:
change console baud rate? y/n [n]: y
enter rate: 0 = 9600, 1 = 4800, 2 = 1200, 3 = 2400 [0]: 0
change the boot characteristics? y/n [n]: y
enter to boot:
0 = ROM Monitor
1 = the boot helper image
2-15 = boot system
[0]: 0
Configuration Summary
enabled are:
diagnostic mode
console baud: 9600
boot: the ROM Monitor
do you wish to change the configuration? y/n [n]:
You must reset or power cycle for new config to take effect
http://www.cisco.com.
cco.cisco.com.
ccohelp@cisco.com.
For additional information, contact
ccoteam@cisco.com.
tac@cisco.com.
To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or
csrep@cisco.com.
