ciscosales@bo-net.com 0086-13538247228 Online Service

Cisco network switch,Cisco Router, NEW used Cisco comparison

Technical
Current location:Home > News > Technical

How to upgrade N3K software version Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.x

By 14,01,2022

Perform install all to upgrade the BIOS and also upgrade the NX-OS image to Release 7.x. Upgrade the Cisco NX-OS software using the install all nxos bootflash:filename [no-reload | non-disruptive | non-interruptive | serial]

Example:

switch# install all nxos bootflash:nxos.7.0.3.I3.1.bin 

The following options are available:

  • no-reload—Exits the software upgrade process before the device is reloaded.

  • non-disruptive—Performs an in-service software upgrade (ISSU) to prevent the disruption of data traffic. (By default, the software upgrade process is disruptive.)

Note 

The non-disruptive option is supported only from Release 7.0(3)I3(1) to the later releases of Cisco Nexus 3000 Series switches.

  • non-interruptive—Upgrades the software without any prompts. This option skips all error and sanity checks.

  • serial—Upgrades the line cards in the system one at a time. (By default, the line cards are upgraded in batches to save time.)

The "Unsupported in new image, module needs to be powered off" message displays during a disruptive upgrade. It explains that the device automatically reloads to complete the upgrade.

Installer is forced disruptive
 
Verifying image bootflash:/nxos.7.0.3.I3.1.bin for boot variable "nxos".
[########################################] 100% -- SUCCESS
 
Verifying image type.
[########################################] 100% -- SUCCESS
 
Extracting "nxos" version from image bootflash:/nxos.7.0.3.I3.1.bin.
[########################################] 100% -- SUCCESS
 
Extracting "bios" version from image bootflash:/nxos.7.0.3.I3.1.bin.
[########################################] 100% -- SUCCESS
 
Performing runtime checks.
[########################################] 100% -- SUCCESS
 
Performing module support checks.
[########################################] 100% -- SUCCESS
 
Notifying services about system upgrade.
[########################################] 100% -- SUCCESS
 
 
Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes disruptive reset Unsupported in new image, module needs to be powered off
 
 
 
Images will be upgraded according to following table:
Module Image Running-Version New-Version Upg-Required
------ ---------------- ---------------------- ---------------------- ------------
1 kickstart 6.0(2)U6(3) 7.0(3)I3(1) yes
1 bios v2.7.0(04/01/2014) v3.2.0(08/06/2015) yes
 
 
Switch will be reloaded for disruptive upgrade.
 
Time Stamp: Wed Sep 2 17:28:22 2015
 
 
Install is in progress, please wait.
 
Performing runtime checks.
[########################################] 100% -- SUCCESS
 
Setting boot variables.
[########################################] 100% -- SUCCESS
 
Performing configuration copy.
[########################################] 100% -- SUCCESS
 
Module 1: Refreshing compact flash and upgrading bios/loader/bootrom/power-seq.
Warning: please do not remove or power off the module at this time.
Note: Power-seq upgrade needs a power-cycle to take into effect.
On success of power-seq upgrade, SWITCH OFF THE POWER to the system and then, power it up.
[########################################] 100% -- SUCCESS
 
Time Stamp: Wed Sep 2 17:32:08 2015
Finishing the upgrade, switch will reboot in 10 seconds 

The configuration must be backed up prior to upgrading to a new release as the configuration is required for the downgrade later.

Caution 

For Cisco Nexus 3000 vPC topologies, a non-disruptive upgrade from Cisco NX-OS Release 6.0(3)U6(3) to 7.0(3)I2(1) is not supported as the upgrade will cause a traffic disruption. An upcoming maintenance release will support non-disruptive upgrades for vPC topologies. It is highly recommended that customers with vPC topologies wait for the next maintenance release of 7.0(3)I2(x), to avoid traffic disruption.


Upgrade Prerequisites

  • Ensure that the network is stable and no changes are made while an upgrade is in progress.

  • Ensure that you check for feature compatibility between the current running release and the target release.

Management Services After an Upgrade

Before the switch is reset for an upgrade, inband and management ports are brought down and are brought back up after the upgrade completes. Services that depend on the inband and management ports are impacted during this time.

Table 3. Inband and Management Ports Services Impacted During Upgrade Reset

Service

Description

Telnet/SSH

When an upgrade resets the system to load the target Cisco NX-OS version, all Telnet/SSH sessions are disconnected and need to be reestablished after the upgrade completes.

AAA/RADIUS

Applications that leverage the AAA Service (such as login) are disabled during an upgrade, because all Network Management services are disabled during this time, this behavior is consistent.

HTTP

HTTP sessions to the switch are disconnected during an upgrade reboot. After the reboot, the HTTP is restarted and the switch will accept an HTTP sessions.

NTP

NTP sessions to and from the switch are disrupted during an upgrade reboot. After the reboot, NTP session are reestablished based on the saved startup configuration.

Layer-2 Protocols Impact

The following table lists the upgrade impacts to Layer 2 protocols.

Table 4. Upgrade Impact to Layer 2 Protocols

Protocol

Description

LACP

IEEE 802.3ad provides for the default slow aging timers to be transmitted once every 30 seconds in steady state and to expire after 90 seconds. Upgrade should not impact peers that rely on LACP because the recovery time is less than 90 seconds.

IGMP

IGMP does not disrupt existing flows of multicast traffic that are already present, but new flows are not learned (and are dropped) until an upgrade completes. New router ports or changes to router ports are not detected during this time.

DCBX and LLDP

DCBX uses LLDP to exchange parameters between peer devices. Because DCBX is a link-local protocol, when the switch undergoes an upgrade, the age time is increased on all ports on the switches that are being upgraded.

Manual configurations are ignored during this time.

CDP

During an upgrade, the time-to-live value is increased (180 seconds) if it is less than the recommended timeout value. The configuration is ignored if manually specified.

L2MP IS-IS

Before a switch reboots for an upgrade, the switch transmits L2 IS-IS hellos on all interfaces to prevent neighbor switches from marking routes to the upgrade switch as down. Any topology changes during this time are also not acted upon until the upgrade completes.

Ethernet Interfaces on the Switch

To avoid link down to link up transitions during the control plane outage time, the laser is turned off for administratively up ports that are operationally down. This situation occurs during the upgrade reboot starting state. After the upgrade reboot and a stateful restart, the laser is turned back on. This action prevents the link state from transitioning from down to up during an upgrade.

Pre-Installation Checks

You should do certain sanity checks to ensure that the system is ready for an upgrade and to understand the impact of the upgrade:

  • Enter the show incompatibility command to verify that the target image is feature-wise compatible with the current image.

  • Enter the show logging level command to ensure that the severity level for all processes is set to 5 or below.

  • Enter the show install all impact command to identify the upgrade impact.

  • A BIOS incompatibility issue has been discovered on specific Cisco Nexus 3000 and 3100 Series switches. When you upgrade these switches from Cisco NX-OS Release 6.0(2)U6(8) or an earlier release to Cisco NX-OS Release 7.0(x), an MD5 mismatch error might occur and leave the switch at the loader prompt. We recommend that you view the field notice for this release to see if your software or hardware platforms are affected. You can find the field notice at the following URL http://www.cisco.com/c/en/us/support/docs/field-notices/642/fn64233.html

  • Enter the install all command to update to the latest Cisco NX-OS software.

  • Review the installer impact analysis and choose to continue.

Note

The switch might reload at this time and cause a traffic disruption.


  • Monitor the installation progress.

  • Verify the upgrade.

  • Enter the show install all status command to verify the status of the installation

The following table lists the show commands that identify the impact or potential problems that may occur when performing an upgrade.

Table 5. Upgrade show Commands

Command

Definition

show incompatibility system

Displays incompatible configurations on the current system that will impact the upgrade version.

show logging level

Displays the facility logging severity level configuration.

Logging levels for all processes must be set at 5 or below when performing an upgrade. Processes with a logging level greater than 5 are not displayed when you enter the show install all impact command.

show install all impact

Displays information that describes the impact of the upgrade. This command also displays if the upgrade is disruptive or not and if the switch needs to be rebooted and the reason why.

You can also perform the following tasks to identify potential problems before they occur:

  • Ensure that you have enough space to store the images on bootflash:

  • Display incompatible configurations on the current system that will impact the upgrade version.

    switch# show incompatibility system pcco.s No incompatible configurations
  • Verify the impact of the upgrade.

    switch# show install all impact nxos bootflash:nxos.7.0.3.I2.1.bin