|
1. |
Log in to the device on the console port connection. |
|
2. |
Ensure that the required space is available for the image file to be copied.
switch# dir bootflash:
16384 Oct 30 17:05:32 2020 lost+found/
1964291584 Dec 08 19:44:33 2020 nxos.10.1.1.bin
...
Usage for bootflash://sup-local
4825743360 bytes used
16312102912 bytes free
21137846272 bytes total
Note
We recommend that you have the image file for at least one previous release of the NX-OS software on the device to use if the new image file does not load successfully.
-
If you need more space on the active supervisor module, delete unnecessary files to make space available.
switch# delete bootflash:nxos.9.2.1.bin
-
Verify that there is space available on the standby supervisor module.
switch# dir bootflash://sup-standby/
16384 Oct 30 17:05:32 2020 lost+found/
1964291584 Dec 08 19:44:33 2020 nxos.10.1.1.bin
...
Usage for bootflash://sup-standby
4825743360 bytes used
16312102912 bytes free
21137846272 bytes total
-
(Optional) If you need more space on the standby supervisor module, delete any unnecessary files to make space available.
switch# delete bootflash://sup-standby/nxos.9.2.1.bin
|
|
3. |
Log in and choose the software image file for your device from the Software Download website, and download it to a file server. |
|
4. |
Copy the software image to the active supervisor module using a transfer protocol. You can use FTP, TFTP, SCP, or SFTP.
switch# copy scp://user@scpserver.cisco.com//download/nxos64.10.2.1.F.bin bootflash:nxos64.10.2.1.F.bin
Note
The compaction feature is deprecated from NX-OS Release 10.5(2)F
For software images requiring compaction, you must use SCP, HTTP, or HTTPS as the source and bootflash or USB as the destination. This example uses SCP and bootflash:
switch# copy scp://user@scpserver.cisco.com//download/nxos64.10.2.1.F.bin
bootflash:nxos64.10.2.1.F.bin compact vrf management use-kstack
user1@10.65.42.196's password:
nxos64.10.2.1.F.bin 100% 1887MB 6.6MB/s 04:47
Copy complete, now saving to disk (please wait)...
Copy complete.
The compact keyword compacts the NX-OS image before copying the file to the supervisor module.
Note
Software image compaction is only supported on SCP, HTTP, or HTTPS. If you attempt compaction with any other protocol, the system returns the following error:
Compact option is allowed only with source as scp/http/https and destination
as bootflash or usb
Note
Compacted images are not supported with LXC boot mode.
Note
Software image compaction is only supported on Nexus 9300-series platform switches.
-
You can detect an incomplete or corrupt NX-OS software image prior to performing an upgrade by verifying the MD5, SHA256 or SHA512 checksum of the software image. To verify the MD5 checksum of the software image, run the show file bootflash:<IMAGE-NAME>md5sum command and compare the resulting value to the published MD5 checksum for the software image on Software Download website. To verify the SHA512 checksum of the software image, run the show file bootflash:<IMAGE-NAME>sha512sum command and compare the resulting value to the published SHA512 checksum for the software image on Cisco’s Software Download website.
switch# show file bootflash:nxos.10.1.1.bin md5sum
2242a7f876f1304118fd175c66f69b34
switch# show file bootflash:nxos.10.1.1.bin sha512sum
7f25cce57ca137a79211fb3835338aae64acf9b021b75cec5d4156e873b4274ca4f98e9a74fe4c8961
f5ace99ed65f3826650599369f84ab07265d7c5d61b57f
-
You can detect an incomplete or corrupt NX-OS software image prior to performing an upgrade by verifying the MD5, SHA256 or SHA512 checksum of the software image. To verify the MD5 checksum of the software image, run the show file bootflash:<IMAGE-NAME>md5sum command and compare the resulting value to the published MD5 checksum for the software image on Cisco’s Software Download website. To verify the SHA512 checksum of the software image, run the show file bootflash:<IMAGE-NAME>sha512sum command and compare the resulting value to the published SHA512 checksum for the software image on the Software Download website.
switch# show file bootflash:nxos64.10.2.1.F.bin md5sum
c49660952215822afd30bb7958a0765a
switch# show file bootflash:nxos64.10.2.1.F.bin sha256sum
2a64efbb381fabbb52054af74cf3efda1691772a49a70ddd35550431cadecf8e
switch# show file bootflash:nxos64.10.2.1.F.bin sha512sum
3bf6a771aa4a192a8e1383e348b26bb483356a9774d74ba39edbf7718248483b3391942d8103de8104deea8fda212266e70bd736220cff34943bd8e359432975
|
|
5. |
Check the impact of upgrading the software before actually performing the upgrade.
switch# show install all impact nxos bootflash:nxos64.10.2.1.F.bin
During the compatibility check, the ISSU-related messages listed in this table can appear in the Reason field.
| Reason Field Message |
Description |
| Incompatible image for ISSU |
The NX-OS image to which you are attempting to upgrade does not support ISSU. |
| Default upgrade is not hitless |
By default, the software upgrade process is disruptive. You must configure the non-disruptive option to perform an ISSU. |
|
|
6. |
Save the running configuration to the startup configuration.
switch# copy running-config startup-config
|
|
7. |
Upgrade the NX-OS software using the install all nxos bootflash:filename [no-reload | non-disruptive | non-interruptive | serial | skip-epld | skip-bios-upgrade | skip-kernel-upgrade ] command.
switch# install all nxos bootflash:nxos64.10.5.3.F.bin
Note
From NX-OS Release 10.5(3)F, EPLD upgrade can be performed with either the no-reload or the non-disruptive option.
The available options are:
-
no-reload—Exits the software upgrade process before the device reloads.
Note
When you use install all with no-reload option, no additional configuration changes can be made before you reload the device. Saving configuration in this state can result in incorrect startup configuration once you reload the device with the new version of NX-OS (along with EPLD from 10.5(3)F). From Release 10.5(3)F onwards, though the EPLD and BIOS are programmed but not upgraded, a switch reload is required for them to take effect.
-
non-disruptive—Performs an in-service software upgrade (ISSU) to prevent the disruption of data traffic. (By default, the software upgrade process is disruptive.) From Release 10.5(3)F onwards, though the EPLD and BIOS are programmed but not upgraded, a switch reload is required for them to take effect.
-
non-interruptive—Upgrades the software without any prompts. This option skips all error and sanity checks.
-
serial—Upgrades the I/O modules in Nexus 9500 Series switches one at a time. (By default, the I/O modules are upgraded in parallel, which reduces the overall upgrade time. Specifically, the I/O modules are upgraded in parallel in this order: the first half of the line cards and fabric modules, the second half of the line cards and fabric modules, the first system controller, the second system controller.)
-
skip-epld—Installs only the nxos image, and not the epld image. This option is available from 10.5(3)F.
-
skip-bios-upgrade—Installs only the nxos image, and skips the BIOS upgrade. This option is available from 10.5(3)F.
-
skip-kernel-upgrade—Installs only the nxos image, and skips the kernel upgrade. This option is available from 10.5(3)F.
Note
-
If you enter the install all command without specifying a filename, the command performs a compatibility check, notifies you of the modules that will be upgraded, and confirms that you want to continue with the installation. If you choose to proceed, it installs the NX-OS software image that is currently running on the switch and upgrades the BIOS of various modules from the running image, if necessary.
-
Starting from 10.5(3)F, during the image upgrade, you can also apply SMUs so the SMU is installed with the new image using the
install all nxos <nxos image> package <smu package> non-disruptive non-interruptive command.
install all nxos nxos64-cs.10.5.3.F.bin.upg package nxos64-cs.CSCab123456
-1.0.0-10.5.3.lib32_64_n9000.rpm non-disruptive non-interruptive
|
|
8. |
(Optional) Post upgrade actions.
-
Display the entire upgrade process.
switch# show install all status
-
Log in and verify that the device is running the required software version.
-
If necessary, install the relevant licenses to ensure that the required features are available on the device. For more information about the licenses, see the Cisco NX-OS Licensing Options Guideand Cisco Nexus 9000 and 3000 Series NX-OS Smart Licensing Using Policy User Guide.
|