Ios Xe - Upgrade Rommon
Ios Xe - Upgrade Rommon
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
© 2003–2014 Cisco Systems, Inc. All rights reserved.
ROMMON Image Overview
Note If you are not using the PXE boot feature, you do not have to upgrade to ROMMON IOS Version
15.1(1r)SG7.
Note If you are not using the PXE boot feature, you do not have to upgrade to ROMMON IOS Version
15.1(1r)SG8.
Caveats
The following caveat is fixed in ROMMON IOS Version 15.1(1r)SG14:
• The Cisco IOS image bootup time is increased by 5 minutes, to ensure there is sufficient time for
the standby Supervisor to come up in SSO. The time delay occurs only when upgrading the
ROMMON on Supervisor Engine 9-E. CSCvf09359
The following caveat is fixed in ROMMON IOS Version 15.1(1r)SG10:
• The ROMMON upgrade process has been improved by
– Providing log messages that indicate failures in write processes, during an upgrade.
– Increasing the number of times the system retries ( in case of a failure), to three retries.
CSCvd49800.
The following caveats are open for ROMMON IOS Version 15.1(1r)SG7:
• The PXE file download does not display accurate logs for ova download.
Workaround: None. CSCva41858
The following caveat is fixed in ROMMON Version 15.1(1r)SG6:
• A Catalyst 4500 Series switch with redundant Supervisor Engine 8-E may crash after a switchover
- if there has been a ROMMON upgrade before the switchover.
Workaround: Perform a simultaneous upgrade on both supervisor engine. CSCuu14223
The following caveat is fixed in ROMMON Version 15.1(1r)SG5:
• Fixed the root-cause of PoE reset on the WS-X4248 and WS-X4548 modules on Supervisor Engine
8-E. CSCuq16235
The following caveat is fixed for ROMMON Version 15.1(1r)SG4:
• A switch using a config-register ending in 0x2 may drop into ROMMON if a powercycle interrupts
the bootup.
Workaround: Use config-register 0x2101. CSCue19458
The following caveats are open for ROMMON Version 15.1(1r)SG4:
• No persistent record exists for kernel panics (like kernel software caveats, Layer 2 hardware
glitches, and DDR parity errors), making [their] debugging impossible.
Workaround: Connect the system console to a device that records the output. CSCtj80874
• ROMMON prints R*E instead of R+E or R-E chassis type in the output of the version command in
ROMMON.
Workaround: None. CSCul23608.
The following caveat is open for ROMMON Version 15.1(1r)SG.
• With IOS Release XE 3.3.0XE (15.1.(1)XO), ROMMON supports the Fa1 management interface at
10/100/1000Mbps full duplex mode only; 10/100/1000Mbps half-duplex is not supported. This
prevents the FA1 management interface from operating when connected to a hub.
Note Only ROMMON version 15.1(1r)SG works on Supervisor Engine 8-E. However, the latest
ROMMON version 15.1(1r)SG6 is backward compatible; we can boot IOS XE 3.3.0XE
(15.1.(1)XO) images with the 15.1(1r)SG6 ROMMON.
Note This release also supports up to 4 Gigabytes of memory and a maximum length of the ROMMON
command line from 128 to 256 bytes.
The following [error] messages might be observed if IOS XE 3.6.0XE images are booted with older
ROMMON images:
rommon 1 > boot bootflash:cat4500es8-universalk9.SPA.03.06.00.E.152-2.E.bin
File has bad file magic number: 0x0. Is it a valid file?
boot: cannot load "bootflash:cat4500es8-universalk9.SPA.03.06.00.E.152-2.E.bin?;
Note The examples in this section use the programmable read-only memory (PROM) upgrade IOS Version
15.1(1r)SG4 and Cisco IOS Release 15.2(2)E. For other releases, replace the ROMMON release and
Cisco IOS software release with the appropriate releases and filenames. This document describes the
procedure for a single supervisor system. You must perform the process on each supervisor in a dual
supervisor system.
Step 1 Directly connect a serial cable to the console port of the supervisor engine.
Note This section assumes that the console baud rate is set to 9600 (default). If you want to use a different
baud rate, change the configuration register value for your switch.
Step 2 Download the cat4500-e-ios-promupgrade-151-1r-SG4 program from Cisco.com, and place it on a TFTP
server in a directory that is accessible from the switch that is upgraded.
The cat4500-e-ios-promupgrade-151-1r-SG4 program is available on Cisco.com at the same location
from which Catalyst 4500 system images are downloaded.
Step 3 Use the dir bootflash: command to ensure that sufficient space exists in Flash memory to store the
PROM upgrade image. If you are using an SD card, replace bootflash: with slot0:
Step 4 Download the cat4500-e-ios-promupgrade-151-1r-SG4 program into Flash memory using the copy tftp
command.
The following example shows how to download the PROM upgrade image
cat4500-e-promupgrade-150_1r_SG2 from the remote host 172.20.58.78 to bootflash:
Switch# copy tftp: bootflash:
Address or name of remote host [172.20.58.78]?
Source filename [cat4500-e-ios-promupgrade-151-1r-SG4]?
Destination filename [cat4500-e-ios-promupgrade-151-1r-SG4]?
Accessing tftp://172.20.58.78/ cat4500-e-ios-promupgrade-151-1r-SG4...
Loading cat4500-e-ios-promupgrade-151-1r-SG4 from 172.20.58.78 (via
GigabitEthernet2/1):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!
!!!!!!!!!!
[OK - 901380 bytes]
Step 5 On a dual-supervisor system, copy the same ROMMON image to the standby supervisor engine with the
copy bootflash: cat4500-e-ios-promupgrade-151-1r-SG4 slavebootflash command.
Step 6 Enter the reload command to reset the switch, press Ctrl-C to stop the boot process, then re-enter
ROMMON mode.
The following example shows the output after a reset into ROMMON:
Switch# reload
Proceed with reload? [confirm]
03:57:16:%SYS-5-RELOAD:Reload requested
.
.(output truncated)
.
Caution No intervention is necessary to complete the upgrade. To ensure a successful upgrade, do not interrupt
the upgrade process. Do not perform a reset, power cycle, or OIR of the supervisor engine until the
upgrade completes.
The following example shows the output from a successful upgrade, followed by a system reset:
boot bootflash:cat4500-e-ios-promupgrade-151-1r-SG4
************************************************************
* *
* Unified FPGA Upgrade Utility *
* Copyright (c) 2012-2014 by Cisco Systems, Inc. *
* All rights reserved. *
* *
************************************************************
Version 15.1(1r)SG4
Compiled Thu 05-Jun-14 11:18 [RLS]
Uncompressing image...
Uncompressing image...
Validating FPGA:>
Programming FPGA:>
-----------------------
***********************
Verifying FPGA:>
.......................
FPGA[W] MD5 : d6106d9343b9595a0465449bf6c77f9b
Unpacking ROMMON:>
Uncompressing image...
Uncompressing image...
Validating ROMMON:>
Programming ROMMON:>
---------
*********
Verifying ROMMON:>
.........
ROMMON[W] MD5 : b92b79fc3566c3700d3b2b87c5d0898f
Step 8 Boot the Cisco IOS software image. This may happen automatically if the system is configured to
auto-boot.
Step 9 On a redundant system, hook up a console to the now-active supervisor engine. After the system achieves
an SSO state, repeat steps 6-8.
Step 10 Use the show module command to verify that you have upgraded the ROMMON:
Switch# show module
Chassis Type : WS-C4503-E
Step 11 Use the delete command on the active supervisor to delete the PROM upgrade program from bootflash.
The following example shows how to delete cat4500-e-ios-promupgrade-151-1r-SG4 image from
bootflash:
Switch# delete bootflash: cat4500-e-ios-promupgrade-151-1r-SG4
Step 12 On a redundant system, also delete the upgrade file from the standby supervisor engine.
Switch# # delete slavebootflash: cat4500-e-ios-promupgrade-151-1r-SG4
Follow this procedure to upgrade your supervisor engine ROMMON to Release 15.0(1r)SG2. This
procedure can be used when console access is not available and when the ROMMON upgrade must be
performed remotely.
Note In the following discussion, we assume that at least one IP address has been assigned to either an SVI or
a routed port.
Step 5 Use the no boot system flash bootflash:file_name command to clear all BOOT variable commands in
the configuration file. In this example, the BOOT variable was set to boot the image
cat4500e-universal.SPA.03.02.00.SG.150-2.SG.bin from bootflash:
Switch# configure terminal
Switch(config)# no boot system flash
bootflash:cat4500e-universal.SPA.03.02.00.SG.150-2.SG.bin
Switch(config)# exit
Switch# write
Building configuration...
Compressed configuration from 3641 to 1244 bytes [OK]
Switch#
Use the boot system flash bootflash:file_name command to set the BOOT variable. You will
use two BOOT commands: one to upgrade the ROMMON and a second to load the Cisco IOS
software image after the ROMMON upgrade is complete. Notice the order of the BOOT
variables in the example below. At bootup the first BOOT variable command upgrades the
ROMMON. When the upgrade is complete the supervisor engine will autoboot, and the second
BOOT variable command will load the Cisco IOS software image specified by the second BOOT
command
Note For a successful ROMMON upgrade, the config-register must be set to enable reading the boot system
commands (i.e. the last digit of the configuration register is set to 2; for example, 0x0102.)
In this example, we assume that the console port baud rate is set to 9600 bps and that the
config-register is set to 0x0102.
Use the config-register command to autoboot using image(s) specified by the BOOT variable.
Configure the BOOT variable to upgrade the ROMMON and then autoboot the IOS image after
the ROMMON upgrade is complete. In this example, we are upgrading the ROMMON to version
15.0(1r)SG2. After the ROMMON upgrade is complete, the supervisor engine will boot Cisco
IOS-XE software Release 03.02.03.SG.
config-register to 0x0102.
Step 6 Use the show bootvar command to verify the boot string. The BOOT variable in this example will first
run the PROM upgrade to upgrade ROMMON. Then, the upgrade software will reload and the supervisor
engine will load the Cisco IOS software image.
Switch# show bootvar
BOOT variable =
bootflash:cat4500-e-ios-promupgrade-150-1r-SG2,1;bootflash:cat4500e-universal.SPA.03.02.03
.SG.150-2.SG3.bin,1;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2102
Step 7 Run the PROM upgrade program by issuing the reload command. Issuing this command will terminate
your Telnet session.
Caution Verify the boot string in step 6. No intervention is necessary to complete the upgrade. To ensure a
successful upgrade, do not interrupt the upgrade process. Do not perform a reset, power cycle, or OIR
of the supervisor engine until the upgrade is complete.
The following example shows the console port output from a successful ROMMON upgrade followed
by a system reset. Your Telnet session is disconnected during the ROMMON upgrade, so you will not
see this output. This step could take 2-3 minutes to complete. You will need to reconnect your Telnet
session after 2-3 minutes when the Cisco IOS-XE software image and the interfaces are loaded.
Switch# reload
Proceed with reload? [confirm]
Restarting system.
************************************************************
* *
* Welcome to Rom Monitor for WS-X45-SUP7-E System. *
* Copyright (c) 2008-2010 by Cisco Systems, Inc. *
* All rights reserved. *
* *
************************************************************
config-register = 0x2102
Autobooting using BOOT variable specified file.....
************************************************************
* *
* ROM Monitor/FPGA Upgrade for WS-X45-SUP7-E System *
* *
* Copyright (c) 2008-2011 by Cisco Systems, Inc. *
* All rights reserved. *
* *
************************************************************
Uncompressing image.....
Done!
**********************************************************
* ** Now Upgrading Primary ROMMON Image ** *
**********************************************************
erasing... ********************************
writing... ********************************
reading... verifying... Done!
Uncompressing image.....
Done!
Uncompressing image.....
Done!
Uncompressing image.....
Done!
**********************************************************
* ** Now Programming FPGA Image ** *
**********************************************************
erasing... **********
writing... **********
reading... verifying... Done!
Uncompressing image.....
Done!
**********************************************************
* ** Now Programming FPGA Signature ** *
**********************************************************
erasing... *
writing... *
reading... verifying... Done!
**********************************************************
System will now reset itself and reboot within few seconds
**********************************************************
.
.(output truncated)
.
***** The system will autoboot in 5 seconds *****
config-register = 0x2102
Autobooting using BOOT variable specified file.....
Step 8 Use the no boot system flash bootflash:file_name command to clear the BOOT command used to
upgrade the ROMMON.
Switch# configure terminal
Switch(config)# no boot system flash bootflash:cat4500-e-ios-promupgrade-150-1r-SG2
Switch(config)# exit
Switch# write
Building configuration...
Compressed configuration from 3641 to 1244 bytes [OK]
Switch#
Step 9 Use the show version command to verify that the ROMMON has been upgraded.
Switch# show version
Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software
(cat4500e-UNIVERSAL-M), Version 03.02.03.SG RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Mon 09-Jan-12 03:25 by prod_rel_team
ROM: 15.0(1r)SG2
Jawa Revision 7, Snowtrooper Revision 0x0.0x116
Switch#
Step 10 Use the delete command to delete the PROM upgrade program from bootflash.
The following example shows how to delete the cat4500-e-ios-promupgrade-150-1r-SG2 image from
bootflash and reclaim unused space:
Switch# delete bootflash:cat4500-e-ios-promupgrade-150-1r-SG2
Delete filename [cat4500-e-ios-promupgrade-150-1r-SG2]?
Delete bootflash:cat4500-e-ios-promupgrade-150-1r-SG2? [confirm]
Switch#
Step 11 Use the show bootvar command to verify that the ROMMON upgrade program has been removed from
the BOOT variable.
Switch# show bootvar
BOOT variable = bootflash:cat4500e-universal.SPA.03.02.03.SG.150-2.SG3.bin,1
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x0102
Note To use ROMON tftp boot, the TFTP server must be accessible from the Ethernet management
port on the supervisor engine.
To boot from ROMMON, perform the following tasks while in ROMMON mode:
a. Ensure that the Ethernet management port on the supervisor engine is physically connected to the
network.
b. Set IP address of the Ethernet management port on the supervisor engine by entering the following
command: set interface fa1 ip_address ip_mask
For example, to set the supervisor engine Ethernet port with an IP address 172.16.1.5 and IP
mask 255.255.255.0, enter the following command:
rommon 2> set interface fa1 172.16.1.5 255.255.255.0
c. Set default gateway for the Ethernet management port on the supervisor engine by entering the
following command: set ip route default gateway_ip_address. The default gateway should be
directly connected to the supervisor engine Ethernet management port subnet.
d. Ping the TFTP server to ensure that there is connectivity to the server from the Ethernet management
port on the supervisor engine by entering the following command: ping tftp_server_ip_address.
e. Once the ping is successful, boot the image from the TFTP server by entering the following
command: boot tftp://tftp_server_ip_address / image_path_and_file_name
For example, to boot the Cisco IOS XE image cat4500es8-universalk9.03.01.00
.SG.151-1.XO.bin located on the TFTP server 172.16.1.8, enter the following command:
rommon 3> boot
tftp://172.16.1.8/tftpboot/cat4500es8-universalk9.03.01.00.SG.151-1.XO.bin
Related Documentation
Although their Release Notes are unique, the 4 platforms (Catalyst 4500, Catalyst 4900, Catalyst ME
4900, and Catalyst 4900M) use the same Software Configuration Guide, Command Reference Guide, and
System Message Guide. Refer to the following home page for additional information:
http://www.cisco.com//en/US/products/hw/switches/ps4324/prod_release_notes_list.html
Hardware Documents
Installation guides and notes including specifications and relevant safety information are available at the
following URLs:
• Catalyst 4500 E-series Switches Installation Guide
http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/hardware/catalyst4500e/installation/g
uide/Eseries.html
• For information about individual switching modules and supervisors, refer to the Catalyst 4500
Series Module Installation Guide at:
http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/hardware/configuration/notes/OL_25
315.html
• Regulatory Compliance and Safety Information for the Catalyst 4500 Series Switches
http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/hardware/regulatory/compliance/78_
13233.html
• Installation notes for specific supervisor engines or for accessory hardware are available at:
http://www.cisco.com/en/US/products/hw/switches/ps4324/prod_installation_guides_list.html
Software Documentation
Software release notes, configuration guides, command references, and system message guides are
available at the following URLs:
• Catalyst 4500E release notes are available at:
http://www.cisco.com/en/US/products/hw/switches/ps4324/prod_release_notes_list.html
Software documents for the Catalyst 4500 E-Series switches are available at the following URLs:
• Catalyst 4500 Series Software Configuration Guide
http://www.cisco.com/en/US/products/hw/switches/ps4324/products_installation_and_configurati
on_guides_list.html
• Catalyst 4500 Series Software Command Reference
http://www.cisco.com/en/US/products/hw/switches/ps4324/prod_command_reference_list.html
• Catalyst 4500 Series Software System Message Guide
http://www.cisco.com/en/US/products/hw/switches/ps4324/products_system_message_guides_list
.html
This document is to be used in conjunction with the documents listed in the “Related Documentation” section.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, the Cisco logo, DCE, and Welcome to the Human
Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet,
AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork
Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation,
EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ
Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace,
MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare,
SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo
are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply
a partnership relationship between Cisco and any other company. (0807R)