Showing results for 
Search instead for 
Did you mean: 


Hi cisco gurus!

I had an issue with my cisco 4900m, after firmware upgrade. Finally I could reboot the switch using cat4500e-ipbasek9-mz.152-4.E8.bin

The thing is : How should I do the upgrade and also what is this file for? Should I also copy for the upgrade or it's just for rom boot



Mark Malone

Thats the recommended image for that switch .8
If you want to upgrade you load the image file you chose to flash or USB , FTP ,SCP etc whatever is available to you locally
Then set the boot statement like below in global config mode
Then save it with copy run start
Then check the right image is going to boot with show boot
Then reload the switch

boot system flash bootflash:cat4500e-universalk9.SPA.03.08.07.E.152-4.E7.bin
boot system flash bootflash:cat4500e-universalk9.SPA.03.06.07.E.152-2.E7.bin
no ip bootp server

sh boot
BOOT variable = bootflash:cat4500e-universalk9.SPA.03.08.07.E.152-4.E7.bin,1;bootflash:cat4500e-universalk9.SPA.03.06.07.E.152-2.E7.bin,1;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2102

Standby BOOT variable = bootflash:cat4500e-universalk9.SPA.03.08.07.E.152-4.E7.bin,1;bootflash:cat4500e-universalk9.SPA.03.06.07.E.152-2.E7.bin,1;
Standby CONFIG_FILE variable does not exist
Standby BOOTLDR variable does not exist
Standby Configuration register is 0x2102


Thanks for your answer. The thing is my switch is 4900m and the firmware is cat4500e-entservicesk9-mz.152-4.E8.bin

Should I use universal too?

Stick to same image name you currently have if its available in download section, my output is just an example

This is my download section page


so you rebooted the switch and it came up as ipbase image but you really should be running the enterprise version , thats what you had before the issue yes ?
if thats the correct and you want to add a fresh enterprise k9 image then you want the 4th link on that screenshot you posted

the original enterprise image should be in flash too though have you tried to just reboot it with that since you brought it back up or do you just want to replace it with a fresh copy , you could check the image in flash and see if its corrupt using the verify /md5 flash:image_name ... command and check the output against the value in the download section , it it matches it should be ok to still use

Hi mark!

Thanks for your answer! Exactly, number 4 was the bin I haved installed

Let me show a dir of my FS

Directory of bootflash:/

   23  -rw-    41482478  Jul 10 2019 22:38:08 -03:00  cat4500e-entservicesk9-mz.152-4.E8.bin
    6  -rw-       14673  Jul 10 2019 22:40:00 -03:00  cat4500e-entservicesk9-mz.152-4.E2.bin

122007552 bytes total (72515584 bytes free)
switch4900m#verify /md5 cat4500e-entservicesk9-mz.152-4.E2.bin      
verify /md5 (bootflash:cat4500e-entservicesk9-mz.152-4.E2.bin) = cf1e2f36e3eae5dc0ba8f15820905097

switch4900m#show bootvar 
BOOT variable = bootflash:cat4500e-entservicesk9-mz.152-4.E8.bin,1;
CONFIG_FILE variable = 
BOOTLDR variable does not exist
Configuration register is 0x2102

This is my bootvar.

What I find extrange is the size of the cat4500e-entservicesk9-mz.152-4.E2.bin. Is that correct? Should be 40 mb.

Let me know if I had to change something. I don't want to reload and have a failure.



hi mark!

Any idea?

sorry i missed your last post , you need to verify this image if that's what is being used , your bootvar is correct and your config register but you need to run verify md5 against the new image name----cat4500e-entservicesk9-mz.152-4.E8.bin , you verified the E2 image not the E8 looking at your output

The md5 checksum should be this ------- dccb54dc6197d45d439c1d26b0767626

From 4th option down on this page

The file size is 39.6 mb

hi thks for your answer

This is my verify command

verify /md5 (bootflash:cat4500e-entservicesk9-mz.152-4.E8.bin) = dccb54dc6197d45d439c1d26b0767626

Seems to be fine! Do you think I can reboot the sw without any problem?

What about the ipbase file? Do I need it?

Yes looks fine now , leave the ipbase in the flash its not really needed but if something goes seriously wrong always good to have an image in flash you know you can get the device back up on