Table of Contents

n5000_upgrade_downgrade_521_n1_2a

Cisco Nexus 5000 Series NX-OS Software Upgrade and Downgrade Guide, Release 5.2(1)N1(2a)

First Published: October 23, 2012

Last Modified: February 8, 2017

This document describes how to upgrade or downgrade Cisco NX-OS software on Cisco Nexus 5000 Series switches and Cisco Nexus 2000 Series Fabric Extenders. Use this document in combination with documents listed in the “Obtaining Documentation and Submitting a Service Request” section.

This document includes these sections:

- Information About Software Images

- Supported Hardware

- Upgrade Guidelines

- Using the Install All Command

- In-Service Software Upgrades

- Supported Upgrade and Downgrade Paths for Cisco NX-OS Release 5.2(1)N1(2a)

- Upgrading Procedures

- Disruptive Installation Process

- Forcing an Upgrade

- Upgrading From Cisco NX-OS Release 5.0(2)N2(1a) and Earlier Releases (Disruptive Upgrade)

- Minimizing the Impact of a Disruptive Upgrade

- Monitoring the Upgrade Status

- Downgrading from a Higher Release

- Troubleshooting ISSUs and Disruptive Installations

- Obtaining Documentation and Submitting a Service Request

Information About Software Images

Cisco Nexus 5000 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 document to understand the guidelines, prerequisites, and procedures for upgrading the software. For updated information about the Cisco NX-OS software for the Cisco Nexus 5000 Series switch, see the Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Fabric Extender Release Notes.

The Cisco NX-OS software consists of the kickstart image and the system image. The system image includes the software for the Cisco Nexus 5000 Series switch and the Cisco Nexus 2000 Series Fabric Extenders (FEXs) that are connected to the switch. The images contain a major release identifier, a minor release identifier, and a maintenance release identifier, and they can also contain a rebuild identifier, which may also be referred to as a support patch. The following figure shows the version identifiers that are used with a combination of platform-independent and platform-dependent schemes for the Cisco NX-OS software.

Figure 1-1 Cisco NX-OS Version Identifier

The platform designator is N for the Nexus 5000 Series Switches, E for the Nexus 4000 Series Switches, and S for the Nexus 1000 Series Switches. Applicable features, functions, and fixes in the platform-independent code are present in the platform-dependent release.

Applicable fixes in the Cisco NX-OS Software Release 4.0(1a) are present in the 4.0(1a)N1(1a) release.

Supported Hardware

Cisco Nexus 5000 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 following sections:

Cisco Nexus 5000 Series Switches and Associated Expansion Modules

- Cisco Nexus 5000 2RU Chassis (N5K-C5020P-BF)

- Cisco Nexus 5000 1RU Chassis (N5K-C5010P-BF)

- Cisco Nexus 5000 Series Module 6-port 10 Gigabit Ethernet (N5K-M1600)

- Cisco Nexus 5000 Series Module 4x10GE 4xFC 4/2/1 (N5K-M1404)

- Cisco Nexus 5000 Series Module 6xFC 8/4/2/1 (N5K-M1060)

- Cisco Nexus 5000 Series Module 8xFC 4/2/1 (N5K-M1008)

Cisco Nexus 5500 Platform Switches and Associated Expansion Modules

- Cisco Nexus 5500 1RU Chassis (N5K-C5548P-FA)

- Cisco Nexus 5500 Series 8x10GE 8xFC 8/4/2/1 (N55-M8P8FP)

- Cisco Nexus 5500 Series 16-port 10GE (N55-M16FP)

Cisco Nexus 2000 Series Fabric Extenders

- Cisco Nexus 2148T Fabric Extender

- Cisco Nexus 2248TP Fabric Extender

- Cisco Nexus 2224TP Fabric Extender

- Cisco Nexus 2232PP Fabric Extender

- Cisco Nexus 2232TM Fabric Extender

- Cisco Nexus 2232TT Fabric Extender

- Cisco Nexus 2248T Fabric Extender

- Cisco Nexus 2248TP-E Fabric Extender

Upgrade Guidelines

When upgrading system software, follow these guidelines:

- Configuration changes

You cannot enter configuration mode during an upgrade. You should save, commit, or discard any active configuration sessions before upgrading or downgrading the Cisco NX-OS software image. The active configuration session is deleted without a warning during a reload.

Use the show configuration session summary command to verify that there are no active configuration sessions.

switch# show configuration session summary

There are no active configuration sessions

For more information on configuration sessions, see the Cisco Nexus 5000 Series NX-OS System Management Configuration Guide.

Note CLI and SNMP configuration change requests are denied during a in-service software upgrade (ISSU).

- Topology—You should make topology changes such as Spanning Tree Protocol (STP) or Fiber Channel (FC) fabric changes, that affect zoning, Fabric Shortest Path First (FSPF), or FC domains before you perform an upgrade. You should perform module installations or removals only before or after an upgrade.

- Scheduling—You should upgrade when your network is stable and steady. Ensure that everyone who has access to the switch or the network is not configuring the switch or the network during this time. You 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 200 MB of free space.

- Hardware—Avoid power 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 10/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 same subnetwork if you do not have a router to route traffic between subnets.

- Software image—Ensure that the specified system and kickstart images are compatible with each other as follows:

– If the kickstart image is not specified, the switch uses the current running kickstart image.

– If you specify a different system image, ensure that it is compatible with the running kickstart image.

- Retrieve 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 be used locally.

- Command—Use the following commands to prepare for and install the new software:

– Use the ping command to verify connectivity to the remote server.

– Use the dir command to verify the required space is available for the image files to be copied.

– Use the show install all impact command to identify the upgrade impact. This command displays information describing the impact of the upgrade on each Fabric Extender such as the current and upgrade-image versions. This command also displays if the upgrade is disruptive or the reason why the upgrade is disruptive, if the Fabric Extender needs to be rebooted, and the reason why it needs to be rebooted.

Note We recommended that you log in to the console port to begin the upgrade process. In Virtual Port Channel (vPC) topologies, the first upgrade can be performed on either the primary or secondary switch in the topology

- Terminology

Table 1-1 summarizes the terms used in the install all command output to verify module and software image compatibility.

Table 1-1 install all Commands and Output Terminology

Term

Definition

bootable

Ability of the module to boot or not boot based on image compatibility.

Impact

Type of software upgrade mechanism—disruptive or nondisruptive.

install-type reset

sw-reset

rolling

copy-only

Resets the module.

Resets the module immediately after a switchover.

Upgrades each module in sequence.

Updates the software for BIOS, loader, or boot ROM.

force

Option to force a disruptive upgrade, even when an ISSU is possible

Using the Install All Command

The install all command triggers an ISSU on Cisco Nexus 5000 Series switches and Cisco Nexus 2000 Series Fabric Extenders. The following images are upgraded during the installation:

- Kickstart image

- System image

- Fabric Extender image

- System BIOS

- Power sequencers on the system

The install-all command provides the following benefits:

- You can upgrade the Cisco Nexus 5000 Series switches and the Nexus 2000 Series Fabric Extenders using just one command.

- You can receive descriptive information about the intended changes to your system before you continue with the installation. For example, it identifies potential disruptive upgrades.

- You can continue or cancel the upgrade when you see this question (the default is no):

Do you want to continue (y/n) [n] : y

- You can upgrade the Cisco NX-OS software using a non disruptive procedure, when supported.

- The command automatically checks the image integrity, which includes the running kickstart and system images. The command sets the kickstart and system boot variables.

- The command performs a platform validity check to verify that a wrong 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.

- After entering the install all command, if any step in the sequence fails, the upgrade ends.

- The following message appears to warn you about the impact of upgrading the power sequencer:

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.

Note After a successful power sequence upgrade, you must switch off the power to the system and then power it up.

- You can force a disruptive upgrade. For information on forcing an upgrade, see Forcing an Upgrade.

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 system image, 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 After a successful power sequence upgrade, you must switch off the power to the system and then power it up.

Supported Upgrade and Downgrade Paths for Cisco NX-OS Release 5.2(1)N1(2a)

Cisco NX-OS supports in-service software upgrades (ISSUs) that allow a Cisco Nexus 5000 Series switch and any connected FEXs to be upgraded without any traffic disruption (with a brief control plane disruption). A few conditions have to be met for the system to be upgraded via ISSU process – the access layer topology should be ISSU compliant, the current and target versions should be ISSU capable and the network should be stable.

If the conditions required for ISSU are not met or if the user intends to downgrade the software version, the installation process will be disruptive. For example the Cisco Nexus 5000 Series switch and any connected FEX are rebooted, which causes a disruption. If Cisco’s virtual port channel (vPC) is configured on Cisco Nexus 5000 Series switches, it is possible to achieve an upgrade/downgrade with very minimal traffic disruption to servers/hosts.

Table 2 Supported Upgrade and Downgrade Paths for Cisco NX-OS Release 5.2(1)N1(2a)

Current Cisco NX-OS Release

Upgrade to NX-OS Release 5.2(1)N1(2a)

Downgrade from NX-OS Release 5.2(1)N1(2a)

5.2(1)N1(1b)—5.2(1)N1(2)

No support for direct nondisruptive upgrade (ISSU)

Disruptive downgrade

5.1(3)N2(1c)

5.1(3)N2(1b)1

5.1(3)N2(1a)

5.1(3)N2(1)

Nondisruptive upgrade (ISSU)

Disruptive downgrade

5.0(3)N2(2b)

5.0(3)N2(2a)

5.0(3)N2(2)

5.0(3)N2(1)

5.0(3)N1(1c)

Nondisruptive upgrade (ISSU)

Disruptive downgrade

1.Upgrading and downgrading are both disruptive between releases 5.1(3)N2(1b) and 5.2(1)N1(2) only.

Note Doing a disruptive upgrade between incompatible images will result in loss of certain configurations such as unified ports, Fibre Channel (FC), breakout, and FEX configurations. See CSCul22703 for details.

Note If a supported upgrade or downgrade path is not taken, then certain configurations, especially related to unified ports, Fibre Channel (FC) ports, breakout, and FEX may be lost.

Note If you want to upgrade from a release not listed in the “Current Cisco NX-OS Release” column of Table 2 to 5.2(1)N1(2a), then you must first upgrade to a release that is listed in the “Current Cisco NX-OS Release" column and then to 5.2(1)N1(2a).

Note If you want to upgrade from a release, that is not listed in the “Current Cisco NX-OS Release” column of Table 2 to the latest Cisco NX-OS release version, then you must first upgrade to a release that is listed in the “Current Cisco NX-OS Release” column and then to the latest release version.

In-Service Software Upgrades

Support for an ISSU on Cisco Nexus 5000 Series switches and Cisco Nexus 2000 Series Fabric Extenders was added with the 4.2(1)N1(1) NX-OS software release.

With a single supervisor system like a Cisco Nexus 5000 Series switch, an ISSU on the Cisco Nexus 5000 Series switch causes the supervisor CPU to reset and load the new software version. The control plane is inactive, but the data plane keeps forwarding packets that lead to an upgrade with no service disruption. After the CPU loads the updated version of Cisco NX-OS, the system restores the control plane to a previous ly known configuration and the runtime state and the data plane are synchronized, because the data plane keeps forwarding packets while the control plane is upgraded, any servers connected to the Cisco Nexus 5000 Series switch access layer should see no traffic disruption.

ISSU and Layer 3

Cisco Nexus 5500 Platform switches support Layer 3 functionality. However, the system cannot be upgraded with the ISSU process (non disruptive upgrade) when Layer 3 is enabled. It is required to unconfigure all Layer 3 features, remove the L3 license, and reload the switch, to be able to upgrade in a nondisruptive way with an ISSU.

ISSU Supported Topologies

This section includes the following topics:

- ISSU Support For Cisco Nexus 2000 Series Fabric Extenders

- ISSU Support for vPC Topologies

- ISSU Support for vPC Topologies with Fabric Extenders

- ISSU Support With Fibre Channel and FCoE Topologies

- Summary of ISSU-Supported Topologies

- Summary of ISSU Unsupported Topologies

- Management Services After an ISSU

- Fiber Channel/FCoE Protocol and Services During an ISSU

- Layer-2 Protocols Impact

- Fiber Channel/FCoE Protocol and Services During an ISSU

ISSU Support For Cisco Nexus 2000 Series Fabric Extenders

Cisco Nexus 2000 Series Fabric Extenders act as line cards to Cisco Nexus 5000 Series switches. The fabric extenders add flexibility to datacenter networking infrastructure by decoupling the physical and logical (Layer 2) topology, reducing the operation expense by lowering management and troubleshooting points, and building a larger layer 2 fabric that is loop-free, with a single layer of switching.

The ISSU process initiated on the Cisco Nexus 5000 Series switches upgrades the entire access layer including the switch and the FEXs that are connected to the switch.

An ISSU first upgrades the switches. Once the switch is operational with the upgraded software, the FEX’s are upgraded. This upgrade of the FEX is done in a rolling fashion, one FEX at a time. This upgrade on the Fabric Extenders is nondisruptive, similar to the upgrade of the switch.

The time required for an ISSU to complete depends on the number of FEX’s that are connected. You should plan a maintenance window with the total upgrade time in mind. The entire upgrade is nondisruptive and is not expected to cause any outage to connected servers.

ISSU Support for vPC Topologies

An ISSU is completely supported when two switches are paired in a vPC configuration. In a vPC configuration, one switch functions as a primary switch and the other functions as a secondary switch .They both run the complete switching control plane, but coordinate forwarding decisions to have optimal forwarding to devices at the other end of the vPC. Additionally, the two devices appear as a single device that supports EtherChannel (static and 802.3ad) and provide simultaneously data forwarding services to that device.

While upgrading devices in a vPC topology,you should start with the switch that is the primary switch. The vPC secondary device should be upgraded after the ISSU process completes successfully on the primary device. The two vPC devices continue their control plane communication during the entire ISSU process (except when the ISSU process resets the CPU of the switch being upgraded).

This example shows how to determine the vPC operational role of the switch:

n5020-2# show vpc brief

Legend:

(*) - local vPC is down, forwarding via vPC peer-link

vPC domain id : 1000

Peer status : peer adjacency formed ok

vPC keep-alive status : peer is alive

Configuration consistency status : success

vPC role : primary

Number of vPCs configured : 247

Peer Gateway : Disabled

Dual-active excluded VLANs : -

You can monitor the status of an ISSU on the primary from the primary device command, after the primary switch reloads by using the show install all status command.

Any attempt to initiate an upgrade on the vPC peer switch, when ISSU is progress on the other switch, is blocked.

Note During an upgrade, the configuration on peer switches is locked and the vPC state on vPC peer switches is suspended until the upgrade is complete.

Verifying the vPC Status on a Peer Switch During an Upgrade

To view the vPC status, enter the show vpc command on a peer switch as follows:.

switch-2# show vpc

Legend:

(*) - local vPC is down, forwarding via vPC peer-link

vPC domain id : 1000

Peer status : peer adjacency formed ok

vPC keep-alive status : Suspended during ISSU

Configuration consistency status: success

vPC role : primary, operational secondary

Number of vPCs configured : 100

Peer Gateway : Disabled

Dual-active excluded VLANs : 40

vPC Peer-link status

------------------------------------------------

id Port Status Active vlans

-- ---- ------ -----------------------------

1 Po100 up 1,40

The following message is displayed on the vPC peer switch when an ISSU is started on the other switch:

2014 Feb 4 00:07:16 MN5020-4 %$ VDC-1 %$ %VPC-2-VPC_ISSU_START: Peer vPC switch ISSU

start, locking configuration

Viewing System Messages on Peer Switches

A keepalive message such as the following may appear on a peer switch during an upgrade:

2014 Feb 4 00:09:26 MN5020-4 %$ VDC-1 %$ %VPC-2-PEER_KEEP_ALIVE_RECV_FAIL: In domain

1000, VPC peer keep-alive receive has failed

Installation status messages such as the following may appear on peer switches as the primary switch is upgraded.

switch-2# 2014 Jun 10 18:27:25 N5K2 %$ VDC-1 %$ %SATCTRL-2-SATCTRL_IMAGE: FEX100 Image

update in progress.

switch-2# 2014 Jun 10 18:32:54 N5K2 %$ VDC-1 %$ %SATCTRL-2-SATCTRL_IMAGE: FEX100 Image

update complete. Install pending

ISSU Support for vPC Topologies with Fabric Extenders

An ISSU is supported in vPC topologies that include FEXs that are connected in dual-homed topologies to a parent switch and when the FEX is in a single-homed topology.

To perform a nondisruptive upgrade, in a vPC environment that has FEXs connected to a switch, perform the following steps:

1. Perform a nondisruptive upgrade on the first switch.

2. Check the status of FEXs on the second switch prior to performing a nondisruptive upgrade on it. If any of the FEXs are in Active-Active (AA) version mismatch state, shut the corresponding NIF ports of the impacted FEXs.

3. Perform a nondisruptive upgrade on the second switch using the install all command.

4. After the upgrade is complete on the second s witch, bring up the ports that were shut in the Step 2.

Note After the upgrade procedure, ensure all the FEX ports are in online state, including the Active-Active version mismatch ports.

ISSU Support With Fibre Channel and FCoE Topologies

ISSUs are supported on access layer switches when Fibre Channel and Fibre Channel over Ethernet (FCoE) is enabled. You must ensure that the FC fabric is stable before initiating an ISSU in this topology.

Summary of ISSU-Supported Topologies

The following figure shows an access switch topology.

Figure 1-2 Access Switch Topology

The following figure shows a vPC peering topology.

Figure 1-3 vPC Peering Topology

The following figure shows a virtual modular system with static fabric connectivity for FEXs.

Figure 1-4 Virtual Modular System With Static Fabric Connectivity For FEXs

The following figure shows a vertical modular system.

Figure 1-5 Virtual Modular System

The following figure shows a vPC-peered dual-supervisor virtual modular system with dual-homed FEXs.

Figure 1-6 vPC-Peered Dual-Supervisor Virtual Modular System Dual-Homed FEXs

The following figure shows a vPC-peered dual-supervisor virtual modular system with dual-homed and single-homed FEXs.

Figure 1-7 vPC-Peered Dual-Supervisor Virtual Modular System Dual-Homed and Single-Homed FEXs

The following figure shows a vPC-peered dual-supervisor virtual modular system with dual-homed FEXs.

Figure 1-8 vPC Peered Dual-Supervisor Virtual Modular System Dual-Homed FEXs

Summary of ISSU Unsupported Topologies

Two important spanning tree-related requirements for a Cisco Nexus 5000 Series switch undergoing an ISSU are as follows. Note that a switch undergoing an ISSU has its control plane inactive while the switch is reset and the new software version is loaded. Not having these restrictions could render the network unstable, if there are any unexpected topology changes:

- STP enabled switches cannot be present downstream to the switch undergoing an ISSU.

- The STP Bridge Assurance feature cannot be configured except on a vPC peer link. Bridge Assurance is enabled by configuring an interface as a spanning-tree port type network.

If the STP conditions are not met, the installation check will indicate that the upgrade would be disruptive. In this case, you can perform an upgrade at a later time after making necessary changes to the topology to meet these conditions or perform a disruptive upgrade.

The following figure shows a Cisco Nexus 5000 Series switch that is connected to a blade switch that is running STP.

Figure 1-9 Connection to a Blade Switch that is Running STP

The following figure shows a Cisco Nexus 5000 Series switch that is connected to a downstream switch that is running STP.

Figure 1-10 Connection to a Downstream Switch that is Running STP

The following figure shows a Cisco Nexus 5000 Series switch that is running Bridge Assurance with another switch.

Figure 1-11 Cisco Nexus 5000 Series Switch Running Bridge Assurance with Another Switch

The following figure shows dual-homed FEXs connected to a stub switch.

Figure 1-12 Dual-Homed FEXs Connected to a Stub Switch

The following figure shows a single-homed FEX that is connected to stub switches.

Figure 1-13 Single-Homed FEX Connected to Stub Switches

The following figure shows a dual-homed FEX that is connected to stub switches.

Figure 1-14 Dual-Homed FEX Connected to Stub Switches

ISSU Prerequisites

All the upgrade guidelines listed in Cisco NX-OS Upgrade Guidelines section should be strictly adhered to for ISSU to work smoothly. In particular, make sure that the network is stable and no changes are made while an ISSU is in progress. Make sure that you check for feature compatibility between the current running release and the target release.

The following figure shows upgrade restrictions.

Figure 1-15 Upgrade Restrictions

In addition, there are some specific requirements for a non disruptive upgrade (ISSU).

Topology requirements— A Cisco Nexus 5000 Series switch on which an ISSU is being initiated should not be in one of the unsupported topologies listed in the previous figure. No interface should be in a spanning-tree designated forwarding state. Also, bridge assurance should not be configured on any interface of the Cisco Nexus 5000 series switch. vPC peer-link is an exception to these requirements.

Layer 2 requirement— The ISSU process will be aborted if the system has any Link Agregration Control Protocol (LACP) fast timers configured.

FC/FCoE requirements—Check that the topology is stable for an ISSU to work smoothly. The following is a list of things you must check:

Domain Manager—As part of the installation process, domain manager checks if the fabric is in a stable state. If the fabric is not stable, the installation will abort.

CFS—As part of the installation process, CFS checks if any application (ntp,fsm, rcsn, fctime) is locked. If any application is holding a CFS lock, the installation will abort.

Zone Server— The installation process aborts if a zone merge or zone change request is in progress.

FSPF—As part of the upgrade process, Fabric Shortest Path First (FSPF) verifies if the configured interface dead interval is more than 80 seconds; otherwise, installation will abort.

Management Services After an ISSU

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

Table 1-3 Inband and Management Ports Services Impacted During ISSU Reset

Service

Description

Telnet/SSH

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

AAA/RADIUS

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

HTTP

HTTP sessions to the switch are disconnected during an ISSU 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 ISSU reboot. After the reboot, NTP session are reestablished based on the saved startup configuration.

Fiber Channel/FCoE Protocol and Services During an ISSU

During an ISSU, the control plane is offline for up to 80 seconds. Any state changes in the network during this time are not processed. Depending on the change, the impact may vary. We always recommended that you ensure a stable fabric during an ISSU. See the following table for other ISSU impacts.

Table 1-4 ISSU Impact to Fibre Channel and FCoE Services

Service

Description

Name Server

When a new switch in the fabric is brought up and queries the Name Server on the ISSU switch, the ISSU switch cannot respond and does not receive Nx_port information.

Domain Manager

Domain Manager on a switch undergoing an ISSU does not process any BF/RCF/DIA/RDI caused by topology changes, which might result in traffic disruption in the fabric.

CFS

During an ISSU upgrade, CFS applications on other switches cannot obtain CFS locks on the ISSU switch, which might result in CFS distribution failures until the ISSU completes.

N-Port Virtualization

During an ISSU, the NPV process is down. Any FLOGI/fdisc or logo request from a server fails until the ISSU has completes.

Zone Server

During an ISSU, because EPP and merge requests are not processed, the peer switch cannot bring up E and TE ports connected to the ISSU switch until the ISSU completes.

A peer switch zone change request is not answered by the switch undergoing an ISSU. Any zone configuration changes on other switches connected to the ISSU switch fails until the ISSU completes.

FSPF

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

EPP

During an ISSU process, EPP messages are not received/transmitted on the ISSU switch. New ports in FC port channels are not negotiated until the ISSU completes. Additionally, FC Trunk Mode changes (E port to TE Port and vice versa and the allowed VSAN list) are also not processed.

FCoE NPV Links

When NPV/FCoE NPV switch is logged into a core switch through an FCoE NPV link, it will punch heartbeats (FIP keep alives - FKA), towards the core switch for its own internal login session and all the host login sessions pinned through this FCoE NPV link. This FKA interval of 8 seconds is lesser than the ISSU downtime. Set disable-fka on the core switch VFC parameters to ensure that the core switch ignores any FKA events.

Layer-2 Protocols Impact

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

Table 1-5 ISSU 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. ISSU should not impact peers that rely on LACP because the recovery time is less than 90 seconds.

Note that a Fast LACP timers (hello=1 sec, dead=3 sec) are not supported with a nondisruptive ISSU.

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 ISSU 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 ISSU, the age time is increased on all ports on the switches and FEXs that are being upgraded.

Manual configurations are ignored during this time.

CDP

During an ISSU, 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 ISSU, the switch transmits L2 IS-IS hellos on all interfaces to prevent neighbor switches from marking routes to the ISSU switch as down. Any topology changes during this time are also not acted upon until the ISSU completes.

Ethernet Interfaces on the Switch and the Fabric Extenders

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 ISSU reboot starting state when the switch and the FEX applications stop communicating with each other. After the ISSU 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 ISSU.

PreInstallation Checks

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

- 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.

- Enter the show fex command to verify that all the FEXs are online.

- Enter the show vpc role command to verify the vPC switch role in a vPC topology.

- 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 if the upgrade is not an ISSU.

- 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 ISSU.

Table 1-6 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 ISSU. 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 on each Fabric Extender including the current and upgrade-image versions. This command also displays if the upgrade is disruptive or not and if the Fabric Extender needs to be rebooted and the reason why.

show spanning-tree issu-impact

Displays the spanning-tree configuration and whether or not there are potential STP issues.

show lacp issu-impact

Displays the port priority information and whether or not there are potential issues.

show fcoe-npv issu-impact

Checks whether disable-fka is set on any of the FCoE NPV (VNP) ports as a pre-ISSU check.

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 bootflash:n5000-uk9.5.2.1.N1.2a.bin

No incompatible configurations

- Display the status of FEXs connected to the system.

switch# show fex

FEX FEX FEX FEX

Number Description State Model Serial

------------------------------------------------------------------------------------------------

100 FEX0100 Online N2K-C2224TP-1GE JAF1427BQME

101 FEX0101 Online N2K-C2224TP-1GE JAF1427BQMK

- Display the STP configuration and whether potential STP issues exist.

switch# show spanning-tree issu-impact

For ISSU to Proceed, Check the Following Criteria :

1. No Topology change must be active in any STP instance

2. Bridge assurance(BA) should not be active on any port (except MCT)

3. There should not be any Non Edge Designated Forwarding port (except MCT)

4. ISSU criteria must be met on the VPC Peer Switch as well

Following are the statistics on this switch

No Active Topology change Found!

Criteria 1 PASSED !!

No Ports with BA Enabled Found!

Criteria 2 PASSED!!

No Non-Edge Designated Forwarding Ports Found!

Criteria 3 PASSED !!

ISSU Can Proceed! Check Peer Switch.

Use the show lacp issu-impact command to display if any port or a peer switch is configured in rate fast mode.

- Verify that ISSU is nondisruptive. By displaying the information about the impact of the upgrade on each FEX including details such as upgrade image versions. This command also displays if the upgrade is disruptive/nondisruptive and the reason why.

N5K1# show install all impact kickstart n5000-uk9-kickstart.5.2.1.N1.2a.bin system n5000-uk9.5.2.1.N1.2a.bin

Verifying image bootflash:/n5000-uk9-kickstart.5.2.1.N1.2a.bin for boot variable "kickstart".

[####################] 100% -- SUCCESS

Verifying image bootflash:/n5000-uk9.5.2.1.N1.2a.bin for boot variable "system".

[####################] 100% -- SUCCESS

Verifying image type.

[########### ] 50%

[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.bin.

[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/n5000-uk9-kickstart.5.2.1.N1.2a.bin.

[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.bin.

[####################] 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 non-disruptive reset

Images will be upgraded according to following table:

Module Image Running-Version New-Version Upg-Required

------ ---------- ---------------------- ---------------------- ------------

1 system 5.2(1)N1(2) 5.2(1)N1(2a)5.2(1)N1(2a) yes

1 kickstart 5.2(1)N1(2) 5.2(1)N1(2a) yes

1 bios v3.6.0(05/09/2012) v3.6.0(05/09/2012) no

1 SFP-uC v1.0.0.0 v1.0.0.0 no

1 power-seq v1.0 v1.0 no

1 uC v1.2.0.1 v1.2.0.1 no

- Check whether disable-fka is set on any of the FCoE NPV (VNP) ports as a pre-ISSU check.

N5010# show fcoe-npv issu-impact

show fcoe-npv issu-impact

-------------------------

Please make sure to enable "disable-fka" on all logged in VFCs

Please increase the FKA duration to 60 seconds on FCF

Active VNP ports with no disable-fka set

----------------------------------------

Upgrading Procedures

The ISSU process is triggered when you enter the install all command. This section describes the sequence of events that occur when you upgrade a single Cisco Nexus 5000 Series switch or a single Cisco Nexus 5000 Series switch that is connected to one or more FEXs.

Note To use the ISSU process for Release 4.2(1)N1(1) through Release 5.0(2)N2(1a), you must first upgrade to Release 5.1(3)N1(1). After that, use the ISSU process to upgrade to Release 5.2.

The section includes the following topics:

- Installation At-A-Glance

- Copying the Running Configuration from an External Flash Memory Device

- Copying the Startup Configuration from an External Flash Memory Device

- Upgrade Process in a Non-vPC Topology

- Upgrade Process for a vPC Topology on the Primary Switch

- Upgrade Process for a vPC Topology on the Secondary Switch

- Upgrading From Cisco NX-OS Release 5.0(2)N2(1a) and Earlier Releases (Disruptive Upgrade)

- Minimizing the Impact of a Disruptive Upgrade

- Upgrading a Direct vPC or a Single-Homed FEX Access Layer

- Upgrading a Dual-Homed FEX Access Layer

Installation At-A-Glance

The following table shows an overview of the upgrade process.

Table 1-7 Upgrade Process At-A-Glance

Upgrade Preparation

1. Log in to the first Cisco Nexus 5000 Series switch. We recommend that you log in to the console port. In vPC topologies, the first upgrade can be performed on either the primary or secondary switch in the topology.

2. Log in to Cisco.com to access the Software Download Center. To log in to Cisco.com, go to http://www.cisco.com/ and click Log In at the top of the page. Enter your Cisco username and password.

3. Choose and download the kickstart and system software files to the server.

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

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

6. Copy the Cisco NX-OS kickstart and system images to the bootflash using a transfer protocol such as ftp:, tftp:, scp:, or sftp.

7. Compare the file sizes of the images that were transferred using the dir bootflash command. The file sizes of the images obtained from Cisco.com and the image sizes of the transferred files should be the same.

8. Complete the above steps through Step 9 for each Cisco Nexus 5000 Series switch in the topology.

Pre-ISSU Checks

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

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

3. Enter the show spanning-tree issu-impact command to display the impact of the upgrae impact.

4. Enter the show lacp issue-impact command to display the impact of the upgrade.

5. Enter the show fex command to verify that all the FEXs are online.

Upgrade Begins

1. Enter the show vpc role command to verify the vPC switch role.

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

3. Peruse the installer impact analysis and accept to proceed.

4. Installer on Nexus 5000 upgrades the software – the switch will now run new version of the software.

Upgrade Verification

1. Enter the show install all status command to verify the status of the installation.

Copying the Running Configuration from an External Flash Memory Device

You can copy configuration files from an external flash memory device.

Note This procedure applies to the Cisco Nexus 5500 Platform running Cisco NX-OS Release 5.0.2 and later releases.

Before You Begin

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

Command or Action

Purpose

Step 1

dir {usb1: | usb2:}[directory/]

Example:

switch# dir usb1:

(Optional) Displays the files on the external flash memory device.

Step 2

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

Example:

switch# copy usb1:n5000-uk9.5.2.1.N1.2a.bin bootflash:n5000-uk9. 5.2.1.N1.2a.bin

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

Step 3

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

Example:

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

Copies the running configuration from an external flash memory device. The filename argument is case sensitive.

Step 4

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

Example:

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

(Optional) You can copy the running configuration from an external flash memory device to the bootflash.

Step 5

show running-config

Example:

switch# show running-config

(Optional) Displays the running configuration.

Step 6

copy running-config startup-config

Example:

switch# copy running-config startup-config

(Optional) Copies the running configuration to the startup configuration.

Step 7

show startup-config

Example:

switch# show startup-config

(Optional) Displays the startup configuration.

Copying the Startup Configuration from an External Flash Memory Device

You can recover the startup configuration on your Cisco NX-OS device by downloading a new startup configuration file saved on an external flash memory device.

Note This procedure applies to the Cisco Nexus 5000 Platform running Cisco NX-OS Release 5.0.2 and later releases.

Before You Begin

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

Command or Action

Purpose

Step 1

dir {usb1: | usb2:}[directory/]

Example:

switch# dir usb1:

(Optional) Displays the files on the external flash memory device.

Step 2

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

Example:

switch# copy usb1:n5000-uk9.5.2.1.N1.2a.bin bootflash:n5000-uk9. 5.2.1.N1.2a.bin

Copies the image 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 memory device. The filename argument is case sensitive.

Step 4

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

Example:

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

(Optional) You can copy the startup configuration from an external flash memory device to the bootflash.

Step 5

show startup-config

Example:

switch# show startup-config

(Optional) Displays the startup configuration.

Step 1

copy running-config startup-config

Example:

switch# copy running-config startup-config

(Optional) Copies the running configuration to the startup configuration.

Step 1

show startup-config

Example:

switch# show startup-config

(Optional) Displays the startup configuration.

Upgrade Process in a Non-vPC Topology

The following list summarizes the upgrade process in a non-vPC topology:

1. The install all command triggers the installation upgrade.

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

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

4. The current state is saved.

5. The system unloads and runs the new image.

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

7. The installer resumes with the new image.

8. The FEXs are upgraded sequentially.

9. The installation completes.

The following example deisplays the ISSU process.

switch# install all kickstart n5000-uk9-kickstart.5.2.1.N1.2a.bin system n5000-uk9.5.2.1.N1.2a.bin

Verifying image bootflash:/n5000-uk9-kickstart.5.2.1.N1.2a.bin for boot variable "kickstart".

[####################] 100% -- SUCCESS

Verifying image bootflash:/n5000-uk9.5.2.1.N1.2a.bin for boot variable "system".

[####################] 100% -- SUCCESS

Verifying image type.

[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.bin.

[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/n5000-uk9-kickstart.5.2.1.N1.2a.bin.

[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.bin.

[####################] 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 non-disruptive reset

Images will be upgraded according to following table:

Module Image Running-Version New-Version Upg-Required

------ ---------- ---------------------- ---------------------- ------------

1 system 5.2(1)N1(2) 5.2(1)N1(2a) yes

1 kickstart 5.2(1)N1(2) 5.2(1)N1(2a) yes

1 bios v3.6.0(05/09/2012) v3.6.0(05/09/2012) no

1 SFP-uC v1.0.0.0 v1.0.0.0 no

1 power-seq v1.0 v1.0 no

1 uC v1.2.0.1 v1.2.0.1 no

Do you want to continue with the installation (y/n)? [n] y

Install is in progress, please wait.

Performing runtime checks.

[####################] 100% -- SUCCESS

Notifying services about the upgrade.

[####################] 100% -- SUCCESS

Setting boot variables.

[####################] 100% -- SUCCESS

Performing configuration copy.

[####################] 100% -- SUCCESS

Upgrade can no longer be aborted, any failure will result in a disruptive upgrade.

Requesting Line Cards to stop communication.

[####################] 100% -- SUCCESS

Requesting Sup Apps to stop communication.

[####################] 100% -- SUCCESS

Freeing memory in the file system.

[####################] 100% -- SUCCESS

Loading images into memory.

[####################] 100% -- SUCCESS

Saving supervisor runtime state.

[####################] 100% -- SUCCESS

Saving mts state.

[####################] 100% -- SUCCESS

Rebooting the switch to proceed with the upgrade.

All telnet and ssh connections will now be temporarily terminated.

Starting new kernel

Calling kexec callback

Moving to new kernel

Calling into reboot_code_buffer code

\ufffdserial 00:04: unable to assign resources

INIT: I2C - Mezz present

nohup: redirecting stderr to stdout

autoneg unmodified, ignoring

autoneg unmodified, ignoring

Checking all filesystems..... done.

Loading system software

Uncompressing system image: bootflash:/n5000-uk9.5.2.1.N1.2a.bin Tue Jul 3 14:55:27 PST 2012

Load plugins that defined in image conf: /isan/plugin_img/img.conf

load_plugin: Plugin-swid map exists. Any plugin exists in the map will be assigned from the map

Loading plugin 0: core_plugin...

load_plugin: Can't get exclude list from /isan/plugin/0/boot/etc/plugin_exclude.conf (rc 0x40ea0017)

Loading plugin 1: eth_plugin...

Loading plugin 2: fc_plugin...

ethernet switching mode

INIT: Entering runlevel: 3

touch: cannot touch `/var/lock/subsys/netfs': No such file or directory

Mounting other filesystems: [ OK ]

touch: cannot touch `/var/lock/subsys/local': No such file or directory

/isan/bin/muxif_config: fex vlan id: -f,4042

fwm_install....control_vlan: ret: 0

Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config

Added VLAN with VID == 4042 to IF -:muxif:-

Continuing with installation process, please wait.

The login will be disabled until the installation is completed.

Performing supervisor state verification.

[####################] 100% -- SUCCESS

Supervisor non-disruptive upgrade successful.

Install has been successful.

o2-48# show version

Cisco Nexus Operating System (NX-OS) Software

TAC support: http://www.cisco.com/tac

Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_serie

s_home.html

Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved.

The copyrights to certain works contained herein are owned by

other third parties and are used and distributed under license.

Some parts of this software are covered under the GNU Public

License. A copy of the license is available at

http://www.gnu.org/licenses/gpl.html.

Software

BIOS: version 3.6.0

loader: version N/A

kickstart: version 5.2(1)N1(2a) [build 5.2(1)N1(0.001)]

system: version 5.2(1)N1(2a) [build 5.2(1)N1(0.001)]

power-seq: Module 1: version v1.0

uC: version v1.2.0.1

SFP uC: Module 1: v1.0.0.0

BIOS compile time: 05/09/2012

kickstart image file is: bootflash:///n5000-uk9-kickstart.5.2.1.N1.2a.bin

kickstart compile time: 6/8/2012 23:00:00 [07/02/2012 18:38:30]

system image file is: bootflash:///n5000-uk9.5.2.1.N1.2a.bin

system compile time: 6/8/2012 23:00:00 [06/29/2012 03:09:20]

Hardware

cisco Nexus5010 Chassis ("O2 32X10GE/Modular Universal Platform Supervisor")

Intel(R) Xeon(R) CPU with 8263840 kB of memory.

Processor Board ID JAF1442aCNJ

Device name: o2-48

bootflash: 2007040 kB

Kernel uptime is 0 day(s), 3 hour(s), 30 minute(s), 13 second(s)

Last reset at 333847 usecs after Tue Jul 3 14:55:10 2012

Reason: Reset due to upgrade

System version: 5.0(3)N2(2b)

Service:

plugin

Core Plugin, Ethernet Plugin, Fc Plugin

Upgrade Process for a vPC Topology on the Primary Switch

The following list summarizes the upgrade process on a primary switch in a vPC topology. Steps that differ from a switch upgrade in a non-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 impact of the upgrade.

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

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

5. The current state is saved.

6. The system unloads and runs the new image.

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

8. The installer resumes with the new image.

9. The FEXs are upgraded sequentially.

10. The installation is complete.

When the installation is complete, the vPC primary switch and the FEXs that are connected to the primary switch are upgraded. The single-homed FEXs and the dual-homed FEXs are now running the upgraded software.

Note The dual-homed FEXs are now connected to the primary and secondary switches that are running two different versions of the Cisco NX-OS software. The vPC primary switch is running the upgraded version and the vPC secondary switch is running the original software version. The Cisco NX-OS software has been designed to allow an upgraded dual-home FEX to interoperate with vPC secondary switches running the original version of Cisco NX-OS while the primary switch is running the upgrade version.

Upgrade Process for a vPC Topology on the Secondary Switch

The following list summarizes the upgrade process on a secondary switch in a vPC topology. Steps that differ from a switch upgrade in a non-vPC topology are in bold.

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

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

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

4. The current state is saved.

5. The system unloads and runs the new image.

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

7. The installer resumes with the new image.

8. The FEXs are upgraded sequentially. The upgrade completes on the single-homed FEXs and a sanity check is performed on the dual-homed FEXs.

Note The dual-homed FEXs were upgraded by the primary switch.

9. The configuration is unlocked on the primary and secondary switches.

10. The installation is complete.

Disruptive Installation Process

Caution Doing a disruptive upgrade between incompatible images will result in loss of certain configurations such as unified ports, breakout, and FEX configurations. See CSCul22703 for details.

The following lists conditions where a nondisruptive ISSU might not be possible when upgrading a Cisco Nexus 5000 Series access layer switch:

- The topology and/or features are not ISSU ready. See the section on ISSU prerequisites for more information.

- The current release or target release is lower than 5.0(3)N1(1). An ISSU can work only when both the current and target releases are equal or later than 5.0(3)N1(1).

Note To use the ISSU process for Release 4.2(1)N1(1) through Release 5.0(2)N2(1a), you must first upgrade to Release 5.1(3)N1(1). After that, use the ISSU process to upgrade to Release 5.2(1)N1(2a).

- The installation is a downgrade, such as a higher release to a lower release, unless stated otherwise in Upgrade Guidelines section.

- You want to do a disruptive upgrade. See the Forcing an Upgrade section.

Restoring the Configuration

Perform the following steps to restore the configuration if the configurations contain interface breakout or unified port configurations:

1. Save the configuration to bootflash using the command copy running-config bootflash:[directory/]filename.

2. Use the default interface command to restore the default configurations of the breakout interfaces. Example: default interface e1/49/1-4, e2/25/1-4.

3. Save the running configuration to startup configuration using the copy running-config startup-config command.

4. Perform software migration using the install all command from Cisco NX-OS Release 5.2(1)N1(2a) to a lower version. In case of VPC, downgrade the primary switch first and then the secondary switch.

5. After the switch is up, power-off and power-on the module for the interface breakout to be effective. If the breakout is configured on Baseboard module, save the running configuration to startup configuration using the copy running-config startup-config command and then reload the switch again.

6. If breakout is not configured on the Baseboard, then an additional reload is required if running configuration contains hardware profile route resource service-template.

7. After the switch is up (with all the modules), copy the saved configuration from bootflash:<filename> to running-config.

8. Verify if all the interfaces are up and traffic is resumed.

Forcing an Upgrade

You can choose to do a disruptive upgrade if one of the ISSU conditions are not met. One additional reason where you might choose to do a disruptive upgrade is when FEXs are upgraded in a rolling fashion (one FEX at a time), which requires a longer maintenance window. With a disruptive upgrade, all the connected FEXs are upgraded simultaneously, so the maintenance window can be shorter. If you need a shorter maintenance window (with traffic disruption), you can force a disruptive upgrade even if an ISSU can be leveraged. It is important to note the possibility of an outage if you do a disruptive upgrade.

switch # install all force kickstart bootflash:/kickstart_image.bin system

bootflash:/system_image.bin

Installer is forced disruptive

Verifying image bootflash:/kickstart_image.bin for boot variable "kickstart".

[####################] 100% -- SUCCESS

Verifying image bootflash:/system_image.bin for boot variable "system".

...

You can also add force at the end of the install all command as follows:

switch # install all kickstart bootflash:/kickstart_image.bin system

bootflash:/system_image.bin force

Installer is forced disruptive

Verifying image bootflash:/kickstart_image.bin for boot variable "kickstart".

...

Upgrading From Cisco NX-OS Release 5.0(2)N2(1a) and Earlier Releases (Disruptive Upgrade)

This section describes how to upgrade from Cisco NX-OS Release 5.0(2)N2(1a) and earlier releases. An upgrade from these releases will be disruptive. Upgrading a Cisco Nexus 5000 Series switch also upgrades connected Fabric Extenders.

Note To perform a nondisruptive upgrade from Cisco NX-OS Release 5.0(3)N1(1) and later releases, see the “In-Service Software Upgrades” section. You can upgrade Cisco NX-OS Release 4.2(1)N1(1) through Release 5.0(2)N2(1a) using a two-step ISSU process.

DETAILED STEPS

Step 1 Log in to Cisco.com to access the Software Download Center. To log in to Cisco.com, go to http://www.cisco.com/ and click Log In at the top of the page. Enter your Cisco username and password.

Note Unregistered Cisco.com users cannot access the links provided in this document.

Access the Software Download Center at http://www.cisco.com/cisco/software/navigator.html?a=a&i=rpm. Navigate to the software downloads for Cisco Nexus 5000 Series switches. Links to the download images for the switch are listed.

Step 2 Choose and download the kickstart and system software files to a local server.

Step 3 Verify that the required space is available in the bootflash: directory for the image file(s) to be copied.

switch# dir bootflash:

4681 May 24 02:43:52 2014 config

13176836 May 24 07:19:36 2014 gdb.1

49152 Jan 12 18:38:36 2009 lost+found/

310556 Dec 23 02:53:28 2008 n1

25213952 Jun 14 19:11:12 2012 n5000-uk9-kickstart.5.0.3.N1.1c.bin

20058112 Jun 25 23:17:44 2013 n5000-uk9-kickstart.4.1.3.N1.1.bin

188774802 Jun 14 19:11:48 2012 n5000-uk9.5.0.3.N1.1c.bin

76930262 Jun 25 23:11:47 2013 n5000-uk9.4.1.3.N1.1.bin

Usage for bootflash://sup-local

74934272 bytes used

5550080 bytes free

80484352 bytes total

We recommend that you keep the kickstart and system image files for at least one previous software release to use if the new image files do not load successfully.

Step 4 (Optional) If you need more space on the bootflash, delete unnecessary files to make space available.

switch# delete bootflash:n5000-uk9-kickstart.4.1.3.N1.1.bin

switch# delete bootflash:n5000-uk9.4.1.3.N1.1.bin

Step 5 Copy the new kickstart and system images to the switch bootflash by using a transfer protocol such as FTP, TFTP, SCP, or SFTP. The examples in this procedure use SCP.

switch# copy scp://user@scpserver.cisco.com/downloads/n5000-uk9.5.2.1.N1.2a.bin bootflash:n5000-uk9.5.2.1.N1.2a.bin

switch# copy scp://user@scpserver.cisco.com/downloads/n5000-uk9-kickstart.5.2.1.N1.2a.bin

bootflash:n5000-uk9-kickstart.5.2.1.N1.2a.bin

Step 6 Display the impact of the upgrade.

switch# show install all impact kickstart bootflash:n5000-uk9-kickstart.5.2.1.N1.2a.bin

system bootflash:n5000-uk9.5.2.1.N1.2a.bin

Verifying image bootflash:/n5000-uk9-kickstart.5.2.1.N1.2a.bin for boot variable

"kickstart".

[####################] 100% -- SUCCESS

Verifying image bootflash:/n5000-uk9.5.2.1.N1.2a.bin for boot variable "system".

[####################] 100% -- SUCCESS

Verifying image type.

[########### ] 50%

[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.bin.

[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/n5000-uk9-kickstart.5.2.1.N1.2a.bin.

[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.bin.

[####################] 100% -- SUCCESS

Extracting "fex" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.bin.

[####################] 100% -- SUCCESS

Notifying services about system upgrade.

[####################] 100% -- SUCCESS

Compatibility check is done:

Module bootable Impact Install-type Reason

------ -------- -------------- ------------ ------

1 yes disruptive reset Reset due to single supervisor

100 yes disruptive reset Reset due to single supervisor

Images will be upgraded according to following table:

Module Image Running-Version New-Version Upg-Required

------ ---------- ---------------------- ---------------------- ------------

1 system 5.2.(1)N1(2) 5.2(1)N1(2a) yes

1 kickstart 5.2.(1)N1(2) 5.2(1)N1(2a) yes

1 bios v3.6.0(05/09/2012) v3.6.0(05/09/2012) no

100 fex 5.2.(1)N1(2) 5.2(1)N1(2a) yes

Step 7 Install the new images, specifying the new image names that you downloaded in the previous step.

switch# install all kickstart bootflash:n5000-uk9-kickstart.5.2.1.N1.2a.bin system

bootflash:n5000-uk9.5.2.1.N1.2a.bin

Verifying image bootflash:/n5000-uk9-kickstart.5.2.1.N1.2a.bin for boot variable

"kickstart".

[####################] 100% -- SUCCESS

Verifying image bootflash:/n5000-uk9.5.2.1.N1.2a.bin for boot variable "system".

[####################] 100% -- SUCCESS

Verifying image type.

[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.bin.

[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/n5000-uk9-kickstart.5.2.1.N1.2a.bin.

[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/n5000-uk9.4.5.2.1.N1.2a.bin.

[####################] 100% -- SUCCESS

Extracting "fex" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.bin.

[####################] 100% -- SUCCESS

Notifying services about system upgrade.

[####################] 100% -- SUCCESS

Compatibility check is done:

Module bootable Impact Install-type Reason

------ -------- -------------- ------------ ------

1 yes disruptive reset Reset due to single supervisor

100 yes disruptive reset Reset due to single supervisor

Images will be upgraded according to following table:

Module Image Running-Version New-Version Upg-Required

------ ---------- ---------------------- ---------------------- ------------

1 system 5.2.(1)N1(2) 5.2(1)N1(2a) yes

1 kickstart 5.2.(1)N1(2) 5.2(1)N1(2a) yes

1 bios v3.6.0(05/09/2012) v3.6.0(05/09/2012) no

100 fex 5.2.(1)N1(2) 5.2(1)N1(2a) yes

Switch will be reloaded for disruptive upgrade.

Do you want to continue with the installation (y/n)? [n] y

Install is in progress, please wait.

Setting boot variables.

[####################] 100% -- SUCCESS

Performing configuration copy.

[####################] 100% -- SUCCESS

Module 1: Refreshing compact flash and upgrading bios/loader/bootrom.

Warning: please do not remove or power off the module at this time.

[####################] 100% -- SUCCESS

Pre-loading modules.

[This step might take up to 20 minutes to complete - please wait.]

[# ] 0%2014 Jun 10 18:27:25 N5K1 %$ VDC-1 %$ %SATCTRL-2-SATCTRL_IMAGE:

FEX100 Image update in progress.

[##### ] 20%

[###### ] 25%2014 Jun 10 18:32:54 N5K1 %$ VDC-1 %$ %SATCTRL-2-SATCTRL_IMAGE:

FEX100 Image update complete. Install pending

[####################] 100% -- SUCCESS

Finishing the upgrade, switch will reboot in 10 seconds.

switch#

switch#

switch# writing reset reason 31,

Broadcast message from root (Thu Jun 10 18:33:16 2014):

INIT: Sending processes the TERM signal

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "stp" (PID 2843) is forced exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "netstack" (PID 2782) is forced

exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Security Daemon" (PID 2706) is

forced exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Cert_enroll Daemon" (PID 2707) is

forced exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "igmp" (PID 2808) is forced exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Radius Daemon" (PID 2806) is

forced exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "AAA Daemon" (PID 2708) is forced

exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vshd" (PID 2636) is forced exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vlan_mgr" (PID 2737) is forced

exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vdc_mgr" (PID 2681) is forced exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "urib" (PID 2718) is forced exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "u6rib" (PID 2717) is forced exit.

Jun 10 18:33:17 %TTYD-2-TTYD_ERROR TTYD Error ttyd bad select

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "statsclient" (PID 2684) is forced

exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "smm" (PID 2637) is forced exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "res_mgr" (PID 2688) is forced

exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "licmgr" (PID 2641) is forced

exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "l3vm" (PID 2715) is forced exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "icmpv6" (PID 2781) is forced

exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "eth_dstats" (PID 2700) is forced

exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "arp" (PID 2780) is forced exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "fs-daemon" (PID 2642) is forced

exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "ascii-cfg" (PID 2704) is forced

exit.

Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "adjmgr" (PID 2771) is forced

exit.

Jun 10 18:33:19 Unexporting directories for NFS kernel daemon...done.

Stopping NFS kernel daemon: rpc.mountd rpc.nfsddone.

Unexporting directories for NFS kernel daemon...

done.

Stopping portmap daemon: portmap.

Stopping kernel log daemon: klogd.

Sending all processes the TERM signal... done.

Sending all processes the KILL signal... done.

Unmounting remote filesystems... done.

Deactivating swap...umount: none busy - remounted read-only

done.

Unmounting local filesystems...umount: none busy - remounted read-only

done.

mount: you must specify the filesystem type

Starting reboot command: reboot

Rebooting...

Restarting system.

The switch reboots and restarts with the new image.

For detailed information about the install all command, see Using the install all Command.

Caution

After completing the installation, all traffic through the switch is disrupted while the

switch reboots.

Step 8 Verify that the switch is running the required software release.

switch# show version

Cisco Nexus Operating System (NX-OS) Software

TAC support: http://www.cisco.com/tac

Copyright ) 2002-2014, Cisco Systems, Inc. All rights reserved.

The copyrights to certain works contained herein are owned by

other third parties and are used and distributed under license.

Some parts of this software are covered under the GNU Public

License. A copy of the license is available at

http://www.gnu.org/licenses/gpl.html.

Software

BIOS: version 3.6.0

loader: version N/A

kickstart: version 5.2(1)N1(2a) [build 5.2(1)N1(0.001)]

system: version 5.2(1)N1(2a) [build 5.2(1)N1(0.001)]

power-seq: Module 1: version v1.0

uC: version v1.2.0.1

SFP uC: Module 1: v1.0.0.0

BIOS compile time: 05/09/2012

kickstart image file is: bootflash:///n5000-uk9-kickstart.5.2.1.N1.2a.bin

kickstart compile time: 6/8/2012 23:00:00 [07/02/2012 18:38:30]

system image file is: bootflash:///n5000-uk9.5.2.1.N1.2a.bin

system compile time: 6/8/2012 23:00:00 [06/29/2012 03:09:20]

Hardware

cisco Nexus5010 Chassis ("O2 32X10GE/Modular Universal Platform Supervisor")

Intel(R) Xeon(R) CPU with 8263840 kB of memory.

Processor Board ID JAF1442aCNJ

Device name: switch

bootflash: 2007040 kB

Kernel uptime is 0 day(s), 3 hour(s), 30 minute(s), 13 second(s)

Last reset at 333847 usecs after Tue Jul 3 14:55:10 2012

Reason: Reset due to upgrade

System version: 5.2.(1)N1(2a)

Service:

plugin

Core Plugin, Ethernet Plugin, Fc Plugin

Minimizing the Impact of a Disruptive Upgrade

A non-ISSU upgrade is a disruptive upgrade that results in the reload of the Cisco Nexus 5000 Series switch and the Cisco Nexus 2000 Series Fabric Extenders. The reload is a cold reboot that brings down the control plan and the data plane. The reload causes disruptions to the connected servers and hosts. When a vPC is deployed in the access layer, it is possible to minimize the impact of a non-ISSU upgrade. When one of the vPC switches is being reset during the upgrade process, all the server traffic can flow through its vPC peer.

Upgrading a Direct vPC or a Single-Homed FEX Access Layer

The following figures show topologies in which the access layer includes a vPC configuration to hosts or downstream switches.

Figure 1-16 Hosts Directly Connected to vPC Peers

Figure 1-17 vPC Peered Dual-Supervisor Virtual Modular System Dual-Homed FEXs and Singled-Homed FEXs

Figure 1-18 Cisco Nexus 5000 Series Switches Connected To Downstream Switches

To upgrade the access layer without a disruption to hosts, follow these tasks:

- Upgrade the first vPC switch (vPC primary switch). During this upgrade, the switch is reloaded. When the switch is reloaded, the servers or the downstream switch detects a loss of connectivity to the first switch and starts forwarding traffic to the second (vPC secondary) switch.

- Verify that the upgrade of the switch has completed successfully. At the completion of the upgrade, the switch restores vPC peering, connected Nexus 2000 Fabric Extenders and all the links.

- Upgrade the second switch. Repeating the same process on the second switch causes the second switch to reload during the upgrade process. During this reload, the first (upgraded) switch forwards all the traffic to/from servers.

- Verify that the upgrade of the second switch has completed successfully.

Note Flows that are forwarded to a switch during an upgrade on the switch, will failover to the second switch. Also, flows are redistributed when vPC peers are active. The traffic disruption is limited to the time required for the server or host to detect the link-down and link-up events and to redistribute the flows.

Note Upgrading Cisco NX-OS Software by changing the boot-variables and performing a reload is not supported in Cisco Nexus 5000 and 6000 Series Switches. This may result in loss of configuration and forwarding issues.

Upgrading a Dual-Homed FEX Access Layer

A disruptive upgrade causes a switch and connected FEXs to reload. The time required for a FEX to reload is less than the time required for a switch to reload. When hosts are connected to a dual-homed FEX, it is possible to keep the traffic disruption of the hosts to same time as required by FEX to reload (approximately 120 seconds), instead of the time required for an upgrade of the entire access layer.

The following figure shows a dual-homed FEX topology in which the access layer includes a vPC configuration to hosts or downstream switches.

Figure 19 vPC-Peered Dual-Supervisor Virtual Modular System Dual-Homed FEXs

Note The following dual-homed FEX procedure is supported only for an upgrade and not for a downgrade.

Step 1 Configure FEX module pre-provisioning for all the FEXs connected to both the switches (vPC primary and vPC secondary switches).

Upgrade the vPC primary switch with the new image using the install all kickstart image system image command. During the upgrade process, the switch is reloaded. When the switch is reloaded, only singled-homed FEXs connected to the switch are reloaded and dual-homed FEXs are not reloaded. Servers connected to the dual-homed FEXs retain network connectivity through the vPC secondary switch.

Step 2 Verify that the upgrade of the vPC primary switch is completed successfully. At the completion of the upgrade, the vPC primary switch restores vPC peering. However, dual-homed FEXs are connected only to the secondary vPC switch.

Step 3 Reload the dual-homed FEXs using the reload fex command from the vPC secondary switch. Reload the FEXs one-by-one or in a bunch of two or three FEXs. The servers connected to the dual-homed FEXs will lose connectivity.

Step 4 Wait for the FEXs to reload. After the reload, the FEXs connect to the upgraded switch (vPC primary switch).

Step 5 Upgrade the vPC secondary switch with the new image using the install all kickstart image system image command. During the upgrade process, the switch is reloaded. When the switch is reloaded, only singled-homed FEXs connected to the switch are reloaded and dual-homed FEXs are not reloaded.

Step 6 Verify that the upgrade of the vPC secondary switch is completed successfully. At the completion of the upgrade, the vPC secondary switch restores vPC peering. Dual-homed FEXs connect to both the peer switches and start forwarding traffic.

Detailed Steps

Step 1 Log in to Cisco.com to access the Software Download Center. To log in to Cisco.com, go to http://www.cisco.com/ and click Log In at the top of the page. Enter your Cisco username and password.

Note Unregistered Cisco.com users cannot access the links provided in this document.

Access the Software Download Center at http://www.cisco.com/cisco/software/navigator.html?a=a&i=rpm. Navigate to the software downloads for Cisco Nexus devices. Links to the download images for the switch are listed.

Step 2 Choose and download the kickstart and system software files to a local server.

Step 3 Verify that the required space is available in the bootflash: directory for the image file(s) to be copied.

switch# dir bootflash: | sec Usage

Usage for bootflash://sup-local

1748185088 bytes used

5806157824 bytes free

7554342912 bytes total

We recommend that you keep the kickstart and system image files for at least one previous software release to use if the new image files do not load successfully.

Step 4 (Optional) If you need more space on the bootflash, delete unnecessary files to make space available.

Step 5 Copy the new kickstart and system images to each switch bootflash by using a transfer protocol such as FTP, TFTP, SCP, or SFTP.

switch-1# dir bootflash: inc 5.2

35756544 Feb 18 13:24:46 2016 n5000-uk9-kickstart.5.2. 1.N1.9.bin

35792384 Oct 21 10:49:30 2016 n5000-uk9-kickstart.5.2.1.N1.2a

325724988 Feb 18 13:23:22 2016 n5000-uk9.5.2.1.N1.9

324046051 Oct 21 10:49:10 2016 n5000-uk9.5.2.1.N1.2a

Step 6 Configure FEX Module pre-provisioning for the type of FEX present in the system. Perform this step on both the switches in a vPC pair. For more information on how to configure FEX module pre-provisioning, refer the Cisco Nexus 5000 Series NX-OS System Management Configuration Guide.

This example shows how to select slot 130 and the N2K-C2348UPQ module to pre-provision.

switch# show fex

FEX FEX FEX FEX Fex

Number Description State Model Serial

------------------------------------------------------------------------

130 FEX0130 Online N2K-C2348UPQ FOC1818R2MF

198 FEX0198 Online N2K-C2332TQ-10GT FOC1910R0R1

switch# configure terminal

switch(config)# slot 130

switch(config-slot)# provision model N2K-C2348UPQ

switch(config-slot)# slot 198

switch(config-slot)# provision model N2K-C2332TQ

Step 7 Enter the show install all impact command to validate the upgrade process and the components being upgraded.

switch-1# show install all impact kickstart bootflash:n5000-uk9-kickstart.5.2.1.N1.2a system bootflash:n5000-uk9.5.2.1.N1.2a

Verifying image bootflash:/n5000-uk9-kickstart.5.2.1.N1.2a for boot variable "kickstart".

[####################] 100% -- SUCCESS

Verifying image bootflash:/n5000-uk9.5.2.1.N1.2a for boot variable "system".

[####################] 100% -- SUCCESS

Verifying image type.

[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.

[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/n5000-uk9-kickstart.5.2.1.N1.2a.

[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.

[####################] 100% -- SUCCESS

Extracting "fex4" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.

[####################] 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 Non-disruptive install not supported if L3 was enabled

2 yes disruptive reset Non-disruptive install not supported if L3 was enabled

130 yes disruptive reset Non-disruptive install not supported if L3 was enabled

198 yes disruptive reset Non-disruptive install not supported if L3 was enabled

Images will be upgraded according to following table:

Module Image Running-Version New-Version Upg-Required

------ ---------------- ---------------------- ---------------------- ------------

1 system 5.2(1)N1(2) 5.2(1)N1(2a) yes

1 kickstart 5.2(1)N1(2) 5.2(1)N1(2a) yes

1 bios v2.1.7(06/16/2016) v2.1.7(06/16/2016) no

1 power-seq v4.0 v4.0 no

1 fabric-power-seq v4.0 v4.0 no

2 power-seq v4.0 v4.0 no

130 fex4 5.2(1)N1(2) 5.2(1)N1(2a) yes

198 fex4 5.2(1)N1(2) 5.2(1)N1(2a) yes

1 microcontroller v0.0.0.15 v0.0.0.15 no

Step 8 Enter the install all kickstart image system image command on the vPC primary switch.

switch# install all kickstart bootflash:n5000-uk9-kickstart.5.2.1.N1.2a system bootflash:n5000-uk9.5.2.1.N1.2a

Verifying image bootflash:/n5000-uk9-kickstart.5.2.1.N1.2a for boot variable "kickstart".

[####################] 100% -- SUCCESS

Verifying image bootflash:/n5000-uk9.5.2.1.N1.2a for boot variable "system".

[####################] 100% -- SUCCESS

Verifying image type.

[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.

[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/n5000-uk9-kickstart.5.2.1.N1.2a.

[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.

[####################] 100% -- SUCCESS

Extracting "fex4" version from image bootflash:/n5000-uk9.5.2.1.N1.2a.

[####################] 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 Non-disruptive install not supported if L3 was enabled

2 yes disruptive reset Non-disruptive install not supported if L3 was enabled

130 yes disruptive reset Non-disruptive install not supported if L3 was enabled

198 yes disruptive reset Non-disruptive install not supported if L3 was enabled

Images will be upgraded according to following table:

Module Image Running-Version New-Version Upg-Required

------ ---------------- ---------------------- ---------------------- ------------

1 system 5.2(1)N1(2) 5.2(1)N1(2a) yes

1 kickstart 5.2(1)N1(2) 5.2(1)N1(2a) yes

1 bios v2.1.7(06/16/2016) v2.1.7(06/16/2016) no

1 power-seq v4.0 v4.0 no

1 fabric-power-seq v4.0 v4.0 no

2 power-seq v4.0 v4.0 no

130 fex4 5.2(1)N1(2) 5.2(1)N1(2a) yes

198 fex4 5.2(1)N1(2) 5.2(1)N1(2a) yes

1 microcontroller v0.0.0.15 v0.0.0.15 no

Switch will be reloaded for disruptive upgrade.

Do you want to continue with the installation (y/n)? [n] y

Install is in progress, please wait.

Performing runtime checks.

[####################] 100% -- SUCCESS

Setting boot variables.

[####################] 100% -- SUCCESS

Performing configuration copy.

[####################] 100% -- SUCCESS

Pre-loading modules.

[This step might take upto 20 minutes to complete - please wait.]

[*Warning -- Please do not abort installation/reload or powercycle fexes*]

[# ] 0%2017 Apr 4 11:58:11 switch %$ VDC-1 %$ %SATCTRL-FEX130-2-SATCTRL_IMAGE: FEX130 Image update in progress.

2017 Apr 4 11:58:21 switch %$ VDC-1 %$ %SATCTRL-FEX198-2-SATCTRL_IMAGE: FEX198 Image update in progress.

[#### ] 15%2017 Apr 4 12:03:41 switch %$ VDC-1 %$ %SATCTRL-FEX198-2-SATCTRL_IMAGE: FEX198 Image update complete. Install pending

[###### ] 25%2017 Apr 4 12:05:49 switch %$ VDC-1 %$ %SATCTRL-FEX130-2-SATCTRL_IMAGE: FEX130 Image update complete. Install pending

[####################] 100% -- SUCCESS

Finishing the upgrade, switch will reboot in 10 seconds.

switch# [2007269.320144] Shutdown Ports..

[2007269.329300] writing reset reason 49,

2017 Apr 4 12:06:03 switch %$ VDC-1 %$ %KERN-0-SYSTEM_MSG: [2007269.320144] Shutdown Ports.. - kernel

2017 Apr 4 12:06:03 switch %$ VDC-1 %$ %KERN-0-SYSTEM_MSG: [2007269.329300] writing reset reason 49, - kernel

2017 Apr 4 12:06:07 switch %$ VDC-1 %$ %VPC-2-PEER_KEEP_ALIVE_RECV_FAIL: In domain 572, VPC peer keep-alive receive has failed

Broadcast message from root (Tue Apr 4 12:06:08 2017):

The system is going down for reboot NOW!

INIT: Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "patch-installer" (PID 4196) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "u6rib" (PID 4285) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "__inst_001__ospf" (PID 5442) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "__inst_001__ospfv3" (PID 5535) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "bgp" (PID 5549) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "fs-daemon" (PID 4145) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "adjmgr" (PID 4284) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "assoc_mgr" (PID 4927) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "arp" (PID 4315) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "AAA Daemon" (PID 4226) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "rib" (PID 4930) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Security Daemon" (PID 4223) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vman" (PID 4183) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "statsclient" (PID 4251) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vshd" (PID 4139) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Radius Daemon" (PID 4455) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "stp" (PID 4640) is forced exit.

Apr 4 12:06:08 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Cert_enroll Daemon" (PID 4225) is forced exit.

Apr 4 12:06:09 %ADJMGR-3-URIB_SEND_TO_ERROR Send to URIB failed: Invalid argument

INIT: Sending processes the KILL signal

Sending all processes the TERM signal...

Apr 4 12:06:15 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "icmpv6" (PID 4324) is forced exit.

Apr 4 12:06:15 %ICMPV6-3-MTS_RECV icmpv6 [4324] Error returned from mts_recv(), errno: Interrupted system call

Apr 4 12:06:15 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "arp" (PID 4315) is forced exit.

Apr 4 12:06:15 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "adjmgr" (PID 4284) is forced exit.

Sending all processes the KILL signal...

Unmounting filesystems...

[2007288.129255] Resetting board

x?x?xx??xx???????x????x??????????????x????x???x?????????????xx??????x??x??????xx?x???x???x?xx??x???????????xx?x???x???????x?????x????xx??x???x??????x????????xx?????x????x????x????????x?????xx???x?xx?x????x????xx???x?x?????x??x???x????xx???x?x?????x??x???x????xx???x?x?????x??x???x????xx???x?x?????x?????x????xx???x?x?????x??x???x????xx???x?x?????x??x???x????xx???x?x?????x??x???x????xx???x?x?????x???????x????xx???x?x?????x??x???x????xx???x?x?????x??x???x????xx???x?x?????x??x???x????xx???x?x?????x??x???x????xx???x?x?????x??x???x????xx???x?x?????x???????x????xx???x?x?????x??xxxx?x?x??x?xx?x?x??x?x?x?x?????x????x??x??x?xx?x???xxx?x?xxx??x?xx?xx??xx??xx?x?xx??????????xxxx??x??x?x?xx?xx?xxx??????xx?????x????x?????xx

Booting kickstart image: bootflash:/n5000-uk9-kickstart.5.2.1.N1.2a

...............................................................................

..............................Image verification OK

Booting kernel

INIT: [ 13.413136] val:4, count7 .

[ 13.421467] TCO_TMR val:1023, SMI_EN= 0x42033 NMI_STS_CNT_REG = 0x3d count7 .

devmemfd:0x7fbcdc58

phys->virt: 0x7fbcdb9c7fbcdc58-->0x0

devmemfd:0x7fbcdc98

phys->virt: 0xa44000087fbcdc98-->0x0

devmemfd:0x7fbcdc98

phys->virt: 0xa44000087fbcdc98-->0x0

devmemfd:0x7fbcdc98

phys->virt: 0xa44000087fbcdc98-->0x0

Starting system POST.....

P(0x102) board

Executing Mod 1 1 SEEPROM Test:

...done (0 sec, 194 msec, 38 usec)

Executing Mod 1 1 GigE Port Test:

....done (16 sec, 86 msec, 824 usec)

Executing Mod 1 1 PCIE Test:

........done (0 sec, 1 msec, 176 usec)

Mod 1 1 Post Completed Successfully

POST is completed

can't create lock file /var/lock/mtab~308: No such file or directory (use -n flag to override)

nohup: redirecting stderr to stdout

autoneg unmodified, ignoring

autoneg unmodified, ignoring

Checking all filesystems..... done.

Loading system software

Tue Apr 4 12:07:54 EDT 2017 BIGSUR SYNC getting started issu = 0

Uncompressing system image: bootflash:/n5000-uk9.5.2.1.N1.2a Tue Apr 4 12:08:05 EDT 2017

Load plugins that defined in image conf: /isan/plugin_img/img.conf

Loading plugin 0: core_plugin...

load_plugin: Can't get exclude list from /isan/plugin/0/boot/etc/plugin_exclude.conf (rc 0x40ea0017)

Loading plugin 1: eth_plugin...

ln: creating symbolic link `/lib/libcrypto.so.4': File exists

ln: creating symbolic link `/lib/libssl.so.4': File exists

ethernet switching mode

rm: cannot remove `/isan/bin/bigsursimd': No such file or directory

rm: cannot remove `/isan/bin/bigsursimd_revB': No such file or directory

INIT: Entering runlevel: 3

touch: cannot touch `/var/lock/subsys/netfs': No such file or directory

Mounting other filesystems: [ OK ]

/isan/bin/muxif_config: fex vlan id: -f,4042

Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config

Added VLAN with VID == 4042 to IF -:muxif:-

card index: 0x2b58

2017 Apr 4 12:08:49 switch %$ VDC-1 %$ %SYSLOG-2-SYSTEM_MSG : Syslogs wont be logged into logflash until logflash is online

2017 Apr 4 12:08:50 switch %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files begin - clis

2017 Apr 4 12:08:53 switch %$ VDC-1 %$ %KERN-0-SYSTEM_MSG: [ 13.413136] val:4, count7 . - kernel

2017 Apr 4 12:08:53 switch %$ VDC-1 %$ %KERN-0-SYSTEM_MSG: [ 13.421467] TCO_TMR val:1023, SMI_EN= 0x42033 NMI_STS_CNT_REG = 0x3d count7 . - kernel

2017 Apr 4 12:09:02 switch %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files end - clis

2017 Apr 4 12:09:02 switch %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: init begin - clis

2017 Apr 4 12:09:02 switch %$ VDC-1 %$ %DAEMON-2-SYSTEM_MSG: <<%XMLMA-2-XMLMACRIT>> XML master agent: Starting sysmgr handshake. - xmlma[4313]

2017 Apr 4 12:09:02 switch %$ VDC-1 %$ %DAEMON-2-SYSTEM_MSG: <<%XMLMA-2-XMLMACRIT>> XML master agent: Done with sysmgr handshake. - xmlma[4313]

2017 Apr 4 12:09:57 switch %$ VDC-1 %$ %PFMA-2-PS_FAIL: Power supply 2 failed or shutdown(Serial number POG151850HC)

System is coming up ... Please wait ...

System is coming up ... Please wait ...

System is coming up ... Please wait ...

System is coming up ... Please wait ...

System is coming up ... Please wait ...

System is coming up ... Please wait .

Nexus 5548 Switch

switch login: 2017 Apr 4 12:13:35 switch %$ VDC-1 %$ clis: Enabling feature ospf: and calling licmgr_resgister

2017 Apr 4 12:13:35 switch %$ VDC-1 %$ clis: Enabling feature bgp: and calling licmgr_resgister

2017 Apr 4 12:13:36 switch %$ VDC-1 %$ clis: Enabling feature ospfv3: and calling licmgr_resgister

2017 Apr 4 12:13:36 switch %$ VDC-1 %$ clis: Enabling feature pim: and calling licmgr_resgister

2017 Apr 4 12:13:40 switch %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online

2017 Apr 4 12:14:36 switch %$ VDC-1 %$ %VPC-2-VPC_SVI_DELAY_RESTORE_TIMER: Delay restore timer will be overwritten to 150 sec when l3 is installed. Old value:(150)

2017 Apr 4 12:15:34 switch %$ VDC-1 %$ %PFMA-2-MOD_PWRUP: Module 2 powered up (Serial number FOC18293WRV)

During the software upgrade on the primary switch, you can view the FEX upgrade progress using the vPC secondary switch (see the bold output):

switch-2# 2017 Apr 4 11:58:11 switch %$ VDC-1 %$ %SATCTRL-FEX130-2-SATCTRL_IMAGE: FEX130 Image update in progress.

2017 Apr 4 11:58:21 switch %$ VDC-1 %$ %SATCTRL-FEX198-2-SATCTRL_IMAGE: FEX198 Image update in progress.

2017 Apr 4 12:03:41 switch %$ VDC-1 %$ %SATCTRL-FEX198-2-SATCTRL_IMAGE: FEX198 Image update complete. Install pending

2017 Apr 4 12:05:49 switch %$ VDC-1 %$ %SATCTRL-FEX130-2-SATCTRL_IMAGE: FEX130 Image update complete. Install pending

Verify the status of the Fabric Extender from the secondary vPC switch.

switch-2# show fex 130

FEX: 130 Description: FEX0130 state: Online

FEX version: 5.2(1)N1(2a) [Switch version: 5.2(1)N1(2a)]

Extender Serial: FOC1818R2MF

Extender Model: N2K-C2348UPQ, Part No: 73-15489-03

Pinning-mode: static Max-links: 1

Fabric port for control traffic: Eth2/1

FCoE Admin: false

FCoE Oper: false

FCoE FEX AA Configured: true

Fabric interface state:

Po130 - Interface Up. State: Active

Eth2/1 - Interface Up. State: Active

switch-2# show fex 198

FEX: 198 Description: FEX0198 state: Online

FEX version: 5.2(1)N1(2a) [Switch version: 5.2(1)N1(2a)]

Extender Serial: FOC1910R0R1

Extender Model: N2K-C2332TQ-10GT, Part No: 73-16733-04

Pinning-mode: static Max-links: 1

Fabric port for control traffic: Eth2/2

FCoE Admin: false

FCoE Oper: false

FCoE FEX AA Configured: true

Fabric interface state:

Po198 - Interface Up. State: Active

Eth2/2 - Interface Up. State: Active

switch-2# show fex

FEX FEX FEX FEX Fex

Number Description State Model Serial

------------------------------------------------------------------------

130 FEX0130 Online N2K-C2348UPQ FOC1818R2MF

198 FEX0198 Online N2K-C2332TQ-10GT FOC1910R0R1

Note The Fabric Extender remains online on the vPC secondary switch while the vPC primary switch is reloaded.

Step 9 Ensure that the upgrade on vPC primary switch is completed. Use the show version command to verify the upgrade on vPC primary switch.

switch-1# show version

Software

BIOS: version 2.1.7

Power Sequencer Firmware:

Module 1: v4.0

Module 1: v4.0

Fabric Power Sequencer Firmware: Module 1: version v4.0

Microcontroller Firmware: version v1.2.0.5

QSFP Microcontroller Firmware:

Module 1: v1.3.0.0

CXP Microcontroller Firmware:

Module not detected

kickstart: version 5.2(1)N1(2a)

system: version 5.2(1)N1(2a)

BIOS compile time: 06/01/2016

kickstart image file is: bootflash:///n5000-uk9-kickstart.5.2.1.N1.2a

kickstart compile time: 10/6/2016 14:00:00 [10/07/2016 00:07:02]

system image file is: bootflash:///n5000-uk9-kickstart.5.2.1.N1.2a

system compile time: 10/6/2016 14:00:00 [10/07/2016 00:08:34]

Step 10 On the vPC primary switch after the upgrade, the FEXs connected to the switch are in Active/Active mismatch state.

switch-1# show fex

FEX FEX FEX FEX Fex

Number Description State Model Serial

------------------------------------------------------------------------

130 FEX0130 AA Version Mismatch N2K-C2348UPQ FOC1818R2MF

198 FEX0198 AA Version Mismatch N2K-C2332TQ-10GT FOC1910R0R1

Step 11 On the vPC secondary switch, reload the first Fabric Extenders (reload only dual-homed FEXs) one at a time and wait for them to come online on the newly upgraded vPC primary switch before proceeding to the next FEX.

switch-2# reload fex 130

reload fex 130

WARNING: This command will reboot FEX 130

Do you want to continue? (y/n) [n] y

2017 Apr 4 13:49:14 switch %$ VDC-1 %$ %ETH_PORT_CHANNEL-5-FOP_CHANGED: port-channel130: first operational port changed from Ethernet2/1 to none

2017 Apr 4 13:49:14 switch %$ VDC-1 %$ %ETH_PORT_CHANNEL-5-PORT_DOWN: port-channel130: Ethernet2/1 is down

2017 Apr 4 13:49:14 switch %$ VDC-1 %$ %ETH_PORT_CHANNEL-5-PORT_DOWN: port-channel130: port-channel130 is down

2017 Apr 4 13:49:14 switch %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 1 of Fex 130 that is connected with Ethernet2/1 changed its status from Active to Disconnected

2017 Apr 4 13:49:14 switch %$ VDC-1 %$ %NOHMS-2-NOHMS_ENV_FEX_OFFLINE: FEX-130 Off-line (Serial Number FOC1818R2MF)

2017 Apr 4 13:49:14 switch %$ VDC-1 %$ %PFMA-2-FEX_STATUS: Fex 130 is offline

switch-2# reload fex 198

WARNING: This command will reboot FEX 198

Do you want to continue? (y/n) [n] y

switch# 2017 Apr 4 13:55:35 switch %ETH_PORT_CHANNEL-5-FOP_CHANGED: port-channel198: first operational port changed from Ethernet2/2 to none

2017 Apr 4 13:55:35 switch %ETH_PORT_CHANNEL-5-PORT_DOWN: port-channel198: Ethernet2/2 is down

2017 Apr 4 13:55:35 switch %ETH_PORT_CHANNEL-5-PORT_DOWN: port-channel198: port-channel198 is down

2017 Apr 4 13:55:35 switch %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 1 of Fex 198 that is connected with Ethernet2/2 changed its status from Active to Disconnected

2017 Apr 4 13:55:35 switch %NOHMS-2-NOHMS_ENV_FEX_OFFLINE: FEX-198 Off-line (Serial Number FOC1910R0R1)

Note Only the vPC primary switch shows that the Fabric Extender is online because the vPC secondary switch does not have the new image. The secondary switch shows the Fabric Extender in Active/Active version mismatch state.

switch-2# show fex

FEX FEX FEX FEX Fex

Number Description State Model Serial

------------------------------------------------------------------------

130 FEX0130 AA Version Mismatch N2K-C2348UPQ FOC1818R2MF

198 FEX0198 AA Version Mismatch N2K-C2332TQ-10GT FOC1910R0R1switch-2#

Note Make sure that the first Fabric Extender comes up before reloading the subsequent Fabric Extenders on the vPC secondary switch.

When all the Fabric Extenders are loaded, go to the next step.

To upgrade the vPC secondary switch, follow Step 2 to Step 9.

Step 12 Verify all the FEXs connected to the vPC secondary switch are online. Use the show fex command to view the FEX status.

switch-2# show fex

FEX FEX FEX FEX Fex

Number Description State Model Serial

------------------------------------------------------------------------

130 FEX0130 Online N2K-C2348UPQ FOC1818R2MF

198 FEX0198 Online N2K-C2332TQ-10GT FOC1910R0R1

Note You should do certain sanity checks to ensure that the system is ready for an ISSU and to understand the impact of an ISSU.

Monitoring the Upgrade Status

Table 1-8 lists the show commands that are used to monitor installation upgrades.

Table 1-8 Monitoring the Upgrade Process

Command

Definition

show fex

Displays the Fabric Extender status during an ISSU.

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.

show system internal log install details

Displays detailed logs of the last installation-related command.

show system internal log install history

Displays detailed logs of the last five installation-related commands, from the oldest to the newest logs.

show tech-support

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

The following example shows the output from the show install all status command:

There is an on-going installation...

Enter Ctrl-C to go back to the prompt.

Continuing with installation process, please wait.

The login will be disabled until the installation is completed.

Performing supervisor state verification.

SUCCESS

Supervisor non-disruptive upgrade successful.

Pre-loading modules.

SUCCESS

Module 198: Non-disruptive upgrading.

SUCCESS

Module 199: Non-disruptive upgrading.

SUCCESS

Install has been successful. (hit Ctrl-C here)

The following example shows the output from the show fex command on two vPC peer switches where FEX 198 and FEX 199 are upgraded:

switch-1# show fex

FEX FEX FEX FEX

Number Description State Model Serial

------------------------------------------------------------------------

198 FEX0198 Hitless Upg Idle N2K-C2248TP-1GE JAF1342ANQP

199 FEX0199 Online N2K-C2248TP-1GE JAF1342ANRL

switch-2# show fex

FEX FEX FEX FEX

Number Description State Model Serial

------------------------------------------------------------------------

198 FEX0198 FEX AA Upg Idle N2K-C2248TP-1GE JAF1342ANQP

199 FEX0199 Online N2K-C2248TP-1GE JAF1342ANRL

Downgrading from a Higher Release

Downgrading from Cisco NX-OS Release 5.2(1)N1(2a) to any lower version using the install all command is the same as manually setting the boot variables and reloading the switch. Note that the downgrades are disruptive. The ASCII configuration replay for downgrade on Cisco Nexus 5000 Series switches will be enabled. You can use the show incompatibility system command to ensure that there are no feature incompatibilities between the current release and the target release.

Note For FEX configurations, before performing a downgrade, the FEX configurations must be converted to use the FEX pre-provisioning configurations. For pre-provisioning a FEX, use the slot <slot-id> provision model <model-number> command.

After FEX pre-provisioning is done, perform the following steps to restore the configuration if the configurations contain interface breakout or unified port configurations:

1. Save the configuration to bootflash using the command copy running-config bootflash:[directory/]filename.

2. Use the default interface command to restore the default configurations of the breakout interfaces. Example: default interface e1/49/1-4, e2/25/1-4.

3. Save the running configuration to startup configuration using the copy running-config startup-config command.

4. Perform in-service software downgrade (ISSD) using the install all command from Cisco NX-OS Release 5.2(1)N1(2a) to a lower release. In case of vPC, downgrade the primary switch first and then the secondary switch.

5. After the switch is up, power-off and power-on the module for the interface breakout to be effective. If the breakout is configured on Baseboard module, save the running configuration to startup configuration using the copy running-config startup-config command and then reload the switch again.

6. If breakout is not configured on the Baseboard module, then an additional reload is required if running configuration contains hardware profile route resource service-template.

7. After the switch is up (with all the modules), copy the saved configuration from bootflash:<filename> to running-config.

8. Verify if all the interfaces are up and traffic is resumed.

Note Before you downgrade to a specific release, check the release notes for the current release installed on the switch to ensure that your hardware is compatible with the specific release. You must be aware of special caveats before you downgrade the switch software to a Cisco NX-OS 4.0(0)-based release. See the Release Notes for your platform for details.

Troubleshooting ISSUs and Disruptive Installations

Some common causes for ISSU failure are as follows:

- ISSU requirements are not met – bridge assurance is active or the switch is not a leaf node in the STP topology. These problems are described in the commands explained in Pre-ISSU Checks section.

- bootflash: does not have enough space to accept the updated image.

- Specified system and kickstart are not compatible.

- Hardware is installed or removed while the upgrade is in process.

- Any power disruption while an upgrade is in progress.

- The entire path for the remote server location is not specified accurately.

Related Documentation

Documentation for Cisco Nexus 5000 Series Switches and Cisco Nexus 2000 Series Fabric Extenders is available at the following URL:

http://www.cisco.com/c/en/us/support/switches/nexus-5000-series-switches/tsd-products-support-series-home.html

The documentation set includes the following types of documents:

- Licensing Information Guide

- Release Notes

- Installation and Upgrade Guides

- Configuration Guides

- Configuration Examples and TechNotes

- Programming Guides

- Operations Guides

- Error and System Message Guides

- Field Notices

- Security Advisories, Responses and Notices

- Troubleshooting Guide

- Command References

- MIB Reference Guide

Documentation Feedback

To provide technical feedback on this document or to report an error or omission, please send your comments to nexus5k-docfeedback@cisco.com. We appreciate your feedback.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What’s New in Cisco Product Documentation RSS feed. The RSS feeds are a free service.

©2012-2017 Cisco Systems, Inc. All rights reserved