11-08-2007 12:34 PM - edited 03-03-2019 05:45 AM
A contractor used a flash drive to copy a new IOS image into flash; however, I cannot get the second image to boot - a 'boot flash:[file]' command had no effect after reboot.
3560#sh flash
Directory of flash:/
2 drwx 192 Feb 28 1993 19:09:36 -05:00 c3560-ipservices-mz.122-23
406 -rwx 109 Feb 28 1993 19:09:36 -05:00 info
407 -rwx 616 Feb 28 1993 19:02:31 -05:00 vlan.dat
409 -rwx 79 Feb 28 1993 19:07:25 -05:00 private-config.text
410 -rwx 9031259 Nov 8 2007 12:30:34 -05:00 c3560-ipservices-mz.122-4n
411 -rwx 7382 Feb 28 1993 19:07:25 -05:00 config.text
412 -rwx 1048 Feb 28 1993 19:07:25 -05:00 multiple-fs
32514048 bytes total (14492672 bytes free)
3560#sh boot
BOOT path-list : c3560-ipservices-mz.122-40.SE.bin
Config file : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break : no
Manual Boot : no
HELPER path-list :
Auto upgrade : yes
3560#
Are there any commands to move images within flash directories, or how else can I direct the boot loader to the second image?
Thanks,
Marc
11-08-2007 12:51 PM
If, from your posted output, this is the second image:
c3560-ipservices-mz.122-4n
It doesn't match your
BOOT path-list : c3560-ipservices-mz.122-40.SE.bin
Entry.
Is the image file named correctly? Is the boot path statement correct?
11-08-2007 12:51 PM
Hi Marc
Just to confirm have you tried the following command in config mode
boot system flash flash:"filename" ?
Jon
11-08-2007 12:58 PM
Thanks for the replies, guys;
The original image is: c3560-ipservices-mz.122-23
The new image is c3560-ipservices-mz.122-40
The output I showed depicts the 'sh boot' following my command 'boot system flash:c3560-ipservices-mz.122-40':
3560#sh boot
BOOT path-list: flash:c3560-ipservices-mz.122-40.SE.bin
It's as if the switch is booting the old image despite what the command says to do.
Since the new image was copied from a usb drive, might the location of the image in the flash directory play into whether it can be "seen" by the hardware?
Directory of flash:/
2 drwx 192 Feb 28 1993 19:09:36 -05:00 c3560-ipservices-mz.122-2
406 -rwx 109 Feb 28 1993 19:09:36 -05:00 info
407 -rwx 616 Feb 28 1993 19:02:24 -05:00 vlan.dat
409 -rwx 79 Feb 28 1993 19:07:25 -05:00 private-config.text
410 -rwx 9031259 Nov 8 2007 12:30:34 -05:00 c3560-ipservices-mz.122-4
What's the difference between "drwx" and "-rwx" ?
Marc
11-08-2007 01:05 PM
Marc
The difference is
drwx = this is a directory that contains files
-rwx = this is a file.
What you have is
2 drwx 192 Feb 28 1993 19:09:36 -05:00 c3560-ipservices-mz.122-2
This is a directory and contains not just the IOS but also html files etc. which allows you to configure the switch via a web interface
410 -rwx 9031259 Nov 8 2007 12:30:34 -05:00 c3560-ipservices-mz.122-4
This is just the IOS file itself - not the directory so you won't be able to configure it from the web interface. But it should have a .bin suffix. Your
boot system flash:c3560-ipservices-mz.122-40
should read
boot system flash:c3560-ipservices-mz.122-40.SE.bin
if that indeed is the IOS you are trying to load.
Jon
11-08-2007 01:08 PM
the =drwx signifies a directory, that is created when you use the archive /download-sw command using a zipped .tar IOS image package.
It has a lot of web page images and code. The actual bootable .bin image in that directory is down a sub-directory. Whenever you see a -drwx you can drill down it using the old dos style CD command, followed by the directory name.
I'm not sure if your screen outputs are complete, there's no -40.SE.bin in the output you are showing.
I believe 3560's, as well as other gear, boot the newest valid IOS image it comes across, so if there's a corrupt image or it can't find the image, it looks for another image.
I would recommend you recheck the filenames in flash:\. What you're showing is not complete. Either that or change the boot statement to include the actual file name of the image in flash:
Or, I would recommend deleting the 122-40-SE.bin file from flash and using the archive /download-sw /overwrite command with the .tar version of the image on a tftp server.
11-08-2007 01:29 PM
Yes, the output was incomplete:
I didn't make any other changes, but apparently a second reboot got the image to stick:
DR-3560#sh ver
Cisco IOS Software, C3560 Software (C3560-IPSERVICES-M), Version 12.2(40)SE, RE)
Copyright (c) 1986-2007 by Cisco Systems, Inc.
Compiled Thu 23-Aug-07 20:03 by myl
Image text-base: 0x00003000, data-base: 0x01600000
ROM: Bootstrap program is C3560 boot loader
BOOTLDR: C3560 Boot Loader (C3560-HBOOT-M) Version 12.2(25r)SE1, RELEASE SOFTWA)
DR-3560 uptime is 52 minutes
System returned to ROM by power-on
System image file is "flash:c3560-ipservices-mz.122-40.SE.bin"
cisco WS-C3560G-48TS (PowerPC405) processor (revision A0) with 122880K/8184K by.
Processor board ID xxxxxx
Last reset from power-on
3 Virtual Ethernet interfaces
52 Gigabit Ethernet interfaces
The password-recovery mechanism is enabled.
512K bytes of flash-simulated non-volatile configuration memory.
Model number : WS-C3560G-48TS-E
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 52 WS-C3560G-48TS 12.2(40)SE C3560-IPSERVICES-M
Configuration register is 0xF
3560#
Thanks for being a good sounding board!
Marc
11-08-2007 02:04 PM
Glad it helped Marc,
Just jump on Cisco.com and do some 3560 image loading reading. Having a standard image loading process is a good thing, especially when your device numbers start growing.
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