Cisco Catalyst SD-WAN Upgrade Guide

Manage software maintenance upgrade images using the CLI

Updated: July 1, 2026

Want to summarize with AI?

Describes how to manage SMU image installation, activation, deactivation, and removal using CLI commands. Helps users perform SMU image operations efficiently on the device.

Use CLI commands to install, activate, deactivate, and remove SMU images on the device.

These sections describe the CLI procedures:

Note

When an SMU image is activated and deactivated, the device reboot may be triggered based on non-reload or reload SMU types. A non-reload SMU type does not trigger a device reboot, but a reload SMU type triggers a device reboot.

Install and activate an SMU image using the CLI

Procedure

Upload the SMU image from the file server to the bootflash of the device.

Use the copy command to upload an SMU image. For information about the copy command, see Step 2 of the Install the Cisco IOS XE Software topic.
If not already configured, configure the time limit for confirming that a SMU image activation is successful.

The time limit can be 1 through 60 minutes. We recommend that you configure the time limit to be at least 15 minutes.
```
Device# config-transaction 
Device(config)# system 
Device(config-system)# upgrade-confirm minutes 
```
Install an SMU image from the bootflash of your device and perform a compatibility check for the device and SMU package version.
```
Device# request platform software sdwan smu install file-path 
```

Activate the SMU image on a Cisco IOS XE Catalyst SD-WAN device .

Device# request platform software sdwan smu activate build-number.smu-defect-id

Confirm the upgrade of the SMU image within the configured confirmation time limit.
```
Device# request platform software sdwan smu upgrade-confirm  
```
Note

If you don’t issue this command on the device within the time limit that is specified in the upgrade-confirm minutes command, the device automatically reverts to the state that it was in before the SMU image activation.

Deactivate and remove an SMU image using the CLI

Procedure

If not already configured, configure the time limit for confirming that a SMU image deactivation is successful.

The time limit can be 1 through 60 minutes. We recommend that you configure the time limit to at least 15 minutes.
```
Device# config-transaction
Device(config)# system
Device(config-system)# upgrade-confirm minutes
```
Deactivate an SMU image on a Cisco IOS XE Catalyst SD-WAN device.
```
Device# request platform software sdwan smu deactivate build-number.smu-defect-id
Device# request platform software sdwan smu upgrade-confirm
```
Note

If you do not issue this command on the device within the time limit specified in the upgrade-confirm minutes command, the image deactivation fails and the device automatically reverts to the state that it was in before the SMU image deactivation.

Remove an SMU image from a Cisco IOS XE Catalyst SD-WAN device .

Device# request platform software sdwan smu remove build-number.smu-defect-id

These examples show commands that you can use to manage the SMU image operations.

Check the upgrade and confirm the configuration:
```
show sdwan running system
```

Add and upgrade the confirm timer:

Device# config-transaction
Device(config)# system
Device(config-system)# upgrade-confirm 15
Device(config-system)# commit

Execution commands:

request platform software sdwan smu install bootflash:c8000v-universalk9.2022-08-17_23.44_mcpre.24042.CSCvq24042.SSA.smu.bin

request platform software sdwan smu activate 17.09.01a.0.247.CSCvq24042

request platform software sdwan smu upgrade-confirm

request platform software sdwan smu deactivate 17.09.01a.0.247.CSCvq24042

request platform software sdwan smu upgrade-confirm

request platform software sdwan smu remove 17.09.01a.0.247.CSCvq24042

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.