• Adding the SMU to the filesystem.
• Activating the SMU on the system.
• Committing the SMU changes so that it is persistent across reloads.
Software Maintenance Upgrade Package
The SMU package contains a small set of files for patching the release along with meta data that describes
the contents of the package.
SMU Workflow
The SMU process is initiated with a request to the SMU committee. Contact your customer support to raise
an SMU request.
At release time, the SMU package is posted to the Cisco Software Download page and can be downloaded
and installed.
SMU Package
An SMU package contains the metadata and fix for the reported issue that the SMU is requested for.
SMU Reload
The SMU type describes the effect to a system after installing the SMU. SMUs can be non-traffic affecting
or can result in device restart, reload, or switchover.
All SMUs require a cold reload of the system during activation. A cold reload is the complete reload of the
operating system. This action affects the traffic flow for the duration of the reload (~5 min currently). This
reload ensures that all processes are started with the correct libraries and files that are installed as part of the
SMU.
How to Manage Software Maintenance Updates
The following sections provide information about managing SMUs.
You can install, activate, and commit an SMU package using a single command or using separate commands
.
Managing an SMU Package
SUMMARY STEPS
1.
enable
2.
install add file location filename
3.
install activate file location filename
4.
install commit
5.
install rollback to
{
base
|
committed
|
id commit-ID
}
System Management Configuration Guide, Cisco IOS XE Fuji 16.8.x (Catalyst 9500 Switches)
232
Software Maintenance Upgrade
SMU Workflow