TRT Global Limited

Cisco 6509E
IOS Upgrade Procedure
Brief Outline of Procedure
Follow this procedure to upgrade the L3 module:
1Provide TCP/IP connectivity to the L3 module.
2Copy the image into the L3 module through the TFTP.
3Set boot statements to load the new image upon startup.
4Reboot the L3 module to load the new image.
Note: For each L3 module, the procedure is similar and, generally, the same procedure applies. When
differences or specifics apply to each L3 module, there are notes after each step.
Step-by-Step Procedure
Section I Provide TCP/IP Connectivity to the L3 Module
The L3 module has the ability to receive new Cisco IOS images through the TFTP. To use TFTP
with the image, you must ensure that the TFTP server (the computer that runs TFTP server
software) can reach the L3 engine through TCP/IP. If you are able to ping the computer from the
command-line interface (CLI) of the L3 module, you have successfully completed this step.

Section II Copy the Image into the L3 Module Through the TFTP
Verify Free Space on the Bootflash
At this point, you need to verify that you have enough space in the bootflash to copy the new
image. If there is not enough room, you have to delete some files to make space. In some
situations, if the image is very large, you must delete the current image in the bootflash. On the
MSFC, this deletion can be made safely if you also have the boot image in the bootflash. You use
the boot image if the main image is corrupt or not available.
Note: The main image is the full feature set Cisco IOS image, whereas the boot image is
essentially a scaled-down version of the main image. The boot image has limited sub-IP
functionality with the intent to provide TFTP capabilities.
To determine the amount of free space and whether there is a boot image in the bootflash, issue
the dir [device:]command.
Example:
In this example, the bootflash has 1,265,440 bytes free, and there is a boot image present

Australia

Hong Kong

Malaysia

Singapore

India

Philippines

Document created by: Robert Pivac (13 Sep 2016)

Document updated by: Robert Pivac (13 Sep 2016)
The Netherlands USA
Brazil
Russia

TRT Global Limited

(c6msfc2-boot-mz.121-6.E1). The word "boot" in the file name indicates a boot image.
c-MSFC15# dir bootflash:
Directory of bootflash:/
1 -rw1667488 Apr 20 2001 20:56:41 c6msfc2-boot-mz.121-6.E1
2 -rw- 12269412 Feb 05 2002 18:08:32 c6msfc2-jsv-mz.121-8a.E2
15204352 bytes total (1265440 bytes free)
Copy the Image into Bootflash
At this stage, you have IP connectivity and can ping between the computer that acts as a TFTP
server and the L3 module. Now, copy the image into the bootflash. If you cannot ping between
devices, see the Step 1: Provide TCP/IP Connectivity to the L3 Module section of this document.
Step 1 provides appropriate links for IP connectivity.
At the enable prompt, issue this command to copy from the TFTP server to your bootflash:
c-MSFC15# copy tftp bootflash
You see a prompt with this information:
Address or name of remote host []? 172.16.84.119
Address or name of remote host is the IP address of the TFTP server. The ping test in Step 1:
Provide TCP/IP Connectivity to the L3 Module confirms the IP.
Source filename []? c6msfc2-jsv-mz.121-8a.E5
Source filename is the image file name. The file must be in your TFTP directory path so that the
TFTP server can locate the file.
Note: The file name must be spelled exactly the same, which includes any capitalization.
Destination filename [flash]? c6msfc2-jsv-mz.121-8a.E5
Source filename is the image file name. The file must be in your TFTP directory path so that the
TFTP server can locate the file.
Note: The file name must be spelled exactly the same, which includes any capitalization.
Destination filename [flash]? c6msfc2-jsv-mz.121-8a.E5
Destination filename is the file name of the image that you intend to save onto the bootflash.
Use of the same file name as the source name ensures that, in the future, you can correctly
identify the software features and version run.
If you do not have enough space in the bootflash, Cisco IOS Software asks if you want to delete
the current image to make room for the new image.
The transfer can take some time, which depends on the speed of the connection and the size of
the image. During the transfer, you see exclamation marks ("!" ) for good packets. The
appearance of periods (".") indicates that the link has taken some hits. Investigate the problem
afterward.
A successful TFTP transfer reports an OK, along with the number of bytes transferred. If you do
not receive an OK, investigate IP connectivity and possible TFTP server issues.
Example:

Australia

Hong Kong

Malaysia

Singapore

India

Philippines

Document created by: Robert Pivac (13 Sep 2016)

Document updated by: Robert Pivac (13 Sep 2016)
The Netherlands USA
Brazil
Russia

TRT Global Limited

c-MSFC15# copy tftp bootflash

Address or name of remote host []? 172.16.84.119
Source filename []? c6msfc2-jsv-mz.121-8a.E5
Destination filename [flash]? c6msfc2-jsv-mz.121-8a.E5
Accessing tftp://172.16.84.119/c6msfc2-jsv-mz.121-8a.E5...
Loading c6msfc2-jsv-mz.121-8a.E5 from 172.16.84.119 (via Vlan1):

After you have successfully transferred the file, verify that the file is in the bootflash:
Issue the dir [device:] command to show files that are currently in the bootflash.
Example:
c-MSFC15# dir bootflash:
Directory of bootflash:/
1 -rw- 1667488
2 -rw- 12269412

Apr 20 2001 20:56:41

Feb 05 2002 18:08:32

c6msfc2-boot-mz.121-6.E1
c6msfc2-jsv-mz.121-8a.E5

Verify that the name and the file size are correct.

Section III Set Boot Statement

After you copy the image through TFTP, you must provide the L3 module with the name of the
image to load upon boot.
Check Current Boot Statements
The image is now in the bootflash. You must set the L3 module to boot the new image. By
default, the L3 module boots the first available image. (An absence of boot commands in the
configuration enables the default.) There is a possibility that you have a previous boot
statement defined.
There are two ways to determine the current boot parameter settings.
Method 1 is to issue the show config command:
Method 2 is to issue the show boot command:
Example:
c-MSFC15# show boot
BOOT variable = bootflash:c6msfc2-jsv-mz.121-8a.E4,1
CONFIG_FILE variable =
BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-6.E1
Configuration register is 0x102
Check to see if the boot statements appear under the parameter BOOT variable.
If you have boot entries, you must remove them from the configuration. For more information on
the removal of boot entries
Remove Previous Boot Statements
To remove the statements, enter into configuration terminal mode. From the configuration
mode, you can negate any command with the issue of no in front of each boot statement.
This example illustrates the removal of a boot statement:
Example:

Australia

Hong Kong

Malaysia

Singapore

India

Philippines

Document created by: Robert Pivac (13 Sep 2016)

Document updated by: Robert Pivac (13 Sep 2016)
The Netherlands USA
Brazil
Russia

TRT Global Limited

c-MSFC15# show config

Building configuration...
Current configuration : 1625 bytes
!
version 12.1
service timestamps debug datetime msec localtime
!
hostname c-MSFC15
!
boot system flash bootflash:c6msfc2-jsv-mz.121-8a.E4
boot bootldr bootflash:c6msfc2-boot-mz.121-6.E1
!
ip subnet-zero
!
--More-At this point, you have the boot statement that you want to remove. The statement to remove
is boot system flash bootflash:c6msfc2-jsv-mz.121-8a.E4.
c-MSFC15# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
c-MSFC15(config)# no boot system flash bootflash:c6msfc2-jsv-mz.121-8a.E4
c-MSFC15(config)# ^Z
c-MSFC15#
Verify that you have removed the command:
Example:
c-MSFC15# show config
Building configuration...
Current configuration : 1625 bytes
!
version 12.1
service timestamps debug datetime msec localtime
!
hostname c-MSFC15
!
boot bootldr bootflash:c6msfc2-boot-mz.121-6.E1
Once the commands are removed, you can issue the copy run start command or the write
memory command to save the configuration to NVRAM.
Example:
c-MSFC15# write memory
3d01h: %SYS-5-CONFIG_I: Configured from console by vty0 (127.0.0.11)
Building configuration...
c-MSFC15#

Set the New Boot Statement

You must add the boot statement to indicate which image the L3 module needs to load.
Issue this command to set the boot parameter:
boot system flash bootflash:[image_name]
Note: In this command, image_name is the name of the new Cisco IOS image.
Australia

Hong Kong

Malaysia

Singapore

India

Philippines

Document created by: Robert Pivac (13 Sep 2016)

Document updated by: Robert Pivac (13 Sep 2016)
The Netherlands USA
Brazil
Russia

TRT Global Limited

Example:
c-MSFC15# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
c-MSFC15(config)# boot system flash bootflash:c6msfc2-jsv-mz.121-8a.E5
c-MSFC15(config)# ^Z
c-MSFC15# write memory
3d01h: %SYS-5-CONFIG_I: Configured from console by vty0 (127.0.0.11)
Building configuration...
c-MSFC15#
Be sure to verify that the config-register value is set to 0x2102 with the issue of the show
boot command. If config-register is set to a different value, you can change it with the issue of
this command in configuration mode:
config-register 0xvalue
Example:
c-MSFC15# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
c-MSFC15(config)# config-register 0x2102
c-MSFC15(config)# ^Z
c-MSFC15# write memory
Verify the boot parameters with the issue of the show boot command:
c-MSFC15# show boot
BOOT variable = bootflash:c6msfc2-jsv-mz.121-8a.E5,1
CONFIG_FILE variable =
BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-6.E1
Configuration register is 0x102 (will be 0x2102 at next reload)
c-MSFC15#
After you change the config-register, the change takes place at the next reload, as the example
shows.
Section IV Reload the L3 Module
For the L3 module to run the new Cisco IOS image, you must reload the module. Make sure that
you have saved the configuration. Issue the copy run start command or the write memory to
save the configuration.
Example:
c-MSFC15# write memory
3d01h: %SYS-5-CONFIG_I: Configured from console by vty0 (127.0.0.11)
Building configuration...
c-MSFC15#
Issue the reload command to soft reset the L3 module, as this example shows:
Example:
c-MSFC15# reload
Proceed with reload? [confirm]
00:00:40: %SYS-5-RELOAD: Reload requested
System Bootstrap, Version 12.1(2r)E, RELEASE SOFTWARE (fc1)
Copyright (c) 20 0 0 by cisco Systems, Inc.
Cat6k-MSFC2 platform with 131072 Kbytes of main memory
Self decompressing the image :

Australia

Hong Kong

Malaysia

Singapore

India

Philippines

Document created by: Robert Pivac (13 Sep 2016)

Document updated by: Robert Pivac (13 Sep 2016)
The Netherlands USA
Brazil
Russia

TRT Global Limited

#########################################################
[OK]
%SYS-6-BOOT_MESSAGES: Messages above this line are from the boot loader.
Self decompressing the image :
##########################################################
######################### [OK]
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 95134-1706
Cisco Internetwork Operating System Software
IOS (tm) MSFC2 Software (C6MSFC2-JSV-M), Version 12.1(8a)E5, EARLY DEPLOYMENT RELEASE
SOFTWARE (fc2)
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Mon 22-Oct-01 21:51 by eaarmas
Image text-base: 0x40008980, data-base: 0x418D2000
cisco Cat6k-MSFC2 (R7000) processor with 114688K/16384K bytes of memory.
Processor board ID SAD042106RN
R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache
Last reset from power-on
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
509K bytes of non-volatile configuration memory.
16384K bytes of Flash internal SIMM (Sector size 512K).
Press RETURN to get started!
00:00:02: Currently running ROMMON from S (Gold) region
00:00:04: %SYS-5-CONFIG_I: Configured from memory by console
00:00:04: %SYS-5-RESTART: System restarted -Cisco Internetwork Operating System Software
IOS (tm) MSFC2 Software (C6MSFC2-JSV-M), Version 12.1(8a)E5, EARLY DEPLOYMENT RELEASE
SOFTWARE (fc2)
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Mon 22-Oct-01 21:51 by eaarmas
00:00:06: %SCP-5-ONLINE: Module online
00:00:09: %LINK-3-UPDOWN: Interface Vlan1, changed state to up
00:00:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
c-MSFC15>

Section V Verify the Upgrade

After the L3 module comes up, make sure that you run the new version of code. Issue the show
version command to check.

Australia

Hong Kong

Malaysia

Singapore

India

Philippines

Document created by: Robert Pivac (13 Sep 2016)

Document updated by: Robert Pivac (13 Sep 2016)
The Netherlands USA
Brazil
Russia

TRT Global Limited

Example:
c-MSFC15# show version
Cisco Internetwork Operating System Software
IOS (tm) MSFC2 Software (C6MSFC2-JSV-M), Version 12.1(8a)E5, EARLY
DEPLOYMENT RELEASE SOFTWARE (fc2)
!--- Note: Now the MSFC runs the new software image.
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Mon 22-Oct-01 21:51 by eaarmas
Image text-base: 0x40008980, data-base: 0x418D2000
ROM: System Bootstrap, Version 12.1(2r)E, RELEASE SOFTWARE (fc1)
BOOTFLASH: MSFC2 Software (C6MSFC2-BOOT-M), Version 12.1(6)E1, EARLY DEPLOYMENT
RELEASE
SOFTWARE (fc1)
c-MSFC15 uptime is 0 minutes
System returned to ROM by power-on
Running default software
cisco Cat6k-MSFC2 (R7000) processor with 114688K/16384K bytes of memory.
Processor board ID SAD042106RN
R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache
Last reset from power-on
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
4 Virtual Ethernet/IEEE 802.3 interface(s)
509K bytes of non-volatile configuration memory.
16384K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
c-MSFC15#
Verify that the version (12.1(8a)E5) is correct and that the config-register is set (0x2102).
The upgrade is complete.
Note: If you have dual MSFCs, you must download the image onto the second MSFC bootflash:
device. The image does not automatically download to the second MSFC. This requirement is
also applies to config-sync mode and Single Router Mode (SRM). In config-sync mode and SRM,
changes in the boot variables automatically propagate to the nondesignated or standby MSFC.
To copy an image from bootflash to the bootflash of a nondesignated or standby MSFC, issue
the copy bootflash:source_filename slavebootflash:target_filename command.
Boot the MSFC with CatOS Software from Flash PC
When you run Catalyst OS (CatOS) software on the Supervisor Engine, you can choose to boot
the MSFC from an image in the Supervisor Engine slot0 Flash PC Card slot. Your boot system
statement refers to the Flash device as sup-slot0. Although there is support for such a boot
process, avoid use of it. Use this boot process only as a temporary step, such as when you test
an image. Be aware of Cisco bug ID CSCdr35304
(registered customers only) .
You cannot issue commands such as the dir sup-slot0: command or the show supslot0: commands from the MSFC because the MSFC does not consider slot0 to be a local file
Australia

Hong Kong

Malaysia

Singapore

India

Philippines

Document created by: Robert Pivac (13 Sep 2016)

Document updated by: Robert Pivac (13 Sep 2016)
The Netherlands USA
Brazil
Russia

TRT Global Limited

system. If you specify sup-slot0 as the source of the operating system image, the switch transfers the
file through TFTP across the internal switching bus between the sc0 interface on the Supervisor
Engine and a special loopback IP address on the MSFC.
From the MSFC CLI, you can issue this command:
FIRE-MSFC1# copy tftp ?
bootflash:
Copy to bootflash: file system
ftp:
Copy to ftp: file system
microcode:
Copy to microcode: file system
null:
Copy to null: file system
nvram:
Copy to nvram: file system
rcp:
Copy to rcp: file system
running-config Update (merge with) current system configuration
slavenvram:
Copy to slavenvram: file system
startup-config Copy to startup configuration
sup-slot0:
Copy to sup-slot0: file system
system:
Copy to system: file system
tftp:
Copy to tftp: file system
The sup-slot0 device also appears in the show file systems command output:
FIRE-MSFC1# show file systems
File Systems:
Size(b)
Free(b)
Type Flags Prefixes
4395600
0 opaque
ro microcode:
- opaque
rw null:
- opaque
rw system:
- network
rw sup-slot0:
- network
rw tftp:
126968
124130
nvram
rw nvram:
* 15990784
2028888
flash
rw bootflash:
- network
rw rcp:
- network
rw ftp:
nvram
rw slavenvram:
Cat6500 (enable) show module
Mod Slot Ports Module-Type Model Sub Status
--- ---- ----- ------------------------- ------------------- --- -------1 1 2 1000BaseX Supervisor WS-X6K-SUP1A-2GE yes ok
Mod Module-Name Serial-Num
--- -------------------- ----------1 SAD040200B3
Cat6500 (enable) session 15
Module 15 is not installed.
This is sample command output from the show module command when the MSFC is in
the other state:
Cat6500 (enable) show module
Mod Slot Ports Module-Type Model Sub Status
--- ---- ----- ------------------------- ------------------- --- -------1 1 2 1000BaseX Supervisor WS-X6K-SUP1A-2GE yes ok
15 1 1 Multilayer Switch Feature WS-F6K-MSFC no other
Cat6500 (enable) session 15
Trying Router-15...

Australia

Hong Kong

Malaysia

Singapore

India

Philippines

Document created by: Robert Pivac (13 Sep 2016)

Document updated by: Robert Pivac (13 Sep 2016)
The Netherlands USA
Brazil
Russia

TRT Global Limited

!--- The session is not created. Press Ctrl-C to escape.

Link for reference: http://www.cisco.com/c/en/us/support/docs/switches/catalyst6500-series-switches/20685-129.html

Australia

Hong Kong

Malaysia

Singapore

India

Philippines

Document created by: Robert Pivac (13 Sep 2016)

Document updated by: Robert Pivac (13 Sep 2016)
The Netherlands USA
Brazil
Russia