There are no dependencies in upgrading from non-K9 to a K9 image. So you can proceed with the upgrade.
I am not sure why do you want to re-name your old firmware. If that is your general practice then go ahead. Else, you just need to change the boot variable pointing to the new image and remove the previous one.
Something like this:
no boot system
boot system flash bootflash:cat4500es8-universalk9.SPA.03.09.00.E.152-5.E.bin
Hi Thank you! I tried this method, but had to change the confreg to 0x2102 ( as it was still pointing to 0x2101). Force reloaded the peer and waited for it to come up. It came up as RPR (Cold Standby). Made sure standby had the latest firmware. Did "Redundancy force-switchover" and it took a about 5mins to come up. Strange thing is that the switchover did not work, it came back to primary sup with downtime, but firmware came up ok and changed to SSO after few more minutes. Is this expected?
After my first publication of the book OSPF Demystified With RFC in 2014 which goes beyond the CCIE level which explores OSPF from the RFC's perspective. Since one year I had the idea : why not write a book for CCIE Enterprise and Infrastructure to be an ...
Do you use Cisco DNA Center? Have you used and are you willing to provide your feedback in using the Cisco DNA Center help and documentation?
If so, we’d like you to complete the survey linked below. Your feedback will help provide more effective and easi...
Listen: https://smarturl.it/CCRS9E18Follow us: https://twitter.com/CiscoChampion Reaching the height of your career is no simple feat. It often requires a combination of pursuing the right education, building the right professional network and being ...