cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1374
Views
0
Helpful
18
Replies

Native IOS for catalyst6009

simonvyrdal
Level 1
Level 1

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)

18 Replies 18

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

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

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

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

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: