migrating from ipbasek9-mz to entservicesk9.mz on 4500E

[mohit.chauhan]

Hi there,

I have requirement where i need to have full EIGRP feature set on my 4500 running on Sup-6L-E which is currently running on "cat4500e-ipbasek9-mz.122-54.SG1.bin".

i was looking on the options and i think "cat4500e-entservicesk9-mz.122-54.SG1.bin" should suffice the need.

now the Q is :

1. is it possible to upgrade from the given source to the given destination ios?

2. any special caution to be taken, any doc specifying that?

Thanks!

[Leo Laohoo · Accepted solution]

1. is it possible to upgrade from the given source to the given destination ios?

Yes you can if you paid for the upgrade.

2. any special caution to be taken, any doc specifying that?

Go over the Release Notes.

[mohit.chauhan]

thanks leolaohoo.

I'll let you know how i go with it..i m doing that very soon today.

thanks

[mohit.chauhan]

thanks mate...i got this out of my way...few things that I learnt in the process:

1. Even after I set the boot to use the new image by using the following commands:

     "Switch(config)#no boot system flash cat4500e-baseipk9-mz.122-54.SG1.bin"

     "Switch(config)#boot system flash cat4500e-entservicesk9-mz.122-54.SG1.bin"

but then saving the config when i used to reboot the box, the switch used to pick up the old image only with a message like "using the first file in the flash..."

I had confirmed, when we did sho run it was only showing one boot option in the config...

2. Now to fix this issue, I had to get onto the Rommon mode,

and say

"boot bootflash:cat4500e-entservicesk9-mz.122-54.SG1.bin"

And this way it used to boot properly...

3. And later when the switch has booted completely loading the config file, I deleted the old image from the flash and rebooted to confirm the switch was responding normal.... and it was, so all well!

Thanks for your input anyway cos it is always helpful.

[Leo Laohoo · Accepted solution]

Can you please mark this thread as "Answered" please?  Thank you  very much.

[glen.grant · Accepted solution]

  It booted the first first image because of the setting on the config register  . All that needed to be done is change it to 0x2102 and use the correct boot statement and it would have booted the correct one without deleting the old image .

[Leo Laohoo]

Thanks for the ratings.