Native IOS for catalyst6009

Answered Question
Sep 25th, 2007

I need to upgrade a catalyst6009 running Native IOS.

The IOS I need is c6sup12-psv-mz.121-26.E9.bin that requires 20MB of flash.

I interpret the info below this such that I have

flash: 24MB

sup-bootflash: 16MB

bootflash: 16MB

QUESTION. Can I place the boot image on all 3 types of flash (as long as there is room for it).

In this case can I use the the 24MB flash: and then use the config cmd boot system flash:c6sup12-psv-mz.121-26.E9.bin

If you know a link where the cisco explain this architure it would be much appriciated.

----------------------------------------- INFO

-----------------------------------------gwdibb1#sh flash

-#- ED ----type---- --crc--- -seek-- nlen -length- -----date/time------ name

1 .. image 0B08E86D DB4938 29 14239928 Aug 19 2002 08:57:22 c6sup12-psv-mz.121-11b.E1.bin

10532552 bytes available (14240056 bytes used)

gwdibb1#sh sup-bootflash:

-#- ED ----type---- --crc--- -seek-- nlen -length- -----date/time------ name

1 .. image 1BA2ABE9 F728F0 29 15935600 Nov 03 2004 18:04:09 c6sup12-psv-mz.121-13.E12.bin

55056 bytes available (15935728 bytes used)

gwdibb1#sh bootflash:

-#- ED ----type---- --crc--- -seek-- nlen -length- -----date/time------ name

1 .. image 7134F837 21BDC8 25 1686856 Nov 30 2001 23:33:29 c6msfc2-boot-mz.121-8a.E3

2 .. crashinfo CC2D1602 2486F4 25 182444 May 17 2002 15:26:43 crashinfo_20020517-152643

3 .. crashinfo 244F441D 27484C 25 180438 May 23 2002 11:09:01 crashinfo_20020523-110901

4 .. crashinfo 2713FE72 29F9CC 25 176381 Jun 03 2002 11:38:13 crashinfo_20020603-113813

5 .. crashinfo 697AF640 2CA684 25 175160 Aug 06 2002 08:56:54 crashinfo_20020806-085654

6 .. crashinfo 276C7229 2F3B40 25 169019 Aug 06 2002 09:07:17 crashinfo_20020806-090717

7 .. crashinfo D0842495 31AB00 25 159551 Aug 07 2002 11:20:25 crashinfo_20020807-112025

12473600 bytes available (2730752 bytes used)

I have this problem too.
0 votes
Correct Answer by ankbhasi about 9 years 2 months ago

Hi Simon,

Thanks for your comments. The difference between the 2 commands is one is executed on router which is "sh bootvar" and other is executed on sup engine which is "remote command"

When you run native ios it is a bundled image which controls both sup and msfc but it has a single console access which is a router prompt. Image is controlled by both sup and router and because you always have an access of router prompt with native image you have to issue remote command to check boot valiable settings on supervisor.

HTH

Ankur

*Pls rate all helpfull post

Correct Answer by ankbhasi about 9 years 2 months ago

Hi Simon,

MSFC has a boot image which you do not need to upgrade as the new Native IOS image which you are upgrading has an in built bundle for boot image. You can leave the boot image on MSFC as it is.

HTH

Ankur

*Pls rate all helpfull post

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
ankbhasi Tue, 09/25/2007 - 02:24

Hi Simon,

When you run Native IOS on your box (sup 2)image is always stored either on pcmcia card or bootflash of supervisor engine.

So as you have you bootflash of 16 MB which is a flash on MSFC , image cannot and should not be stored on that. Now your sup-bootflash is also 16MB so new image will not fit ino that also.

Only option left with you is to store it on pcmcia card. I believe you are referring flash as slot0/pcmcia card so you can store it on the same and point your bootpath to boot from slot0:

http://www.cisco.com/warp/public/473/161.html

Please come back if you have any doubts.

HTH

Ankur

*Pls rate all helpfull post

simonvyrdal Tue, 09/25/2007 - 03:51

Hi Ankur

Yes apparently the external flash (pcmcia card) can be referred to by slot0: flash: sup-slot0:

So just to recapitulate

1. the native IOS must boot on either sup-bootflash or ecternal media in this case slot0:

2. also bootflash: resides on the MSFC2 card and cannot be used to store native IOS.

In conclusion I should be fine if I

1. store c6sup12-psv-mz.121-26.E9.bin on slot0:

2. configure the IOS command boot system slot0:c6sup12-psv-mz.121-26.E9.bin

THANKS

Simon

gwdibb1#sh file systems

File Systems:

Size(b) Free(b) Type Flags Prefixes

* 24772608 10532552 flash rw slot0: flash: sup-slot0:

15990784 55056 flash rw sup-bootflash:

15444864 0 opaque ro sup-microcode:

- - opaque wo sup-image:

129004 126544 nvram rw const_nvram:

- - opaque rw null:

- - opaque rw system:

- - network rw tftp:

391160 370993 nvram rw nvram:

15204352 12473600 flash rw bootflash:

- - network rw rcp:

- - network rw ftp:

ankbhasi Tue, 09/25/2007 - 03:53

Hi Simon,

Exactly and you got it very right. Just a small change in your boot command and it should be like

boot system flash slot0:c6sup12-psv-mz.121-26.E9.bin

HTH

Ankur

*Pls rate all helpfull post

simonvyrdal Tue, 09/25/2007 - 04:11

Hi Ankur

Thanks for the correction of the boot system cmd. It is appriciated.

One last question. Do I need to upgrade the msfc2 image as well, or can I just keep this ?

gwdibb1#sh bootflash:

-#- ED ----type---- --crc--- -seek-- nlen -length- -----date/time------ name

1 .. image 7134F837 21BDC8 25 1686856 Nov 30 2001 23:33:29 c6msfc2-boot-mz.121-8a.E3

Thanks

Simon

Correct Answer
ankbhasi Tue, 09/25/2007 - 04:14

Hi Simon,

MSFC has a boot image which you do not need to upgrade as the new Native IOS image which you are upgrading has an in built bundle for boot image. You can leave the boot image on MSFC as it is.

HTH

Ankur

*Pls rate all helpfull post

simonvyrdal Sun, 09/30/2007 - 08:32

Hi Ankur

Can I take this case up you again ? I did not succeed to boot the catalyst 6000 from c6sup12-psv-mz.121-26.E9.bin.

The information below shows how the cat6000 is configured. Do you have any idea why it boot on the image in sup-bootflash and not slot0: ??

Your help is much appriciated. If you want i can oppen a new post.

Technical info:

Info from cisco's software upgrade planner.

File name Min. Memory(MB) Min. Flash(MB) Date Released

c6sup12-psv-mz.121-26.E9.bin 64 20 17-AUG-2007

My config (sh bootvar showed that it would select slot0: as first choice, then sup-bootflash:)

boot system flash slot0:c6sup12-psv-mz.121-26.E9.bin

boot system flash sup-bootflash:c6sup12-psv-mz.121-8a.E3

gwdibb1#sh sup-bootflash:

-#- ED ----type---- --crc--- -seek-- nlen -length- -----date/time------ name

1 .. image 1BA2ABE9 F728F0 29 15935600 Nov 03 2004 18:04:09 c6sup12-psv-mz.121-13.E12.bin

55056 bytes available (15935728 bytes used)

gwdibb1#sh slot0:

-#- ED ----type---- --crc--- -seek-- nlen -length- -----date/time------ name

1 .. image 34CABC53 10599BC 28 17013052 Sep 26 2007 06:24:36 c6sup12-psv-mz.121-26.E9.bin

7759428 bytes available (17013180 bytes used)

gwdibb1#

gwdibb1#sh ver

Cisco Internetwork Operating System Software

IOS (tm) c6sup2_rp Software (c6sup2_rp-PSV-M), Version 12.1(13)E12, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)

TAC Support: http://www.cisco.com/tac

Copyright (c) 1986-2003 by cisco Systems, Inc.

Compiled Sat 22-Nov-03 06:29 by hqluong

Image text-base: 0x40008C00, data-base: 0x417A0000

ROM: System Bootstrap, Version 12.1(4r)E, RELEASE SOFTWARE (fc1)

BOOTLDR: c6sup2_rp Software (c6sup2_rp-PSV-M), Version 12.1(13)E12, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)

gwdibb1 uptime is 1 day, 5 hours, 21 minutes

Time since gwdibb1 switched to active is 1 day, 5 hours, 21 minutes

System returned to ROM by power-on (SP by reload)

System restarted at 12:57:08 Sommartid Sat Sep 29 2007

System image file is "sup-bootflash:c6sup12-psv-mz.121-13.E12.bin"

cisco Catalyst 6000 (R7000) processor with 112640K/18432K bytes of memory.

Processor board ID SAL0541D53L

R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache

Last reset from power-on

X.25 software, Version 3.0.0.

Bridging software.

32 Virtual Ethernet/IEEE 802.3 interface(s)

42 Gigabit Ethernet/IEEE 802.3 interface(s)

381K bytes of non-volatile configuration memory.

16384K bytes of Flash internal SIMM (Sector size 512K).

Configuration register is 0x2102

gwdibb1#sh mod

Mod Ports Card Type Model Serial No.

--- ----- -------------------------------------- ------------------ -----------

1 2 Cat 6k sup 1 Enhanced QoS (Active) WS-X6K-SUP1A-2GE SAL0542DDTQ

2 16 16 port 1000mb GBIC ethernet WS-X6416-GBIC SAL0543DRMW

3 16 SFM-capable 16 port 1000mb GBIC WS-X6516-GBIC SAL06355AY8

4 8 8 port 1000mb GBIC Enhanced QoS WS-X6408A-GBIC SAL050632RE

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------

1 0006.d659.deec to 0006.d659.deed 7.1 5.4(2) 7.5(0.6)HUB1 Ok

2 0007.4f6d.bcc0 to 0007.4f6d.bccf 1.0 5.4(2) 7.5(0.6)HUB1 Ok

3 0009.11e5.28c4 to 0009.11e5.28d3 5.1 6.3(1) 7.5(0.6)HUB1 Ok

4 0002.fc44.ac90 to 0002.fc44.ac97 1.3 5.4(2) 7.5(0.6)HUB1 Ok

Mod Sub-Module Model Serial Hw Status

--- --------------------------- --------------- --------------- ------- -------

1 Policy Feature Card WS-F6K-PFC SAL0541D4GQ 1.1 Ok

1 Cat6k MSFC 2 daughterboard WS-F6K-MSFC2 SAL0541D53L 1.2 Ok

gwdibb1#

ankbhasi Sun, 09/30/2007 - 09:02

Hi Simon,

Can you post the output of "remote command switch show boot" and "remote command switch show version"?

Regards,

Ankur

simonvyrdal Mon, 10/01/2007 - 07:02

Hi Ankur, Regards Simon

gwdibb1#remote command switch show bootvar

gwdibb1-sp#

BOOT variable = bootflash:c6sup12-psv-mz.121-13.E12.bin,1

CONFIG_FILE variable =

BOOTLDR variable =

Configuration register is 0x2021

gwdibb1#remote command switch show version

gwdibb1-sp#

Cisco Internetwork Operating System Software

IOS (tm) c6sup1_sp Software (c6sup1_sp-SPV-M), Version 12.1(13)E12, EARLY DEPLOYMENT RELEASE SOFTWAR

E (fc1)

TAC Support: http://www.cisco.com/tac

Copyright (c) 1986-2003 by cisco Systems, Inc.

Compiled Sat 22-Nov-03 07:02 by hqluong

Image text-base: 0x60020BD8, data-base: 0x607BE000

ROM: System Bootstrap, Version 5.3(1)

BOOTLDR: c6sup1_sp Software (c6sup1_sp-SPV-M), Version 12.1(13)E12, EARLY DEPLOYMENT RELEASE SOFTWAR

E (fc1)

gwdibb1 uptime is 2 days, 3 hours, 55 minutes

Time since gwdibb1 switched to active is 2 days, 3 hours, 55 minutes

System returned to ROM by reload at 12:56:05 Sommart Sat Sep 29 2007

System image file is "bootflash:c6sup12-psv-mz.121-13.E12.bin"

cisco 6000 (NMP150) processor with 49152K/16384K bytes of memory.

R4700 CPU at 150Mhz, Implementation 33, Rev 1.0, 512KB L2 Cache

Last reset from power-on

X.25 software, Version 3.0.0.

42 Gigabit Ethernet/IEEE 802.3 interface(s)

381K bytes of non-volatile configuration memory.

24576K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).

16384K bytes of Flash internal SIMM (Sector size 256K).

Configuration register is 0x2021

gwdibb1#

ankbhasi Mon, 10/01/2007 - 07:16

Hi Simon,

The problem is with teh config register value which is defined on sup engine. If you see the config register value is set to 0x2021 where last number which is 1 defines the boot feild and 1 means "Boots the first system image in onboard Flash memory" and that is the reason your switch is always booting form the old image available on you rbootflash because that in onboard Flash.

Now if you change the config register value to 0x2102 where last number 2 enables boot system commands.

So I will recommend you to issue a command on your router config prompt

gwdibb1(config)#config-register 0x2102

gwdibb1(config)#wr mem

and then reload the switch and it should boot from the new image.

HTH

Ankur

*Pls rate all helpfull post

simonvyrdal Mon, 10/01/2007 - 07:52

Hi Ankur

Your help is outstanding !!

Will you pls explain the difference between

sh bootvar and remote command switch show bootvar

sh version and remote command switch show version

now it looks more correct

gwdibb1#remote command switch show bootvar

gwdibb1-sp#

BOOT variable = bootflash:c6sup12-psv-mz.121-13.E12.bin,1

CONFIG_FILE variable =

BOOTLDR variable =

Configuration register is 0x2021 (will be 0x2102 at next reload)

gwdibb1#

But why can i not rely on sh ver and sh bootvar ??

Correct Answer
ankbhasi Mon, 10/01/2007 - 07:59

Hi Simon,

Thanks for your comments. The difference between the 2 commands is one is executed on router which is "sh bootvar" and other is executed on sup engine which is "remote command"

When you run native ios it is a bundled image which controls both sup and msfc but it has a single console access which is a router prompt. Image is controlled by both sup and router and because you always have an access of router prompt with native image you have to issue remote command to check boot valiable settings on supervisor.

HTH

Ankur

*Pls rate all helpfull post

simonvyrdal Mon, 10/01/2007 - 10:43

Hi Ankur.

The cat6000 still boot on sup-bootflash.

To me it seems like the parameters we discussed earlier today is what we agreed on. In fact I got 2 cat6000 and they behave exactly the same.

Great if you still want to help me. Thanks Simon.

gwdibb1#remote command switch sh bootvar

gwdibb1-sp#

BOOT variable = slot0:c6sup12-psv-mz.121-26.E9.bin,1;bootflash:c6sup12-psv-mz.121-13.E12.bin,1

CONFIG_FILE variable =

BOOTLDR variable =

Configuration register is 0x2102

gwdibb1#sh slot0

-#- ED ----type---- --crc--- -seek-- nlen -length- -----date/time------ name

1 .. image 34CABC53 10599BC 28 17013052 Sep 26 2007 06:24:36 c6sup12-psv-mz.121-26.E9.bin

7759428 bytes available (17013180 bytes used)

gwdibb1#sh sup-bootflash:

-#- ED ----type---- --crc--- -seek-- nlen -length- -----date/time------ name

1 .. image 1BA2ABE9 F728F0 29 15935600 Nov 03 2004 18:04:09 c6sup12-psv-mz.121-13.E12.bin

55056 bytes available (15935728 bytes used)

gwdibb1#sh ver

Cisco Internetwork Operating System Software

IOS (tm) c6sup2_rp Software (c6sup2_rp-PSV-M), Version 12.1(13)E12, EARLY DEPLOYMENT RELEASE SOFTWAR

E (fc1)

TAC Support: http://www.cisco.com/tac

Copyright (c) 1986-2003 by cisco Systems, Inc.

Compiled Sat 22-Nov-03 06:29 by hqluong

Image text-base: 0x40008C00, data-base: 0x417A0000

ROM: System Bootstrap, Version 12.1(4r)E, RELEASE SOFTWARE (fc1)

BOOTLDR: c6sup2_rp Software (c6sup2_rp-PSV-M), Version 12.1(13)E12, EARLY DEPLOYMENT RELEASE SOFTWAR

E (fc1)

gwdibb1 uptime is 9 minutes

Time since gwdibb1 switched to active is 9 minutes

System returned to ROM by power-on (SP by reload)

System restarted at 20:23:21 Sommartid Mon Oct 1 2007

System image file is "sup-bootflash:c6sup12-psv-mz.121-13.E12.bin"

cisco Catalyst 6000 (R7000) processor with 112640K/18432K bytes of memory.

Processor board ID SAL0541D53L

R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache

Last reset from power-on

X.25 software, Version 3.0.0.

Bridging software.

36 Virtual Ethernet/IEEE 802.3 interface(s)

42 Gigabit Ethernet/IEEE 802.3 interface(s)

381K bytes of non-volatile configuration memory.

16384K bytes of Flash internal SIMM (Sector size 512K).

Configuration register is 0x2102

gwdibb1#

ankbhasi Tue, 10/02/2007 - 07:03

Hi Simon,

Looking at the data posted it should have booted by image in slot0: not sure why it is still taking image in sup-bootflash.

Can you give a try upgrading boot image also on msfc to 121-26.E9 and set the boot path for boot image using a command

"qwdibb1(config)#boot bootldr bootflash:" and see if that works.

But before upgarding the boot image can you remove the old boot statement and reload the router to see if it boots from new image in slot0:

Will wait for your updates!!

HTH

Ankur

simonvyrdal Tue, 10/02/2007 - 10:34

Hi Ankur.

Unfortunately I need a timeslot to boot again. It is a switch in production. I will see when I can reload again (if I can)

1. Is it correct understood that the first thing you want me to do is

no boot system flash slot0:c6sup12-psv-mz.121-26.E9.bin

no boot system flash sup-bootflash:c6sup12-psv-mz.121-13.E12.bin

and then reload.

2. By a closer look I noticed this. It seems strange that the remote command shows bootflash:c6sup12-psv-mz.121-13.E12.bin,1 as the second option ??

this image is in sup-bootflash.

gwdibb1#remote command switch sh bootvar

gwdibb1-sp#

BOOT variable = slot0:c6sup12-psv-mz.121-26.E9.bin,1;bootflash:c6sup12-psv-mz.121-13.E12.bin,1

CONFIG_FILE variable =

BOOTLDR variable =

Configuration register is 0x2102

gwdibb1#sh bootvar

BOOT variable = slot0:c6sup12-psv-mz.121-26.E9.bin,1;sup-bootflash:c6sup12-psv-mz.121-13.E12.bin,1

CONFIG_FILE variable does not exist

BOOTLDR variable does not exist

Configuration register is 0x2102

3. Catalyst 6500 Series Cisco IOS Command Reference, 12.1 E

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.1E/native/command/reference/chap2a.html

The 12.1 E reference does not include the boot system command. Is it supported ??

Regards

Simon

ankbhasi Tue, 10/02/2007 - 21:28

Hi Simon,

No do not remove both boot statements. Just remove second one which is "no boot system flash sup-bootflash:c6sup12-psv-mz.121-13.E12.bin"

It should show you as the second option because you set the boot path to boot with new image which gets updates for sup also.

Boot statement commands are supported.

HTH

Ankur

simonvyrdal Wed, 10/03/2007 - 00:18

Hi Ankur

I removed boot system flash sup-bootflash:c6sup12-psv-mz.121-13.E12.bin, then the status looks like below.

Will the cat6000 come up on sup-bootflash: if it fails on slot0: ?

gwdibb1#sh run | incl boot sys

boot system flash slot0:c6sup12-psv-mz.121-26.E9.bin

gwdibb1#sh bootvar

BOOT variable = slot0:c6sup12-psv-mz.121-26.E9.bin,1

CONFIG_FILE variable does not exist

BOOTLDR variable does not exist

Configuration register is 0x2102

gwdibb1#remote command switch sh bootvar

gwdibb1-sp#

BOOT variable = slot0:c6sup12-psv-mz.121-26.E9.bin,1

CONFIG_FILE variable =

BOOTLDR variable =

Configuration register is 0x2102

Regards

Simon

ankbhasi Wed, 10/03/2007 - 00:35

Hi Simon,

I believe it should boot from slot0: now and incase not it will boot from available image on sup-bootflash: but incase if something wrong goes and you find your self in rommon just issue manually boot and it should boot again. Do it when you are in maintainence window.

Best of Luck!!

Ankur

simonvyrdal Thu, 06/12/2008 - 02:51

Hi Ankur.

This conversation was long time ago, when I had trouble booting on slot0. I had to upgrade again and loaded a new image into slot0. I worked well - so I believe that the old image in slot0 was currupted. This time I used verify /md5 to be sure. Thanks for your help.

best regards

Simon

Actions

This Discussion