Recovering Catalyst Switches Running CatOS from Booting FailuresPrintable Pdf
Document ID: 17052
Introduction Before You Begin
Conventions
Prerequisites
Components Used
Background Information Recovering the Catalyst 4000, Catalyst 2948G, Catalyst 2980G, and Catalyst 4912G
General Information
Recovery Procedure Recovering the Catalyst 5000 with Supervisor Engine I or II, IIG, IIIG and Catalyst
2926
General Information
Recovery Procedure
Console Download Recovering the Catalyst 5000 with Supervisor III and IIIF and Catalyst 2926G
General Information
Recovery Procedure Recovering the Catalyst 6000 with Supervisor I and II
General Information
Recovery Procedure Xmodem Options Summary Preventing the Switch from Booting in ROMmon Mode: Verifying Boot Variables and
Configuration Register Values Related Information
Introduction
This document explains how to recover a Catalyst switch when its software becomes corrupted. This
document covers Catalyst models running Cisco CatOS® Software: Catalyst 4000 (including 2948G, 2980G,
4912G, but not the -L3 series), Catalyst 5000 (including Catalysts 5500, 5505, 5509 and some of the 2900
series models - not the XL series), and the Catalyst 6000 series switches with Supervisor running CatOS.
Refer to the following documents for switch recovery procedures not included in the list above:
Recovery From Corrupt or Missing Software Image on Cisco Catalyst 2900XL and 3500XL Series
Switches
Recovering a Catalyst 4000 Switch with Supervisor III or IV from a Corrupted or Missing Image and
from ROMmon Mode
Recovering a Catalyst 4000 Layer 3 Module (WS-X4232-L3) from a Corrupted or Missing Image, or
from ROMmon Mode
Recovering a Catalyst 5000 RSM from a Corrupted or Missing Image, Boot, or ROMmon Mode
Recovering a Catalyst 6000 Running Native IOS from a Corrupted or Missing Boot Loader Image or
ROMmon Mode
How-to Recover a Missing MSFC from the Supervisor's show module Command
Before You Begin
Conventions
For more information on document conventions, see the Cisco Technical Tips Conventions.
Prerequisites
There are no specific prerequisites for this document.
Components Used
The information in this document is based on the Catalyst 4000, 5000, and 6000 series switches running
CatOS.
The information presented in this document was created from devices in a specific lab environment. All of the
devices used in this document started with a cleared (default) configuration. If you are working in a live
network, ensure that you understand the potential impact of any command before using it.
Background Information
These switches run their software from RAM, after loading it from a Flash device. If all Flash images get
corrupted or deleted, the switch will not be able to boot up properly. In this condition, the switch generally
falls back in a ROM monitor (ROMmon) mode, which has limited feature capability. This document explains
how to download a new image and recover the switch from this situation.
During software upgrade, the old image may be deleted from Flash by issuing the delete command to load the
new image. The new image transfer may fail due to network/Trivial File Transfer Protocol (TFTP) server
problems, or the old image may be deleted (by mistake) from the Flash device. The image can still be
recovered by issuing the undelete command, provided that the following guidelines have been used:
The switch is not reloaded after deleting the image.
or
The squeeze command is not used to remove the deleted image permanently from Flash.
When an image is deleted from the Flash using the delete command, the image will not be permanently
deleted from Flash and can be recovered using the undelete command. This is applicable to Catalyst 4000,
5000, and 6000 series switches.
In the case of the Catalyst 4000, if the switch is reloaded after deleting the image, the deleted image can still
be recovered in ROMmon mode using the undelete ROM monitor command. The del, undelete, and
squeeze commands are supported in ROMmon mode only for Catalyst 4000 series switches with CatOS
release 6.1 and later. For more details on these commands, refer to the following documents:
Catalyst 4500 Series Command Reference, 7.6
Catalyst 5000 Switch and ROM Monitor Commands Release 6.3
Catalyst 6000 Switch and ROM Monitor Commands Release 7.4
If the above possibilities do not work with your Catalyst 4000, 5000, and 6000 series switches, you will need
to follow the recovery procedures given in this document
Note: Trivial File Transfer Protocol (TFTP) may be used to transfer software image files from a PC to your
device. This document was written using output from the Cisco TFTP Server application. Cisco has
discontinued this application and no longer supports it. If you do not have a TFTP server, obtain any
third-party TFTP server application from another source.
Recovering the Catalyst 4000, Catalyst 2948G, Catalyst
2980G, and Catalyst 4912G
General Information
The Catalyst 4000 has an onboard bootflash Flash system that is used to store image files. During normal
bootup, the Supervisor typically loads a software image from Flash. The Flash is not needed anymore for
switch operation when an image is already loaded in RAM. You can then upgrade the software while the
switch is up and operational, using the traditional copy tftp Flash command. However, if you encounter a
problem with the software you currently have in Flash, and are unable to fully bootup the switch, or if the
switch ends up in ROMmon for any reason and you need to get the switch back up, you can now perform a
netboot using the procedure described below.
Before proceeding to the recovery procedure, make sure that you do not have any valid files in the bootflash:.
Issue the dir bootflash: command from the rommon> mode to determine if there are any files in the
bootflash:. If a valid file exists, issue the boot bootflash: filename to attempt to bring up the switch. As noted
in the background information section, it is possible to undelete a deleted file from ROMmon on these
switches. You can undelete the file by issuing the undelete bootflash: filename command; the file can then
be used to boot the switch. If you have no valid file in the bootflash, go to the recovery procedures below.
Note: For more information on connecting a console to your switch, as well as managing and upgrading
software, please see the Related Information section of this document.
Recovery Procedure
A netboot will allow you to download an image from a TFTP server directly into RAM, where the Supervisor
can run it. This procedure does not create any files on the Flash system. It only allows you bring up your
switch and perform a normal software download.
A netboot is fairly easy, but there are a couple of things you need to know before you start. When your switch
is in ROM, you must be directly connected to the console, and the only network port that will be active will be
interface ME1 (this is the Ethernet port on the Catalyst 4000 series Supervisor next to the console connection).
This requires that you have an IP address on the ME1 interface and ensure that it is up. If your TFTP server is
not on the same network, you will also need to set a default gateway. Additionally, you will need to have the
TFTP server environment variable set, because the syntax of the commands does not allow you to specify an
IP/host address.
1.Start with verifying that all the variables are set, and that you are able to reach the TFTP server. rommon 1> show interface
me1: inet 172.20.58.227 netmask 255.255.255.0 broadcast 172.20.58.255
!--- If you do not see an IP address on the ME1 interface,
!--- issue the following command to set the IP address:
!--- set interface me1 [netmask]
!--- For example, set interface me1 172.20.58.227 255.255.255.0. rommon 2 > show ip route
Destination Gateway Interface
------------ ------- ---------
default 0.0.0.0 m me1
In this example, there is no default gateway set. If the TFTP server is not on the same network, we
need to set a default route.
2.Set the default gateway, if needed.
rommon 3> set ip route default 172.20.58.1
The command gives no response, but we can issue the show ip route command again for verification.
rommon 4> show ip route
Destination Gateway Interface
----------- ------- ---------
default 172.20.58.1 me1
3.Check that the TFTP server variable is correctly set.
The set command issued by itself displays the environment variables.
Since we do not have the TFTP server variable as part of the environment, we will need to set it
before we can proceed. We set the variable, verify that it is actually in the environment, and then ping
the server to validate connectivity. You do not need to have the TFTP server environment variable set
to be able to ping the server. It is required to access the file on the server using the boot command,
which is explained below.
rommon 6> Tftpserver=172.20.59.67
!--- Setting TFTP server variable.
rommon 7 > set
!--- Verifying the setting.
PS1=rommon ! >
AutobootStatus=success
MemorySize=32
DiagBootMode=post
Tftpserver=172.20.59.67
?=0
ROMVERSION=4.4(1)
WHICHBOOT=bootflash:cat4000.4-4-1.bin
BOOT=bootflash:cat4000.4-4-1.bin,1;
4.Netboot the system.
rommon 9> boot cat4000.4-4-1.bin
5.After netbooting the system, you will get the switch console. Use the copy tftp Flash command
copy the valid image to the Flash, that is when the system is fully operational once again. To make
sure that the switch boots with the valid image in the next reload, verify the boot variables and
configuration register values.
Recovering the Catalyst 5000 with Supervisor Engine I or II,
IIG, IIIG and Catalyst 2926
General Information
The Catalyst Supervisor Engines I, II, IIG, and IIIG for the Catalyst 5000 family have an onboard Flash that
can only store one system image. The switch runs its image from RAM, so there is no need for a valid
software image in Flash after the switch is correctly booted.
Note: The Catalyst 2926 has Supervisor II and follows the Supervisor II recovery procedure.
The upgrade procedure for these Supervisors is pretty safe. A new image is first copied into the Supervisor
RAM, where its checksum is verified. If this image is declared valid, it is then programmed into the Flash,
overwriting the previous one. If an error occurs during the download from the TFTP server, for instance, the
current image in Flash is not modified. Corrupting images on these Supervisors happens rarely and is often
related to a problem on the Flash itself or caused by an issue during the Flash programming process.
Note: For more information on connecting a console to your switch, as well as managing and upgrading
software, please see the Related Information section of this document.
Recovery Procedure
If no image is available in Flash for booting, the Supervisor also has a very basic software image permanently
stored in ROMmon. A jumper on the Supervisor needs to be used in order to activate this image. Once loaded,
it will at least enable the ports of the Supervisors and can even recognize some of your linecards, depending
on the firmware version.
1.Remove the Supervisor Engine and identify the boot jumper using the information in the table above.
There is generally no jumper connector available on the Supervisor, so you need to get one to
establish contact between the pins.
2.Place the Supervisor Engine back into the chassis and boot up the switch. 3.You end up in a boot mode, which is actually a CatOS image burnt into ROM (firmware). Depending
on the level of this firmware, the switch may even recognize some of the switch's line cards.
boot> sh mod
Mod Ports Module-Type Model Serial-Num Status
--- -------------------------- --------- ---------- -------
1 0 Supervisor IIG WS-X5540 013447622 ok
2 12 100BaseFX MM Ethernet WS-X5111 003499884 ok
312 100BaseFX MM Ethernet WS-X5201 007499406 ok
Mod MAC-Address(es)Hw Fw Fw1
;--- ---------------------------------------- ------ ------------ ------------
1 00-d0-63-6a-a8-00 thru 00-d0-63-6a-ab-ff 1.1 5.1(1) 0.5(1)
200-60-3e-8e-2b-48 thru 00-60-3e-8e-2b-53 1.0 1.3
3 00-e0-1e-b7-77-68 thru 00-e0-1e-b7-77-73 2.0 3.1(1)
In this example, the two line cards in the switch are recognized by the software. With Supervisors I or
II, even though they are likely to have an older firmware version than the Supervisor IIG, the two
uplinks are always recognized by the software.
Using the interfaces available, you now have to get connectivity to a TFTP server and perform the
usual upgrade.
4.By default, ports are disabled; you have to enable them manually.
boot> sh port
Port Status Duplex Speed Type
----- -------- ------ ----- ---------------
2/1 disabled half 100 100BaseFX MM
;2/2 disabled half 100 100BaseFX MM
2/3 disabled half 100 100BaseFX MM
2/4 disabled half100 100BaseFX MM
boot> set port en 2/1
Port 2/1 enabled/ 5.Ensure connectivity to your TFTP server as usual. 6.Once you have downloaded a new image into Flash, you have two options, as follows:
Simply turn off the switch, slide out the Supervisor Engine, remove the jumper, and boot the
Catalyst normally once the Supervisor Engine is correctly re-installed.
Boot the image downloaded in Flash directly from the boot mode using the execFlash
command, as follows:
boot> execFlash
uncompressing nmp image
;This will take a minute...
--- output suppressed ---
Note: If you boot up the switch this way, remember that until you remove the jumper, your switch will always
restart in boot mode first.
Console Download
You can download an image to the Supervisor without a TFTP server, directly through the console
connection, using the kermit protocol. Refer to Preparing to Download an Image Using Kermit for more
information. This may be useful if you cannot get any port to be recognized on the switch during the recovery
procedure; however, this method is much slower than the previous one and should be avoided if possible.
Recovering the Catalyst 5000 with Supervisor III and IIIF
and Catalyst 2926G
General Information
The Catalyst 5000 Supervisor IIIF has an onboard Flash file system that can handle several image files. In
addition to this Flash, the Supervisor III also has a PCMCIA Flash slot. These Supervisors run their software
from RAM and do not need their Flash system once correctly booted up.
Note: The Catalyst 2926G has Supervisor III installed and follows the Supervisor III recovery procedure.
If an image is then corrupted or deleted, the standard upgrade procedure is always possible as long as the
Supervisor is running a valid image. If the Supervisor is not booting up because there is no valid image to
boot from the ROMmon, you will have to use the recovery procedure described in the following section.
Before proceeding to the recovery procedure, make sure that you do not have any valid files in the bootflash:.
Issue the dir bootflash: command from the rommon> mode to determine if there are any files in the
bootflash:. If a valid file exists, issue the boot bootflash: filename to attempt to bring up the switch. As noted
in the background information section, it is possible to undelete a deleted file from ROMmon on these
switches. You can undelete the file by issuing the boot bootflash: filename to boot the switch. If you have no
valid file in the bootflash, go to the recovery procedures below.
Note: For more information on connecting a console to your switch, as well as managing and upgrading
software, please see the Related Information section of this document.
Recovery Procedure
Booting from a PCMCIA Flash Card
If you have a Supervisor III with a PCMCIA Flash slot, the best way to recover the Supervisor is to boot it
from a PCMCIA Flash card by using the boot slot0: image_name command in ROMmon mode. Try to get a
PCMCIA Flash card with a Supervisor III image on it. If you do not have another operational Supervisor III to
write an image on the Flash card, you can use other Cisco devices that have a compatible format. Refer to the
following compatibility matrix for more information.
Console Download
If you have a Supervisor IIIF or if a PCMCIA Flash card is not available, the only alternate recovery
procedure is an xmodem download via the console port. This feature is only available if you have ROMmon
version 5.1(1) or above. If you cannot use the console download, the only possibility left is to replace the
Supervisor.
The exact ROMmon version will be displayed on the console when the switch starts up in ROMmon, as
shown below:
This command will reset the system.
Do you want to continue (y/n) [n]? y
2000 May 14 15:06:13 %SYS-5-SYS_RESET:System reset from Console//
makar (enable)
System Bootstrap, Version 5.1(2)
Copyright (c) 1994-1999 by cisco Systems, Inc.
Presto processor with 32768 Kbytes of main memory
This is also the firmware release shown for the Supervisor when issuing a show module command. If you are
able to issue the show mod command, however, you probably will not need a recovery procedure.
Console> (enable) sh mod
--- output suppressed ---
Mod MAC-Address(es) Hw Fw Sw
--- --------------------------------------- --- -- ---
1 00-50-0f-43-cc-00 to 00-50-0f-43-cf-ff 3.3 5.1(2) 4.5(7)
--- output suppressed ---
The most simple way of checking whether this console download procedure is available to you or not is to
attempt it. The feature is not currently documented, but it works exactly the same as for Cisco routers that are
in ROMmon.
The following is the log of a console session while doing a console download on a Supervisor III, using
console speed 38400 bps. The command is xmodem, option -s. The command is self explanatory, however
there is more information on the available options.
rommon 5> xmodem -s 38400
Do not start the sending program yet...
Invoke this application only for disaster recovery.
Do you wish to continue? (y/n) [n]: y
Note, if the console port is attached to a modem, both the console port and the modem must the same baud rate. Use console speed 38400 bps for download? (y/n) [n]: y
At this stage, change the speed of your terminal emulation software to 38400 before sending the file using the
xmodem protocol. This example is done using Hyperterm on a PC that is restarted in order to have the change
of terminal speed take effect.
Download will be performed at 38400 bps. Make sure your terminal
emulator is set to this speed before sending file.
Ready to receive file ...®ø.
Returning console speed to 9600.
Reset your terminal baud rate to 9600and hit return.
You will see garbage characters until you do so.
The terminal speed is changed back in Hyperterm to 9600 bps and restarted again. Once you confirm that the
baud rate has been reset, the switch immediately starts uncompressing the image that was stored into memory
and executes it, as follows:
Baud rate is correctly set now. Enter y to continue (y/n) [n]:
Baud rate is correctly set now. Enter y to continue (y/n) [n]:
Baud rate is correctly set now. Enter y to continue (y/n)[n]: y
Download Complete!
received file size=3473280
Loading Network Management Processor image
Uncompressing file:##########################
#############################################
#############################################
#############################################
System Power On Diagnostics
NVRAM Size ....................512KB
ID Prom Test ..................Passed
--- output suppressed ---
Cisco Systems Console
Enter password:
2000 May 14 15:45:06 %MLS-5-MLSENABLED:IP Multilayer switching is enabled
2000 May 14 15:45:06 %MLS-5-NDEDISABLED:Netflow Data Export disabled
2000 May 14 15:45:06 %SYS-5-MOD_OK:Module 1 is online
2000 May 14 15:45:18 %SYS-5-MOD_OK:Module 2 is online
2000 May 14 15:45:25 %SYS-5-MOD_OK:Module 4 is online
2000 May 14 15:45:27 %SYS-5-MOD_OK:Module 5 is online
2000 May 14 15:45:29 %SYS-5-MOD_OK:Module 3 is online
Console> en
The switch is now correctly booted with the image that has been downloaded via the console. Be careful:
currently, the image just downloaded has not been saved in bootflash. For example, 4.5(7) was downloaded
via the console, and you can see that the image has not yet been stored in Flash in the example below.
Enter password:
Console> (enable) sh mod
Mod Module-Name Ports Module-Type Model Serial-Num Status
Mod Module-Name Ports Module-Type Model Serial-Num Status
1 0 Supervisor III WS-X5530 013492250 ok
2 12 10BaseFL Ethernet WS-X5011 003375899 ok
3 24 10/100BaseTX Ethernet WS-X5224 008688914 ok
4 12 10/100BaseTX Ethernet WS-X5213 003549295 ok
5 12 100BaseFX MM Ethernet WS-X5201 006596753 ok
Mod MAC-Address(es) Hw Fw Sw
--- --------------------------------------- --- -- ---
1 00-50-0f-43-cc-00 to 00-50-0f-43-cf-ff 3.3 5.1(2) 4.5(7)
2 00-60-3e-c9-30-6c to 00-60-3e-c9-30-77 1.1 1.2 4.5(7)
3 00-10-7b-58-a6-c8 to 00-10-7b-58-a6-df 1.4 3.1(1) 4.5(7)
4 00-60-2f-96-6a-f8 to 00-60-2f-96-6b-03 1.2 1.4 4.5(7)
5 00-e0-1e-7a-18-48 to 00-e0-1e-7a-18-53 1.1 2.3(2) 4.5(7)
Mod Sub-Type Sub-Model Sub-Serial Sub-Hw
--- -------- --------- ---------- ------
1 NFFC II WS-F5531 0013512332 2.0
Console> (enable) dir
-#- -length- -----date/time------ name
1 15708 Apr 19 1993 05:44:04 config
2 4864897 Apr 09 2000 15:26:06 cat5000-sup3.5-4-2.bin
2721312 bytes available (4880864 bytes used)
Console> (enable)
You now have a fully operational switch. If you do not store a valid image in bootflash and restart the switch,
however, you will have to attempt the recovery procedure all over again. Note: Use the copy tftp Flash command to copy the valid image to the Flash. To make sure that the switch
boots with a valid image in the next reload, verify the boot variables and configuration register values.
Recovering the Catalyst 6000 with Supervisor I and II
General Information
This section describes the recovery procedure for the Catalyst 6000 Supervisor I and II. The recovery
procedure for Catalyst 6000 is similar to the above Catalyst 5000 with Supervisor III recovery procedure. The
Catalyst 6000 Supervisor I and II modules have an onboard Flash file system that can handle several image
files. In addition to this Flash, they also have a PCMCIA Flash slot. These Supervisors run their software from
RAM and do not need their Flash system once correctly booted up. If an image is then corrupted or deleted,
the standard upgrade procedure is always possible as long as the Supervisor is running a valid image. If the
Supervisor is not booting up because there is no valid image to boot from the ROMmon, you will have to use
the recovery procedure described in the following section.
Before proceeding to the recovery procedure, make sure that you do not have any valid files in the bootflash:.
Issue the dir bootflash: command from the rommon> mode to determine if there are any files in the
bootflash:. If a valid file exists, issue the boot bootflash: filename to attempt to bring up the switch. As noted
in the background information section, it is possible to undelete a deleted file from ROMmon on these
switches. You can undelete the file by issuing the boot bootflash: filename to boot the switch. If you have no
valid file in the bootflash, go to the recovery procedures below.
Note: For more information on connecting a console to your switch, as well as managing and upgrading
software, please see the Related Information section of this document.
Recovery Procedure
Booting from a PCMCIA Flash Card
The best way to recover the Supervisor is to boot it from a PCMCIA Flash card by using the following
command from ROMmon mode:
boot slot0:image_name
Try to get a PCMCIA Flash card with a valid image on it. If you do not have another operational Supervisor
to write an image on the Flash card, you can use another Cisco devices that has a compatible format. Refer to
the compatibility matrix. Using a PCMCIA card formatted in the source platform may work in some cases;
however, there are a number of situations where the bootstrap version of the switch does not support the
formatted card, even if the filesystems are compatible.
It is always recommended to make a duplicate copy of image present on Flash into the PCMCIA card by
issuing the copy bootflash:image_name slot0:command. This is useful if the image on the Flash is deleted or
corrupted for some reason and your switch runs into ROMmon mode. You will be able to boot the switch
from the slot0: and recover the switch. If you do not have a PCMCIA card or valid image on the PCMCIA
card, follow the xmodem recovery procedure given below.
Console Download or xmodem Recovery
The example below is the log of a console session while doing a console download on a Supervisor II, using
console speed 38400 bps. The command is Xmodem, option -s. The command is self explanatory, however
there is more information on the available options. The same procedure applies to Supervisor I. Copy the valid
image from the Cisco Software Download Center to the PC running terminal emulation software.Note that
you should have a valid CCO login and contract with Cisco to download images from the Software Download
Center.
rommon 15> xmodem -s 38400
Do you wish to continue? (y/n) [n]: y
Console port and Modem must operate at same baud rate.
Use console & modem at 38400 bps for download ? (y/n) [n]: y
At this stage, change the speed of your terminal emulation software to 38400 bps before sending the file using
the xmodem protocol. This example was done using Hyperterm on a PC, and HyperTerminal was restarted in
order to have the change of terminal speed take effect.
Ready to receive file ...Will wait for a minute
Reset your terminal to 9600 baud.
Note that you may see garbage characters until you do so.
The terminal speed in Hyperterm was turned back to 9600 bps and restarted again. Once you confirm that the
baud rate has been reset, the switch immediately starts uncompressing the image it had stored into memory
and executes it, as follows:
Baud rate is correctly set now. Enter y to continue (y/n) [n]:
Baud rate is correctly set now. Enter y to continue (y/n) [n]:
Baud rate is correctly set now. Enter y to continue (y/n) [n]:
Baud rate is correctly set now. Enter y to continue (y/n) [n]: y
Download Complete!
Self decompressing the image :###################
#############################################
#############################################
#################################[OK]
System Power On Diagnostics
DRAM Size ..........................128 MB
Testing DRAM .......................Passed
Verifying Text Segment .............Passed
NVRAM Size .........................512 KB
Level2 Cache .......................Present
Level3 Cache .......................Present
System Power On Diagnostics Complete
Currently running ROMMON from S (Gold) region
Boot image:
Runtime image not stored in the Flash. Flash sync disabled.
Running System Diagnostics from this Supervisor (Module 2)
This may take up to 2 minutes....please wait
Cisco Systems Console
2002 Apr 05 08:06:25 %SYS-3-MOD_PORTINTFINSYNC:Port Interface in sync for Module 2
Enter password: 2002 Apr 05 08:06:27 %SYS-1-SYS_ENABLEPS: Power supply 1 enabled
2002 Apr 05 08:06:28 %SYS-5-MOD_PWRON:Module 3 powered up
2002 Apr 05 08:06:28 %SYS-5-MOD_PWRON:Module 6 powered up
2002 Apr 05 08:06:32 %MLS-5-NDEDISABLED:Netflow Data Export disabled
2002 Apr 05 08:06:34 %MLS-5-MCAST_STATUS:IP Multicast Multilayer Switching is enabled
2002 Apr 05 08:06:34 %MLS-5-FLOWMASKCHANGE:IP flowmask changed from FULL to DEST
console>
console>
The switch is now correctly booted with the image that has been downloaded via the console. Be careful:
currently, the image just downloaded has not been saved in bootflash. For example, 6.3(3) is downloaded via
the console and you can see in the example below that the image has not yet been stored in Flash.
console>
console> en
console> (enable)
console> (enable) dir bootflash:
No files on device
31981568 bytes available (0 bytes used)
console> (enable)
You now have a fully operational switch. However, if you do not store a valid image in bootflash and restart
the switch, you will have to attempt the recovery procedure all over again.
Note: Use the copy tftp Flash command to copy a valid image to the Flash. To make sure that the switch
boots with a valid image in the next reload, verify the boot variables and configuration register values.
Xmodem Options Summary
Xmodem is invoked via entering the xmodem command in the ROMmon prompt, as shown below.
xmodem [-cys]
-c CRC-16
-y ymodem-batch protocol
-s Set speed of download, where speed may be 1200|2400|4800|9600|19200|38400
The detailed descriptions of the options are as follows:
The following table provides examples of the download times you can expect, assuming a 3.2 MB image size.
Preventing the Switch from Booting in ROMmon Mode:
Verifying Boot Variables and Configuration Register Values
Once the Catalyst switch is recovered from corrupted or missing software image, make sure that the boot
variables and configuration register values are set correctly. This is essential to prevent the switchfrom
booting in ROMmon, even if you have a valid file in your bootflash: or slot0: device.
You can verify the settings using the show boot command. The Catalyst 4000, 5000, and 6000 family
switches use the same procedure to verify boot variables and to set the configuration register value. The
outputs below are shown on a Catalyst 6000 switch.
Note: This command applies only to the Catalyst 5000 Supervisor Engine III or the Catalyst 4000 family and
2948G switch Supervisor Engine modules. If you attempt to use this command on a Catalyst 5000 Supervisor
Engine I or II, you will receive an error message.
The sample output of the show boot command is as follows:
Switch (enable) show boot
BOOT variable = bootflash:cat6000-sup.6-3-3.bin,1;
!--- Switch boots from valid image present in bootflash.
CONFIG_FILE variable =
slot0:switch.cfg
Configuration register is 0x2102
!--- Configuration register values is set correctly.
ignore-config: disabled
auto-config: non-recurring, overwrite, sync disabled
console baud: 9600
boot: image specified by the boot system commands
Switch (enable)
In this example, the config-register is set to the proper setting (0x2102). If you see that "Configuration
register is 0x0", you must change the setting to 0x2102. Otherwise, when the switch is reset or rebooted it will
return to ROMmon mode and you will have to boot the image manually for the switch to run that image. In
the example below, the boot variable is not set and the config-register is set to 0x0.
Switch (enable) show boot
BOOT variable =
!--- Boot Variable is not set to boot the switch from a valid image.
CONFIG_FILE variable = slot0:switch.cfg
Configuration register is 0x0
!--- Note that configuration register value is set to 0x0.
ignore-config: disabled
auto-config: non-recurring, overwrite, sync disabled
console baud: 9600
boot: the ROM monitor
Switch (enable)
If this switch is reset or rebooted, it will go to ROMmon. The image must be booted manually from ROMmon
mode using the boot bootflash: command. The boot variable and the configuration register value can be set,
as follows:
Switch (enable) set boot system Flash bootflash:cat6000-sup.6-3-3.bin
BOOT variable = bootflash:cat6000-sup.6-3-3.bin,1;
Switch (enable) set boot config-register 0x2102
Configuration register is 0x2102
ignore-config: disabled
auto-config: non-recurring, overwrite, sync disabled
console baud: 9600
boot: image specified by the boot system commands
Switch (enable)
Switch (enable) show boot
BOOT variable = bootflash:cat6000-sup.6-3-3.bin,1;
!--- Switch boots from valid image present in bootflash.
CONFIG_FILE variable = slot0:switch.cfg
!--- Configuration register values are set correctly.
Configuration register is 0x2102
ignore-config: disabled
auto-config: non-recurring, overwrite, sync disabled
console baud: 9600
boot: image specified by the boot system commands
Switch (enable)
After recovery, even if the switch goes to ROMmon mode, you can set the configuration register value in
ROMmon mode, as shown below. After reloading, the switch will load the valid image so that you do not
have to boot the switch manually, as shown below.
rommon 1> confreg 0x2102
You must reset or power cycle for new config to take effect.
rommon 2> reset
System Bootstrap, Version 5.3(1)
Copyright (c) 1994-1999 by cisco Systems, Inc.
c6k_sup1 processor with 65536 Kbytes of main memory
Autoboot executing command: "boot bootflash:cat6000-sup.6-3-3.bin"
Uncompressing file:###################
System Power On Diagnostics
DRAM Size ....................64 MB
Testing DRAM..................Passed
NVRAM Size ...................512 KB
Level2 Cache .................Present
System Power On Diagnostics Complete
Boot image: bootflash:cat6000-sup.6-3-3.bin
Running System Diagnostics from this Supervisor (Module 1)
This may take up to 2 minutes....please wait
..
..
Switch (enable)
Related Information
Connecting a Terminal to the Catalyst 5000
Catalyst 5000 Upgrade Procedure
Upgrading Software Images and Working with Configuration Files on Catalyst Switches
Catalyst 4000 Software Upgrade Procedure
Recovering a Catalyst 6000 Running Native IOS from a Corrupted or Missing Boot Loader
Image or ROMmon Mode
