Guest

Cisco Nexus 5000 Series Switches

Cisco Nexus 5600 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.0

  • Viewing Options

  • PDF (2.0 MB)
  • EPUB (407.6 KB)
  • MOBI (507.2 KB)
  • PDF (2.0 MB)
  • Feedback

Table of Contents

Cisco Nexus 5600 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.0

Information About Software Images

Supported Hardware

Cisco Nexus 5600 S eries Switches and Associated Expansion Modules

Cisco Nexus Fabric Extenders

Upgrade Guidelines

Using the Install All Command

Upgrading the BIOS and Power Sequencer Images

Impact of Upgrades and Downgrades

In-Service Software Upgrades

ISSU and Layer 3

ISSU Supported Topologies

ISSU Support For Cisco Nexus Fabric Extenders

ISSU Support for vPC Topologies

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

Forcing an 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

Monitoring the Upgrade Status

Downgrading from a Higher Release

Troubleshooting ISSUs and Disruptive Installations

Obtaining Documentation and Submitting a Service Request

Cisco Nexus 5600 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.0

First Published: May 5, 2014

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.

This document includes these sections:

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 6000 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 5672 (N5K-C5672UP)
  • Cisco Nexus 56128 (N5K-C56128P)
  • Nexus 24x10GE Unified Port + 2xQSFP (N56-M24UP2Q)

Cisco Nexus 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
  • Cisco Nexus 2232TM-E Fabric Extender
  • Cisco Nexus 2248PQ Fabric Extender

Upgrade Guidelines

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


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

 

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

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.


Impact of Upgrades and Downgrades

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 2 Upgrade/Downgrade Impact

Current Cisco NX-OS Release
Upgrade to NX-OS Release 7.0(2)N1(1)
Downgrade from NX-OS Release 7.0(2)N1(1)

7.0(1)N1(1)

Nondisruptive upgrade (ISSU)

Disruptive downgrade.


Note The previous table only applies to the Cisco Nexus 5672. The Cisco Nexus 56128 cannot be downgraded from Release 7.0(2)N1(1).


In-Service Software Upgrades

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 to be have a nondisruptive upgrade with an ISSU. It might be necessary to remove the Layer 3 license.

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

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.

Figure 2 Access Switch Topology

 

 

The following figure shows a vPC peering topology.

Figure 3 vPC Peering Topology

 

 

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

Figure 4 Virtual Modular System with Static Fabric Connectivity for FEXs

 

The following figure shows a vertical modular system.

Figure 5 Virtual Modular System

 

 

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

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

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

 

 

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

Figure 11 Cisco Nexus Device Running Bridge Assurance with Another Switch

 

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

 

Figure 12 Dual-Homed FEXs Connected to a Stub Switch

 

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

Figure 13 Single-Homed FEX Connected to Stub Switches

 

 

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

Figure 14 Dual-Homed FEX Connected to Stub Switches

 

 

ISSU Prerequisites

Follow all the upgrade guidelines listed in the “Upgrade Guidelines” section 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).

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

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.

 

Table 4 ISSU Impact to 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 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 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.

FCoE NPV Links

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.

Layer-2 Protocols Impact

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

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

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 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:n6000-uk9.7.0.2.N1.1.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.
switch# show install all impact kickstart bootflash:n6000-uk9-kickstart.7.0.2.N1.1.bin system bootflash:n6000-uk9.7.0.2.N1.1.bin
 
Verifying image bootflash:/n6000-uk9-kickstart.7.0.2.N1.1.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/n6000-uk9.7.0.2.N1.1.bin for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/n6000-uk9.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/n6000-uk9-kickstart.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/n6000-uk9.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "fex3" version from image bootflash:/n6000-uk9.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "fexth" version from image bootflash:/n6000-uk9.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "fex" version from image bootflash:/n6000-uk9.7.0.2.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 Reason
------ -------- -------------- ------------ ------
1 yes non-disruptive none
2 yes non-disruptive rolling
3 yes non-disruptive rolling
101 yes non-disruptive none
102 yes non-disruptive none
103 yes non-disruptive none
104 yes non-disruptive none
121 yes non-disruptive none
131 yes non-disruptive none
Images will be upgraded according to following table:
Module Image Running-Version New-Version Upg-Required
------ ---------------- ---------------------- ---------------------- ------------
1 system 7.0(2)N1(1) 7.0(2)N1(1) no
1 kickstart 7.0(2)N1(1) 7.0(2)N1(1) no
1 bios no
1 power-seq v1.0 v1.0 no
1 fabric-power-seq v2.0 v2.0 no
2 power-seq v2.0 v2.0 no
3 power-seq v2.0 v2.0 no
101 fex3 7.0(2)N1(1) 7.0(2)N1(1) no
102 fexth 7.0(2)N1(1) 7.0(2)N1(1) no
103 fexth 7.0(2)N1(1) 7.0(2)N1(1) no
104 fexth 7.0(2)N1(1) 7.0(2)N1(1) no
121 fexth 7.0(2)N1(1) 7.0(2)N1(1) no
131 fex 7.0(2)N1(1) 7.0(2)N1(1) no
1 microcontroller v0.0.0.40 v0.0.0.37 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

The following table shows an overview of the upgrade process.

 

Table 7 Upgrade Process At-a-Glance

Upgrade Preparation

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

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

The Installer for the Cisco Nexus device upgrades the software. The switch will now run a 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.

Before You Begin

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

 

Command or Action
Purpose

Step 1

dir usb1 :[ directory/ ]

Example:
switch# dir usb1:

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

Step 2

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

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

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

Step 3

copy { usb1 :[ 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 :[ directory/ ] filename running-config

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

(Optional) Copies 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.

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:n6000-uk9.7.0.2.N1.1.bin bootflash:n6000-uk9. 7.0.2.N1.1.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) Copies 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 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.

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 displays the ISSU process.

switch# install all kickstart bootflash:n6000-uk9-kickstart.7.0.2.N1.1.bin system bootflash:n6000-uk9.7.0.2.N1.1.bin
Verifying image bootflash:/n6000-uk9-kickstart.7.0.2.N1.1.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/n6000-uk9.7.0.2.N1.1.bin for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/n6000-uk9.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/n6000-uk9-kickstart.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/n6000-uk9.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "fex3" version from image bootflash:/n6000-uk9.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "fexth" version from image bootflash:/n6000-uk9.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "fex" version from image bootflash:/n6000-uk9.7.0.2.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 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
3 yes disruptive reset Non-disruptive install not supported if L3 was enabled
101 yes disruptive reset Non-disruptive install not supported if L3 was enabled
102 yes disruptive reset Non-disruptive install not supported if L3 was enabled
103 yes disruptive reset Non-disruptive install not supported if L3 was enabled
104 yes disruptive reset Non-disruptive install not supported if L3 was enabled
121 yes disruptive reset Non-disruptive install not supported if L3 was enabled
131 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 7.0(1)N1(1) 7.0(2)N1(1) yes
1 kickstart 7.0(1)N1(1) 7.0(2)N1(1) yes
1 bios no
1 power-seq v1.0 v1.0 no
1 fabric-power-seq v2.0 v2.0 no
2 power-seq v2.0 v2.0 no
3 power-seq v2.0 v2.0 no
101 fex3 7.0(1)N1(1) 7.0(2)N1(1) yes
102 fexth 7.0(1)N1(1) 7.0(2)N1(1) yes
103 fexth 7.0(1)N1(1) 7.0(2)N1(1) yes
104 fexth 7.0(1)N1(1) 7.0(2)N1(1) yes
121 fexth 7.0(1)N1(1) 7.0(2)N1(1) yes
131 fex 7.0(1)N1(1) 7.0(2)N1(1) yes
1 microcontroller v0.0.0.40 v0.0.0.37 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.
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.0.2.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.0.2.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
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
2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ Apr 23 06:50:08 %KERN-3-SYSTEM_MSG: [ 87.236137] PFM: 1 Initializing the kernel module - kernel
2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ Apr 23 06:50:08 %KERN-3-SYSTEM_MSG: [ 87.236143] PFM: 2 Initializing the kernel module - kernel
2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ Apr 23 06:50:08 %KERN-3-SYSTEM_MSG: [ 87.236146] PFM: 3 Initializing the kernel module - kernel
2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ Apr 23 06:50:08 %KERN-3-SYSTEM_MSG: [ 87.236148] PFM: 4 Initializing the kernel module - kernel
2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ Apr 23 06:50:08 %KERN-3-SYSTEM_MSG: [ 87.236159] PFM: 5 Initializing the kernel module - kernel
2014 Apr 23 06:50:15 N128CR-2 %$ VDC-1 %$ Apr 23 06:50:08 %KERN-3-SYSTEM_MSG: [ 87.236311] 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
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/18 changed its status from Created to Configured
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/19 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 121 that is connected with Ethernet2/3 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 121 that is connected with Ethernet3/3 changed its status from Created to Configured
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/20 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 131 that is connected with Ethernet1/50/1 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 103 that is connected with Ethernet2/26/1 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 102 that is connected with Ethernet1/50/2 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 104 that is connected with Ethernet2/26/2 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 131 that is connected with Ethernet1/50/3 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 103 that is connected with Ethernet2/26/3 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 102 that is connected with Ethernet1/50/4 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 102 that is connected with Ethernet2/24 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 104 that is connected with Ethernet2/26/4 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 101 that is connected with Ethernet1/52/1 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 101 that is connected with Ethernet1/52/2 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 101 that is connected with Ethernet1/52/3 changed its status from Created to Configured
2014 Apr 23 06:50:21 N128CR-2 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 101 that is connected with Ethernet1/52/4 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 ...
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 ...
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:44 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/23, hardware type changed to No-Transceiver
2014 Apr 23 06:54:44 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/24, hardware type changed to No-Transceiver
2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/25, hardware type changed to No-Transceiver
2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/26, hardware type changed to No-Transceiver
2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/29, hardware type changed to No-Transceiver
2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/32, hardware type changed to No-Transceiver
2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/33, hardware type changed to No-Transceiver
2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/38, hardware type changed to No-Transceiver
2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/39, hardware type changed to No-Transceiver
2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/40, hardware type changed to No-Transceiver
2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/41, hardware type changed to No-Transceiver
2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/44, hardware type changed to No-Transceiver
2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/45, hardware type changed to No-Transceiver
2014 Apr 23 06:54:45 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/46, 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
System is coming up ... Please wait ...
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
2014 Apr 23 06:55:21 N128CR-2 %$ VDC-1 %$ %ETH_PORT_CHANNEL-5-CREATED: port-channel1112 created
2014 Apr 23 06:55:21 N128CR-2 %$ VDC-1 %$ %ETH_PORT_CHANNEL-5-CREATED: port-channel1113 created
2014 Apr 23 06:55:21 N128CR-2 %$ VDC-1 %$ %ETH_PORT_CHANNEL-5-CREATED: port-channel1114 created
2014 Apr 23 06:55:21 N128CR-2 %$ VDC-1 %$ %ETH_PORT_CHANNEL-5-CREATED: port-channel1132 created
2014 Apr 23 06:55:21 N128CR-2 %$ VDC-1 %$ %ETH_PORT_CHANNEL-5-CREATED: port-channel1248 created
2014 Apr 23 06:55:21 N128CR-2 %$ VDC-1 %$ %ETH_PORT_CHANNEL-5-CREATED: port-channel1312 created
2014 Apr 23 06:55:21 N128CR-2 %$ VDC-1 %$ %ETH_PORT_CHANNEL-5-CREATED: port-channel1412 created
2014 Apr 23 06:55:21 N128CR-2 %$ VDC-1 %$ %ETH_PORT_CHANNEL-5-CREATED: port-channel2311 created
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_UP: Interface loopback2 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: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_UP: Interface loopback2 is up
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)
2014 Apr 23 06:55:26 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface port-channel1312 is down (No operational members)
2014 Apr 23 06:55:26 N128CR-2 %$ VDC-1 %$ %ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: 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.0(2)N1(1)
system: version 7.0(2)N1(1)
Power Sequencer Firmware:
Module 1: version v1.0
Module 2: version v2.0
Module 3: version v2.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.0.2.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.0.2.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. 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

The following lists conditions where a nondisruptive 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 for more information.
  • The installation is a downgrade, such as a higher release to a lower release, unless stated otherwise in the release specific information section.
  • You want to do a disruptive upgrade. See the “Forcing an Upgrade” section.

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

Minimizing the Impact of a Disruptive Upgrade

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

 

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

 

Figure 18 Cisco Nexus Device 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.


Upgrading a Dual-Homed FEX Access Layer


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


A disruptive upgrade causes the switch and any connected FEX to reload. The time required for a FEX to reload is shorter 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 to the hosts to the time required for the FEX to reload (approximately 120 seconds), instead of the time required for the upgrade of the entire access layer. These steps bypass the Cisco NX-OS installer while upgrading the second switch and should be used with caution. Additionally, BIOS and power-sequencer components of the switch are not upgraded, because of the bypass of the Cisco NX-OS installer.

The following are the steps:

  • Upgrade the first vPC switch (vPC primary switch). During this upgrade, the switch is reloaded. When the switch is reloaded, any dual-homed FEX is not reloaded. Only singled-homed FEXs are reloaded. Servers connected to these dual-homed FEXs retain network connectivity through the second (vPC secondary) switch.
  • Verify that the upgrade of the first switch has completed successfully. At the completion of the upgrade, the switch restores vPC peering. However, dual-homed FEXs stay singly connected to the second switch.
  • Set the boot variable on the second switch and save the configuration (preferably from the switch console).

1. Update the boot variable on the switch to point to reflect the new target image.

2. Save the configuration by entering the copy running-config startup-config command.

  • Reload the dual-homed FEXs using the reload fex command. The servers connected to these dual-homed FEXs lose connectivity at this point.
  • Wait for the FEXs to reload. They connect to the first (already upgraded) switch after the reload. The downtime for the servers connected to these FEXs is limited to this reload and reconnect time.
  • Reload the switch by entering the reload command.
  • When the second vPC switch is back up with the new software, vPC peering is reestablished and dual-homed FEXs connect to both peer switches and start forwarding traffic to both switches.

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:
327568 Sep 12 18:31:51 2013 20130912_182850_poap_4401_init.log
4096 Mar 11 20:50:19 2013 DiagLogs/
4194217 Apr 25 17:41:56 2013 bigsur.log
3707 Apr 18 17:26:57 2013 config-on54
2809 Nov 21 23:36:39 2013 config_b4_writeEras
496 Jan 27 00:11:15 2014 convert_pfm1.log
66683392 Mar 20 21:59:43 2013 diag-n5k-o3-4.0.0.014.bin
66474496 Mar 22 22:31:13 2013 diag-n5k-o3-4.0.0.015.1.bin
2830247 Apr 24 21:35:11 2013 dplug
342 Jan 27 00:11:15 2014 fcoe_mgr_cnv.log
115 Jan 27 00:10:10 2014 fib_pre_issu_dump.txt
4558 Sep 12 18:16:01 2013 for-iluka-9_12
3078 Jan 27 00:10:10 2014 fwm_pre_issu_dump.txt
3413 Jun 18 18:53:18 2013 hplus_6_18
8531402 Mar 20 21:59:47 2013 hw_tools.tar.gz
2830 Nov 25 22:19:50 2013 iluka_11_25
65536 Mar 20 21:59:47 2013 lepton-1.3-P2.csco
34737152 Nov 21 18:05:31 2013 n6000-uk9-kickstart.6.0.2.N2.1.bin
37314048 Dec 19 23:06:20 2013 n6000-uk9-kickstart.7.0.0.N1.0.436.bin
37309952 Jan 26 18:43:09 2014 n6000-uk9-kickstart.7.0.0.N1.0.516.bin
244156539 Nov 21 18:06:58 2013 n6000-uk9.6.0.2.N2.1.bin
241848989 Dec 19 23:07:05 2013 n6000-uk9.7.0.0.N1.0.436.bin
241908697 Jan 26 18:43:51 2014 n6000-uk9.7.0.0.N1.0.516.bin
8388608 Mar 20 22:01:45 2013 norcal64_bios_8MB-v15-1229.bin
2830247 Apr 24 21:15:41 2013 nuova-or-dplug-mzg.6.0.2.N2.0.30.bin
11351 Jul 10 18:54:30 2013 out
11351 Jul 10 18:56:44 2013 out1
4096 Apr 24 18:25:11 2013 proc3687/
4096 Apr 24 18:25:11 2013 pss3687/
4096 Sep 12 18:28:48 2013 scripts/
4316 Jan 27 00:10:10 2014 stp.log.1
2457600 Mar 20 22:01:46 2013 tcl_lib.tar
4096 Mar 21 20:29:29 2013 vdc_2/
4096 Mar 21 20:29:29 2013 vdc_3/
4096 Mar 21 20:29:29 2013 vdc_4/
641 Jan 27 00:11:15 2014 vfc_cnv.log
4096 Mar 21 20:29:29 2013 virt_strg_pool_bf/
163840 Mar 20 22:01:46 2013 w2_64-1.2.0.2.csco
 
Usage for bootflash://sup-local
1426644992 bytes used
6127697920 bytes free
7554342912 bytes total
switch#
 

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. The examples in this procedure use SCP.

switch-1# dir bootflash:
25213952 Jun 14 19:11:12 2012 n6000-uk9-kickstart.7.0.2.N1.1.bin
31659520 Dec 31 17:05:37 20012 n6000-uk9-kickstart.7.0.2.N1.1.bin
188774802 Jun 14 19:11:48 2012 n6000-uk9.7.0.1.N1.1.bin
173063276 Jul 03 14:51:16 2012 n6000-uk9.7.0.2.N1.1.bin
 

Step 6 Enter the show install all impact command.

switch-1# show install all impact kickstart bootflash:n6000-uk9-kickstart.7.0.2.N1.1.bin system bootflash:n6000-uk9.7.0.2.N1.1.bin
Verifying image bootflash:/n6000-uk9-kickstart.7.0.2.N1.1.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/n6000-uk9.7.0.2.N1.1.bin for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/n6000-uk9.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/n6000-uk9-kickstart.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/n6000-uk9.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "fex3" version from image bootflash:/n6000-uk9.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "fexth" version from image bootflash:/n6000-uk9.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Extracting "fex" version from image bootflash:/n6000-uk9.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
Performing module support checks.
[####################] 100% -- SUCCESS
Notifying services about system upgrade.
2014 Apr 23 17:23:41 N128CR-3 %$ VDC-1 %$ %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on vsh.13030
[####################] 100% -- SUCCESS
Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes non-disruptive none
2 yes non-disruptive rolling
3 yes non-disruptive rolling
101 yes non-disruptive none
103 yes non-disruptive none
104 yes non-disruptive none
121 yes non-disruptive none
123 yes non-disruptive none
131 yes non-disruptive none
Images will be upgraded according to following table:
Module Image Running-Version New-Version Upg-Required
------ ---------------- ---------------------- ---------------------- ------------
1 system 7.0(2)N1(1) 7.0(2)N1(1) no
1 kickstart 7.0(2)N1(1) 7.0(2)N1(1) no
1 bios v2.7.0(03/12/2014) v2.7.0(03/12/2014) no
1 power-seq v1.0 v1.0 no
1 fabric-power-seq v2.0 v2.0 no
2 power-seq v2.0 v2.0 no
3 power-seq v2.0 v2.0 no
101 fex3 7.0(2)N1(1) 7.0(2)N1(1) no
103 fexth 7.0(2)N1(1) 7.0(2)N1(1) no
104 fexth 7.0(2)N1(1) 7.0(2)N1(1) no
121 fexth 7.0(2)N1(1) 7.0(2)N1(1) no
123 fexth 7.0(2)N1(1) 7.0(2)N1(1) no
131 fex 7.0(2)N1(1) 7.0(2)N1(1) no
1 microcontroller v0.0.0.42 v0.0.0.42 no
 

Step 7 Enter the install all kickstart image system image command.

Substeps 5.a., 5.b., and 5.c. describe how to verify the status of the upgrade while it is occurring.

 
switch-1# install all kickstart bootflash:n6000-uk9-kickstart.7.0.2.N1.1.bin system bootflash:n6000-uk9.7.0.2.N1.1.bin
 
Verifying image bootflash:/n6000-uk9-kickstart.7.0.2.N1.1.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
 
Verifying image bootflash:/n6000-uk9.7.0.2.N1.1.bin for boot variable "system".
[####################] 100% -- SUCCESS
 
Verifying image type.
[####################] 100% -- SUCCESS
 
Extracting "system" version from image bootflash:/n6000-uk9.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
 
Extracting "kickstart" version from image bootflash:/n6000-uk9-kickstart.7.0.2.N1.1.bin.
[####################] 100% -- SUCCESS
 
Extracting "bios" version from image bootflash:/n6000-uk9.7.0.2.N1.1.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 disruptive Reset due to single supervisor
 
 
 
Images will be upgraded according to following table:
Module Image Running-Version New-Version Upg-Required
------ ---------- ---------------------- ---------------------- ------------
1 system 7.0(1)N1(1) 7.0(2)N1(1) yes
1 kickstart 7.0(1)N1(1) 7.0(2)N1(1) yes
1 bios v3.6.0(05/09/2012) v3.6.0(05/09/2012) no
1 power-seq v4.0 v4.0 no
2 power-seq v1.0 v1.0 no
1 uC v1.2.0.1 v1.0.0.14 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.
[# ] 0%2014 Jan 24 21:58:15 Norcal_34 %$ VDC-1 %$ %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by on vsh.5943
[####################] 100% -- SUCCESS
 
Performing configuration copy.
[####################] 100% -- SUCCESS
 
Finishing the upgrade, switch will reboot in 10 seconds.
switch-1# Shutdown Ports..
writing reset reason 49,
2014 Jan 24 21:58:31 Norcal_34 %$ VDC-1 %$ Jan 24 21:58:31 %KERN-0-SYSTEM_MSG: Shutdown Ports.. - kernel
2014 Jan 24 21:58:31 Norcal_34 %$ VDC-1 %$ Jan 24 21:58:31 %KERN-0-SYSTEM_MSG: writing reset reason 49, - kernel
 
Broadcast message from root (Fri Jan 24 21:58:36 2014):
 
The system is going down for reboot NOW!
INIT: Sending processes the TERM signal
2014 Jan 24 21:5Sending all processes the TERM signal...
Sending all processes the KILL signal...
Unmounting filesystems...
Resetting board
Restarting system.
Booting kickstart image: bootflash:/n6000-uk9-kickstart.7.0.2.N1.1.bin....
...............................................................................
..........................................Image verification OK
 
INIT: [ 6.438002] I2C - Mezz absent
devmemfd:0x7fc9eea8
phys->virt: 0x7fc9eec87fc9eea8-->0x8054d12
devmemfd:0x7fc9eef8
phys->virt: 0x7fc9ef187fc9eef8-->0x8054d12
devmemfd:0x7fc9eef8
phys->virt: 0x7fc9ef187fc9eef8-->0x8054d12
devmemfd:0x7fc9eef8
phys->virt: 0x7fc9ef187fc9eef8-->0x8054d12
Starting system POST.....
Executing Mod 1 1 SEEPROM Test:...done (0 seconds)
Executing Mod 1 1 GigE Port Test:....done (32 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~194: 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
Uncompressing system image: bootflash:/n6000-uk9.7.0.2.N1.1.bin Fri Jan 24 22:00:35 PST 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 Jan 24 22:00:58 Norcal_34 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files begin - clis
2014 Jan 24 22:01:09 Norcal_34 %$ VDC-1 %$ Jan 24 22:01:00 %KERN-0-SYSTEM_MSG: [ 6.438002] I2C - Mezz absent - kernel
2014 Jan 24 22:01:09 Norcal_34 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files end - clis
2014 Jan 24 22:01:09 Norcal_34 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: init begin - clis
2014 Jan 24 22:02:54 Norcal_34 %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online
 
 
User Access Verification
switch-1 login:
 

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

switch-2# 2010 Jun 10 18:27:25 N5K2 %$ VDC-1 %$ %SATCTRL-2-SATCTRL_IMAGE: FEX100 Image
update in progress.
 
switch-2# 2010 Jun 10 18:32:54 N5K2 %$ VDC-1 %$ %SATCTRL-2-SATCTRL_IMAGE: FEX100 Image
update complete. Install pending
 

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

switch-2# show fex 100
FEX: 100 Description: FEX0100 state: Online
FEX version: 4.1(3)N1(1) [Switch version: 4.1(3)N1(1)]
Extender Model: N2K-C2148T-1GE, Extender Serial: JAF1343BHCK
Part No: 73-12009-06
pinning-mode: static Max-links: 1
Fabric port for control traffic: Eth1/37
Fabric interface state:
Po5 - Interface Up. State: Active
Eth1/37 - Interface Up. State: Active
 

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


Step 8 Update the boot variable on the secondary switch to reflect the new image.

switch-2(config)# boot system bootflash:n6000-uk9.7.0.2.N1.1.bin
switch-2(config)# boot kickstart bootflash:n6000-uk9-kickstart.7.0.2.N1.1.bin
Issue the copy running startup-configuration command.
switch-2(config)# copy running startup-configuration
[########################################] 100%
 

Step 9 From the secondary switch, reload the first Fabric Extender and then the subsequent Fabric Extenders.

switch-2(config)# reload fex 127
WARNING: This command will reboot FEX 127
Do you want to continue? (y/n) [n] y
Norcal_34(config)#
2014 Jan 24 18:18:14 Norcal_34 %$ VDC-1 %$ %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 2 of Fex 127 that is connected with Ethernet2/7 changed its status from Active to Disconnected
2014 Jan 24 18:18:14 Norcal_34 %$ VDC-1 %$ %NOHMS-2-NOHMS_ENV_FEX_OFFLINE: FEX-127 Off-line (Serial Number SSI153402XS)
2014 Jan 24 18:18:14 Norcal_34 %$ VDC-1 %$ %PFMA-2-FEX_STATUS: Fex 127 is offline
 

Note Only the primary switch shows that the Fabric Extender is online because the secondary switch does not have the new image. The secondary switch shows the Fabric Extender is downloading an image.


switch-2# show fex 127
FEX: 127 Description: FEX127 state: Image Download
FEX version: 7.0(2)N1(1) [Switch version: 6.0(2)N1(2)]
Extender Serial: SSI153402XS
Extender Model: N2K-C2232TM-E-10GE, Part No: 73-14645-02
Keepalive pending for 1 intervals
Pinning-mode: static Max-links: 1
Fabric port for control traffic: Eth2/9
FCoE Admin: false
FCoE Oper: true
FCoE FEX AA Configured: false
Fabric interface state:
Po127 - Interface Up. State: Active
Eth2/9 - Interface Up. State: Active
switch-2#
 
switch-1# sh fex 127
FEX: 127 Description: FEX127 state: Online
FEX version: 7.0(2)N1(1) [Switch version: 7.0(2)N1(1)]
Extender Serial: SSI153402XS
Extender Model: N2K-C2232TM-E-10GE, Part No: 73-14645-02
Keepalive pending for 1 intervals
Pinning-mode: static Max-links: 1
Fabric port for control traffic: Eth2/9
FCoE Admin: false
FCoE Oper: true
FCoE FEX AA Configured: false
Fabric interface state:
Po127 - Interface Up. State: Active
Eth2/9 - Interface Up. State: Active
switch-1#
 

Note Make sure that the first Fabric Extender comes up before reloading the subsequent Fabric Extenders.


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

Step 10 On the secondary switch, enter the reload command.


Note Do not save the configuration to ensure that the Fabric Extenders are not lost because the secondary switch does not see the Fabric Extenders online.


switch-2# reload
 
Norcal_34# reload
WARNING: There is unsaved configuration!!!
WARNING: This command will reboot the system
Do you want to continue? (y/n) [n] y
[23065.556813] Shutdown Ports..
[23065.559745] writing reset reason 9,
2014 Jan 24 18:52:53 Norcal_34 %$ VDC-1 %$ Jan 24 18:52:52 %KERN-0-SYSTEM_MSG: [23065.556813] Shutdown Ports.. - kernel
2014 Jan 24 18:52:53 Norcal_34 %$ VDC-1 %$ Jan 24 18:52:52 %KERN-0-SYSTEM_MSG: [23065.559745] writing reset reason 9, - kernel
 
Broadcast message from root (ttyS0) (Fri Jan 24 18:52:57 2014):
 
The system is going down for reboot NOW!
INIT: Sending processes the TERM signal
Norcal_34# Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "npacl" (PID 3258) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "netstack" (PID 3381) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "stp" (PID 3514) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "mrib" (PID 3323) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "m2rib" (PID 3483) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "mcastfwd" (PID 3525) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "l3vm" (PID 3281) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "licmgr" (PID 3205) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "igmp" (PID 3469) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "icmpv6" (PID 3377) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "idehsd" (PID 3264) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "fs-daemon" (PID 3206) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "eth_dstats" (PID 3268) is forced exit.
 
Jan 24 18:52:58 %TTYD-2-TTYD_ERROR TTYD Error ttyd bad select
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "statsclient" (PID 3343) is forced exit.
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "callhome server" (PID 3384) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "arp" (PID 3372) is forced exit.
 
[23071.223966] usdk_sse: mts_send failed:-32 sending to 0xfe000000.274 errno 32
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "adjmgr" (PID 3317) is forced exit.
 
Jan 24 18:52:58 %ADJMGR-3-URIB_SEND_TO_ERROR Send to URIB failed: Invalid argument
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Cert_enroll Daemon" (PID 3278) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Radius Daemon" (PID 3464) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "AAA Daemon" (PID 3279) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Security Daemon" (PID 3277) is forced exit.
 
Jan 24 18:52:58 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vshd" (PID 3201) is forced exit.
 
Sending all processes the TERM signal...
Sending all processes the KILL signal...
Unmounting filesystems...
[23079.740309] Resetting board
 

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 8 lists the show commands that are used to monitor installation upgrades.

 

Table 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

The procedure for entering the install all command to downgrade the switch is identical to using the install all command for a switch upgrade, except that the image files to be loaded are for an earlier release than the image that is currently running on the switch. You can use the show incompatibility system command to ensure that there are no feature incompatibilities between the current release and the target release. Note that downgrades are disruptive. Refer to the release-specific information section to get information about certain downgrades that are nondisruptive.


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.


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.
  • 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-series-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-guides-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-reference-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-and-configuration-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-message-guides-list.html

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 at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html .

Subscribe to What’s New in Cisco Product Documentation , which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.