Lifecycle · IOS-XE upgrades
Pick your target IOS-XE train (17.9 LTS, 17.12 LTS, 17.15) for Catalyst, ISR, and ASR platforms. Get a pre-upgrade checklist, the exact install CLI, and a reload plan.
IOS-XE upgrades used to be "copy the .bin, boot, cross fingers." Modern IOS-XE uses package/install mode with rollback, smart-licensing transport, and rommon-aware upgrades. This tool builds the upgrade plan right.
Install mode splits the IOS-XE image into activate/commit steps. If anything fails between activate and commit, a single reload rolls back. Bundle mode is monolithic — if it boots wrong, you're in rommon.
Cisco IOS-XE follows a train model. Even-numbered minor versions (17.6, 17.9, 17.12) are LTS — 3 years of maintenance. Odd minors (17.7, 17.8, 17.10, 17.11, 17.13, 17.14) are short-lived feature releases. For production, pick the latest LTS. For new platforms requiring new features, 17.15 is the current feature train.
Install mode is Cisco's strong recommendation. It's faster to boot, allows rollback via install rollback, and plays nicely with patching.
Rarely, but yes — some 17.15+ features on Catalyst 8000 require rommon 17.9.x or later. Check show platform for current rommon before upgrading.
Yes on Catalyst 9500 HA, Catalyst 9600 HA, and ASR 1000 ISSU. Catalyst 9300 stacks use StackWise ISSU which is only supported within the same major release — cross-LTS requires a cold reload.
Non-ISSU because of LTS cross. Plan a maintenance window. Copy image to flash on all members, run install add file then install activate — the stack reloads and comes up on 17.12.
Convert to install mode first with install add file flash:c8000be-universalk9.17.12.04.SPA.bin activate commit. After reload, the image is in sub-packages, future upgrades take minutes.