Information About Performing A Software Maintenance Upgrades; Overview Of Smus - Cisco Nexus 5600 Series Configuration Manual

Information About Performing a Software Maintenance Upgrades

• Activation is performed only after the package compatibility checks have been passed. If a conflict is
• While a software package is being activated, other requests are not allowed to run on any of the impacted
• Each CLI install request is assigned a request ID, which can be used later to review the events.
• SMUs are dependent on your physical device. So, an SMU for the Cisco Nexus 6000 Series switch will
• If you perform a software maintenance upgrade and later upgrade your device to a new Cisco NX-OS
• SMUs are dependent on the version of Cisco NX-OS software release installed. You need to install
• Remove the existing SMU if you are loading an image of the Cisco NX-OS software release prior to
• Only reload type SMU is supported.
Information About Performing a Software Maintenance Upgrades

Overview of SMUs

Typically, SMUs do not have a large impact on device operations. SMU versions are synchronized to the
package major, minor, and maintenance versions they upgrade.
SMUs are not an alternative to maintenance releases. They provide a quick resolution of immediate issues.
All defects fixed by SMUs are integrated into the maintenance releases.
Actual deployment of SMUs might vary based on your device.
The type of SME supported is the Reload type SMU, which causes a reload of the whole switch and a parallel
reload of supervisors and line cards.
For information on upgrading your device to a new feature or maintenance release, see the Cisco Nexus 5000
and 6000 Series NX-OS Software Upgrade and Downgrade Guide.
An SMU consists of the SMU binary file and an accompanying README.txt which contains any associated
caveats. The naming convention for an SMU is as below:
<platform>-<pkg-type>.<release_version>.<CDET>.<file-type>
For example:
n6000-uk9.7.2.1.N1.1.CSCuw28765.bin
n6000-uk9.7.2.1.N1.1.CSCuw28765.txt
Cisco Nexus 5600 Series NX-OS System Management Configuration Guide, Release 7.x
334
found, an error message displays.
nodes. Package activation is completed when a message similar to this one appears:
Install operation 1 completed successfully at Thu Jan 9 01:19:24 2014
not work for the Cisco Nexus 5000 Series switch and vice versa.
software release, the new image will overwrite both the previous Cisco NX-OS release and the SMU
package file.
SMUs compatible with your release. Moving to another Cisco NX-OS software release using reload or
ISSU will inactivate the SMUs installed for the previously installed Cisco NX-OS software release. For
example, if you have SMUs for Cisco NX-OS Release 7.2(1)N1(1) in your Cisco Nexus 6000 series
setup, moving to an image of another release, for example, Cisco NX-OS Release 7.1(2)N1(1), will
cause the SMU to become inactive. However, moving back to Cisco NX-OS Release 7.2(1)N1(1) will
reactivate the SMU.
Cisco NX-OS Release 7.2.0 that does not support SMUs.
Performing Software Maintenance Upgrades
OL-31641-01