×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Catalyst 4500 IOS to IOS XE command compatibility check?

Answered Question
Mar 18th, 2014
User Badges:

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.

Correct Answer by Marvin Rhoads about 3 years 5 months ago

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.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Marvin Rhoads Tue, 03/18/2014 - 08:33
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,
  • Cisco Designated VIP,

    2017 Firewalling, Network Management, VPN

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.

Actions

This Discussion

Related Content