Conversion on Supervisor Engine with MSFC1 - Revision history

Roberto at 07:17, 9 June 2010

2010-06-09T07:17:44Z

Roberto at 07:17, 9 June 2010

2010-06-09T07:17:11Z

Roberto at 07:15, 9 June 2010

2010-06-09T07:15:58Z

Roberto at 07:14, 9 June 2010

2010-06-09T07:14:58Z

Roberto at 07:14, 9 June 2010

2010-06-09T07:14:09Z

Roberto at 07:12, 9 June 2010

2010-06-09T07:12:39Z

Roberto at 07:10, 9 June 2010

2010-06-09T07:10:53Z

Roberto at 07:09, 9 June 2010

2010-06-09T07:09:25Z

Roberto at 07:09, 9 June 2010

2010-06-09T07:09:09Z

Roberto: New page: Step 1 Establish a console connection to the SP. Log your console session as a best practice. The log enables you to capture a record of the session and compare the log to the steps in t...

2010-06-09T07:07:20Z

New page: Step 1 Establish a console connection to the SP. Log your console session as a best practice. The log enables you to capture a record of the session and compare the log to the steps in t...

New page

Step 1

Establish a console connection to the SP.

Log your console session as a best practice. The log enables you to capture a record of the session and compare the log to the steps in this document, if you need to troubleshoot. For example, in Windows HyperTerminal, choose Transfer > Capture Text in order to log a console session. Refer to Connecting a Terminal to the Console Port on Catalyst Switches for more information.
Step 2

Back up the CatOS configuration from the Supervisor Engine and the Cisco IOS Software configuration from the MSFC1.

You need to reconfigure the switch after you convert to Cisco IOS Software as the system software because the conversion process loses the configuration. If you back up the files, they can serve as a reference after the conversion or as a backup if you decide to convert back to CatOS. Issue the copy config tftp command on the Supervisor Engine and the copy start tftp command on the MSFC1 in order to back up the configurations.

Refer to Managing Software Images and Working with Configuration Files on Catalyst Switches for more information on the use of the copy config tftp and copy start tftp commands to back up configuration files.
Step 3

Issue the show module command in order to confirm that the PFC and the MSFC1 are installed in the switch.

Note: You cannot run a Cisco IOS Software image (c6sup11*) without a PFC and an MSFC.

Console> (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 ok

!--- In this case, the SP in slot 1 is a Supervisor Engine 1A
!--- with an RP or MSFC1.

3 3 48 10/100BaseTX Ethernet WS-X6348-RJ-45 no ok
Mod Module-Name Serial-Num
--- -------------------- -----------
1 SAD040905LF
15 SAD040701C4
3 SAL0547ENL8
Mod MAC-Address(es) Hw Fw Sw
--- -------------------------------------- ------ ---------- -----------------
1 00-d0-bc-f7-75-96 to 00-d0-bc-f7-75-97 3.2 5.3(1) 8.1(1)

!--- This is the current CatOS software version that runs on the SP.

00-d0-bc-f7-75-94 to 00-d0-bc-f7-75-95
00-02-7e-02-a0-00 to 00-02-7e-02-a3-ff
15 00-d0-bc-f7-75-98 to 00-d0-bc-f7-75-d7 1.4 12.1(19)E1 12.1(19)E1a

!--- This is the current Cisco IOS Software release that runs on the RP.

3 00-05-74-0a-32-70 to 00-05-74-0a-32-9f 6.1 5.4(2) 8.1(1)
Mod Sub-Type Sub-Model Sub-Serial Sub-Hw Sub-Sw
--- ----------------------- ------------------- ----------- ------ ------
1 L3 Switching Engine WS-F6K-PFC SAD040906A9 1.0

!--- This is the PFC.

Console> (enable)

Step 4

Verify that the Cisco IOS Software image (c6sup11*) is available on the SP bootflash or on the PC card in slot0 of the Supervisor Engine module.

Note: Where you choose to store the Cisco IOS Software image (c6sup11*) depends on the Supervisor Engine flash device capacity and image size.

Issue the dir command in order to verify the location of the Cisco IOS Software image (c6sup11*).

Console> (enable) dir bootflash:
-#- -length- -----date/time------ name
1 10965886 Nov 02 2003 23:09:53 cat6000-supk8.8-1-1.bin

!--- This is the SP bootflash and the location for the current
!--- CatOS software version that runs on the SP.

5024768 bytes available (10966016 bytes used)
Console> (enable)

Console> (enable) dir slot0:
-#- -length- -----date/time------ name
1 17160908 Nov 03 2003 00 begin_of_the_skype_highlighting 03 2003 00 end_of_the_skype_highlighting:53:41 c6sup11-jsv-mz.121-19.E1a

!--- This is the PCMCIA or Flash PC device with the name slot0:.
!--- This is the Cisco IOS Software image (c6sup11*) release for this conversion.

7611572 bytes available (17161036 bytes used)
Console> (enable)

If the Cisco IOS Software image (c6sup*) is missing from either bootflash: or slot0:, download the image. Step 5 provides this procedure. If the image is present, go to Step 6.
Step 5 (Optional)

Note: Complete this step only if the Cisco IOS Software image (c6sup11*) is missing from either bootflash: or slot0:. See Step 4 in order to determine if you need to complete this step.

Issue the copy tftp bootflash: command or the copy tftp slot0: command in order to download the image to either the SP bootflash or to the PC card in slot0.

Note: You might need to format the PC cards if it has never been used before or if it was formatted with the Cisco IOS Software algorithm. Issue the format slot0: command or the format slot1: command or both commands in order to format PC cards on a Supervisor Engine 1, 1A or 2.

Note: You can free up space as necessary on the flash devices. Issue the delete bootflash: command or the delete slot0:filename command in order to delete the file. Then, issue the squeeze bootflash: command or the squeeze slot0: command in order to erase all deleted files from the device.

Console> (enable) copy tftp slot0:
IP address or name of remote host []? 10.1.1.2
Name of file to copy from []? c6sup11-jsv-mz.121-19.E1a
24772480 bytes available on device slot0, proceed (y/n) [n]? y
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
File has been copied successfully.
Console> (enable)

!--- Verify the image location.

Console> (enable) dir slot0:
-#- -length- -----date/time------ name
1 17160908 Nov 03 2003 00 begin_of_the_skype_highlighting 03 2003 00 end_of_the_skype_highlighting:53:41 c6sup11-jsv-mz.121-19.E1a
7611572 bytes available (17161036 bytes used)
Console> (enable)

Step 6

Issue either the switch console command or the session module command in order to access the RP.

Console> (enable) switch console
Trying Router-15...
Connected to Router-15.
Type ^C^C^C to switch back...
Router>

!--- Issue the enable command in order to enter privileged EXEC mode.

Router>enable
Router#

Step 7

Issue the dir bootflash: command in order to verify that the MSFC1 boot image is present on the RP bootflash.

A boot image for the MSFC1 (c6msfc-boot) is a requirement and must be in the RP bootflash.

Router#dir bootflash:
Directory of bootflash:/
1 -rw- 1879040 Nov 02 2003 22:29:32 c6msfc-boot-mz.121-19.E1a
15990784 bytes total (14111616 bytes free)
Router#

If the c6msfc-boot image is missing from the RP bootflash, download the image. Step 8 provides this procedure. If the image is present, go to Step 9.
Step 8 (Optional)

Note: Complete this step only if the c6msfc-boot image is missing from the RP bootflash. See Step 7 in order to determine if you need to complete this step.

Issue the copy tftp bootflash: command in order to download the image to the RP bootflash.

Note: You can free up space as necessary on the RP bootflash. Issue the delete bootflash:filename command in order to delete the file. Then, issue the squeeze bootflash: command in order to erase all deleted files from the device.

Router#copy tftp bootflash:
Address or name of remote host []? 10.1.1.2
Source filename []? c6msfc-boot-mz.121-19.E1a
Destination filename [c6msfc-boot-mz.121-19.E1a]?
Accessing tftp://10.1.1.2/c6msfc-boot-mz.121-19.E1a...
Loading c6msfc-boot-mz.121-19.E1a from 10.1.1.2 (via Vlan1): !!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 1879040 bytes]
1879040 bytes copied in 28.848 secs (65136 bytes/sec)
Verifying compressed IOS image checksum...
Verified compressed IOS image checksum for bootflash:/c6msfc-boot-mz.121-19.E1a
Router#

!--- Verify the image location.

Router#dir bootflash:
Directory of bootflash:/
1 -rw- 1879040 Nov 03 2003 01 begin_of_the_skype_highlighting 03 2003 01 end_of_the_skype_highlighting:36:45 c6msfc-boot-mz.121-19.E1a
15990784 bytes total (14111616 bytes free)
Router#

Step 9

Verify that the BOOTLDR variable statement points to the c6msfc-boot image in RP bootflash and that the configuration register is set to 0x2102. This setting tells the MSFC1 to boot automatically.

Issue the show bootvar command in order to check the BOOTLDR variable and configuration register settings.

Router#show bootvar
BOOT variable = sup-slot0:c6msfc-jsv-mz.121-19.E1a,1
CONFIG_FILE variable =
BOOTLDR variable = bootflash:c6msfc-boot-mz.121-19.E1a

!--- The BOOTLDR variable statement is set correctly for the MSFC1.

Configuration register is 0x2102

!--- The configuration register is set to 0x2102, which is correct.

Router#

If the BOOTLDR variable statement or the configuration register is not set correctly, complete Step 10 in order to change the setting. If both these settings are correct, go to Step 11.
Step 10 (Optional)

Note: Complete this step only if the BOOTLDR variable statement or the configuration register was not set correctly. See Step 9 in order to determine if you need to complete this step.

Issue these commands in order to set the BOOTLDR variable statement and change the configuration register setting:

!--- Verify the boot image name.

Router#dir bootflash:
Directory of bootflash:/
1 -rw- 1879040 Nov 03 2003 01 begin_of_the_skype_highlighting 03 2003 01 end_of_the_skype_highlighting:36:45 c6msfc-boot-mz.121-19.E1a
15990784 bytes total (14111616 bytes free)
Router#

!--- Set the BOOTLDR variable.

Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#boot bootldr bootflash:c6msfc-boot-mz.121-19.E1a

!--- Set the configuration register so that the MSFC1 boots automatically.

Router(config)#config-register 0x2102
Router(config)#end
Router#

!--- Save the changes.

Router#write memory
Building configuration...
[OK]

!--- Verify the BOOTLDR variable and configuration register settings.

Router#show bootvar
BOOT variable = sup-slot0:c6msfc-jsv-mz.121-19.E1a,1
CONFIG_FILE variable =
BOOTLDR variable = bootflash:c6msfc-boot-mz.121-19.E1a
Configuration register is 0x2102
Router#

Step 11

In order to go back to the SP, press Ctrl-C three times on the RP.

Note: If you issued the session module command in order to access the RP, you must issue the exit command instead of Ctrl-C.

!--- Press Ctrl-C three times.

Router#^C
Router#^C
Router#^C
Console> (enable)

!--- This is the SP console prompt.

Step 12

Change the configuration register setting on the SP so that the switch does not boot the CatOS image and goes to ROMmon.

Console> (enable) set boot config-register 0x0
Configuration register is 0x0
ignore-config: disabled
auto-config: non-recurring, overwrite, sync disabled
console baud: 9600
boot: the ROM monitor
Console> (enable)

Step 13

Reset the switch so that it goes into ROMmon.

Console> (enable) reset
This command will reset the system.
Do you want to continue (y/n) [n]? y
2003 Nov 03 02:00:26 %SYS-5-SYS_RESET:System reset from Console//
Powering OFF all existing linecards
Console> (enable) 2003 Nov 03 02:00:26 %SPANTREE-2-RX_1QNONTRUNK: Rcved 1Q-BPDU
on non-trunk port 3/1 vlan 1
2003 Nov 03 02:00:27 %ETHC-5-PORTFROMSTP:Port 3/1 left bridge port 3/1
System Bootstrap, Version 5.3(1)

!--- This is the SP ROMmon image version.

Copyright (c) 1994-1999 by cisco Systems, Inc.
c6k_sup1 processor with 131072 Kbytes of main memory

!--- After this message, the router goes into SP ROMmon.

Note: This document provides comments in blue italics in order to differentiate between the SP and RP ROMmon prompts.

rommon 1 >

!--- Note: This prompt is SP ROMmon.

Step 14

Issue the set command at the ROMmon prompt in order to check the environment variables.

Note: The switch is currently set to boot into the CatOS image.

rommon 1 > set

!--- Note: This prompt is SP ROMmon.
!--- Press Enter or Return.

PS1=rommon ! >
BOOTLDR=
SLOTCACHE=cards;
RET_2_RTS=22:54:02 UTC Sun Nov 2 2003
RET_2_RUTC=1067813642
?=0
CONFIG_FILE=bootflash:switch.cfg
BOOT=bootflash:cat6000-supk8.8-1-1.bin,1;
rommon 2

!--- Note: This prompt is SP ROMmon.

Cisco IOS Software does not use the CONFIG_FILE environment variable, so the variable can cause a problem. In order to avoid the problem, remove either bootflash:switch.cfg or slot0:switch.cfg from the environment settings. Issue these commands:

rommon 2 > CONFIG_FILE=

!--- Note: This prompt is SP ROMmon.
!--- The CONFIG_FILE statement is case sensitive and is all capital letters.

rommon 3 > BOOT=

!--- The BOOT statement is case sensitive and is all capital letters.

rommon 4 > confreg 0x2102

You must reset or power cycle for new config to take effect

!--- When you set the config register to 0x2102, the SP autoboots once
!--- the BOOT variable is set to the correct IOS image file name after it
!--- converts to Native IOS mode.

rommon 5 > sync

!--- Note: This prompt is SP ROMmon.
!--- The sync command writes the new environment variable setting to NVRAM.

rommon 6 > reset

!--- Note: This prompt is SP ROMmon.
!--- The reset command is necessary after you change any environment variable.

System Bootstrap, Version 5.3(1)
Copyright (c) 1994-1999 by cisco Systems, Inc.
c6k_sup1 processor with 131072 Kbytes of main memory

Autoboot: failed, BOOT string is empty
rommon 1 >

!--- Note: This prompt is SP ROMmon.
!--- You are still in SP ROMmon after the reset.

Step 15

Boot the switch with the Cisco IOS Software image (c6sup11*).

Issue either the dir bootflash: command or the dir slot0: command. The command you issue depends on the device to which you previously downloaded the Cisco IOS Software image. Then, issue the boot bootflash: command or the boot slot0:filename command in order to start the bootup sequence.

rommon 1 > dir slot0:

!--- Note: This prompt is SP ROMmon.

File size Checksum File name
17160908 bytes (0x105dacc) 0x283e970 c6sup11-jsv-mz.121-19.E1a

!--- The Cisco IOS Software image (c6sup11*) is on slot0: in this case.
!--- This is the device from which the image boots in this procedure.

rommon 2 > boot slot0:c6sup11-jsv-mz.121-19.E1a

!--- Note: This prompt is SP ROMmon.

Self decompressing the image : #################################################
################################################################################
################################################################################
################################################################################
################################################################################
############################### [OK]

!--- Output suppressed.

00:00:02: %PFREDUN-6-ACTIVE: Initializing as ACTIVE processor
00:00:05: %OIR-SP-6-CONSOLE: Changing console ownership to route processor
System Bootstrap, Version 12.0(3)XE, RELEASE SOFTWARE

!--- This is the RP ROMmon image release.

Copyright (c) 1998 by cisco Systems, Inc.
Cat6k-MSFC platform with 131072 Kbytes of main memory

Download Start
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
Download Completed! Booting the image.
Self decompressing the image : #################################################
#################################################################################
#################################################################################
#################################################################################
#################################################################################
#################################################################################
#################################################################################
#################################################################################
#################################################################################
#################################################################################
#################################################################################
#################################################################################
########################################## [OK]

!--- Output suppressed.

Press RETURN to get started!

!--- Output suppressed.

Router>

Step 16

At this point, the Cisco IOS Software image (c6sup11*) has successfully booted, but the Supervisor Engine Flash devices are still formatted with the previous CatOS algorithm. Therefore, Cisco IOS Software cannot correctly write to sup-bootflash: or slot0:. You need to reformat these Flash devices and replace the images that are on the Flash devices.

Issue the format command in order to format both the Supervisor Engine bootflash and slot0 Flash devices.

Router>enable
Router#format sup-bootflash:
Format operation may take a while. Continue? [confirm]

!--- Press Enter or Return.

Format operation will destroy all data in "sup-bootflash:". Continue? [confirm]

!--- Press Enter or Return.

Format of sup-bootflash complete
Router#

Router#format slot0:
Format operation may take a while. Continue? [confirm]

!--- Press Enter or Return.

Format operation will destroy all data in "slot0:". Continue? [confirm]

!--- Press Enter or Return.

Enter volume ID (up to 64 chars)[default slot0]:

!--- Press Enter or Return.

Format of slot0 complete
Router#

Step 17

When you format the Supervisor Engine Flash devices in Step 16, the Cisco IOS Software image (c6sup11*) used to boot the Supervisor Engine, as well as all data on the device, is erased. You need to recopy the Cisco IOS Software image (c6sup11*).

Note: Remember that the conversion lost the configuration. You need to configure an IP address and possibly static or dynamic routing in order to reestablish connectivity to your TFTP server. Verify that you can ping your TFTP server from the switch.

Issue the copy tftp command in order to copy the Cisco IOS Software image (c6sup11*) to either the sup-bootflash: or slot0: Flash device.

Router#copy tftp slot0:

!--- The Cisco IOS Software image (c6sup11*) copies to slot0: in this case.

Address or name of remote host []? 10.1.1.2
Source filename []? c6sup11-jsv-mz.121-19.E1a
Destination filename [c6sup11-jsv-mz.121-19.E1a]?
Accessing tftp://10.1.1.2/c6sup11-jsv-mz.121-19.E1a...
Loading c6sup11-jsv-mz.121-19.E1a from 10.1.1.2 (via FastEthernet3/1): !!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!--- Output suppressed.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 17160908 bytes]
17160908 bytes copied in 859.292 secs (19971 bytes/sec)
Verifying compressed IOS image checksum...
Verified compressed IOS image checksum for slot0:/c6sup11-jsv-mz.121-19.E1a
Router#

Step 18

Set the boot variable to boot from the Cisco IOS Software image (c6sup11*) in sup-bootflash: or slot0:.

!--- Check the current boot variable settings.

Router#show bootvar
BOOT variable = sup-slot0:c6msfc-jsv-mz.121-19.E1a,1

!--- The BOOT variable incorrectly points to an old MSFC image.

CONFIG_FILE variable =
BOOTLDR variable = bootflash:c6msfc-boot-mz.121-19.E1a
Configuration register is 0x2102
Standby is not up.
Router#

!--- Set the boot variable to boot the Cisco IOS Software image (c6sup11*).

Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#boot system flash slot0:c6sup11-jsv-mz.121-19.E1a
Router(config)#end
Router#

!--- Save the changes.

Router#write memory
Building configuration...
[OK]
Router#

Step 19

Verify if the configuration register is set to 0x2102. If not, modify the configuration register to the correct value of 0x2102.

Router#show bootvar
BOOT variable = slot0:c6sup11-jsv-mz.121-19.E1a,1
CONFIG_FILE variable =
BOOTLDR variable = bootflash:c6msfc-boot-mz.121-19.E1a
Configuration register is 0x2102
Standby is not up.
Router#

Step 20

Reload the switch.

Router#reload
Proceed with reload? [confirm]

!--- Output suppressed.

@@ Line 76: / Line 76: @@
      -#- -length- -----date/time------ name
 17160908 Nov
-begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00
+begin_of_the_skype_highlighting              03 2003 00 begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 begin_of_the_skype_highlighting              03 2003 00
 end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00
-end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00
      !--- This is the PCMCIA or Flash PC device with the name slot0:.

@@ Line 75: / Line 75: @@
      Console> (enable) dir slot0:
      -#- -length- -----date/time------ name
-17160908 Nov 03 2003 00 begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00
+17160908 Nov
 end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00
 end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00

@@ Line 75: / Line 75: @@
      Console> (enable) dir slot0:
      -#- -length- -----date/time------ name
-17160908 Nov 03 2003 00 begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting:53:41 c6sup11-jsv-mz.121-19.E1a
+17160908 Nov 03 2003 00 begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting:53:41 c6sup11-jsv-mz.121-19.E1a
      !--- This is the PCMCIA or Flash PC device with the name slot0:.
@@ Line 177: / Line 177: @@
      15990784 bytes total (14111616 bytes free)
      Router#
 '''
-Step 9'''
+'''Step 9'''
 Verify that the BOOTLDR variable statement points to the c6msfc-boot image in RP bootflash and that the configuration register is set to 0x2102. This setting tells the MSFC1 to boot automatically.
@@ Line 197: / Line 197: @@
      Router#
-If the BOOTLDR variable statement or the configuration register is not set correctly, complete Step 10 in order to change the setting. If both these settings are correct, go to Step 11.
+If the BOOTLDR variable statement or the configuration register is not set correctly, complete Step 10 in order to change the setting. If both these settings are correct, go to Step '''Step 11''' .
 '''Step 10''' (Optional)
@@ Line 267: / Line 267: @@
      boot: the ROM monitor
      Console> (enable)
 '''
-Step 13'''
+'''Step 13'''
 Reset the switch so that it goes into ROMmon.
@@ Line 294: / Line 294: @@
      !--- Note: This prompt is SP ROMmon.
 '''
-Step 14'''
+'''Step 14'''
 Issue the set command at the ROMmon prompt in order to check the environment variables.
@@ Line 358: / Line 358: @@
      !--- Note: This prompt is SP ROMmon.
      !--- You are still in SP ROMmon after the reset.
 '''
-Step 15'''
+'''Step 15'''
 Boot the switch with the Cisco IOS Software image (c6sup11*).

@@ Line 4: / Line 4: @@
 Log your console session as a best practice. The log enables you to capture a record of the session and compare the log to the steps in this document, if you need to troubleshoot. For example, in Windows HyperTerminal, choose Transfer > Capture Text in order to log a console session. Refer to Connecting a Terminal to the Console Port on Catalyst Switches for more information.
 '''Step 2'''
@@ Line 11: / Line 12: @@
 Refer to Managing Software Images and Working with Configuration Files on Catalyst Switches for more information on the use of the copy config tftp and copy start tftp commands to back up configuration files.
 '''Step 3'''
@@ Line 73: / Line 75: @@
      Console> (enable) dir slot0:
      -#- -length- -----date/time------ name
-17160908 Nov 03 2003 00 begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting:53:41 c6sup11-jsv-mz.121-19.E1a
+17160908 Nov 03 2003 00 begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting:53:41 c6sup11-jsv-mz.121-19.E1a
      !--- This is the PCMCIA or Flash PC device with the name slot0:.

@@ Line 1: / Line 1: @@
-Step 1
+'''Step 1'''
 Establish a console connection to the SP.
 Log your console session as a best practice. The log enables you to capture a record of the session and compare the log to the steps in this document, if you need to troubleshoot. For example, in Windows HyperTerminal, choose Transfer > Capture Text in order to log a console session. Refer to Connecting a Terminal to the Console Port on Catalyst Switches for more information.
-Step 2
+'''Step 2'''
 Back up the CatOS configuration from the Supervisor Engine and the Cisco IOS Software configuration from the MSFC1.
@@ Line 11: / Line 11: @@
 Refer to Managing Software Images and Working with Configuration Files on Catalyst Switches for more information on the use of the copy config tftp and copy start tftp commands to back up configuration files.
-Step 3
+'''Step 3'''
 Issue the show module command in order to confirm that the PFC and the MSFC1 are installed in the switch.
@@ Line 53: / Line 53: @@
      Console> (enable)
-Step 4
+'''Step 4'''
 Verify that the Cisco IOS Software image (c6sup11*) is available on the SP bootflash or on the PC card in slot0 of the Supervisor Engine module.
@@ Line 73: / Line 73: @@
      Console> (enable) dir slot0:
      -#- -length- -----date/time------ name
-17160908 Nov 03 2003 00 begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting:53:41 c6sup11-jsv-mz.121-19.E1a
+17160908 Nov 03 2003 00 begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting:53:41 c6sup11-jsv-mz.121-19.E1a
      !--- This is the PCMCIA or Flash PC device with the name slot0:.
@@ Line 82: / Line 82: @@
 If the Cisco IOS Software image (c6sup*) is missing from either bootflash: or slot0:, download the image. Step 5 provides this procedure. If the image is present, go to Step 6.
-Step 5 (Optional)
+'''Step 5''' (Optional)
 Note: Complete this step only if the Cisco IOS Software image (c6sup11*) is missing from either bootflash: or slot0:. See Step 4 in order to determine if you need to complete this step.
@@ Line 110: / Line 110: @@
      Console> (enable) dir slot0:
      -#- -length- -----date/time------ name
-17160908 Nov 03 2003 00 begin_of_the_skype_highlighting              03 2003 00      end_of_the_skype_highlighting:53:41 c6sup11-jsv-mz.121-19.E1a
+17160908 Nov 03 2003 00 begin_of_the_skype_highlighting              03 2003 00
      7611572 bytes available (17161036 bytes used)
      Console> (enable)
+'''
-Step 6
+Step 6'''
 Issue either the switch console command or the session module command in order to access the RP.
@@ Line 129: / Line 130: @@
      Router#
-Step 7
+'''Step 7'''
 Issue the dir bootflash: command in order to verify that the MSFC1 boot image is present on the RP bootflash.
@@ Line 142: / Line 143: @@
 If the c6msfc-boot image is missing from the RP bootflash, download the image. Step 8 provides this procedure. If the image is present, go to Step 9.
-Step 8 (Optional)
+'''Step 8''' (Optional)
 Note: Complete this step only if the c6msfc-boot image is missing from the RP bootflash. See Step 7 in order to determine if you need to complete this step.
@@ Line 174: / Line 175: @@
      15990784 bytes total (14111616 bytes free)
      Router#
+'''
-Step 9
+Step 9'''
 Verify that the BOOTLDR variable statement points to the c6msfc-boot image in RP bootflash and that the configuration register is set to 0x2102. This setting tells the MSFC1 to boot automatically.
@@ Line 195: / Line 196: @@
 If the BOOTLDR variable statement or the configuration register is not set correctly, complete Step 10 in order to change the setting. If both these settings are correct, go to Step 11.
-Step 10 (Optional)
+'''Step 10''' (Optional)
 Note: Complete this step only if the BOOTLDR variable statement or the configuration register was not set correctly. See Step 9 in order to determine if you need to complete this step.
@@ Line 237: / Line 238: @@
      Router#
-Step 11
+'''Step 11'''
 In order to go back to the SP, press Ctrl-C three times on the RP.
@@ Line 253: / Line 254: @@
      !--- This is the SP console prompt.
-Step 12
+'''Step 12'''
 Change the configuration register setting on the SP so that the switch does not boot the CatOS image and goes to ROMmon.
@@ Line 264: / Line 265: @@
      boot: the ROM monitor
      Console> (enable)
+'''
-Step 13
+Step 13'''
 Reset the switch so that it goes into ROMmon.
@@ Line 291: / Line 292: @@
      !--- Note: This prompt is SP ROMmon.
+'''
-Step 14
+Step 14'''
 Issue the set command at the ROMmon prompt in order to check the environment variables.
@@ Line 355: / Line 356: @@
      !--- Note: This prompt is SP ROMmon.
      !--- You are still in SP ROMmon after the reset.
+'''
-Step 15
+Step 15'''
 Boot the switch with the Cisco IOS Software image (c6sup11*).
@@ Line 430: / Line 431: @@
      Router>
-Step 16
+'''Step 16'''
 At this point, the Cisco IOS Software image (c6sup11*) has successfully booted, but the Supervisor Engine Flash devices are still formatted with the previous CatOS algorithm. Therefore, Cisco IOS Software cannot correctly write to sup-bootflash: or slot0:. You need to reformat these Flash devices and replace the images that are on the Flash devices.
@@ Line 466: / Line 467: @@
      Router#
-Step 17
+'''Step 17'''
 When you format the Supervisor Engine Flash devices in Step 16, the Cisco IOS Software image (c6sup11*) used to boot the Supervisor Engine, as well as all data on the device, is erased. You need to recopy the Cisco IOS Software image (c6sup11*).
@@ Line 498: / Line 499: @@
      Router#
-Step 18
+'''Step 18'''
 Set the boot variable to boot from the Cisco IOS Software image (c6sup11*) in sup-bootflash: or slot0:.
@@ Line 531: / Line 532: @@
      Router#
-Step 19
+'''Step 19'''
 Verify if the configuration register is set to 0x2102. If not, modify the configuration register to the correct value of 0x2102.
@@ Line 543: / Line 544: @@
      Router#
-Step 20
+'''Step 20'''
 Reload the switch.