How to Upgrade Firmware on Cx 3000

How to Upgrade Firmware on Cx 3000

Upgrading or Downgrading the Cisco Nexus 3000 Series NX-Os Software

This document describes how to upgrade or downgrade the Cisco NX-Os software on Cisco Nexus 3000 Series switches.


Information Nigh Software Images

Cisco Nexus 3000 Series switches are shipped with the Cisco NX-Os software preinstalled on the switches. Before upgrading or downgrading from an existing image, you should read through the information in this certificate to empathize the guidelines, prerequisites, and procedures for upgrading the software. For updated information virtually the Cisco NX-OS software for Cisco Nexus 3000 Serial switches, run into the

Cisco Nexus 3000 Series Release Notes.

The Cisco NX-Os software consists of one Cisco NX-Os software prototype. The prototype filename begins with “nxos.” Merely this image is required to load the Cisco NX-Bone operating arrangement. This paradigm runs on all the Cisco Nexus 3000 and 3100 Series switches. Using the

install all

command is the only supported method of upgrading to new releases.



Note

There is a single image for booting the Cisco Nexus 3000 Series switches. The kickstart and system images are non required. Due to a unmarried image binary, the following commands are updated:


  • boot nxos
    single_image_binary


  • install all nxos
    single_image_binary




Supported Hardware

Cisco Nexus 3000 and 3100 Series switches are shipped with the Cisco NX-OS software preinstalled. Cisco NX-OS upgrades and downgrades are supported on the hardware listed in the post-obit sections:

Cisco Nexus 3000 Series Switches

  • Cisco Nexus 3016 switches

  • Cisco Nexus 3048 switches

  • Cisco Nexus 3064 switches

Cisco Nexus 3100 Series Switches

  • Cisco Nexus 3132Q and 3132Q-XL switches

  • Cisco Nexus 3172 switches



About ISSU

An in-service software upgrade (ISSU) allows you to upgrade the device software while the switch continues to forward traffic. An ISSU reduces or eliminates the downtime typically caused by software upgrades. You tin perform an ISSU, also known equally a nondisruptive upgrade, for some switches. (See the “Guidelines and Limitations for ISSU” department for a list of supported platforms.)


ISSU Prerequisites

Follow the guidelines in the “Guidelines and Limitations for ISSU” section to ensure that the ISSU works smoothly.

Make certain that the network is stable and no changes are made while the ISSU is in progress.

Ensure characteristic compatibility between the current running release and the target release.

Brand certain that interfaces are not in a spanning-tree designated forwarding state. Besides, brand certain that span balls is not configured on any interface. The vPC peer-link is an exception to these requirements.

Verify that the current STP topology is consistent with the ISSU requirements. Use the

show spanning-tree issu-impact

command to display the STP configuration and whether or not at that place are potential STP bug.

Use the

show lacp issu-impact

command to brandish if a port or a peer switch is configured in the rate fast style. The ISSU process is aborted if the arrangement has whatever LACP fast timers configured.

Before performing an ISSU to Cisco NX-Bone Release 9.3(ane), y’all must configure the BGP graceful restart timer to 180 seconds for Cisco Nexus 3132Q-Twoscore, 3172PQ-Forty, and 3172TQ-XL platform switches.



Guidelines and Limitations for ISSU

The following is a list of important guidelines and limitations for ISSU:

  • Non-disruptive standard ISSU on Cisco Nexus 3172PQ, 3172TQ, 3132Q, 3132Q-10, 3064, 3064-10, 3064-T, 3048, 3016 (4 GB low-memory platforms) is not supported to Cisco Nexus nine.3(one) and later releases.

  • Cisco Nexus 3132Q-XL, 3172PQ-XL, and 3172TQ-XL switches support an ISSU to Cisco NX-OS Release 9.iii(ane) and later releases. For more information, see the
    ISSU Support Matrix.

  • Starting time with Cisco NX-OS Release 7.0(3)I5(1), Cisco Nexus 3000 serial platforms with sixteen GB or higher retentiveness support enhanced ISSU.
    The upgrade volition exist confusing.

  • Enhanced ISSU in fallback style from earlier releases to Cisco NX-OS Release 9.3(1) is not supported. Showtime with Cisco NX-Os Release 9.3(1), Cisco Nexus 3164Q, C31108PC-V, C31108TC-V, C3132Q-5 support enhanced ISSU in fallback mode simply. For more details, come across the
    ISSU Support Matrix.

  • The Cisco Nexus 3264C-East switch does non support the enhanced ISSU way fallback characteristic from Cisco NX-OS Release nine.three(ane) to any future 9.iii(ten) releases.

  • For any prior release version upgrading to ix.iii(v) using ISSU, if the following logging level commands are configured, they are missing in the upgraded version and must be reconfigured:


    • logging level evmc
      value


    • logging level mvsh
      value


    • logging level fs-daemon
      value

  • For whatever prior release version upgrading to Cisco NX-Bone Release 9.3(six) using ISSU, if the following logging level commands are configured, they are missing in the upgraded version and must be reconfigured:


    • logging level evmc
      value


    • logging level mvsh
      value

  • You can perform an ISSU for segment routing or VXLAN.

  • The minimum free bootflash space required to perform an ISSU is 550 MB.

  • The CLI and the SNMP configuration change requests are denied during ISSU operations.

  • STP topology changes are not expected during an ISSU.

  • The Guest Shell is disabled during an ISSU, and information technology is reactivated after the upgrade. During an ISSU, all First-Hop Redundancy Protocols (FHRPs) cause the other peer to get agile if the node undergoing the ISSU is active.

  • An ISSU is blocked if

    boot poap enable

    is configured.

  • Upgrading from Cisco NX-Os Release 9.3(1), ix.three(2), or 9.iii(3) to a higher release, with Embedded Result Director (EEM) configurations saved to the running configuration, may crusade a DME error to exist presented. The fault is in the output of the

    show consistency-checker dme running-config enhanced

    command, specifically, the event manager commands. If this occurs, delete all EEM applet configurations afterward completing the ISSU, then reapply the EEM configurations.

  • Cisco Nexus 3048, 3064, 3132, and 3172 switches with a model number that does not terminate in
    -XL
    must run a compact NX-Bone software paradigm due to limited bootflash space. This compact image can be created using the NX-OS Compact Paradigm procedure; alternatively, a compact NX-OS software image can be downloaded direct from
    Cisco’s Software Download website
    . This requirement does non apply to any other model of Nexus 3000 or 3100 series switch.

    • The MD5/SHA512 checksum published on
      Cisco’s Software Download website
      for a compact NX-OS software image may not match the MD5/SHA512 checksum of a compact image created through the NX-Os Compact Image process.



Meaty Image for Cisco Nexus 3000, 3100, and 3500

Early models of Cisco Nexus 3000, 3100, and 3500 Series switches with a model number that does not end in
-XL
have ane.4 to one.six gigabytes of storage infinite allocated to the bootflash. Over time, the file size of NX-OS software images has steadily increased to be over 1 gigabyte. Every bit a event, it is hard for Nexus 3000, 3100, and 3500 Series switches with a model number that does not terminate in
-Xl
to simultaneously store more than than one full NX-OS binary image at a time. Therefore, administrators cannot follow the standard NX-Bone software upgrade procedure on Nexus 3000, 3100, and 3500 Series switches with a model number that does not end in
-XL
that is used for other Nexus platforms, such as Nexus 5000, 6000, 7000, and 9000 Series switches.

Starting with NX-OS software release seven.0(three)I3(1), the file size of NX-OS software images can be reduced through the NX-OS Compact Image procedure. This is a not-disruptive procedure that does not impact the switch’due south command plane or ability to forward data plane traffic.


Meaty NX-OS Software Images on Cisco’s Software Download Website

Compact NX-Bone software images are available for download on
Cisco’southward Software Download website
for a few NX-Bone software releases. These compact images have a published MD5/SHA512 checksum that can be used to verify the integrity of the NX-OS binary image file. The meaty NX-OS software images tin can be downloaded from
Cisco’s Software Download website
for the following NX-OS software releases:

  • nine.three(iv) and afterwards

  • 9.2(4)

  • 7.0(3)I7(8) and later



Notation

The MD5/SHA512 checksum published on
Cisco’s Software Download website
for a compact NX-OS software prototype may not match the MD5/SHA512 checksum of a compact image created through the NX-OS Meaty Epitome process.



Compact Image to be Run for Dissimilar Switch Models

The following table describes the appropriate compact image to be run for each applicable model of switch, using NX-OS software release
ix.3(6)
equally an example.

Table one.

Meaty Paradigm Table for Each Cisco Nexus 3000, 3100, and 3500 Series Platform

Switch Model Number

Meaty NX-OS Software Image Filename

N3K-C3016Q-40GE

n3000-compact.9.3.6.bin

N3K-C3048TP-1GE

n3000-compact.ix.iii.6.bin

N3K-C3064PQ-10GX

n3000-compact.ix.3.6.bin

N3K-C3064TQ-10GT

n3000-compact.9.iii.6.bin

N3K-C3064TQ-32T

n3000-compact.9.iii.half dozen.bin

N3K-C3132Q-40GE

n3100-compact.ix.3.6.bin

N3K-C3132Q-40GX

n3100-compact.9.3.6.bin

N3K-C3172PQ-10GE

n3100-meaty.9.3.6.bin

N3K-C3172TQ-10GT

n3100-compact.9.iii.6.bin

N3K-C3172TQ-32T

n3100-compact.9.3.half dozen.bin

N3K-C3524P-10G

n3500-compact.9.three.6.bin

N3K-C3524P-10GX

n3500-compact.nine.3.half dozen.bin

N3K-C3548P-10G

n3500-compact.9.three.vi.bin

N3K-C3548P-10GX

n3500-compact.9.3.6.bin



NX-Os Compact Paradigm Procedure

There are two means to initiate the NX-Bone Compact Image process. The post-obit subsections depict each option in further detail.


NX-Bone Compact Image Procedure on Bootflash/USB

Starting with NX-OS software release vii.0(iii)I3(1), you tin use the install all command with the meaty option to initiate the NX-OS Meaty Image procedure on an image stored in the switch’southward bootflash or an attached USB bulldoze. This can also exist performed on an NX-OS software image that the switch is currently booted from – yet, a minimum of 750MB of free space on the switch’s bootflash is required to compact the currently booted prototype.

An example of how to initiate the NX-OS Meaty Image procedure on an NX-Os software image stored on the switch’s bootflash is as follows:

switch#

install all nxos booftflash:nxos.7.0.3.I7.viii.bin compact



NX-OS Compact Paradigm Procedure Through SCP

Starting with NX-OS software release 7.0(three)I5(ii), the NX-OS Compact Epitome procedure tin can be initiated while copying the image to the switch’south bootflash or an fastened USB drive with SCP (Secure Copy Protocol) using an additional pick in the copy command. The compact option in the re-create control overrides the bootflash space limitation as the epitome is compacted at the time of transferring the image to the switch’s bootflash or an attached USB drive. This option is simply supported with SCP – other protocols (such as SFTP [Secure File Transfer Protocol] and FTP [File Transfer Protocol]) are not supported.

An example of how to initiate the NX-Os Compact Image process while copying an NX-OS software image to the switch’s bootflash through SCP is as follows:

switch#

copy scp://[email protected]/nxos.vii.0.three.I7.8.bin bootflash:nxos.7.0.3.I7.8.bin meaty vrf management



NX-OS Meaty Image Process Sequence

The sequence of compacting NX-Os software images is of import. Yous cannot compact the currently loaded NX-OS software image if you have another NX-Os software image present on the bootflash due to the limited bootflash size of the switch.

First, y’all should compact the currently booted image on the bootflash using the NX-Os Compact Epitome Procedure on Bootflash/USB method previously described. Side by side, you should copy the desired NX-Bone software image to the switch’s bootflash using the NX-Os Meaty Paradigm Process through SCP method previously described, if possible. If this option is not possible, because you are upgrading to an NX-OS software release prior to 7.0(3)I5(2), you should copy the desired NX-OS software paradigm to the switch’s bootflash normally, then utilize the NX-OS Compact Prototype Procedure on Bootflash/USB method previously described to meaty the image.

The minimum required free infinite to compact a non-booted epitome is 450MB of gratuitous space on the switch’s bootflash. If the free space available on the switch’south bootflash is less than 450MB after copying the target image, then the target epitome needs to be compacted using an attached USB drive or through the NX-OS Compact Image Procedure through SCP method previously described.



NX-OS Compact Image Platform Groups

The NX-OS Compact Image procedure described in this certificate is applicative to three separate platform groups:

  • Nexus 3000 devices (N3K-C3048, N3K-C3064, and and so on)

  • Nexus 3100 devices (N3K-C3132, N3K-C3172, and and so on)

  • Nexus 3500 devices (N3K-C3524, N3K-C3548, and so on)

A compacted NX-OS binary image file can exist re-used among other devices within the aforementioned platform grouping. Notwithstanding, a meaty NX-Bone binary image file cannot exist used on devices that belong to a different platform group.

For example, consider a scenario where you have iv Nexus 3000 devices of the post-obit models:

  • N3K-C3048TP-1GE

  • N3K-C3064PQ-10GE

  • N3K-C3172PQ-40GX

  • N3K-C3548P-10G

An NX-Os binary image file compacted on the N3K-C3048TP-1GE can be transferred directly to the bootflash of the N3K-C3064PQ-10GE through a file transfer protocol of your pick (provided there is enough room on the N3K-C3064PQ-10GE). Furthermore, the N3K-C3064PQ-10GE can be upgraded with the use of this compact NX-Bone binary image file through a supported method. Yet, the same compact NX-Os binary image file cannot be used to upgrade the N3K-C3172PQ-40GX and N3K-C3548P-10G devices. The NX-OS Compact Paradigm process must be executed on both N3K-C3172PQ-40GX and N3K-C3548P-10G devices separately.

This compatibility betwixt Nexus devices within the aforementioned platform group tin be used to optimize the NX-Bone software upgrade of a large number of devices. For example, if you have 100 N3K-C3048TP-1GE devices, you tin use the NX-Os Compact Image procedure on a single device, then transfer the compact NX-Bone binary image file to the resulting 99 devices. There is no need to perform the NX-Os Compact Epitome process on all 100 devices.

Read:  Upgrade Firmware Android Tv Box Mxq Pro UPDATED



Booting the Switch from the USB

An option is provided to kick the switch from the USB using a loader prompt. For example:

              loader>
                
                  kick usb1:nxos.9.2.i.bin
                
              
            



Upgrading the BIOS and Power Sequencer Images

Changes to BIOS and power sequencers are rare; however, when they occur, they are included in the Cisco NX-Os epitome, and the BIOS and power sequencer are upgraded. The summary displayed by the installer during the installation process indicates the current version of the BIOS and power sequencer and the target version.



Note

Afterward a successful power sequence upgrade, you must switch off the power to the organization and then power information technology upwards.



BIOS Upgrade

See the following guidelines for the BIOS upgrade:

Cisco Nexus 3000 Series platforms require a BIOS upgrade to load Release 7.0(iii)I2(ane) or afterwards images. But BIOS versions 3.ten.x are compatible with Release 7.0(3)I2(1) and later releases on all Cisco Nexus 3000 Series switches. This is taken care in the regular

install all

method of upgrade simply it needs to be explicitly upgraded prior to the fast-reload upgrade.

Only after the BIOS upgrade is complete, it allows the system to perform fast-reload to the newer releases.



BIOS Versions for Each Cisco Nexus 3000 Series Platform

See the following BIOS versions for each Cisco Nexus 3000 Series platform.

Table 2.

BIOS Versions Table for Each Cisco Nexus 3000 Series Platform

Sr.No.

Switch Proper noun

Switch Model

Latest BIOS version

1.

Cisco Nexus 3132Q switch

C3132Q-40GE

5.2.0

ii.

Cisco Nexus 3132Q-10 switch

C3132Q-40GX

v.ii.0

3.

Cisco Nexus 3172PQ switch

C3172PQ-10GE

5.2.0

4.

Cisco Nexus 3172CR switch

C3172PQ-10GE

5.two.0

5.

Cisco Nexus 3064-10 switch

C3064PQ-10GX

5.2.0

6.

Cisco Nexus 3064-TQ switch

C3064TQ-10GT

5.0.0

vii.

Cisco Nexus 3016Q switch

C3016Q-40GE

v.0.0

8.

Cisco Nexus 3064-East switch

C3064PQ-10GE

five.0.0

nine.

Cisco Nexus 3064PQ switch

C3064PQ-FA

five.0.0

ten.

Cisco Nexus 3048TP switch

C3048TP-1GE

5.0.0



Guidelines for Upgrading in Fast-Reload Scenarios

Procedure


Upgrade to a new release using fast-reload. Using fast-reload after the BIOS upgrade or using

install all


are the simply supported methods of upgrading to a Cisco NX-Os 9.x release. For example:

                switch#
                    fast-reload nxos bootflash:nxos.ix.ii.one.bin
                  
                
              

Example:

Annotation

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




Guidelines for Upgrading in Non-Fast Reload Scenarios

Consummate the post-obit steps in the given sequence to upgrade to Cisco NX-OS Release 9.x when y’all are non using fast-reload:

Procedure


Perform

install all

to upgrade BIOS and as well upgrade the NX-OS paradigm to Cisco NX-OS Release 9.x. Upgrade the Cisco NX-OS software using the

install all nxos bootflash:
filename
[no-reload
|
not-disruptive
|
not-interruptive
|
series]

control.

Instance:

                switch#
                  
                    install all nxos bootflash:nxos.9.2.1.bin
                  
                
              

The following options are available:

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

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

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

  • series—Upgrades the line cards in the arrangement i at a time. (By default, the line cards are upgraded in batches to save time.)

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




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 betwixt the current running release and the target release.


Management Services Subsequently an Upgrade

Earlier the switch is reset for an upgrade, inband and management ports are brought down and are brought back up afterward the upgrade completes. Services that depend on the inband and direction 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 asunder and demand 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 Direction services are disabled during this fourth dimension, this beliefs 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 take an HTTP sessions.

NTP

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



Layer-2 Protocols Affect

The following tabular array lists the upgrade impacts to Layer 2 protocols.

Table 4.

Upgrade Touch to Layer 2 Protocols

Protocol

Description

LACP

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

IGMP

IGMP does non 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 betwixt 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 fourth dimension.

CDP

During an upgrade, the time-to-alive 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 forestall neighbor switches from mark routes to the upgrade switch as down. Any topology changes during this time are besides 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 country. After the upgrade reboot and a stateful restart, the light amplification by stimulated emission of radiation is turned dorsum on. This action prevents the link state from transitioning from downwardly to up during an upgrade.



Pre-Installation Checks

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

  • Enter the

    bear witness incompatibility

    command to verify that the target paradigm is feature-wise compatible with the current image.

  • Enter the

    show logging level

    control to ensure that the severity level for all processes is set to 5 or below.

  • Enter the

    show install all touch on

    command to identify the upgrade impact.

  • Enter the

    install all

    command to update to the latest Cisco NX-OS software.

  • Review the installer bear on 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

    prove install all status

    command to verify the status of the installation

The following table lists the evidence commands that identify the bear on 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.


prove logging level

Displays the facility logging severity level configuration.

Logging levels for all processes must exist 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 data 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 tin can as well perform the post-obit tasks to identify potential issues earlier they occur:

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

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

                    switch#
                      
                        evidence incompatibility organisation pcco.s
                      
                      No incompatible configurations
                  
  • Verify the touch on of the upgrade.

                    switch#
                      
                        show install all impact nxos bootflash:nxos.9.two.1.bin
                      
                    
                  



Information Most Fast Reboot

During fast reboot, the image that runs on the CPU reloads the new image and runs it without a CPU or firmware reset. Although there is a brief disruption in traffic during fast reboot, it enables a switch to reload faster than during common cold reboot.

Cisco NX-OS software allows you to use fast reboot in a non-interruptive style. In this style, fast reboot begins the installation process without any prompts. In this release, fast reboot also supports BGP svelte restart (GR) for compatible peers. Y’all can trigger a fast reboot with graceful restart past using the

trigger-gr

option.


Fast Reboot Timing Requirements

Fast reboot has the following timing requirements for the configurations that it supports:

  • Time taken to reset the ASIC and disrupt the data plane subsequently control airplane disruption—Less than 90 seconds, when the command aeroplane is disrupted.

  • Time taken to resume forwarding traffic—Less than 30 seconds from ASIC reset.



Fast Reboot Guidelines

Fast reboot is supported merely with express configurations and topologies. Some of supported configurations and guidelines are listed in this section. When reloading system software past using the

fast-reload

control, employ the supported follow these guidelines:

  • Configuration changes—You cannot enter configuration mode during a reload or an upgrade. You lot should save, commit, or discard any active configuration sessions before upgrading or downgrading the Cisco NX-OS software epitome. The active configuration session is deleted without a alert during a reload.

    Use the

    testify configuration session summary

    command to verify that there are no active configuration sessions.

                      switch#
                        
                          bear witness configuration session summary
                        
                        There are no active configuration sessions
                    

    Ensure that you check the compatibility of configurations earlier using the

    fast-reload

    command.



    Note

    Do non apply the

    fast-reload


    command for upgrades that may pb to kernel or BIOS changes.


    For more than information on configuration sessions, see the
    Cisco Nexus 3000 Serial NX-OS System Management Configuration Guide.



    Note

    The CLI and SNMP configuration alter requests are denied.


  • Topology—You should make topology changes such as Spanning Tree Protocol (STP) before you perform an upgrade. You should perform module installations or removals only before or afterwards an upgrade. However, you should non make changes to the Layer ii and routing topologies, and the default root bridge should not be configured.

  • Scheduling—Y’all should upgrade when your network is stable and steady. Ensure that anybody who has access to the switch or the network is not configuring the switch or the network during this time. You lot cannot configure a switch during an upgrade.

  • Space—Verify that sufficient space is available in the location where you are copying the images. The internal bootflash requires approximately 650 MB of free space.

  • Hardware—Avoid ability interruptions during an installation procedure. Power interruptions can corrupt the software image.

  • Connectivity to remote servers—Configure the IPv4 address or IPv6 address for the x/100/1000 BASE-T Ethernet port connection (interface mgmt0). Ensure that the switch has a route to the remote server. The switch and the remote server must be in the aforementioned subnetwork if you do not have a router to route traffic betwixt subnets.

  • Link Assemblage Control Protocol (LACP) fast timers—To permit fast-reload, ensure that LACP fast timers are not configured.

  • Recollect compatible images in one of two ways:

    • Locally—Images are locally available on the switch.

    • Remotely—Images are in a remote location and you specify the destination using the remote server parameters and the filename to exist used locally.

  • Control—Utilise the post-obit commands to prepare for and install the new software:

    • Use the

      ping

      command to verify connectivity to the remote server.

    • Utilise the

      dir

      command to verify the required space is available for the prototype files to be copied.

    • Use the

      evidence install all impact

      control to identify the upgrade touch on. This command besides displays whether the upgrade is disruptive or the reason why the upgrade is disruptive, whether the switch needs to be rebooted, and the reason why it needs to exist rebooted.



    Notation

    Nosotros recommended that y’all log in to the console port to begin the upgrade process.


  • Between control aeroplane disruption and data plane disruption, the CPU stops responding.

  • Configuration—Fast reboot currently supports the following configuration:

    • BGP v4 and v6

    • sixteen-way ECMP

    • 48 downlink L2 ports

    • iv SVIs

    • Less than x VLANs

    • 2000 v4 routes and 2000 v6 routes

    • RACLs

    • ARPs

    • STP edge port configuration

  • Repaved fast-reload also supports the change in configurations that earlier required a complete reload, for example, portmode contour, URPF enable/disable, and TCAM re-etching.

  • Do non utilize the

    fast-reload

    pick for upgrade to/from a version that has reached EOL.

  • The fast reload feature besides supports the change in the configurations that earlier required a complete reload, for case, portmode profile, URPF enable/disable, and TCAM re-carving.

  • Fast reload does non upgrade the BIOS.

  • If you lot upgrade from a Cisco NX-OS release that does not support the CoPP feature to a release that does back up the CoPP feature, you lot must run the setup utility later on the upgrade to enable CoPP on the device.

  • Fast reload upgrades are supported from Cisco NX-Os Release 7.0(3)I7(four) or 7.0(iii)I7(5) to a Cisco NX-OS ix.ten release.

  • If you downgrade to a release lower than Cisco NXOS release 6.0(two)U2(ane) using the

    install-all

    control, fast reload does non work.

Read:  How Do I Upgrade Tf201 Firmware Manually UPDATED



Using the Fast-Reload Command

The

fast-reload

command reloads Cisco Nexus 3000 or Nexus 3100 Series switches faster than the

reload

control.

ASCII configuration based fast-reload is also supported in improver to the PSS/binary configuration based fast-reload. The Cisco Nexus 3000 Series switches exercise not go through a complete reset with fast reload. The boards of Cisco Nexus 3000 and 3100 Serial switches have two reset domains. The reset domain 1 contains the CPU, the Platform Controller Hub (PCH), the Management Ethernet controller, the PCI bridge, the OBFL, the USB, and the Fan Controller. The reset domain 2 contains the ASIC, the PHY retimers, the SFP+ modules, and the QSFP modules. Fast reload resets merely the reset domain ii and at that place is no reset of CPU, reload of BIOS, and firmware.

Later on you run the

fast-reload

command, the following sequence of events have place:

  1. The switch loads the NXOS software image and upgrades the kernel. All applications undergo a stateless cold reboot and they are restarted through the startup configuration.

  2. The control plane is disrupted. During control plane disruption, all control protocol communication stops. Control plane disruption is always less than 90 seconds.

  3. After the command aeroplane disruption, all command airplane applications undergo a stateless cold reboot and practice not retain their land. The new configuration is applied when the switch reloads.

  4. The data plane is disrupted. Data plane disruption is always less than xxx seconds.

  5. On the forwarding airplane, all links go unavailable and the data plane does not retain its state later on reload. Traffic forwarding is resumed inside less than 30 seconds.



Note

Ensure that you have a working image and that you analyze the impact of the fast reboot functioning before using this control.



Fast Reload in PSS/Binary Configuration

Procedure


Step ane

Log in to the switch.

Step 2

To perform fast reboot on Cisco Nexus 3000 and 3100 Series switches, apply the post-obit command:

fast-reload
[salve-config] [trigger-gr] [nxos bootflash:
nxos-epitome-name] [non-interruptive] control to perform a fast reload.




Fast Reload In ASCII Configuration

ASCII configuration based fast-reload is also supported in addition to the PSS/binary configuration based fast-reload.



Note

The re-create file startup and fast reload are supported only for specific configurations, namely Layer 3 ports with port channels, eBGP, and a few physical l2 ports having SVI only towards the hosts.


To utilize ASCII-file based fast reload, use the following command:


copy
configuration-file
startup-config


fast-reload nxos bootflash:
nxos-image-name

The

configuration-file

is an ASCII file that contains the arrangement configurations that fast reload uses on upgrade or fast reload. Information technology tin be copied from the remote location also. If the NXOS software prototype is non specified, the image existing on the switch is reloaded. If the NXOS software paradigm provided is a higher version than the existing version, an upgrade is triggered.



Note

To ensure that subsequent fast reboot operations, apply the NXOS software image every bit the kicking variables, specify the save-config choice while running the fast-reload command. If the save-config option is non specified, the fast-reload command does not salve the boot variables.




Fast Reload Upgrade

Yous can perform a faster reload and upgrade to a newer release with minimal data reanimation compared to install all control.

The characteristic is similar to existing fast-reload support on Cisco Nexus 3000 Serial switches from Release 6.0(two)U2(i) onwards with a few additional steps to upgrade BIOS before upgrading to Release 7.0(3)I2(1) or afterward releases.



Caution

The fast-reload to Release 7.0(three)I2(one) is supported only from Release six.0(2)U6(3a) or later releases, subsequently the BIOS has been upgraded. Using fast-reload from Release 6.0(two)U6(3a) to Release vii.0(3)I2(1) without upgrading the BIOS will effect in the switch non booting up. See BIOS upgrade for more than information.




Note

If guest beat or whatever virtual-services are enabled, the

install all

command should be used. Use the

bear witness virtual-service list

command to verify the presence or the land of the guest shell or any virtual services..




Enabling BGP Svelte Restart with Fast Reboot

Cisco NX-OS software allows you to enable BGP graceful restarts (GR) with fast reboot. You can now use the

fast-reload trigger-gr

command to enable BGP GR. Use this command simply when all BGP peers are GR-capable.

To enable BGP GR with fast reboot on Cisco Nexus 3000 and 3100 Series switches, utilise the following command:


fast-reload
[relieve-config] [trigger-gr] [nxos bootflash:nxos-image-proper name] [non-interruptive] command to perform a fast reload.

              switch#
                  
                    fast-reload trigger-gr nxos bootflash:nxos.9.2.1.bin non-interruptive
                
              
            



Upgrading and Downgrading Using Fast Reboot


Upgrading Using Fast Reboot

You tin can upgrade the software on a switch by using fast reboot. To upgrade, you must specify the NXOS software epitome.

Earlier You Brainstorm

Ensure that the version of the NXOS software image specified in the fast-reload control is higher than the version of the epitome currently existing on the switch.

              switch#
                
                  fast-reload nxos bootflash:nxos.9.2.1.bin
                
              
            



Downgrading Using Fast Reboot

Downgrading the system software by using fast reboot is not supported. To downgrade the image software, use the

install all

command instead of fast reboot.


Using the Install All Command

The

install all

command triggers a disruptive software install on Cisco Nexus 3000 and Nexus 3100 Series switches. The post-obit images are upgraded during the installation:

  • The NXOS software image

  • System BIOS

  • Ability sequencers on the system

The

install all

command provides the following benefits:

  • You can upgrade the Cisco Nexus 3000 Serial switches by using just ane command.

  • You can receive descriptive information well-nigh the intended changes to your organisation before y’all continue with the installation. For example, information technology identifies potential disruptive upgrades.

  • You can go on or abolish the upgrade when you see this question (the default is no):

                          Do yous desire to go on (y/due north) [n]: y
                        
  • Yous can also use the

    install all


    non-interruptive

    control to install a new paradigm without any prompts.

  • The command automatically checks the image integrity, which includes the NXOS software image.

  • The command performs a platform validity check to verify that a incorrect image is not used.

  • Pressing Ctrl + C gracefully ends the

    install all

    command. The command sequence completes the update step in progress and returns to the EXEC prompt.

  • Afterwards inbound the

    install all

    control, if whatever step in the sequence fails, the upgrade ends.

  • The following bulletin appears to warn y’all about the impact of upgrading the power sequencer:

                          Warning: please do not remove or power off the module at this fourth dimension.
                        
                          Note: Ability-seq upgrade needs a power-cycle to take into effect.
                        


Note

After a successful ability sequence upgrade, you must switch off the power to the organization and and then power information technology up.




Using the Install All Non-Interruptive Command

Cisco NX-OS software supports the use of non-interruptive

install all

command. You can now employ the

install all
non-interruptive

command to install a new image without whatsoever prompts.

To perform a not-interruptive install all on Cisco Nexus 3000 and 3100 Series switches, use the following command:


install all
nxos bootflash: [nxos-prototype-proper noun] [non-interruptive]

                  switch#
                    
                      install all nxos bootflash:nxos.ix.two.1.bin
                    
                  
                



Upgrading Procedures

The upgrade process is triggered when you enter the

install all

command. This department describes the sequence of events that occur when yous upgrade a single Cisco Nexus 3000 Series switch.



Note

If you take a release prior to Release seven.0(iii)I2(1), upgrade to Cisco Nexus 3000 Release half dozen.0.2.U6(3a) kickoff and and then upgrade to Release vii.0(3)I2(1) or afterward releases.




Notation

During the compatibility bank check, the following ISSU-related messages might appear in the Reason field:


Table 6.

ISSU- related messages

Reason Field Message — in Cisco NX-Os Release 7.0(3)I3(1)

Reason Field Message — in Cisco NX-Os Release 7.0(three)I4(1) or a Later on Release

Description

Incompatible paradigm

Incompatible paradigm for ISSU

The Cisco NX-OS image to which y’all are attempting to upgrade does not support ISSU.

Hitless upgrade is not supported

Default upgrade is non hitless

By default, the software upgrade process is disruptive. You must configure the not-confusing choice to perform an ISSU.


Installation At-A-Glance

The following table shows an overview of the upgrade process.

Table 7.

Upgrade Process At-A-Glance

Upgrade Preparation

  1. Log into the beginning Cisco Nexus 3000 Series switch. We recommend that you log into the console port. In vPC topologies, the starting time upgrade tin can exist performed on either the primary or secondary switch in the topology.

  2. Log into Cisco.com to admission the Software Download Eye. To log into Cisco.com, become to
    https://www.cisco.com
    and click Log In at the top of the folio. Enter your Cisco username and password.

  3. Choose and download the software image to the server.

  4. Verify that the required space is bachelor in the bootflash: directory for the image file(due south) to be copied.

  5. If you need more than space in the bootflash: directory, delete unnecessary files to make infinite available.

  6. Re-create the Cisco NX-OS software image to the bootflash using a transfer protocol such as ftp:, http:, https:, tftp:, scp:, or sftp. Case:

                              switch#
                                
                                  copy scp://[email protected]//download/nxos.9.iii.i.bin bootflash:nxos.9.3.i.bin
                                
                              
                            

    To reduce the software image size during the copy execution, utilise the

    compact

    keyword. Y’all must employ SCP, HTTP, or HTTPS equally the source and bootflash or USB as the destination. The post-obit example uses SCP and bootflash:

                              switch#
                                
                                  copy scp://[email protected]//download/nxos.9.3.5.bin  bootflash:nxos.9.iii.5.bin compact vrf direction apply-kstack
                                
                                [email protected]'s password: nxos.9.3.five.bin 100% 1887MB six.6MB/due south 04:47 Copy complete, now saving to deejay (delight wait)... Copy complete.
                              
                            
    Annotation

    Software prototype compaction is simply supported on SCP, HTTP, or HTTPS. If you attempt compaction with any other protocol, the arrangement returns the following error:

                                        Meaty option is allowed merely with source equally scp/http/https and destination as bootflash or usb
                                      
    Notation

    Compacted images are non supported with LXC boot fashion.

  7. Compare the file sizes of the images that were transferred using the

    dir

    bootflash

    command. The file sizes of the images obtained from
    https://www.cisco.com
    and the image sizes of the transferred files should be the same.

  8. Complete these steps for each switch in the topology.

Pre-upgrade Checks

  1. Enter the

    bear witness incompatibility

    command to verify that the target epitome is feature-wise compatible with the current paradigm.

  2. Enter the

    show install all impact

    command to identify the upgrade impact.

Upgrade Begins

  1. Enter the

    install all

    command to update to the latest Cisco NX-Os software.

  2. Peruse the installer impact assay and accept to proceed.

  3. The installer upgrades the software.

Upgrade Verification

  1. Enter the

    prove install all status

    command to verify the status of the installation.



Copying the Running Configuration from an External Flash Memory Device

You tin can copy configuration files from an external wink memory device.

Earlier you brainstorm

Insert the external wink memory device into the agile supervisor module.

Procedure

Command or Action Purpose
Step one

(Optional)

dir{usb1😐usb2:}[directory/]

Example:

                        switch#
                          
                            dir usb1:
                          
                        
                      
(Optional)

Displays the files on the external wink memory device.

Step 2


copy{usb1😐usb2:}[directory/] filename{bootflash:}[directory/] filename

Example:

                        switch#
                          
                            copy usb1:pcco.yard bootflash:pcco.k
                          
                        
                      

Copies the image from an external wink memory device into the bootflash. The filename argument is case sensitive.

Stride three


copy{usb1😐usb2:}[directory/] filename
running-config

Example:

                        switch#
                          
                            copy usb1:dsn-config.cfg running-config
                          
                        
                      

Copies the running configuration from an external flash retentiveness device. The filename argument is example sensitive.

Step 4

(Optional)

bear witness running-config

Example:

                        switch#
                          
                            show running-config
                          
                        
                      
(Optional)

Displays the running configuration.

Footstep 5

(Optional)

copy running-config startup-config

Example:

                        switch#
                          
                            copy running-config startup-config
                          
                        
                      
(Optional)

Copies the running configuration to the startup configuration.



Copying the Startup Configuration from an External Flash Memory Device

Y’all tin can recover the startup configuration on your Cisco NX-OS device past downloading a new startup configuration file saved on an external wink memory device.

Before you begin

Insert the external flash memory device into the agile supervisor module.

Procedure

Command or Action Purpose
Step 1

(Optional)

dir{usb1😐usb2:}[directory/]

Example:

                        switch#
                          
                            dir usb1:
                          
                        
                      
(Optional)

Displays the files on the external flash memory device.

Step ii


re-create{usb1😐usb2:}[directory/] filename{bootflash:}[directory/]filename

Example:

                        switch#
                          
                            copy usb1:pcco.yard bootflash:pcco.one thousand.
                          
                        
                      

Copies the prototype from an external flash memory device into the bootflash. The filename argument is case sensitive.

Step 3


copy{usb1😐usb2:}[directory/] filename
startup-config

Example:

                        switch#
                          
                            copy usb1:dsn-config.cfg startup-config
                          
                        
                      

Copies the startup configuration from an external flash retentiveness device. The filename argument is case sensitive.

Step four

(Optional)

evidence startup-config

Example:

                        switch#
                          
                            show startup-config
                          
                        
                      
(Optional)

Displays the startup configuration.

Step five

(Optional)

copy running-config startup-config

Example:

                        switch#
                          
                            copy running-config startup-config
                          
                        
                      
(Optional)

Copies the running configuration to the startup configuration.



Upgrade Process in a Non-vPC Topology

The following list summarizes the upgrade procedure in a not-vPC topology:

  1. The

    install all

    command triggers the installation upgrade.

  2. The compatibility checks brandish the bear upon of the upgrade.

  3. The installation proceeds or not based on the upgrade bear on.

  4. The current state is saved.

  5. The system unloads and runs the new epitome.

  6. The stateful restart of the system software and application occurs.

  7. The installer resumes with the new image.

  8. The installation completes.

The post-obit example displays the upgrade process:

                switch#
                  
                    install all nxos bootflash:<nxos-prototype-name>
                  
                
              



Upgrade Process for vPCs


Upgrade Procedure for a vPC Topology on the Primary Switch

The following list summarizes the upgrade process on a switch in a vPC topology that holds either the Chief or Operational Primary vPC roles. Steps that differ from a switch upgrade in a not-vPC topology are in bold.



Note

In vPC topologies, the two peer switches must be upgraded individually. An upgrade on one peer switch does not automatically update the vPC peer switch.


  1. The install all command issued on the vPC primary switch triggers the installation upgrade.

  2. The compatibility checks display the bear on of the upgrade.

  3. The installation proceeds or non based on the upgrade impact.

  4. The configuration is locked on both vPC peer switches.

  5. The electric current state is saved.

  6. The system unloads and runs the new image.

  7. The stateful restart of the arrangement software and application occurs.

  8. The installer resumes with the new image.

  9. The installation is complete.

When the installation is complete, the vPC main switch is upgraded.



Note

The vPC principal switch is running the upgraded version, and the vPC secondary switch is running the original software version.




Upgrade Process for a vPC Topology on the Secondary Switch

The following listing summarizes the upgrade process on a switch in a vPC topology that holds either the Secondary or Operational Secondary vPC roles. Steps that differ from a switch upgrade in a non-vPC topology are in assuming.

  1. The install all command issued on the vPC secondary switch triggers the installation upgrade.

  2. The compatibility checks display the affect of the upgrade.

  3. The installation proceeds or non based on the upgrade affect.

  4. The current state is saved.

  5. The system unloads and runs the new paradigm.

  6. The stateful restart of the system software and awarding occurs.

  7. The installer resumes with the new image.

  8. The configuration is unlocked on the main and secondary switches.

  9. The installation is complete.



vPC Upgrade and Downgrade Process

In vPC topologies, the two peer switches normally must exist upgraded individually. An upgrade on one peer switch does not automatically update the vPC peer switch.

However, Cisco NX-OS Releases 7.0(3)F3(3c) and 7.0(3)F3(4) are non compatible with Cisco NX-OS Release 9.2(10) for vPC peer switches. Both vPC peers must exist upgraded simultaneously to Cisco NX-OS Release 9.2(x) to avoid ane switch running a seven.0(3)F3(x) release and the other switch running 9.two(10). Optionally, if the switches are being upgraded from Cisco NX-OS Release 7.0(iii)F3(4), y’all tin can employ the following procedure to minimize the traffic impact during upgrade.

  1. Switch A and B are running a Cisco NX-OS release. Switch A is the main switch, and switch B is the secondary switch. Use the

    re-create r s

    control on both switches.

                      
                        primary_switch# show vpc role vPC Role status ---------------------------------------------------- vPC role : primary  vPC organization-mac : 00:23:04:ee:be:64  vPC organization-priority : 32667 vPC local system-mac : 70:df:2f:eb:86:1f  vPC local role-priority : 90  vPC peer system-mac : seventy:df:2f:eb:1c:ab  vPC peer role-priority : 100  primary_switch#  secondary_switch# evidence vpc part vPC Office status ---------------------------------------------------- vPC role : secondary  vPC organisation-mac : 00:23:04:ee:exist:64  vPC arrangement-priority : 32667 vPC local system-mac : 70:df:2f:eb:1c:ab  vPC local role-priority : 100  vPC peer system-mac : seventy:df:2f:eb:86:1f  vPC peer part-priority : xc  secondary_switch#   primary_switch# copy r southward v [########################################] 100% Copy complete.   secondary_switch# copy r s v [########################################] 100% Copy consummate.
                      
                    
  2. Bring down the peer link (PL) on the main switch. The secondary switch brings down its vPC legs.

                      
                        primary_switch# conf t Enter configuration commands, one per line. Cease with CNTL/Z. primary_switch(config)# int port-channel 100 primary_switch(config-if)# shutdown    Reload the secondary switch with Release nine.ii.i image (change bootvar /reload)   secondary_switch(config)# boot nxos nxos.9.2.1.bin Performing image verification and compatibility cheque, please look.... secondary_switch(config)#  secondary_switch(config)# copy r southward five [########################################] 100% Copy complete.     secondary_switch# reload This command will reboot the system. (y/due north)? [n] y    After reload ---------------------  secondary_switch# evidence vpc Legend: (*) - local vPC is down, forwarding via vPC peer-link vPC domain id : 100  Peer status : peer link is downward  vPC proceed-alive status : peer is live  Configuration consistency status : failed  Per-vlan consistency status : success  Configuration inconsistency reason: Consistency Bank check Not Performed Type-2 inconsistency reason : Consistency Check Non Performed vPC role : none established  Number of vPCs configured : 20  Peer Gateway : Enabled Dual-active excluded VLANs : - Svelte Consistency Check : Disabled (due to peer configuration) Auto-recovery status : Disabled Delay-restore condition : Timer is off.(timeout = 90s) Delay-restore SVI status : Timer is off.(timeout = 10s) Operational Layer3 Peer-router : Disabled vPC Peer-link condition --------------------------------------------------------------------- id Port Status Active vlans  -- ---- ------ ------------------------------------------------- 1 Po100 downward -   secondary_switch#   primary_switch(config-if)# evidence vpc  Legend: (*) - local vPC is down, forwarding via vPC peer-link vPC domain id : 100  Peer condition : peer link is down  vPC keep-alive status : peer is alive  Configuration consistency status : success  Per-vlan consistency status : success  Type-2 consistency status : success  vPC function : primary  Number of vPCs configured : xx  Peer Gateway : Enabled Peer gateway excluded VLANs : - Dual-active excluded VLANs and BDs : - Graceful Consistency Check : Enabled Auto-recovery status : Enabled, timer is off.(timeout = 240s) Operational Layer3 Peer-router : Disabled vPC Peer-link condition --------------------------------------------------------------------- id Port Condition Agile vlans  -- ---- ------ -------------------------------------------------- 1 Po100 downwardly -
                      
                    
  3. Configure vPC auto-recovery under the vPC domain on the secondary switch. Enable

    vpc upgrade

    (exec command).

                      
                        secondary_switch(config)# vpc domain 100 secondary_switch(config-vpc-domain)# auto-recovery  secondary_switch(config-vpc-domain)# terminate  secondary_switch# prove running-config vpc !Control: show running-config vpc !Running configuration last done at: Midweek May 16 06:34:10 2018 !Fourth dimension: Wed May 16 06:34:14 2018 version 9.two(1) Bios:version 01.11  characteristic vpc vpc domain 100 peer-switch role priority 100 peer-keepalive destination x.1.31.30 source 10.1.31.29 filibuster restore xc peer-gateway motorcar-recovery ipv6 nd synchronize ip arp synchronize interface port-channel100 vpc peer-link interface port-channel2001 vpc 101    secondary_switch# evidence vpc upgrade vPC upgrade : True SVI Timer : 0 Delay Restore Timer : 0 Delay Orphan Port Timer : 0 secondary_switch#  secondary_switch# show vpc upgrade   >> Hidden command  vPC upgrade : Faux SVI Timer : 10 Filibuster Restore Timer : 90 Filibuster Orphan Port Timer : 0     secondary_switch# vpc upgrade   >> Hidden command
                      
                    
  4. Afterwards Layer 3 routes are learned on the secondary switch, reload the primary switch with the new release image. The secondary switch takes over the principal office and brings upwards its vPC legs in approximately 5 seconds.

                      
                        primary_switch(config)# show boot  Electric current Boot Variables: sup-1 NXOS variable = bootflash:/nxos.nine.ii.1.bin No module kick variable set Kicking Variables on next reload: sup-ane NXOS variable = bootflash:/nxos.ix.two.i.bin  No module boot variable fix primary_switch(config)# end  primary_switch# testify kick  Current Boot Variables: sup-1 NXOS variable = bootflash:/nxos.ix.two.1.bin No module boot variable set up Boot Variables on adjacent reload: sup-1 NXOS variable = bootflash:/nxos.9.2.1.bin  No module boot variable set primary_switch# reload This command will reboot the system. (y/northward)? [n] y   secondary_switch# show vpc Fable: (*) - local vPC is down, forwarding via vPC peer-link vPC domain id : 100  Peer status : peer link is down  vPC keep-alive status : peer is non reachable through peer-keepalive Configuration consistency status : failed  Per-vlan consistency status : success  Configuration inconsistency reason: Consistency Bank check Not Performed Type-two inconsistency reason : Consistency Check Non Performed vPC role : principal  Number of vPCs configured : xx  Peer Gateway : Enabled Dual-active excluded VLANs : - Graceful Consistency Check : Disabled (due to peer configuration) Auto-recovery status : Enabled, timer is off.(timeout = 240s) Delay-restore condition : Timer is off.(timeout = 0s) Filibuster-restore SVI status : Timer is off.(timeout = 0s) Operational Layer3 Peer-router : Disabled vPC Peer-link status --------------------------------------------------------------------- id Port Status Active vlans  -- ---- ------ ------------------------------------------------- i Po100 down - vPC status
                      
                    
  5. When the primary switch comes dorsum up, the peer link on information technology is operationally up.

                      
                        primary_switch# evidence vpc Legend: (*) - local vPC is downwardly, forwarding via vPC peer-link vPC domain id : 100  Peer status : peer adjacency formed ok  vPC keep-alive status : peer is alive  Configuration consistency status : success  Per-vlan consistency status : success  Blazon-two consistency status : success  vPC part : primary, operational secondary Number of vPCs configured : 20  Peer Gateway : Enabled Dual-active excluded VLANs : - Graceful Consistency Check : Enabled Motorcar-recovery status : Disabled Delay-restore status : Timer is off.(timeout = 90s) Delay-restore SVI status : Timer is off.(timeout = 10s) Operational Layer3 Peer-router : Disabled vPC Peer-link status --------------------------------------------------------------------- id Port Status Active vlans  -- ---- ------ ------------------------------------------------- one Po100 up 1,101-400
                      
                    

    For downgrade, reload both switches at the same time.



Monitoring the Upgrade Status

The following table lists the
testify
commands that are used to monitor installation upgrades.

Command

Definition

show install all failure-reason

Displays the applications that failed during an installation and why the installation failed.

show install all status

Displays a high-level log of the installation.

prove tech-support

Displays the system and configuration information that you lot can provide to the Cisco Technical Assistance Center when reporting a problem.



NX-OS Upgrade History

During the life of a Cisco Nexus 3000 switch, many upgrade procedures can be performed. Upgrades tin can occur for maintenance purposes or to update the operating system to obtain new features. Over fourth dimension, switches may be updated on numerous occasions. Viewing the types of upgrades and when they occurred tin can help in troubleshooting issues or merely understanding the history of the switch.

Outset with Cisco NX-OS Release 9.3(5), Cisco Nexus 3000 switches log all upgrade activity performed over time providing a comprehensive history of these events. The stored upgrade history types are:

  • Cisco NX-OS System Upgrades

  • Electronic Programmable Logic Device (EPLD) Upgrades

  • Software Maintenance Upgrade (SMU) Installations

View the Cisco NX-OS upgrade history by entering the

show upgrade history

control. The output displays whatever upgrade activity that previously occurred on the switch and defines the start and end times for each event. The following is an example output of the

show upgrade history

command:

            switch# show upgrade history Type                VERSION   DATE                    STATUS NXOS EPLD           n3000-    26 April 2020 11:37:16    EPLD Upgrade completed                     epld.9.3.4.img NXOS EPLD           n3000-    26 Apr 2020 11:32:41    EPLD Upgrade started                     epld.9.3.4.img NXOS system image   ix.iii(5)    24 Mar 2020 20:09:x    Installation End NXOS system image   9.3(5)    24 Mar 2020 20:05:29    Installation started NXOS SMU            9.3(5)    03 Mar 2020 23:34:15    Patch activation concluded for                                                        nxos.libnbproxycli_patch-n3k_                                                       ALL-1.0.0-nine.3.5.lib32_n3000.rpm NXOS SMU            9.3(5)    03 Mar 2020 23:34:03    Patch activation started for                                                        nxos.libnbproxycli_patch-n3k_                                                       ALL-i.0.0-9.three.5.lib32_n3000.rpm
            
          



Downgrading from a Higher Release

The procedure for entering the

install all

command to downgrade the switch is identical to using the

install all

command for a switch upgrade, except that the image files to be loaded are for an earlier release than the image that is currently running on the switch. You lot can utilize the

prove incompatibility system command

to ensure that there are no characteristic incompatibilities between the electric current release and the target release. Annotation that downgrades are disruptive.



Notation

Before yous downgrade to a specific release, cheque the release notes for the current release installed on the switch, to ensure that your hardware is compatible with the specific release. Come across the Cisco

Nexus 3000 Series Switch Release Notes


for details.




Note

The following limitation applies to Cisco Nexus platform switches that support Trust Ballast Module (TAM):

The TACACS global primal cannot exist restored when downgrading from Cisco NX-OS Release nine.3(3) to an earlier version. TAM was updated to version-7 in 9.3(3), just earlier NX-Bone versions used TAM version-iii.



Downgrading from a Higher Release to a Lower Release

This department contains an instance for downgrading from a higher release to a lower release.



Circumspection

Make certain that yous store the configuration file for subsequently use.


Complete the post-obit steps to downgrade:

Procedure


Step 1

Enter the

write erase

command.

Footstep 2

Enter the

write erase kicking

command.

Pace 3

Enter the

copy
Release half-dozen.0(2)U6(3a)-config

startup-config


command.

                        switch#
                          
                            copy downgrade startup-config
                          
                        
                      
Step iv

Enter the

install all

kickstart
img.kick

arrangement img.sys
no-save bios-force

control

Step 5

To verify whether the boot variables exist, enter the

show boot

command. If the boot variables do not exist, enter the following set of commands to update the kick variables manually:

                          switch#
                            
                              configure t
                            
                            switch (config)# boot kickstart <img.kick> switch (config)# boot system <img.sys> switch (config)# write run kickoff
                        
Notation

If lockup occurs on the switch, do a tftp boot.




Troubleshooting Installations

Some common causes for upgrade failure are as follows:

  • The bootflash: does not take enough space to accept the updated image.

  • The hardware is installed or removed while the upgrade is in procedure.

  • A power disruption occurs while an upgrade is in progress.

  • The unabridged path for the remote server location is not specified accurately.



How to Upgrade Firmware on Cx 3000

Check Also

Cara Flash Advan Hammer R3d

Cara Flash Advan Hammer R3d

Cara Flash Advan Hammer R3d Firmware Advan Hammer R3D (Sukses) Assalamu’alaikumSelamat Siang Oke Berjumpa Pun …