Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

6509 IOS upgrade

Hi all,

Over the weekend I tried upgrading our 6509's IOS. I followed what I thought were the correct procedures from the cisco doco but had an error.

When reloading this error occurred:

Autoboot executing command: "boot bootflash:c6sup22-jk2sv-mz.121-27b.E.bin"

open(): Open Error = -9

loadprog: error - on file open

boot: cannot load "bootflash:c6sup22-jk2sv-mz.121-27b.E.bin"

System Bootstrap, Version 7.1(1)

Copyright (c) 1994-2001 by cisco Systems, Inc.

c6k_sup2 processor with 524288 Kbytes of main memory

Autoboot executing command: "boot bootflash:c6sup22-jk2sv-mz.121-26.E1.bin"

Because I left the previous IOS in bootflash after the error the previous version booted.

Basically I setup:

"boot system" to boot the new IOS

copied the new IOS to bootsystem:

reloading the switch

Am I missing something here, I can't work out why the new IOS says file open error?

thanks for any assistance, points given for help.

-----

Xxxxx#sh ver

Cisco Internetwork Operating System Software

IOS (tm) c6sup2_rp Software (c6sup2_rp-JK2SV-M), Version 12.1(26)E1, RELEASE SOF

TWARE (fc2)

Technical Support: http://www.cisco.com/techsupport

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

Compiled Tue 22-Mar-05 00:33 by ccai

Image text-base: 0x40008F90, data-base: 0x41D02000

ROM: System Bootstrap, Version 12.1(11r)E1, RELEASE SOFTWARE (fc1)

BOOTLDR: c6sup2_rp Software (c6sup2_rp-JK2SV-M), Version 12.1(26)E1, RELEASE SOF

TWARE (fc2)

xxxx uptime is 2 days, 1 hour, 1 minute

Time since XXXX switched to active is 2 days, 1 hour, 0 minutes

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

System restarted at 21:34:20 EST Sat Dec 30 2006

System image file is "sup-bootflash:c6sup22-jk2sv-mz.121-26.E1.bin"

This product contains cryptographic features and is subject to United

States and local country laws governing import, export, transfer and

use. Delivery of Cisco cryptographic products does not imply

third-party authority to import, export, distribute or use encryption.

Importers, exporters, distributors and users are responsible for

compliance with U.S. and local country laws. By using this product you

agree to comply with applicable laws and regulations. If you are unable

to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:

http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to

export@cisco.com.

cisco WS-C6509 (R7000) processor (revision 3.0) with 458752K/65536K bytes of mem

ory.

Processor board ID TBP07040004

R7000 CPU at 300Mhz, Implementation 39, Rev 3.3, 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.

100 Virtual Ethernet/IEEE 802.3 interface(s)

184 Gigabit Ethernet/IEEE 802.3 interface(s)

381K bytes of non-volatile configuration memory.

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

Configuration register is 0x2102

1 ACCEPTED SOLUTION

Accepted Solutions

Re: 6509 IOS upgrade

Where is the file located SP bootflash or RP bootflash. I think the problem that you have is that the file is copied to the RP bootflash and it is booting from there. Make sure that you have the correct file located in the SP bootflash and you boot the switch from there using the " boot sup-bootflash:

I see that you are using the "boot bootflash: " command, which will eventually try to boot from the RP's bootflash.

Do " remote switch login " and check the sup's bootflash " dir bootflash: " and see if the file is located. If its not then try to copy it to the SP's bootflash and set the boot path to boot it from there.

Please let us know if there is any other thing.

HTH,Please rate if it does.

-amit singh

4 REPLIES

Re: 6509 IOS upgrade

Where is the file located SP bootflash or RP bootflash. I think the problem that you have is that the file is copied to the RP bootflash and it is booting from there. Make sure that you have the correct file located in the SP bootflash and you boot the switch from there using the " boot sup-bootflash:

I see that you are using the "boot bootflash: " command, which will eventually try to boot from the RP's bootflash.

Do " remote switch login " and check the sup's bootflash " dir bootflash: " and see if the file is located. If its not then try to copy it to the SP's bootflash and set the boot path to boot it from there.

Please let us know if there is any other thing.

HTH,Please rate if it does.

-amit singh

New Member

Re: 6509 IOS upgrade

Thanks for the quick reply Amit. The IOS image that is failing to load is located in:

XXXX#dir bootflash:

Directory of bootflash:/

1 -rw- 26912316 Dec 30 2006 21:24:55 -05:00 c6sup22-jk2sv-mz.121-27b.E

.bin

31981568 bytes total (5069124 bytes free)

Once that fails, the image is loaded from sup-bootflash:

XXXX#dir sup-bootflash:

Directory of sup-bootflash:/

1 -rw- 26862248 Jun 03 2006 08:47:24 -04:00 c6sup22-jk2sv-mz.121-26.E1

.bin

31981568 bytes total (5119192 bytes free)

Is "sup-bootflash" the SP-bootflash?

Re: 6509 IOS upgrade

Yes, "sup-bootflash" is the SP-bootflash. As I suspected you had the same problem. You file is located in the RP bootflash instead of SP-bootflash.This is the problem that we have. Put this file in the sp-bootflash as you have another file in there and set the boot path to boot from the SP. You will be absolutely fine with it.

HTH

-amit singh

New Member

Re: 6509 IOS upgrade

1) Display all storage locations. Make sure the new image is actually available (the transmission may have failed due to insufficient space, for example)

LAB-C6506-C#dir all

Directory of system:/

2 dr-x 0 memory

1 -rw- 7978 running-config

11 dr-x 0 vfiles

No space information available

Directory of bootflash:/

1 -rwx 1686608 Mar 2 2005 23:14:15 -05:00 c6msfc2-boot-mz.121-8a.E5

31981568 bytes total (30294832 bytes free)

Directory of disk0:/

1 -rw- 40937356 Dec 23 2005 06:07:16 -05:00 c6k222-jk9o3sv-mz.122-18.SXD7.bin

64274432 bytes total (23334912 bytes free)

Directory of sup-bootflash:/

1 -rwx 27635032 Mar 2 2005 23:09:13 -05:00 c6k222-pk9s-mz.122-18.SXD3.bin

31981568 bytes total (4346408 bytes free)

Directory of sup-microcode:/

1 -r-- 3662874 CWPA_version_10.10

2 -r-- 4931890 CWTLC_version_10.10

3 -r-- 4140258 CWPA2_version_10.10

4 -r-- 15775910 DRACO2_MP

5 -r-- 5115690 CHILIS-LC

6 -r-- 2344014 MACEDON

7 -r-- 382546 LCP_LX10100

8 -r-- 353418 LCP_LX1000

9 -r-- 380732 LCP_AX1000

10 -r-- 353546 LCP_AX10100

11 -r-- 738686 LCP_CPSLCP

12 -r-- 343710 LCP_CPFAB

13 -r-- 663262 LCP_CPGBIT

14 -r-- 658830 LCP_CP10G

15 -r-- 729054 LCP_CPMBIT2

16 -r-- 813166 LCP_CPMBIT

41388098 bytes total (0 bytes free)

Directory of const_nvram:/

1 -rw- 1036 vlan.dat

129004 bytes total (127968 bytes free)

Directory of nvram:/

382 -rw- 8017 startup-config

383 ---- 24 private-config

384 -rw- 8017 underlying-config

1 ---- 4 rf_cold_starts

2 ---- 32 persistent-data

3 -rw- 0 ifIndex-table

391160 bytes total (379995 bytes free)

2) If the file is where it should be, verify its MD5 sum to make sure the file was not "damaged in transit". Verify against the MD5 signature posted in the download page

LAB-C6506-C#verify disk0:c6k222-jk9o3sv-mz.122-18.SXD7.bin

.........................................................................................................................................................................Done!

Embedded Hash MD5 : 5D4BB7C53B6AB32732A13C554D76DD5F

Computed Hash MD5 : 5D4BB7C53B6AB32732A13C554D76DD5F

CCO Hash MD5 : A598FC6C28A71C886021BB5A68CA3F6E

Signature Verified

Verified disk0:c6k222-jk9o3sv-mz.122-18.SXD7.bin

3) Adjust your boot sequence. You may add multiple "boot system flash" lines, each line is a backup in case the previous command fails.

LAB-C6506-C#sh runn | i boot

boot system flash disk0:c6k222-jk9o3sv-mz.122-18.SXD7.bin

4) Reboot. Capture the bootup sequence, it may give information why the load failed.

Hope this helps,

Cristian

440
Views
3
Helpful
4
Replies
CreatePlease login to create content