Cisco Nexus 5010 Switch Installation Guide

Cisco Nexus 5600 Series NX-OS Software

Upgrade and Downgrade Guide, Release

7.3(1)N1(1)

First Published: May 5, 2014

Last Modified: October 11, 2016

This document describes how to upgrade or downgrade Cisco NX-OS software on Cisco Nexus devices and Cisco Nexus Fabric Extenders. Use this document in combination with documents listed in the

“Obtaining Documentation and Submitting a Service Request” section on page 43

.

This document includes these sections:

•

Information About Software Images, page 2

•

•

•

•

•

•

•

•

•

•

•

•

•

Supported Hardware, page 2

Upgrade Guidelines, page 3

Using the Install All Command, page 5

Supported Upgrade and Downgrade Paths for Cisco NX-OS Release 7.3(1)N1(1), page 7

In-Service Software Upgrades, page 8

Upgrading Procedures, page 25

Disruptive Installation Process, page 36

Forcing an Upgrade, page 37

Monitoring the Upgrade Status, page 40

Downgrading from a Higher Release, page 41

Troubleshooting ISSUs and Disruptive Installations, page 42

Related Documentation, page 42

Obtaining Documentation and Submitting a Service Request, page 43

Americas Headquarters:

Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

Information About Software Images

Information About Software Images

Cisco Nexus devices 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 device, see the Cisco Nexus

5600 Series 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 device and the Cisco Nexus 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 Cisco NX-OS Version Identifies

The platform designator is N for the Nexus 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.

Supported Hardware

Cisco Nexus devices 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 5600 Series Switches and Associated Expansion Modules

•

•

•

•

•

•

•

•

Cisco Nexus 5672UP-16G ( N5K-C5672UP-16G)

Cisco Nexus 5648Q (N5K-C5648Q )

Cisco Nexus 5624Q (N5K-C5624Q)

Cisco Nexus 5696Q (N5K-C5696Q)

Cisco Nexus 5672 (N5K-C5672UP)

Cisco Nexus 56128 (N5K-C56128P)

Cisco Nexus 5624Q Gigabit Ethernet Linecard Expansion Module (N56-M12Q)

Cisco Nexus 5648Q Gigabit Ethernet Linecard Expansion Module

Cisco Nexus 5600 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.3(1)N1(1)

2

Upgrade Guidelines

•

•

•

•

Cisco Nexus 5696Q Unified Port Linecard Expansion Module (N5696-M20UP)

Cisco Nexus 5696Q 40 Gigabit Ethernet Linecard Expansion Module (N5696-M12Q)

Cisco Nexus 5696Q 100 Gigabit Ethernet Linecard Expansion Module (N5696-M4C)

Cisco Nexus 56128P Gigabit Ethernet Linecard Expansion Module

Cisco Nexus Fabric Extenders

•

•

•

•

•

•

•

•

•

•

•

•

•

•

Cisco Nexus 2348TQ-E Fabric Extender

Cisco Nexus N2332TQ Fabric Extender

Cisco Nexus 2348TQ Fabric Extender

Cisco Nexus 2348UPQ Fabric Extender

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

Cisco Nexus 2232TM-E Fabric Extender

Cisco Nexus 2248PQ Fabric Extender


When upgrading system software, follow these guidelines:

• Configuration changes

You cannot enter global 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 5600 Series NX-OS System

Management Configuration Guide, Release 7.0

.

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


3


•

•

•

•

•

•

•

•

•

Topology—You should make topology changes such as Spanning Tree Protocol (STP) that affect zoning or Fabric Shortest Path First (FSPF) 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. Also, run the show system internal flash command to check that the threshold limit for the filesystems /bootflash/mnt/pss

/var/tmp and /var/sysmgr are met.

Bootflash—During ISSU, bootflash must be free. Bootflash can be busy due to open or active SFTP session, file operation, and so on.

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 summarizes the terms used in the

install all command output to verify module and software image compatibility.

4


Using the Install All Command

Table 1 install all Commands and Output Terminology

Term bootable

Impact install-type reset sw-reset rolling copy-only force

Definition

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

Type of software upgrade mechanism—disruptive or nondisruptive.

Resets the module.

Resets the module immediately after a switchover.

Upgrades each module in sequence.

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

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 devices and Cisco Nexus 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 devices and the Cisco Nexus 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.


5

Upgrading the BIOS and Power Sequencer Images

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, page 37 .

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.

.

BIOS Revision for Cisco NX-OS 7.3(1)N1(1)

For Cisco NX-OS Release 7.3(1)N1(1), the BIOS versions have been revised, and the following table shows the latest BIOS versions for the various Nexus 56xx and Nexus 60xx series platforms.

Table 2 BIOS Revision for Cisco NX-OS Release 7.3(1)N1(1)

ISSU

Non-disruptive

Non-disruptive

Reload

Required?

Yes

Yes

Platform Latest BIOS Version

Cisco Nexus 5672 UP 2.1.7

Cisco Nexus 6001

(Base-T supervisor)

2.5.0

Cisco Nexus 6001

Cisco Nexus 6004

Cisco Nexus 5696

Cisco Nexus 56128P

2.5.0

3.3.0

2.6.0

3.7.0

Cisco Nexus 5624Q

Cisco Nexus 5648Q

Cisco Nexus

5672UP-16G

1.1.6

1.1.7

0.2.0

Non-disruptive

Non-disruptive

Non-disruptive

Non-disruptive

Non-disruptive

Non-disruptive

Non-disruptive

Yes

Yes

Yes

Yes

Yes

Yes

Yes

6


Supported Upgrade and Downgrade Paths for Cisco NX-OS Release 7.3(1)N1(1)

Supported Upgrade and Downgrade Paths for Cisco

NX-OS Release 7.3(1)N1(1)

Cisco NX-OS supports in-service software upgrades (ISSUs) that allow a Cisco Nexus device 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 an 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 you intend to downgrade the software version, the installation process will be disruptive. For example, rebooting the Cisco Nexus device and any connected

FEX causes a disruption. If Cisco’s virtual port channel (vPC) is configured on Cisco Nexus devices, it is possible to achieve an upgrade/downgrade with very minimal traffic disruption to servers/hosts.

Table 3 Cisco NX-OS Release 7.3(1)N1(1) Supported Upgrade and Downgrade Paths

Current Cisco NX-OS Release

7.3(0)N1(1)

7.2(1)N1(1) 1

7.1(4)N1(1)

Upgrade to NX-OS Release 7.3(1)N1(1)

Non-disruptive upgrade (ISSU)

Downgrade from NX-OS

Release 7.3(1)N1(1)

Disruptive downgrade 2

1.

Possibility of disruptive upgrade if FC or FCoE is enabled and upgrade is from Cisco NX-OS release 7.2(1)N1(1) or earlier. See CSCuq94445 for more details.

2.

In-service software downgrade (ISSD) from Cisco NX-OS Release 7.3.x to any earlier releases is not supported. All incompatible configurations will be lost in the target release. Performing a downgrade will also result in loss of certain configurations such as unified ports, breakout, and FEX configurations.

See CSCul22703 for details. For more information on restoring the configuration, see the “Restoring the Configuration” section in the Cisco Nexus 5600

Series Software Upgrade and Downgrade Guide, Release 7.3(0)N1(1) .

Note If you want to upgrade from a release earlier than Cisco NX-OS release 7.2(1)N1(1) to Cisco NX-OS release 7.3(1)N1(1), then you must first upgrade to Cisco NX-OS release 7.2(1)N1(1) and then to

7.3(1)N1(1).

Note During an upgrade from Cisco NX-OS Release 7.1(4)N1(1) to Cisco NX-OS Release 7.3(1)N1(1), FEXs connected to the upgrading switch will preload twice, once before the switch upgrade and the other, after the switch upgrade.

During a non-disruptive upgrade if one or more FEXs fail during the preload stage before the switch upgrade, the install process will display the preload failure for that particular FEX and continue with the preload of the remaining FEXs.

If one or more FEXs fail during the preload stage after the switch upgrade, the install process will display the preload failure for the particular FEX and will abort.

Note When a switch is connected to Cisco Nexus 2348UPQ, 2348TQ, and 2332TQ Fabric Extender, and you perform a non-disruptive upgrade to Cisco NX-OS Release 7.0(7)N1(1), 7.1(2)N1(1), 7.2(0)N1(1), or

7.3(0)N1(1) and later, then must reload the mentioned FEXs after the non-disruptive upgrade for the

CSCut90356 fix to be effective; alternatively, you must do a disruptive upgrade for these releases.


7

In-Service Software Upgrades

Note If you are performing a non-disruptive upgrade from Cisco NX-OS release 7.0(6)N1(1) to 7.0(7)N1(1) and later release, or from Cisco NX-OS release 7.0(6)N1(1) to a 7.1, 7.2, or 7.3 release, then you must reload the switch for the CSCur26244 fix to be effective; alternatively, you must perform a disruptive upgrade.

Note If you want to upgrade from a release, that is not listed in the “Current Cisco NX-OS Release” column in Table 2 under the “Supported Upgrade and Downgrade Paths for a Cisco NX-OS Release” section 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.

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

Note The Cisco Nexus 5696Q cannot be downgraded from release 7.0(4)N1(1). The Cisco Nexus 56128 cannot be downgraded from release 7.0(2)N1(1). The Cisco Nexus 5672 cannot be downgraded from release 7.0(1)N1(1a).


With a single supervisor system, such as the Cisco Nexus device, an ISSU on the Cisco Nexus device 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 previously 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 device access layer should see no traffic disruption.

ISSU and Layer 3

Cisco Nexus devices support Layer 3 functionality. The system cannot be upgraded with the ISSU process (nondisruptive upgrade) when Layer 3 is enabled. You must unconfigure all Layer 3 features, remove the L3 license, and reload the switch, to be have a nondisruptive upgrade with an ISSU.

ISSU Supported Topologies

This section includes the following topics:

•

•

ISSU Support For Cisco Nexus Fabric Extenders, page 9

ISSU Support for vPC Topologies, page 9

•

•

ISSU Support for vPC Topologies with Fabric Extenders, page 11

ISSU Support With FCoE Topologies, page 11


8


•

•

•

•

Summary of ISSU-Supported Topologies, page 11

Summary of ISSU Unsupported Topologies, page 15

Management Services After an ISSU, page 19

FCoE Protocol and Services During an ISSU, page 19

ISSU Support For Cisco Nexus Fabric Extenders

Cisco Nexus Fabric Extenders act as line cards to Cisco Nexus devices. The Fabric Extenders add flexibility to the data center 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 devices 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

FEXs are upgraded. The FEX upgrades are done in a rolling fashion, one FEX at a time. This upgrade on the Fabric Extenders is nondisruptive, which is similar to the upgrade of the switch.

The time required for an ISSU to complete depends on the number of FEXs 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: switch-2# show vpc brief

Legend:

(*) - local vPC is down, forwarding via vPC peer-link vPC domain id : 777

Peer status : peer adjacency formed ok vPC keep-alive status : peer is alive

Configuration consistency status : success

Per-vlan consistency status : success

Type-2 consistency status : success vPC role : primary

Number of vPCs configured : 139

Peer Gateway : Disabled

Dual-active excluded VLANs : -

Graceful Consistency Check : Enabled

Auto-recovery status : Enabled (timeout = 240 seconds) vPC Peer-link status


9


--------------------------------------------------------------------id Port Status Active vlans

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

1 Po1012 up 1,1001,1009-1029,2000-2019 vPC status

You can monitor the status of an ISSU on the primary switch, 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 an ISSU is in 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 : 777

Peer status : peer adjacency formed ok vPC keep-alive status : peer is alive

Configuration consistency status : success

Per-vlan consistency status : success

Type-2 consistency status : success vPC role : primary

Number of vPCs configured : 139

Peer Gateway : Disabled

Dual-active excluded VLANs : -

Graceful Consistency Check : Enabled

Auto-recovery status : Enabled (timeout = 240 seconds) vPC Peer-link status

--------------------------------------------------------------------id Port Status Active vlans

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

1 Po1012 up 1,1001,1009-1029,2000-2019 vPC status

The following message is displayed on the vPC peer switch when an ISSU is started on the other switch: switch-2# 2014 Jan 26 10:46:08 switch-2 %$ 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:

2010 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# 2010 Jun 10 18:27:25 N5K2 %$ VDC-1 %$ %SATCTRL-2-SATCTRL_IMAGE: FEX100 Image


10

In-Service Software Upgrades update in progress. switch-2# 2010 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 non-disruptive upgrade, in a vPC environment that has FEXs connected to a switch, perform the following steps:

1.

2.

Perform a non-disruptive upgrade on the first switch.

Check the status of FEXs on the second switch prior to performing a non-disruptive 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.

4.

Perform a non-disruptive upgrade on the second switch using the install all command.

After the upgrade is complete on the second switch, 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.

Note From Cisco NX-OS Release 7.1(4)N1(1) onwards, during a non-disruptive upgrade, if one or more FEX fails, the install process will display the upgrade failure for the failed FEX, but will continue with the upgrade process for other FEXs.

ISSU Support With FCoE Topologies

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

Summary of ISSU-Supported Topologies

The following figure shows an access switch topology.


11


Figure 2 Access Switch Topology

Aggregation

Cisco Nexus

Device

The following figure shows a vPC peering topology.

Figure 3 vPC Peering Topology

Aggregation

Cisco Nexus

Device

Cisco Nexus

Device

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

12



Figure 4 Virtual Modular System with Static Fabric Connectivity for FEXs

Cisco Nexus Device

Cisco Nexus

Fabric Extender

Cisco Nexus

Fabric Extender

Hosts Hosts

The following figure shows a vertical modular system.

Figure 5 Virtual Modular System

Cisco Nexus Device

Cisco Nexus

Fabric Extender

Cisco Nexus

Fabric Extender

Hosts Hosts

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

FEXs.


13


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

Aggregation

Cisco Nexus

Device

Cisco Nexus

Fabric Extender

Cisco Nexus

Device

Cisco Nexus

Fabric Extender

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

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

FEXs

Aggregation

Cisco Nexus

Device

Cisco Nexus

Fabric Extender

Cisco Nexus

Device

Cisco Nexus

Fabric Extender

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

FEXs.

14



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

Aggregation

Cisco Nexus

Device

Cisco Nexus

Device

Cisco Nexus

Fabric Extender

Cisco Nexus

Fabric Extender

Summary of ISSU Unsupported Topologies

Two important spanning tree-related requirements for a Cisco Nexus device 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 device that is connected to a blade switch that is running STP.

Figure 9 Connection to a Blade Switch That is Running STP

Cisco Nexus Device

Blade Switches


15


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

Figure 10 Connection to a Downstream Switch That is Running STP

Cisco Nexus Device

Downstream switch

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

Figure 11

Aggregation

Cisco Nexus Device Running Bridge Assurance with Another Switch

Bridge assurance enabled

Cisco Nexus

Device Undergoing

ISSU

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

16



Figure 12

Cisco Nexus

Device

Dual-Homed FEXs Connected to a Stub Switch

Cisco Nexus

Fabric Extender

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

Figure 13

Cisco Nexus

Device

Single-Homed FEX Connected to Stub Switches

Cisco Nexus

Device

Cisco Nexus

Fabric Extender

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


17


Figure 14

Cisco Nexus

Device

Dual-Homed FEX Connected to Stub Switches

Cisco Nexus

Device

Cisco Nexus

Fabric Extender

ISSU Prerequisites

Follow all the upgrade guidelines listed in the

“Upgrade Guidelines” section on page 3

so that ISSU goes smoothly. Make sure that the network is stable and no changes are made while an ISSU is in progress.

In addition, make sure that you check for feature compatibility between the current running release and the target release.

The following figure shows upgrade restrictions.

Figure 15 Upgrade Restrictions

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

18



T opology requirements— A Cisco Nexus device 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 device . 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.

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 4 Inband and Management Ports Services Impacted During ISSU Reset

Service

Telnet/SSH

AAA/RADIUS

HTTP

NTP

Description

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.

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 sessions to the switch are disconnected during an ISSU reboot. After the reboot, the HTTP is restarted and the switch will accept HTTP sessions.

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.

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 recommend that you ensure a stable fabric during an ISSU. See the following table for other ISSU impacts.


19


Table 5

Service

Name Server

ISSU Impact to FCoE Services

Domain Manager

CFS

N-Port Virtualization

Zone Server

FSPF

EPP

FCoE NPV Links

Description

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

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.

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

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.

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.

During an ISSU process, EPP messages are not received/transmitted on the

ISSU switch. New ports in FCoE 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.

When the NPV/FCoE NPV switch is logged into a core switch through an

FCoE NPV link, it will punch heartbeats (FIP keepalives - FKA), toward 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 less than the ISSU downtime. Set disable-fka on the core switch VFC parameters to ensure that the core switch ignores any FKA events.

20



Layer-2 Protocols Impact

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

Table 6 ISSU Impact to Layer 2 Protocols

Protocol

LACP

IGMP

DCBX and LLDP

CDP

L2MP IS-IS

Description

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

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

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.

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.


21


•

•

•

•

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 7 Upgrade show Commands

Command show incompatibility system show logging level

Definition

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

Displays the facility logging severity level configuration. show install all impact

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.

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:n6000-uk9.7.3.1.N1.1.bin

No incompatible configurations

22



•

D isplay 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

• D isplay 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.

switch# show install all impact kickstart bootflash:n6000-uk9-kickstart.7.3.1.N1.1.bin system bootflash:n6000-uk9.7.3.1.N1.1.bin

Verifying image bootflash:/n6000-uk9-kickstart.7.3.1.N1.1.bin for boot variable

"kickstart".

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

Verifying image bootflash:/n6000-uk9.7.3.1.N1.1.bin for boot variable "system".

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

Verifying image type.

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

Extracting "system" version from image bootflash:/n6000-uk9.7.3.1.N1.1.bin.

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

Extracting "kickstart" version from image bootflash:/n6000-uk9-kickstart.7.3.1.N1.1.bin.

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

Extracting "bios" version from image bootflash:/n6000-uk9.7.3.1.N1.1.bin.

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

Extracting "fex3" version from image bootflash:/n6000-uk9.7.3.1.N1.1.bin.


23


24

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

Extracting "fexth" version from image bootflash:/n6000-uk9.7.3.1.N1.1.bin.

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

Extracting "fex" version from image bootflash:/n6000-uk9.7.3.1.N1.1.bin.

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

Performing module support checks.

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

Notifying services about system upgrade.

2014 Apr 22 23:36:18 N128CR-2 %$ VDC-1 %$ %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on vsh.21124

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

Compatibility check is done:

Module bootable Impact Install-type

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

1 yes

2 yes

3 yes

101 yes

102 yes

103 yes

104 yes

121 yes

131 yes

Reason

------

Images will be upgraded according to following table:

Module Image Running-Version New-Version Upg-Required

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

1 system 7.3(1)N1(1)

1 kickstart 7.3(1)N1(1)

1 bios

7.3(1)N1(1)

7.3(1)N1(1) no no no

3 power-seq v2.0

101 fex3 7.3(1)N1(1)

102 fexth 7.3(1)N1(1) v2.0

7.3(1)N1(1)

7.3(1)N1(1) no no

no

131 fex 7.3(1)N1(1) 7.3(1)N1(1) no

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

switch# sh 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 device or a single Cisco Nexus device that is connected to one or more FEXs.

The section includes the following topics:

•

Installation At-A-Glance, page 25

•

•

•

•

•

•

•

•

•

Copying the Running Configuration from an External Flash Memory Device, page 26

Copying the Startup Configuration from an External Flash Memory Device, page 27

Upgrade Process in a Non-vPC Topology, page 28

Upgrade Process for a vPC Topology on the Primary Switch, page 35

Upgrade Process for a vPC Topology on the Secondary Switch, page 36

Forcing an Upgrade, page 37

Minimizing the Impact of a Disruptive Upgrade, page 38

Upgrading a Direct vPC or a Single-Homed FEX Access Layer, page 38

Monitoring the Upgrade Status, page 40

Installation At-A-Glance

The following table shows an overview of the upgrade process.


25


Table 8

Upgrade Preparation

Pre-ISSU Checks

Upgrade Begins

Upgrade Process At-a-Glance

Upgrade Verification

1.

2.

3.

4.

5.

Log in to the first Cisco Nexus device. 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.

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.

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

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

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

6.

7.

8.

1.

2.

3.

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

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.

Complete the above steps through Step 9 for each Cisco Nexus device in the topology.

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

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

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

4.

5.

1.

2.

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

Enter the

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

show vpc role command to verify the vPC switch role.

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

Peruse the installer impact analysis and accept to proceed.

3.

The Installer for the Cisco Nexus device upgrades the software. The switch will now run a new version of the software.

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.

26



Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Command or Action dir usb1 :[

Before You Begin

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

directory/ ]

Example: switch# dir usb1: copy { usb1 :[ directory/ ] filename

{bootflash:} [ directory/ ] filename

Example: switch# copy usb1:n6000-uk9.7.3.1.N1.1.bin bootflash:n6000-uk9. 7.3.1.N1.1.bin

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

Example: switch# copy usb1:dsn-config.cfg running-config copy { usb1 :[ directory/ ] filename running-config

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

Example: switch# show running-config copy running-config startup-config

Example: switch# copy running-config startup-config show startup-config

Example: switch# show startup-config

Purpose

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

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

filename argument is

Copies the running configuration from an external flash memory device. The sensitive.

filename argument is case

(Optional) Copies the running configuration from an external flash memory device to the bootflash.

(Optional) Displays the running configuration.

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

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

Before You Begin

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

Step 1

Step 2

Command or Action dir usb1 :[ directory/ ]

Example: switch# dir usb1: copy usb1 :[ directory/ ] filename

{bootflash:} [ directory/ ] filename

Example: switch# copy usb1:n6000-uk9.7.3.1.N1.1.bin bootflash:n6000-uk9. 7.3.1.N1.1.bin

Purpose

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

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


27


Step 3

Step 4

Step 5

Step 6

Step 7

Command or Action copy usb1 :[ directory/ ] filename startup-config

Example: switch# copy usb1:dsn-config.cfg startup-config copy usb1 :[ directory/ ] filename startup-config

Example: switch# copy usb1:dsn-config.cfg bootflash:filename show startup-config

Example: switch# show startup-config copy running-config startup-config

Example: switch# copy running-config startup-config show startup-config

Example: switch# show startup-config

Purpose

Copies a saved configuration from an external flash memory device to the startup configuration. The filename argument is case sensitive.

(Optional) Copies a saved configuration from an external flash memory device to the bootflash. The filename argument is case sensitive.


(Optional) Copies the running configuration to 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.

3.

4.

5.

6.

7.

8.

9.

The compatibility checks display the impact of the upgrade.

The installation proceeds or not based on the upgrade impact.

The current state is saved.

The system unloads and runs the new image.

The stateful restart of the system software and application occurs.

The installer resumes with the new image.

The FEXs are upgraded sequentially.

The installation completes.

The following example displays the ISSU process.

switch# install all kickstart bootflash:n6000-uk9-kickstart.7.3.1.N1.1.bin system bootflash:n6000-uk9.7.3.1.N1.1.bin

Verifying image bootflash:/n6000-uk9-kickstart.7.3.1.N1.1.bin for boot variable

"kickstart".

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

Verifying image bootflash:/n6000-uk9.7.3.1.N1.1.bin for boot variable "system".

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

Verifying image type.

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

Extracting "system" version from image bootflash:/n6000-uk9.7.3.1.N1.1.bin.

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

Extracting "kickstart" version from image bootflash:/n6000-uk9-kickstart.7.3.1.N1.1.bin.

28



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

Extracting "bios" version from image bootflash:/n6000-uk9.7.3.1.N1.1.bin.

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

Extracting "fex3" version from image bootflash:/n6000-uk9.7.3.1.N1.1.bin.

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

Extracting "fexth" version from image bootflash:/n6000-uk9.7.3.1.N1.1.bin.

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

Extracting "fex" version from image bootflash:/n6000-uk9.7.3.1.N1.1.bin.

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

Performing module support checks.

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

Notifying services about system upgrade.

2014 Apr 23 06:36:37 N128CR-2 %$ VDC-1 %$ %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on vsh.10184

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

Compatibility check is done:

Module bootable Impact Install-type Reason

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

1

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

3

101

102

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

104

121

131 yes yes yes disruptive reset Non-disruptive install not supported if L3 was enabled disruptive reset Non-disruptive install not supported if L3 was enabled 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 7.0(1)N1(1)

1 kickstart 7.0(1)N1(1)

7.3(1)N1(1)

7.3(1)N1(1) yes yes

1 bios

1 power-seq v1.0

2 power-seq v2.0

3 power-seq v2.0

101 fex3 7.0(1)N1(1) v1.0 v2.0 v2.0 v2.0

7.3(1)N1(1) no no no no no yes

131 fex 7.0(1)N1(1)

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.

7.3(1)N1(1) v0.0.0.37 yes no


29


30

2014 Apr 23 06:40:37 N128CR-2 %$ VDC-1 %$ %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by root on vsh.10259

Performing runtime checks.

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

Setting boot variables.

[# ] 0%2014 Apr 23 06:40:51 N128CR-2 %$ VDC-1 %$ %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by root on vsh.10272

[####################] 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*]

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

Finishing the upgrade, switch will reboot in 10 seconds.

N128CR-2# [20844.494618] Shutdown Ports..

[20844.497558] writing reset reason 49,

2014 Apr 23 06:47:29 N128CR-2 %$ VDC-1 %$ %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by root on vsh.10678

2014 Apr 23 06:47:30 N128CR-2 %$ VDC-1 %$ Apr 23 06:47:29 %KERN-0-SYSTEM_MSG:

[20844.494618] Shutdown Ports.. - kernel

2014 Apr 23 06:47:30 N128CR-2 %$ VDC-1 %$ Apr 23 06:47:29 %KERN-0-SYSTEM_MSG:

[20844.497558] writing reset reason 49, - kernel

2014 Apr 23 06:47:33 N128CR-2 %$ VDC-1 %$ %VPC-2-PEER_KEEP_ALIVE_RECV_FAIL: In domain 400,

VPC peer keep-alive receive has failed

Broadcast message from root (Wed Apr 23 06:47:34 2014):

The system is going down for reboot NOW!

INIT: Sending processes the TERM signal

Apr 23 06:47:35 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "arp" (PID 3767) is forced exit.

Apr 23 06:47:35 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Cert_enroll Daemon" (PID 3687) is forced exit.

Apr 23 06:47:35 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "rpm" (PID 3867) is forced exit.

Apr 23 06:47:35 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "icmpv6" (PID 3768) is forced exit.

Apr 23 06:47:35 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "pktmgr" (PID 3778) is forced exit.

Apr 23 06:47:35 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Radius Daemon" (PID 3857) is forced exit.

Apr 23 06:47:35 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "res_mgr" (PID 3657) is forced exit.

Apr 23 06:47:35 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "ecp" (PID 3861) is forced exit.

Apr 23 06:47:35 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "adjmgr" (PID 3732) is forced exit.

Apr 23 06:47:35 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Security Daemon" (PID 3686) is forced exit.

Apr 23 06:47:35 %ADJMGR-3-URIB_SEND_TO_ERROR Send to URIB failed: Invalid argument



Apr 23 06:47:35 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "AAA Daemon" (PID 3688) is forced exit.

Sending all processes the TERM signal...

Sending all processes the KILL signal...

Unmounting filesystems...

[20859.849841] Resetting board

Booting kickstart image: bootflash:/n6000-uk9-kickstart.7.3.1.N1.1.bin

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

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

Booting kernel

INIT: devmemfd:0x7f9e53d8 phys->virt: 0x7f9e53f87f9e53d8-->0x8054fd2 devmemfd:0x7f9e5428 phys->virt: 0x7f9e54487f9e5428-->0x8054fd2 devmemfd:0x7f9e5428 phys->virt: 0x7f9e54487f9e5428-->0x8054fd2 devmemfd:0x7f9e5428 phys->virt: 0x7f9e54487f9e5428-->0x8054fd2

Starting system POST.....

P(0x3) board

Executing Mod 1 1 SEEPROM Test:

...done (1 seconds)

Executing Mod 1 1 GigE Port Test:

....done (16 seconds)

Executing Mod 1 1 PCIE Test:

........done (0 seconds)

Mod 1 1 Post Completed Successfully

POST is completed can't create lock file /var/lock/mtab~289: No such file or directory (use -n flag to override) nohup: redirecting stderr to stdout rx unmodified, ignoring tx unmodified, ignoring rx unmodified, ignoring tx unmodified, ignoring

Checking all filesystems..... done.

Loading system software

Uncompressing system image: bootflash:/n6000-uk9.7.3.1.N1.1.bin Wed Apr 23 06:49:29 UTC

2014

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

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

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

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

2014 Apr 23 06:50:05 N128CR-2 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files begin - clis

2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ Apr 23 06:50:08 %KERN-3-SYSTEM_MSG: [ 11.801894] sd 0:0:0:0: [sda] Assuming drive cache: write through - kernel

2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ Apr 23 06:50:08 %KERN-3-SYSTEM_MSG: [ 11.803391] sd 0:0:0:0: [sda] Assuming drive cache: write through - kernel


31


32

2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ Apr 23 06:50:08 %KERN-3-SYSTEM_MSG: [ 27.302918]

CMOS: Module initialized - kernel

2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ Apr 23 06:50:08 %KERN-3-SYSTEM_MSG: [ 71.533558] muxif kernel module v1.0 CISCO Systems - kernel

2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ Apr 23 06:50:08 %KERN-3-SYSTEM_MSG: [ 71.611630] inband dev 0:eth4 bfd18000 - kernel

2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ Apr 23 06:50:08 %KERN-3-SYSTEM_MSG: [ 71.693564] vlan: <3>4042 <3> 0 <3> 0 <3> 0 <3> 0 <3> 0 <3> 0 <3> 0 <3> 0 <3> 0 <3> - kernel


PFM: 1 Initializing the kernel module - kernel










PFM: 6 Initializing the platform specific module - kernel

2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files end

- clis

2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: init begin - clis

2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ %VDC_MGR-5-VDC_STATE_CHANGE: vdc 1 state changed to create pending

2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ %SENSOR-3-SENSOR_MSG1: calling sensor_usd_init

2014 Apr 23 06:50:16 N128CR-2 %$ VDC-1 %$ %DAEMON-3-SYSTEM_MSG: Resource Manager Daemon: sdwrap: unknown syslog level:19 - res_mgr

2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex

132 that is connected with Ethernet1/17 changed its status from Created to Configured












131 that is connected with Ethernet1/50/1 changed its status from Created to Configured



























2014 Apr 23 06:50:32 N128CR-2 %$ VDC-1 %$ %IPQOSMGR-4-QOSMGR_PPF_WARNING: PPF library warning: DDB Error: 0x41170040 (ddb_srv_ses_subscribe_launch/6749) .

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






2014 Apr 23 06:54:44 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/22, hardware type changed to No-Transceiver















2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %VDC_MGR-5-VDC_STATE_CHANGE: vdc 1 state changed to create in progress

2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %IM-5-IM_INTF_STATE: mgmt0 is DOWN in vdc 1

2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %VDC_MGR-5-VDC_HOSTNAME_CHANGE: vdc 1 hostname changed to N128CR-2


User Access Verification

N128CR-2 login: 2014 Apr 23 06:54:52 N128CR-2 %$ VDC-1 %$ %IM-5-IM_INTF_STATE: mgmt0 is UP in vdc 1

2014 Apr 23 06:55:21 N128CR-2 %$ VDC-1 %$ %ETH_PORT_CHANNEL-5-CREATED: port-channel10 created








33


34



2014 Apr 23 06:55:22 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_UP: Interface loopback1 is up


2014 Apr 23 06:55:22 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_DOWN_ADMIN_DOWN: Interface loopback1 is down (Administratively down)

2014 Apr 23 06:55:22 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_DOWN_ADMIN_DOWN: Interface loopback2 is down (Administratively down)



2014 Apr 23 06:55:26 N128CR-2 %$ VDC-1 %$ %VDC_MGR-5-VDC_STATE_CHANGE: vdc 1 state changed to active

2014 Apr 23 06:55:26 N128CR-2 %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online

2014 Apr 23 06:55:26 N128CR-2 %$ VDC-1 %$ %VDC_MGR-5-VDC_HOSTNAME_CHANGE: vdc 1 hostname changed to N128CR-2

2014 Apr 23 06:55:26 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN:

Interface port-channel2311 is down (No operational members)


Interface port-channel1312 is down (No operational members)


Interface port-channel1112 is down (No operational members) switch# sh 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-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 2.7.0

loader: version N/A kickstart: version 7.3(1)N1(1) system: version 7.3(1)N1(1)

Power Sequencer Firmware:

Module 1: version v1.0



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

Microcontroller Firmware: version v0.0.0.42

QSFP Microcontroller Firmware:

Module 1: v2.0.0.0

SFP Microcontroller Firmware:

Module 1: v1.1.0.0

Module 2: v1.9.0.0

Module 3: v1.9.0.0

BIOS compile time: 03/12/2014 kickstart image file is: bootflash:///n6000-uk9-kickstart.7.3.1.N1.1.bin

kickstart compile time: 4/21/2014 20:00:00 [04/22/2014 10:08:18] system image file is: bootflash:///n6000-uk9.7.3.1.N1.1.bin

system compile time: 4/21/2014 20:00:00 [04/22/2014 10:09:32]

Hardware cisco Nexus 56128P Chassis ("Nexus 56128P Supervisor")

Intel(R) CPU @ 1.80GHz

with 8243096 kB of memory.



Processor Board ID FOC173354HZ

Device name: N128CR-3 bootflash: 8028160 kB

Kernel uptime is 0 day(s), 10 hour(s), 26 minute(s), 48 second(s)

Last reset at 636710 usecs after Wed Apr 23 06:49:00 2014

Reason: Disruptive upgrade

System version: 7.0(1)N1(1)

Service: plugin

Core Plugin, Ethernet Plugin switch#

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.

4.

5.

2.

3.

6.

7.

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



The configuration is locked on both vPC peer switches.




8.

9.

10.


The FEXs are upgraded sequentially.

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.


35

Disruptive Installation Process

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.

5.

6.

3.

4.





7.

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.

10.

The configuration is unlocked on the primary and secondary switches.

The installation is complete.

Disruptive Installation Process

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

Note Doing a disruptive upgrade or downgrade between incompatible images is not supported with the autoconfig feature. See CSCvb41199 for details.

For FEX configurations, prior to the downgrade, the configuration must be converted (if not already used) to use FEX pre-provisioning configuration.

The following lists the situations where a non-disruptive ISSU might not be possible when upgrading a

Cisco Nexus device:

•

•

The topology and/or features are not ISSU ready. See the “ISSU Prerequisites” section on page 15 for more information.

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

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

7.2(0)N1(1).

36


Forcing an Upgrade

•

•

The installation is a downgrade, such as a higher release to a lower release, unless stated otherwise in the

“Upgrade Guidelines” section on page 3

.

You want to do a disruptive upgrade. See the

“Forcing an Upgrade” section on page 37

.

Restoring the Configuration

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

1.

2.

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

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.

4.

5.

6.

7.

8.

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

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

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.

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 .

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

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

...


37

Minimizing the Impact of a Disruptive Upgrade

You can also add the force keyword 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".

...


A non-ISSU upgrade is a disruptive upgrade that results in the reload of the Cisco Nexus device and the

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 16 Hosts Directly Connected to vPC Peers

Aggregation

Cisco Nexus

Device

Cisco Nexus

Device

38



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

Singled-Homed FEXs

Aggregation

Cisco Nexus

Device

Cisco Nexus

Fabric Extender

Cisco Nexus

Device

Cisco Nexus

Fabric Extender

Figure 18

Cisco Nexus

Device

Cisco Nexus Device Connected to Downstream Switches

Cisco Nexus

Device

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.


39

Monitoring the Upgrade Status

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.

Monitoring the Upgrade Status

Table 9 lists the

show commands that are used to monitor installation upgrades.

Table 9 Monitoring the Upgrade Process

Command show fex show install all failure-reason

Definition

Displays the Fabric Extender status during an ISSU.

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

Displays a high-level log of the installation.

Displays detailed logs of the last installation-related command.

show install all status show system internal log install details show system internal log install history show tech-support

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

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


40

Downgrading from a Higher Release


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

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

199 FEX0199 Online N2K-C2248TP-1GE JAF1342ANRL switch-2# show fex

FEX FEX FEX FEX


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

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 7.3(1)N1(1) 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.

4.

5.

6.

7.

8.

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

Perform in-service software downgrade (ISSD) using the install all command from Cisco NX-OS

Release 7.2(0)N1(1) to a lower release. In case of VPC, downgrade the primary switch first and then the secondary switch.

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.

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

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

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.


41

Troubleshooting ISSUs and Disruptive Installations

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

“PreInstallation Checks” section on page 21

.

•

•

•

•

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

The specified system and kickstart are not compatible.

The hardware is installed or removed while the upgrade is in process.

A power disruption occurs while the upgrade is in progress.

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

Related Documentation

Documentation for the Cisco Nexus 5600 Series Switch is available at the following URL: http://www.cisco.com/c/en/us/support/switches/nexus-5000-series-switches/tsd-products-support-serie s-home.html

The documentation set is divided into the following categories:

Release Notes

The release notes are available at the following URL: http://www.cisco.com/c/en/us/support/switches/nexus-5000-series-switches/products-release-notes-list

.html

Installation and Upgrade Guides

The installation and upgrade guides are available at the following URL: http://www.cisco.com/c/en/us/support/switches/nexus-5000-series-switches/products-installation-guid es-list.html

Command References

The command references are available at the following URL: http://www.cisco.com/c/en/us/support/switches/nexus-5000-series-switches/products-command-refere nce-list.html

Configuration Guides

The configuration guides are available at the following URL: http://www.cisco.com/c/en/us/support/switches/nexus-5000-series-switches/products-installation-andconfiguration-guides-list.html

Error and System Messages

The system message reference guide is available at the following URL: http://www.cisco.com/c/en/us/support/switches/nexus-5000-series-switches/products-system-messageguides-list.html

42


Obtaining Documentation and Submitting a Service Request

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to [email protected]

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


43

44


Cisco Nexus 5010 Switch Installation Guide

Cisco Nexus 5600 Series NX-OS Software

Upgrade and Downgrade Guide, Release

7.3(1)N1(1)

Information About Software Images

Supported Hardware

Cisco Nexus 5600 Series Switches and Associated Expansion Modules

Cisco Nexus Fabric Extenders

Upgrade Guidelines

Using the Install All Command

Upgrading the BIOS and Power Sequencer Images

BIOS Revision for Cisco NX-OS 7.3(1)N1(1)

Supported Upgrade and Downgrade Paths for Cisco

NX-OS Release 7.3(1)N1(1)

In-Service Software Upgrades

ISSU and Layer 3

ISSU Supported Topologies

ISSU Support For Cisco Nexus Fabric Extenders

ISSU Support for vPC Topologies

Verifying the vPC Status on a Peer Switch During an Upgrade

Viewing System Messages on Peer Switches

ISSU Support for vPC Topologies with Fabric Extenders

ISSU Support With FCoE Topologies

Summary of ISSU-Supported Topologies

Summary of ISSU Unsupported Topologies

ISSU Prerequisites

Management Services After an ISSU

FCoE Protocol and Services During an ISSU

Layer-2 Protocols Impact

Ethernet Interfaces on the Switch and the Fabric Extenders

PreInstallation Checks

Upgrading Procedures

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

Disruptive Installation Process

Restoring the Configuration

Forcing an Upgrade

Minimizing the Impact of a Disruptive Upgrade

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

Monitoring the Upgrade Status

Downgrading from a Higher Release

Troubleshooting ISSUs and Disruptive Installations

Related Documentation

Documentation Feedback

Obtaining Documentation and Submitting a Service Request

Related manuals

Cisco

Nexus 5020

Cisco

Nexus 5020

Cisco

Nexus 5020

Cisco

Nexus 5010

Cisco

Nexus 5548P Switch