03-18-2014 08:11 AM - edited 03-07-2019 06:45 PM
Good Day.
I will be performing 4500 non-E chassis to 4500E chassis upgrade this week.
non-E chassis has IOS 12.2 running on it while 4500E will have IOS-XE 3.2.5SG code running. Is there any website where I can paste the IOS configuration to see if they are compatible on IOS XE code?
Thank you, sir.
Solved! Go to Solution.
03-18-2014 08:33 AM
There's no website or tool that I'm aware of to do such a pre-upgrade check for IOS to IOS-XE. That said, I've done several without issue. Just about all old commands carry forward.
One thing indirectly command-related is to make sure you have the same license level on the new switch (i.e. lanbase, ipbase or ipservices). If your new switch has a lower license level and you were using features that require the higher license level on the old switch, those commands won't be parsed on the new one because the features aren't available without the necessary license.
To verify, you should connect to the physical console port and log the output to a file while the system loads. Any commands that aren't parsed or have been deprecated will be logged as exceptions during the boot process. You can do this using the old switch configuration file loaded onto the new switch in advance of the actual cutover and resolve any issues ahead of time.
03-18-2014 08:33 AM
There's no website or tool that I'm aware of to do such a pre-upgrade check for IOS to IOS-XE. That said, I've done several without issue. Just about all old commands carry forward.
One thing indirectly command-related is to make sure you have the same license level on the new switch (i.e. lanbase, ipbase or ipservices). If your new switch has a lower license level and you were using features that require the higher license level on the old switch, those commands won't be parsed on the new one because the features aren't available without the necessary license.
To verify, you should connect to the physical console port and log the output to a file while the system loads. Any commands that aren't parsed or have been deprecated will be logged as exceptions during the boot process. You can do this using the old switch configuration file loaded onto the new switch in advance of the actual cutover and resolve any issues ahead of time.
03-18-2014 10:27 AM
Thanks
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