09-03-2007 01:29 PM - edited 03-05-2019 06:15 PM
I tried to update the IOS on our backbone switch going via the instructions attached. This failed and the switch continuously rebooted saying it could not load the .bin in rommon# mode.
I think I found the problem in the path being incorrect
nzaklnet1(config)#boot system ?
WORD TFTP filename or URL
flash Boot from flash memory
ftp Boot from a server via ftp
mop Boot from a Decnet MOP server
rcp Boot from a server via rcp
tftp Boot from a tftp server
nzaklnet1(config)#boot system flash ?
WORD System image filename
<cr>
nzaklnet1(config)#boot system flash NEWIMAGE NAME
boot-start-marker
boot system flash bootflash:cat4000-i9s-mz.122-25.ewa10.bin - should be?? boot system flash:cat4000-i9s-mz.122-25.ewa10.bin'?
boot system bootflash:cat4000-i9s-mz.122-25.EWA4
boot system bootflash:cat4000-i9s-mz.122-25.EWA4.bin
boot-end-marker
!
Solved! Go to Solution.
09-03-2007 06:59 PM
It would be displayed next to the filename, which it doesn't at the moment.
The problem you had was due to case sensitive differences between the string and the actual filename.
09-03-2007 02:34 PM
The correct command is:
boot system flash bootflash:image-name.bin
However, if you only have one bin file in the bootflash, you don't even need this command.
Can you verify the image was loaded correctly into bootflash by typing,
dir bootflash:
09-03-2007 03:21 PM
That is what I had originally.
Yes I can see the image when typing dir bootflash:
Did you have chance to view my original instruction sheet, did it all look correct?
So best practice would be to remove the existing .bin image so only one .bin exists - What happens if the image fails to load again, how I be able to boot tftp x.x.x.x if the switch is dead for recovery?
Thanks again
Brendan
09-03-2007 04:42 PM
You should not have to get rid of the old image unless you are out of space , as Edison said it should be "boot system flash bootflash:
09-03-2007 05:46 PM
Yes, I reviewed the instructions and they are correct.
Best practice is to keep the original image (if there is enough space in the bootflash) along with the new image. With this approach, you can revert back to the original image in case you encounter a bug with the new image.
With that said, what's really the problem with the upgrade ? It isn't clear to me ...
09-03-2007 06:03 PM
The system came back with
rommon 1 > Unable to load bootflash:cat4000cat4000-i9s-mz.122-25.ewa10.bin system will automatically restart 5
It just continually did this until {ctrl-c} was pressed. Then I used the boot cammand and pointed to the old image.
09-03-2007 06:04 PM
The image that is trying to load is incorrect.
You have cat4000 twice on the filename.
09-03-2007 06:10 PM
Sorry that was a typo.
Should read rommon 1 > Unable to load bootflash:cat4000-i9s-mz.122-25.ewa10.bin system will automatically restart 5
My log is all out of wack.
09-03-2007 06:11 PM
Sounds like the new image is corrupted.
Can you load the old image and please post the output from typing
show version
and
dir bootflash:
Thanks
09-03-2007 06:18 PM
Show ver...
Cisco IOS Software, Catalyst 4000 L3 Switch Software (cat4000-I9S-M), Version 12
.2(25)EWA4, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by Cisco Systems, Inc.
Compiled Fri 23-Sep-05 13:31 by ssearch
Image text-base: 0x10000000, data-base: 0x114DFF08
ROM: 12.2(20r)EW1
Dagobah Revision 226, Swamp Revision 31
nzaklnet1 uptime is 3 days, 15 hours, 43 minutes
System returned to ROM by power-on
System image file is "bootflash:"
cisco WS-C4503 (MPC8245) processor (revision 14) with 524288K bytes of memory.
Processor board ID FOX074104M8
MPC8245 CPU at 333Mhz, Supervisor IV
Last reset from PowerUp
11 Virtual Ethernet interfaces
98 Gigabit Ethernet interfaces
403K bytes of non-volatile configuration memory.
Configuration register is 0x2102
Dir Bootflash:
Directory of bootflash:/
1 -rwx 12495228 Jul 5 2006 07:29:18 +00:00 cat4000-i9s-mz.122-25.EWA4
.bin
61341696 bytes total (36443408 bytes free)
I have removed the new image from the boorflash:
This is part of the Show Run, it doesn't look right either?
oot-start-marker
boot system flash bootflash:cat4000-i9s-mz.122-25.ewa10.bin
boot system bootflash:cat4000-i9s-mz.122-25.EWA4
boot system bootflash:cat4000-i9s-mz.122-25.EWA4.bin
boot-end-marker
Thanks
09-03-2007 06:24 PM
The boot variables keep prepending every time you enter the command. Let's cleaned up a bit and remove all the entries, in config mode, type:
no boot system flash bootflash:cat4000-i9s-mz.122-25.ewa10.bin
no boot system bootflash:cat4000-i9s-mz.122-25.EWA4
no boot system bootflash:cat4000-i9s-mz.122-25.EWA4.bin
I would've loved to see the output from dir bootflash: while the new image was there. It would've shown if the image was corrupted.
You have enough space to have both images in the flash at the same time.
I recommend you download the image once again from Cisco, perhaps the one you have is corrupted. Once downloaded, tftp back onto the switch and enter the appropriate bootflash command.
Ex,
boot system flash bootflash:cat4000-i9s-mz.122-25.EWA10.bin
Edit: One thing I noticed is the EWA10 is lower case in the boot system string. The image is case sensitive so it must match with the filename.
09-03-2007 06:33 PM
Fantastic, I think that will be it then - Images are case sensitive.
Now I don't want to mess with a live system with 1000+ users plugging away, does the removal of the boot system variables affect the running in anyway possible?
Thanks again,
09-03-2007 06:40 PM
No. It doesn't affect the running config. Those commands are only read during bootup to load the image.
09-03-2007 06:44 PM
Awsome, thanks Edison, I will load the new image up on Friday night and see how it goes.
09-03-2007 06:52 PM
I copied the image back to teh switch, here is the output from dir bootflash:
zaklnet1#dir bootflash:
Directory of bootflash:/
1 -rwx 12495228 Jul 5 2006 07:29:18 +00:00 cat4000-i9s-mz.122-25.EWA4
.bin
3 -rwx 12402804 Sep 3 2007 19:42:18 +00:00 cat4000-i9s-mz.122-25.EWA1
0.bin
61341696 bytes total (24040476 bytes free)
Not sure how you tell if the image is corrupt, correct size?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide