I do 'copy tftp flash', reload and image is still the old one!

[news2010a]

On a 2960G switch, I attempt to upgrade image. TFTP server is reachable. Then I execute the command 'copy tftp flash'. I see the exclamation points. It terminates successfully. I do 'reload'. I noticed that the reload did not ask me to "save the configuration changes".

Then I reload the box, but again it uploads the old IOS.

What am I missing?

Please see output pasted below.

Switch Ports Model SW Version SW Image

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

* 1 24 WS-C2960G-24TC-L 12.2(35)SE5 C2960-LANBASE-M

Configuration register is 0xF

sw1#copy tftp flash

Address or name of remote host []? 192.168

Source filename []? c2960-lanbasek9-mz.122-50.SE1.bin

Destination filename [c2960-lanbasek9-mz.122-50.SE1.bin]?

%Warning:There is a file already existing with this name

Do you want to over write? [confirm]

Accessing tftp://192.168/c2960-lanbasek9-mz.122-50.SE1.bin...

Loading c2960-lanbasek9-mz.122-50.SE1.bin from 192.168 (via vlan9): !!!!

[OK - 8055039 bytes]

8055039 bytes copied in 77.284 secs (104226 bytes/sec)

sw1#reload

Proceed with reload? [confirm]

00:15:58: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload Command.

Base ethernet MAC Address: 00:24:f9:fe:30:00

Xmodem file system is available.

The password-recovery mechanism is enabled.

Initializing Flash...

flashfs[0]: 605 files, 19 directories

flashfs[0]: 0 orphaned files, 0 orphaned directories

flashfs[0]: Total bytes: 32514048

flashfs[0]: Bytes used: 16394752

flashfs[0]: Bytes available: 16119296

flashfs[0]: flashfs fsck took 10 seconds.

...done Initializing Flash.

Boot Sector Filesystem (bs) installed, fsid: 3

done.

Loading "flash:c2960-lanbase-mz.122-35.SE5/c2960-lanbase-mz.122-35.SE5.bin".. <*** SAME OLD FLASH AFTER RELOADING!!!

[Pari Thiagasundaram]

Is boot string set in your running-config? (Do a sh run to check if you are loading from the old IOS)

Make sure you remove your old IOS from the flash (after taking a backup).

[Richard Burts]

Marlon

Pari makes a good suggestion about checking the configuration to see if there is a boot system statement that specifies the old image. If there is a boot system statement then obviously it needs to be updated to point to the new image.

If there is not a boot system command then the default behavior is to boot the first image in flash - which would be the old image. So I suggest that you go into config mode and enter a boot system command to point to the new image, save the config, and reload. That should boot the new image.

I would not remove the old image until I had booted the new image and verified that it runs successfully.

HTH

Rick

[news2010a]

I agree.

Guys, you rule. I did that and it works.

I will remove the old image then since the new one works fine.

[news2010a]

I did not see the bootstring. However the old flash is still here.

Do you know if I do 'del flash:c2960-lanbase-mz.122-35.SE5' the new flash will be replace old one? Or do I need to do other operation to assure the new one will be the one used?

Directory of flash:/

2 -rwx 736 Mar 16 1993 00:44:01 +00:00 vlan.dat

3 -rwx 5 Mar 16 1993 01:32:58 +00:00 private-config.text

5 -rwx 8055039 Mar 1 1993 00:15:46 +00:00 c2960-lanbasek9-mz.122-50. SE1.bin

6 -rwx 3823 Mar 16 1993 01:32:58 +00:00 config.text

7 drwx 192 Mar 1 1993 00:06:55 +00:00 c2960-lanbase-mz.122-35.SE 5

[Pari Thiagasundaram]

If you just have one image on your bootflash and no other boot string configured, it should boot from the new image on bootflash.

[punchhab]

Since you already have the new image in the flash, just need to set the boot statement

(config)#boot system flash:c2960-lanbasek9-mz.122-50. SE1.bin

Verify it by using #show boot

Do a reload and it should boot using the new image.

If you want to delete the older image

delete /force /recursive flash:c2960-lanbase-mz.122-35.SE 5

Simply deleting may not replace it, it is recommended to set the boot statement first

Thanks,

Puneesh

[glen.grant]

Boot string does not show up in the running config , you can only verify with a "show boot" command... If there is only 1 image in flash and there is "no" bootstring the switch will find that image.. It will find the first one in flash which would have been your old image and why it kept booting the old one if there was no boot statement.

[iyde]

Hi.

For your own ease and convenience, download the .tar image instead of the .bin image from cisco.com, and then use the 'archive download-sw ...' command. It will do the whole job for you, including changing boot statement, and if you use the CNA or in other way browses to your switch, then your HTML files will be correct as well.

HTH.