Configuration Examples For Software Maintenance Upgrade; Example: Managing An Smu - Cisco Catalyst 9400 System Management Configuration Manual

Configuration Examples for Software Maintenance Upgrade

Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Configuration Examples for Software Maintenance Upgrade
The following is a list of SMU configuration examples.

Example: Managing an SMU

Note • The examples used in this section are of hot patching SMU.
The following example shows how to copy an SMU file to flash:
System Management Configuration Guide, Cisco IOS XE Bengaluru 17.4.x (Catalyst 9400 Switches)
358
Command or Action
install commit
Example:
Device# install commit
install rollback to {base | committed | id
commit-ID}
Example:
Device# install rollback to committed
install deactivate file flash: filename
Example:
Device# install deactivate file
flash:cat9k_iosxe.BLD_SMU_20180302_085005_
TWIG_LATEST_20180306_013805.3.SSA.smu.bin
install remove {file flash: filename | inactive}
Example:
Device# install remove file
flash:cat9k_iosxe.BLD_SMU_20180302_085005_
TWIG_LATEST_20180306_013805.3.SSA.smu.bin
show version
Example:
Device# show version
show install summary
Example:
Device# show install summary
Software Maintenance Upgrade
Purpose
Commits the activation changes to be persistent
across reloads. The commit can be done after
activation when the system is up, or after the
first reload. If a package is activated, but not
committed, it remains active after the first
reload, but not after the second reload.
Returns the device to the previous installation
state.
Deactivates an active package and updates the
package status.
Verifies if the specified SMU is inactive and if
it is, deletes it from the file system. The inactive
option deletes all the inactive packages from
the file system.
Displays the image version on the device.
Displays information about the installation
status of packages. The output of this command
varies according to the install commands that
are configured.