Upgrade Guide for Cisco Catalyst 9000 Series Switches and Smart Switches

PDF

Upgrade Guide for Cisco Catalyst 9000 Series Switches and Smart Switches

Upgrade the device in install mode

Want to summarize with AI?

Log in

Guides you through upgrading supported Catalyst 9000 series switches or stacks in install mode.


Use this procedure to upgrade a Catalyst 9000 switch or switch stack in install mode.

When executing the commands and verifying the outputs, replace CURRENT_RELEASE , TARGET_RELEASE , IMAGE.bin , and SHA-512-VALUE values in the sample outputs with the actual values of your deployment.

Before you begin

For switch stacks, verify that all members report the expected software state before and after the upgrade.

Procedure

  1. Verify the current release, installation state, boot variables, and stack readiness before the upgrade.

    1. Verify that the switch is running from the INSTALL-mode packages file and identify the current Cisco IOS XE release.

      Example:

      
      switch# show version | include IOS XE Software|System image file
      Cisco IOS XE Software, Version <CURRENT_RELEASE>
      System image file is "flash:packages.conf"
      

      The System image file value must be flash:packages.conf. The packages.conf file confirms that the switch is running in INSTALL mode.

    2. Verify that all stack members are in INSTALL mode and running the same software release version.

      Example:

      
      switch# show version | begin Switch Ports
      Switch Ports Model              SW Version       SW Image       Mode
      ------ ----- -----              ----------       --------       ----
      *    1 48    C9300-48P          <CURRENT>        CAT9K_IOSXE    INSTALL
           2 48    C9300-48P          <CURRENT>        CAT9K_IOSXE    INSTALL
      

      Every stack member must show INSTALL in the Mode column and must show the same release in the SW Version column.

    3. Confirm that the current image is activated and committed.

      Example:

      
      switch# show install summary
      State (St): I - Inactive, U - Activated & Uncommitted,
                  C - Activated & Committed
      -----------------------------------------------------------------------
      Type  St   Filename/Version
      -----------------------------------------------------------------------
      IMG   C    <CURRENT_RELEASE>
      
      Auto abort timer: inactive
      

      A state value of C means that the current image is activated and committed.

      The Auto abort timer: inactive output confirms that no previous uncommitted installation or rollback timer is active.

    4. Confirm that the current boot variables and boot variables on next reload point to the INSTALL-mode package file. If not, set it accordingly.

      Example:

      
      switch# show boot
      Current Boot Variables:
      BOOT variable = flash:packages.conf;
      
      Boot Variables on next reload:
      BOOT variable = flash:packages.conf;
      
      Manual Boot = no
      

      Here, both the current boot variable and the boot variable for the next reload point to flash:packages.conf. The Manual Boot = no output indicates that auto-boot is enabled.

      Example:

      If the boot variables were not rightly set, follow these steps to set it and to disable manual boot:

      
      Switch(config)# no boot system
      Switch(config)# boot system flash:packages.conf
      Switch(config)# no boot manual
  2. Validate the target image by verifying its SHA-512 checksum.

    Example:

    
    switch# verify /sha512 flash:<IMAGE.bin>
    verify /sha512 (flash:<IMAGE.bin>) = <SHA-512-VALUE>
    

    The returned checksum value must exactly match the SHA-512 value that is posted on Cisco Software Download site.

  3. Save the running configuration before you start the installation.

    Example:

    
    switch# write memory
    Building configuration...
    [OK]
    

    The [OK] message confirms that the configuration was saved successfully.

  4. Add, activate, and commit the target image as the persistent software version.

    Example:

    
    switch# install add file flash:<IMAGE.bin> activate commit
    install_add_activate_commit: START
    
    --- Starting initial file syncing ---
    Copying flash:<IMAGE.bin> to Switch 1 2
    Info: Finished copying to the selected Switch
    >>> Indicates that the target image was copied to the required stack members
    
    --- Starting Add ---
    Performing Add on all members
     [1] Finished Add package(s) on Switch 1
     [2] Finished Add package(s) on Switch 2
    Add: Passed on [1 2]
    >>> Indicates that the image was validated and expanded successfully on every member
    
    --- Starting Activate ---
    Performing Activate on all members
    Activate: Passed on [1 2]
    >>> Indicates that the target packages were activated successfully
    
    --- Starting Commit ---
    Performing Commit on all members
    Commit: Passed on [1 2]
    >>> Indicates that the target image was made persistent for future reloads
    
    SUCCESS: install_add_activate_commit
    >>> Indicates that the complete add, activate, and commit operations succeeded
    
    Initializing Hardware......
    
    Preparing to autoboot. [Press Ctrl-C to interrupt]  0
    boot: attempting to boot from [flash:packages.conf]
    >>> Indicates that the switch is booting in INSTALL mode
    ...
    ...
    ...
    >>> [Routine boot messages are omitted ]
    

    The installation process copies the target image to the required stack members, validates and expands the packages, activates the target packages, and commits the image for future reloads.

  5. Verify the post-upgrade state on the device.

    1. Verify that the switch is running the target Cisco IOS XE release in INSTALL mode after the reload.

      Example:

      
      switch# show version | include IOS XE Software|System image file
      Cisco IOS XE Software, Version <TARGET_RELEASE>
      
      System image file is "flash:packages.conf"
      

      The output must show Cisco IOS XE Software Version <TARGET_RELEASE> .

      The System image file value must display flash:packages.conf which indicates that the switch remains in install mode.

    2. Confirm that the target image is activated and committed after the upgrade.

      Example:

      
      switch# show install summary
      Type  St   Filename/Version
      -----------------------------------------------------------------------
      IMG   C    <TARGET_RELEASE>
      >>> Indicates that the target image is activated and committed
      
      Auto abort timer: inactive

      The IMG entry must show state C for the <TARGET_RELEASE> .

      The Auto abort timer: inactive output confirms that no incomplete installation or rollback timer remains.

    3. Confirm that every switch stack member has rejoined and is ready.

      Example:

      
      switch# show switch
      Switch#  Role      Priority  State
      ----------------------------------
      *1       Active    15        Ready
       2       Standby   14        Ready

      Every stack member must show Ready in the State column. Verify that the expected active and standby roles are present.

The Catalyst 9000 switch or switch stack runs the target Cisco IOS XE release in install mode. The target image is activated and committed, no rollback timer remains active, and all stack members are ready.