Upgrade Cisco Catalyst 9200 and 9300 switches to IOS XE version 17.15.03

Prepare a pre-upgrade checklist for Catalyst 9200/9300

Here is a reliable pre-upgrade checklist for Cisco Catalyst 9200/9300 switches before upgrading to a new IOS XE version:

Pre-Upgrade Checklist

  1. Verify hardware/software compatibility for version 17.15.03.
  2. Identify any mandatory intermediate upgrade paths, features affected, and known caveats.
copy startup-config tftp: (or SCP/FTP/USB).

Following the above will help prevent common upgrade issues and ensure a smooth transition to IOS XE 17.15.03 on Catalyst 9200/9300 series switches.

============================================================

Process for cisco switch 9200 & 9300 upgrade to version 17.15.03

To upgrade Cisco Catalyst 9200 and 9300 switches to IOS XE version 17.15.03, follow these general steps for each model. Both switches use nearly identical upgrade steps in install mode, which is the recommended method for modern Cisco Catalyst switches.

Preparation

  • Download the correct 17.15.03 .bin image from Cisco's support portal.

  • Ensure 1 GB or more free space in flash memory.

  • Console access to the switch is necessary.

  • Confirm the device is in Install Mode by running:
    show version

  • Save the current configuration:
    write memory

Upgrade Steps

  1. Cleanup Unused Files
    Run:


    install remove inactive

    This command clears old installation files and ensures enough flash space for the new image.

  2. Copy the New Image
    Use TFTP, FTP, USB, or another appropriate method:


    copy tftp://<server_ip>/cat9k_iosxe.17.15.03.SPA.bin flash:

    Replace with the actual filename and source/location as needed.

  3. Set Boot Variable
    Configure the switch to boot from the newly installed image package:


    conf t
boot system flash:packages.conf
no boot manual
end
write memory

    This ensures consistency after reload.

  4. Initiate the Upgrade
    Perform the install and commit actions:

    text
    install add file flash:cat9k_iosxe.17.15.03.SPA.bin activate commit

    The switch will reload automatically during this process.

  5. Verify the Upgrade
    After reboot, check the software version:


    show version

    And verify the flash contents:


    dir flash:

    Also confirm the current boot variables:


    show boot

    The switch should now be running version 17.15.03.

  6. Optional: Remove Old Packages (again)
    For additional flash cleanup (post-upgrade):


    install remove inactive

Notes

  • In a stack, repeat this process for the stack master. Standby members will synchronize automatically.

  • Allow enough maintenance window time for backup, transfer, and reload sequence.

  • Always consult the official release notes and Cisco documentation for model-specific caveats and prerequisites.

These steps are valid for both Catalyst 9200 and 9300 series switches operating in install mode when upgrading to IOS XE 17.15.03


===========================================================

Create a rollback plan and test recovery steps for the upgrade

Here is a detailed rollback plan and test recovery steps for Catalyst 9200/9300 series switch upgrades:

Rollback Plan

  • Backup Before Upgrade

    • Save running and startup configs and download the current IOS XE image to an external server or USB.

  • Set Auto-Abort Timer

    • The install process uses an “auto-abort-timer” (default 120 minutes). If the upgrade isn’t committed (install commit) and a problem occurs, the switch will automatically roll back to the previous version upon timer expiry.

    • You can adjust the timer (in minutes):


      install activate auto-abort-timer <value>

  • Manual Rollback Command

    • If the new software is committed but you need to revert, re-add the prior image and use:


      install add file flash:<old_image>.bin activate commit

    • The system will reload into the previous IOS XE version, restoring the previous state.

  • Stack Considerations

    • On stacks, rollback works for all members, provided the image is present on each.

Test Recovery Steps

  • Upgrade Failure Auto-Restore Test

    • During a pre-scheduled test window, perform an upgrade but intentionally do not issue the install commit command after reboot.

    • Wait for the auto-abort timer (default 120 min):

      • The system will recognize the commit was not completed and automatically roll back to the prior version.

  • Manual Recovery

    • If the switch becomes unresponsive or suffers a failed boot, connect via console.

    • Use ROMmon mode (if necessary) to boot the backup image manually:


      boot flash:<old_image>.bin

    • Restore configuration from the backup copy.

  • Verification Post-Recovery

    • After recovery or rollback, verify:

      • show version

      • show running-config

      • All network services and interfaces are operational as before the upgrade.

Key Best Practices

  • Keep a copy of the prior working image and configuration files on the switch flash and an external device.

  • Practice a test rollback in a lab environment when possible, or schedule a production maintenance window exclusively for recovery testing.

  • Document CLI output and error messages at each step for support reference.

By following this plan and testing the steps, a safe and predictable rollback path is assured for Catalyst 9200/9300 upgrades.

===========================================================       

      Define success criteria and RTO/RPO for rollback 

Success criteria and RTO/RPO definitions are critical for evaluating a Catalyst 9200/9300 upgrade and potential rollback. Here is a precise breakdown:

Success Criteria

  • All switches (standalone or stack) boot successfully to the target or previous IOS XE version with no error messages.

  • All interfaces (uplink, access ports, stack links) come up with the correct state and configuration after rollback.

  • Network connectivity is fully restored (management and user VLANs, routing, PoE, etc.).

  • Feature set and services (L2/L3, ACLs, QoS, authentication) are functional and configured as prior to the upgrade.

  • Verification commands (show version, show running-config, interface/status checks) align with pre-upgrade state.

  • No config loss has occurred, and system logs show no critical errors related to the rollback event, ensuring network and business continuity.

RTO (Recovery Time Objective)

  • The maximum acceptable time to fully recover and restore switch operation after initiating a rollback should typically not exceed 60 minutes for standalone, and 90 minutes for a stack of switches in a standard enterprise setting.

  • RTO may be adjusted based on business SLA, network complexity, and maintenance window length, but should always be defined and tested before production upgrades.

RPO (Recovery Point Objective)

  • RPO for switch upgrades is generally “zero”: No configuration changes or data loss should occur after rollback—meaning the running and startup configs must match the last backup taken before the upgrade.

  • Ensure no network state or critical switch data (VLANs, SNMP, AAA, etc.) is lost during rollback, confirmed by verification checks post-recovery.

Clearly defining and validating these criteria ensures a reliable, recoverable upgrade path for Catalyst 9200/9300 switches.

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Upgrade Cisco Catalyst 9200 and 9300 switches to IOS XE version 17.15.03

Prepare a pre-upgrade checklist for Catalyst 9200/9300 Here is a reliable pre-upgrade checklist for Cisco Catalyst 9200/9300 switches before...