 Feedback
|
Table Of Contents
Cisco Nexus 5000 Series NX-OS Upgrade and Downgrade Guide, Release 5.0
Information About Software Images
Cisco Nexus 5000 Series Switches and Associated Expansion Modules
Cisco Nexus 5500 Platform Switches and Associated Expansion Modules
Cisco Nexus 2000 Series Fabric Extenders
Upgrading the BIOS and Power Sequencer Images
Impact of Upgrades and Downgrades
ISSU Support For Cisco Nexus 2000 Series Fabric Extenders
ISSU Support For vPC Topologies
ISSU Support For vPC Topologies With Fabric Extenders
ISSU Support With Fibre Channel and FCoE Topologies
Summary of ISSU-Supported Topologies
Summary of ISSU Unsupported Topologies
Management Services After an ISSU
Fiber Channel/FCoE Protocol & Services During an ISSU
Ethernet interfaces on the switch and the Fabric Extenders
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 in vPC Topology on the Primary Switch
Upgrade Process in vPC Topology on the Secondary Switch
Disruptive Installation Process
Upgrading From Cisco NX-OS Release 4.1(3)N2(1) and Earlier Releases (Disruptive Upgrade)
Minimizing the Impact of a Disruptive Upgrade
Upgrading A Direct Vpc Or A Single-Homed Fex Access Layer
Upgrading A Dual-Homed FEX Access Layer
Downgrading From a Higher Release
Troubleshooting ISSUs and Disruptive Installations
Installation and Upgrade Guides
Obtaining Documentation and Submitting a Service Request
Cisco Nexus 5000 Series NX-OS Upgrade and Downgrade Guide, Release 5.0
This document describes how to upgrade or downgrade Cisco NX-OS software on Cisco Nexus 5000 Series switches and Cisco Nexus 2000 Series Fabric Extenders.Use this document in combination with documents listed in the"Related Documentation" section on page 44.
This document includes these sections:
•
Information About Software Images, page 1
•
•
•
•
•
•
•
•
•
Information About Software Images
Cisco Nexus 5000 Series switches are shipped with the Cisco NX-OS software pre-installed 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 software. For updated information about the Cisco NX-OS software for the Cisco Nexus 5000 Series switch, see the Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Fabric Extender Release Notes.
The Cisco NX-OS software consists of the kickstart image and the system image. The system image includes software for the Cisco Nexus 5000 Series switch and the Cisco Nexus 2000 Series Fabric Extenders 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. "Figure 1Cisco NX-OS Version Identifies" section on page 2 shows the version identifiers that are used with a combination of platform-independent and platform-dependent schemes for Cisco NX-OS software.
Figure 1 Cisco NX-OS Version Identifies
The platform designator is N for the Nexus 5000 Series Switches, E for the Nexus 4000 Series Switches, and S for the Nexus 1000 Series Switches. Applicable features, functions, and fixes in the platform independent code are present in the platform dependent release, in figure above, applicable fixes in Cisco NX-OS Software Release 4.0(1a) are present in the 4.0(1a)N1(1a) release.
Supported Hardware
Cisco Nexus 5000 Series switches are shipped with the Cisco NX-OS software pre-installed. Cisco NX-OS upgrades and downgrades are supported on the following hardware:
Cisco Nexus 5000 Series Switches and Associated Expansion Modules
•
•
•
•
•
•
Cisco Nexus 5500 Platform Switches and Associated Expansion Modules
•
•
•
Cisco Nexus 2000 Series Fabric Extenders
•
•
•
•
Upgrade Guidelines
When upgrading system software, follow these guidelines:
•
You cannot enter configuration mode during an upgrade. You should save, commit, or discard any active configuration sessions before upgrading or downgrading the Cisco NX-OS software image. The active configuration session is deleted without warning during a reload.
Use the show configuration session summary command to verify that there are no active configuration sessions.
switch# show configuration session summaryThere are no active configuration sessionsFor more information on configuration sessions, see the Cisco Nexus 5000 Series System Management Configuration Guide.
Note•
You should make topology changes such as STP or FC fabric changes that affect zoning, Fabric Shortest Path First (FSPF), or FC domains before you perform an upgrade. You should perform module installations or removals only before or after an upgrade.
•
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.
•
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.
•
Avoid power interruptions during an install procedure. Power interruptions can corrupt the software image.
•
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.
•
Ensure that the specified system and kickstart images are compatible with each other as follows:
•
•
•
–
–
•
Use the following commands to prepare for and install the new software:
•
•
•
We recommended that you log in to the console port to begin the upgrade process. In vPC topologies, the first upgrade can be performed on either the primary or secondary switch in the topology
•
Table 1-1 summarizes the terms used in the install all command output to verify module and software image compatibility.
Using The install all Command
The install all command triggers the ISSU on Cisco Nexus 5000 Series switches and Cisco Nexus 2000 Series Fabric Extenders. The following images are upgraded during the installation:
•
•
•
•
•
The install-all command provides the following benefits:
•
•
•
Do you want to continue (y/n) [n] : y•
•
•
•
•
•
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•
Upgrading the BIOS and Power Sequencer Images
Changes to BIOS and power-sequencers are rare; however, when they occur, they are included in the NX-OS system image and the BIOS and power sequencer are upgraded as during the install process. The summary displayed by the installer during the installation process indicates the current version of the BIOS and power sequencer and the target version.
NoteImpact of Upgrades and Downgrades
NX-OS supports a technology called In-Service Software Upgrade (ISSU) that allows a Cisco Nexus 5000 Series switches and any connected FEXs to be upgraded without any traffic disruption (with a brief control plane disruption). A few conditions have to be met for the system to be upgraded via ISSU process - the access layer topology should be ISSU compliant, the current and target versions should be ISSU capable and the network should be stable. Please see sections on ISSU for more details.
In the case where the conditions required for ISSU are not met or if the user intends to downgrade the software version, the installation process will be disruptive - Cisco Nexus 5000 Series switch and any connected FEX will be rebooted, causing a disruption. If Cisco's Virtual Port-Channel (vPC) technology is configured on Cisco Nexus 5000 Series switches, it is possible to achieve an upgrade/downgrade with very minimal traffic disruption to servers/hosts. Please see the section on Minimizing traffic disruption during a non-ISSU installation process for more details.
In-Service Software Upgrades
ISSU stands for In-Service Software Upgrade. Support for ISSU on Cisco Nexus 5000 Series switches and Cisco Nexus 2000 Series Fabric Extenders was added with the 4.2(1)N1(1) NX-OS software release. With this, it is possible to upgrade a Nexus access layer without causing any traffic disruption to servers.
Traditionally, ISSU has been supported on systems with dual-supervisors modular systems like Cisco Nexus 7000 and Cisco Catalyst 6500. With a dual-supervisor system, it is possible to achieve ISSU via a rolling upgrade process - upgrade the standby supervisor to the new software; failover to the standby supervisor - this causes the control plane to run the newer version of software; upgrade the supervisor that is now the standby (was previously active) - this upgrades both supervisors; finally, upgrade the I/O modules or linecards. In this process, both the control plane and data plane remain available throughout the ISSU process.
With a single supervisor system like a Cisco Nexus 5000 Series switch, ISSU process works differently, but provides the same benefits as in a dual-supervisor system. ISSU on the Cisco Nexus 5000 Series switch causes the supervisor CPU to reset and load the new software version. The control plane is inactive in this duration, but the data plane keeps forwarding packets leading to an upgrade with no service disruption. After the CPU loads the updated version of NX-OS, the system restores the control plane to previous known configuration and runtime state and gets in-sync with the data plane, thereby completing the ISSU process. Since the data plane kept forwarding packets while the control plane was upgraded, any servers connected to the Cisco Nexus 5000 Series switch access layer should see no traffic disruption.
ISSU and Layer 3
Cisco Nexus 5500 Platform switches support Layer 3 functionality. However, the system cannot be upgraded with the ISSU process (non-disruptive upgrade) when Layer-3 is enabled. It is required to un-configure all Layer-3 features to be able to upgrade in a non-disruptive way with ISSU.
ISSU Supported Topologies
This section includes the following topics:
•
•
•
•
•
•
•
•
ISSU Support For Cisco Nexus 2000 Series Fabric Extenders
Cisco Nexus 2000 Series Fabric Extenders act as linecards to Cisco Nexus 5000 Series switches, thereby bringing in a lot of advantages - add flexibility to data-center networking infrastructure (simultaneous Top-of-Rack and End-of-Row access layer) by decoupling physical and logical (Layer-2) topology, reducing operation expense by lowering management and troubleshooting points, ability to build larger layer-2 fabric that is loop-free - all with a single layer of switching.
The ISSU process initiated on the Cisco Nexus 5000 Series switches upgrades the entire access layer including the switch and the FEXs that are connect to the switch.
An ISSU first upgrades the switches. Once the switch is operational with the upgraded software, the FEXs are upgraded. This upgrade of the FEX is done in a rolling fashion - one FEX at a time. Note that this upgrade on the Fabric Extenders is non-disruptive, similar to the upgrade of the switch.
Note: The time required for ISSU to complete depends on the number of FEXs connected. The customer should plan a maintenance window with the total upgrade time in mind. Please note that the entire upgrade is expected to be non-disruptive and is not expected to cause any outage to connected servers.
ISSU Support For vPC Topologies
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 co-ordinate 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 ether-channel (static and 802.3ad) and, hence, provide simultaneously data forwarding services to that device.
While upgrading devices in a vPC topology, it is recommended to start with the switch that is the operational primary. The vPC secondary device should be upgraded after the ISSU process completes successfully on the primary device. The two vPC devices continue control plane communication during the entire ISSU process (except when the ISSU process resets the CPU of the switch being upgraded).
Use the show vpc brief command to determine the vPC operational role of the switch:
n5020-2# show vpc briefLegend:(*) - local vPC is down, forwarding via vPC peer-linkvPC domain id : 1000Peer status : peer adjacency formed okvPC keep-alive status : peer is aliveConfiguration consistency status : successvPC role : primaryNumber of vPCs configured : 247Peer Gateway : DisabledDual-active excluded VLANs : -Status of ISSU on the primary device can be monitored from the primary device, until completion, after the primary switch reloads by using the CLI show install all status.
Any attempt to initiate an upgrade on the vPC peer switch, when ISSU is progress on the other switch, will be blocked.
NoteVerifying the vPC Status on a Peer Switch During an Upgrade
To view the vPC status, enter the show vpc command on a peer switch.
switch-2# show vpcLegend:(*) - local vPC is down, forwarding via vPC peer-linkvPC domain id : 1000Peer status : peer adjacency formed okvPC keep-alive status : Suspended during ISSUConfiguration consistency status: successvPC role : primary, operational secondaryNumber of vPCs configured : 100Peer Gateway : DisabledDual-active excluded VLANs : 40vPC Peer-link status------------------------------------------------id Port Status Active vlans-- ---- ------ -----------------------------1 Po100 up 1,40The following message is displayed on the vPC peer switch when ISSU is started on the other switch.
2010 Feb 4 00:07:16 MN5020-4 %$ VDC-1 %$ %VPC-2-VPC_ISSU_START: Peer vPC switch ISSUstart, locking configurationViewing 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 domain1000, VPC peer keep-alive receive has failedInstallation 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 Imageupdate in progress.switch-2# 2010 Jun 10 18:32:54 N5K2 %$ VDC-1 %$ %SATCTRL-2-SATCTRL_IMAGE: FEX100 Imageupdate complete. Install pendingISSU Support For vPC Topologies With Fabric Extenders
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 Fibre Channel and FCoE Topologies
ISSUs are supported on access layer switches when Fibre Channel and FCoE is enabled. You must ensure that the FC fabric is stable before initiating an ISSU in this topology.
Summary of ISSU-Supported Topologies
Figure 2 Access Switch Topology
Figure 3 vPC Peering Topology
Figure 4 Virtual Modular System With Static Fabric Connectivity For FEXs
Figure 5 Virtual Modular System
Figure 6 vPC Peered Dual-Supervisor Virtual Modular System Dual-homed FEXs
Figure 7 Vpc Peered Dual-Supervisor Virtual Modular System Dual-Homed FEXs and Singled-Homed FEXs
Summary of ISSU Unsupported Topologies
There are a couple of important spanning tree related requirements for a Cisco Nexus 5000 Series switch to support ISSU. These requirements are due to the fact that a switch undergoing 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.
•
•
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.
Figure 8 Connection To A Blade Switch That Is Running Spanning Tree Protocol
Figure 9 Connection To A Downstream Switch That Is Running Spanning Tree Protocol
Figure 10 Cisco Nexus 5000 Series Switch Running Bridge Assurance With Another Switch
Figure 11 Dual-Homed FEXs Connected To A Stub Switch
Figure 12 Single-Homed FEX Connected To Stub Switches
Figure 13 vPC Connection to Stub Switches
ISSU Prerequisites
All the upgrade guidelines listed in Cisco NX-OS Upgrade Guidelines section should be strictly adhered to for ISSU to work smoothly. In particular, it is very important to make sure that the network is stable and no changes are made while ISSU is in progress. It is also necessary to make sure that feature compatibility between the current running release and the target release.
Figure 14 Upgrade Restrictions
In addition, there are some specific requirements for non-disruptive upgrade (ISSU).
Topology requirements—Cisco Nexus 5000 Series switch on which ISSU is being initiated should not be in one of the unsupported topologies listed above. In particular, there must be no switch running spanning-tree connected downstream to the switch - in other words, there should be no interface that is in a spanning-tree designated forwarding state. Also, bridge assurance should not be configured on any interface of the Nexus 5000. vPC peer-link is an exception to these requirements.
Layer-2 requirement—ISSU process will be aborted if the system has any LACP fast timers configured.
FC/FCoE requirements—It is expected that the topology is stable for ISSU to work smoothly. The following is a list of things the administrator needs to run through to check stability. Please note that this list is not exhaustive.
Domain Manager—As part of the install process domain manager will check if fabric is in stable state. If a determination is made that the fabric is not stable, installation will be aborted.
CFS—As part of the install process, CFS will check if any application (ntp,fsm, rcsn, fctime, etc) is locked. If any application is holding a CFS lock, installation will be aborted.
Zone Server—Installation process will abort if zone merge or zone change request is in progress.
FSPF—As part of the upgrade process, FSPF will verify if the configured interface dead-interval is greater than 80 seconds, otherwise installation will abort.
Management Services After an ISSU
Prior to the switch being reset for ISSU, inband and management ports are brought down, and are brought back up after ISSU completes. Services that depend on inband and management ports are impacted during this time.
Fiber Channel/FCoE Protocol & Services During an ISSU
During an ISSU process, the control plane will be offline for up to 80 seconds. Any state changes in the network during this time will not be processed. Depending on the change, the impact may vary. It is always recommended to ensure a stable fabric during ISSU
Layer-2 Protocols Impact
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 effectively prevents the link state from transitioning from down to up during an ISSU.
Pre-Installation Checks
It is beneficial to do certain sanity checks to ensure that the system is ready for an ISSU and to understand the impact of ISSU:
•
•
•
•
•
•
Note•
•
•
This table lists the show commands that identify the impact or potential problems that may occur when performing an ISSU.
You can also perform the following tasks to identify potential problems before they occur:
•
•
n5010# show incompatibility system bootflash:n5000-uk9.4.2.1.N1.1a.binNo incompatible configurations•
nexus5010# show fexFEX FEX FEX FEXNumber Description State Model Serial-------------------------------------------------------------------------------------- ----------100 FEX0100 Online N2K-C2224TP-1GE JAF1427BQME101 FEX0101 Online N2K-C2224TP-1GE JAF1427BQMK•
nexus5010# show spanning-tree issu-impactFor ISSU to Proceed, Check the Following Criteria :1. No Topology change must be active in any STP instance2. 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 wellFollowing are the statistics on this switchNo 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.
•
N5K1# show install all impact kickstart bootflash:n5000-uk9-kickstart.4.2.1.N1.1a.binsystem bootflash:n5000-uk9.4.2.1.N1.1a.binVerifying image bootflash:/n5000-uk9-kickstart.4.2.1.N1.1a.bin for boot variable"kickstart".[####################] 100% -- SUCCESSVerifying image bootflash:/n5000-uk9.4.2.1.N1.1a.bin for boot variable "system".[####################] 100% -- SUCCESSVerifying image type.[########### ] 50%[####################] 100% -- SUCCESSExtracting "system" version from image bootflash:/n5000-uk9.4.2.1.N1.1a.bin.[####################] 100% -- SUCCESSExtracting "kickstart" version from image bootflash:/n5000-uk9-kickstart.4.2.1.N1.1a.bin.[####################] 100% -- SUCCESSExtracting "bios" version from image bootflash:/n5000-uk9.4.2.1.N1.1a.bin.[####################] 100% -- SUCCESSExtracting "fex" version from image bootflash:/n5000-uk9.4.2.1.N1.1a.bin.[####################] 100% -- SUCCESSNotifying services about system upgrade.[####################] 100% -- SUCCESSCompatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------1 yes non-disruptive reset100 yes non-disruptive rollingImages will be upgraded according to following table:Module Image Running-Version New-Version Upg-Required------ ---------- ---------------------- ---------------------- ------------1 system 4.2(1)N1(1) 4.2(1)N1(1a) yes1 kickstart 4.2(1)N1(1) 4.2(1)N1(1a) yes1 bios v1.2.0(06/19/08) v1.3.0(09/08/09) yes100 fex 4.2(1)N1(1) 4.2(1)N1(1a) yes1 power-seq v1.2 v1.2 noUpgrading Procedures
The ISSU process is triggered when you enter the install all command. This section describes the sequence of events that occur when you upgrade a single Cisco Nexus 5000 Series switch or a single Cisco Nexus 5000 Series switch that is connected to one or more FEXs. The section includes the following topics:
•
•
•
•
•
•
•
•
•
•
Installation At-A-Glance
Table 1-6shows an overview of upgrade process:
Copying the Running Configuration From an External Flash Memory Device
You can copy configuration files from an external flash memory device.
NoteBefore You Begin
Insert the external flash memory device into the active supervisor module.
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.
NoteBefore You Begin
Insert the external flash memory device into the active supervisor module.
Upgrade Process in a Non-vPC Topology
The following list summarizes the upgrade process in a non-vPC topology:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Table 7 describes the process based on messages displayed on the console of the switch during an ISSU.
Upgrade Process in 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.
Note1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
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.
NoteUpgrade Process in 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.
2.
3.
4.
5.
6.
7.
8.
Note9.
10.
Disruptive Installation Process
The following lists conditions where a nondisruptive ISSU might not be possible when upgrading a Cisco Nexus 5000 Series access layer switch:
•
•
•
•
Forcing an Upgrade
Users can choose to do a disruptive upgrade, if one of the ISSU conditions are not met. One additional reason where a customer might choose to do a disruptive upgrade is described here - please note that Cisco recommends an ISSU process in this case too. With ISSU, FEXs are upgraded in a rolling fashion - one FEX at a time. This requires a longer maintenance window. With a disruptive upgrade all the connected FEXs are upgraded simultaneously - so, the maintenance window can be shorter. If the user needs a shorter maintenance window (with traffic disruption), he can force a disruptive upgrade even if ISSU can be leveraged. It is important to note the possibility of an outage and take required steps in this case.
switch # install all force kickstart bootflash:/kickstart_image.bin systembootflash:/system_image.binInstaller is forced disruptiveVerifying image bootflash:/kickstart_image.bin for boot variable "kickstart".[####################] 100% -- SUCCESSVerifying image bootflash:/system_image.bin for boot variable "system"....You can also add force at the end of the install all command as follows:
switch # install all kickstart bootflash:/kickstart_image.bin systembootflash:/system_image.bin forceInstaller is forced disruptiveVerifying image bootflash:/kickstart_image.bin for boot variable "kickstart"....Upgrading From Cisco NX-OS Release 4.1(3)N2(1) and Earlier Releases (Disruptive Upgrade)
This section describes how to upgrade from Cisco NX-OS Release 4.1(3)N2(1) and earlier releases. An upgrade from these releases will be disruptive. Upgrading a Cisco Nexus 5000 Series switch also upgrades connected Fabric Extenders.
NoteSUMMARY STEPS
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
DETAILED STEPS
Step 1
NoteAccess the Software Download Center at http://www.cisco.com/public/sw-center/index.shtml. Navigate to the software downloads for Cisco Nexus 5000 Series switches. Links to the download images for the switch are listed.
Step 2
Step 3
switch# dir bootflash:4681 May 24 02:43:52 2010 config13176836 May 24 07:19:36 2010 gdb.149152 Jan 12 18:38:36 2009 lost+found/310556 Dec 23 02:53:28 2008 n120058112 Jun 25 23:17:44 2010 n5000-uk9-kickstart.4.1.3.N1.1.bin20217856 May 09 23:17:11 2010 n5000-uk9-kickstart.4.0.1a.N1.0.62.bin76930262 Jun 25 23:11:47 2010 n5000-uk9.4.1.3.N1.1.bin103484727 May 09 23:10:02 2010 n5000-uk9.4.0.1a.N1.0.62.binUsage for bootflash://sup-local74934272 bytes used5550080 bytes free80484352 bytes totalWe 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
switch# delete bootflash:n5000-uk9-kickstart.4.0.1a.N1.0.62.binswitch# delete bootflash:n5000-uk9.4.0.1a.N1.0.62.binStep 5
switch# copy scp://user@scpserver.cisco.com/downloads/n5000-uk9.4.2.1.N1.1.bin bootflash:n5000-uk9.4.2.1.N1.1.binswitch# copy scp://user@scpserver.cisco.com/downloads/n5000-uk9-kickstart.4.2.1.N1.1.binbootflash:n5000-uk9-kickstart.4.2.1.N1.1.binStep 6
switch# show install all impact kickstart bootflash:n5000-uk9-kickstart.4.2.1.N1.1.binsystem bootflash:n5000-uk9.4.2.1.N1.1.binVerifying image bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin for boot variable"kickstart".[####################] 100% -- SUCCESSVerifying image bootflash:/n5000-uk9.4.2.1.N1.1.bin for boot variable "system".[####################] 100% -- SUCCESSVerifying image type.[########### ] 50%[####################] 100% -- SUCCESSExtracting "system" version from image bootflash:/n5000-uk9.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSExtracting "kickstart" version from image bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSExtracting "bios" version from image bootflash:/n5000-uk9.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSExtracting "fex" version from image bootflash:/n5000-uk9.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSNotifying services about system upgrade.[####################] 100% -- SUCCESSCompatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------1 yes disruptive reset Reset due to single supervisor100 yes disruptive reset Reset due to single supervisorImages will be upgraded according to following table:Module Image Running-Version New-Version Upg-Required------ ---------- ---------------------- ---------------------- ------------1 system 4.1(3)N1(1) 4.2(1)N1(1) yes1 kickstart 4.1(3)N1(1) 4.2(1)N1(1) yes1 bios v1.3.0(09/08/09) no100 fex 4.1(3)N1(1) 4.2(1)N1(1) yesStep 7
switch# install all kickstart bootflash:n5000-uk9-kickstart.4.2.1.N1.1.bin systembootflash:n5000-uk9.4.2.1.N1.1.binVerifying image bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin for boot variable"kickstart".[####################] 100% -- SUCCESSVerifying image bootflash:/n5000-uk9.4.2.1.N1.1.bin for boot variable "system".[####################] 100% -- SUCCESSVerifying image type.[####################] 100% -- SUCCESSExtracting "system" version from image bootflash:/n5000-uk9.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSExtracting "kickstart" version from image bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSExtracting "bios" version from image bootflash:/n5000-uk9.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSExtracting "fex" version from image bootflash:/n5000-uk9.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSNotifying services about system upgrade.[####################] 100% -- SUCCESSCompatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------1 yes disruptive reset Reset due to single supervisor100 yes disruptive reset Reset due to single supervisorImages will be upgraded according to following table:Module Image Running-Version New-Version Upg-Required------ ---------- ---------------------- ---------------------- ------------1 system 4.1(3)N1(1) 4.2(1)N1(1) yes1 kickstart 4.1(3)N1(1) 4.2(1)N1(1) yes1 bios v1.3.0(09/08/09) no100 fex 4.1(3)N1(1) 4.2(1)N1(1) yesSwitch will be reloaded for disruptive upgrade.Do you want to continue with the installation (y/n)? [n] yInstall is in progress, please wait.Setting boot variables.[####################] 100% -- SUCCESSPerforming configuration copy.[####################] 100% -- SUCCESSModule 1: Refreshing compact flash and upgrading bios/loader/bootrom.Warning: please do not remove or power off the module at this time.[####################] 100% -- SUCCESSPre-loading modules.[This step might take up to 20 minutes to complete - please wait.][# ] 0%2010 Jun 10 18:27:25 N5K1 %$ VDC-1 %$ %SATCTRL-2-SATCTRL_IMAGE:FEX100 Image update in progress.[##### ] 20%[###### ] 25%2010 Jun 10 18:32:54 N5K1 %$ VDC-1 %$ %SATCTRL-2-SATCTRL_IMAGE:FEX100 Image update complete. Install pending[####################] 100% -- SUCCESSFinishing the upgrade, switch will reboot in 10 seconds.switch#switch#switch# writing reset reason 31,Broadcast message from root (Thu Jun 10 18:33:16 2010):INIT: Sending processes the TERM signalJun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "stp" (PID 2843) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "netstack" (PID 2782) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Security Daemon" (PID 2706) isforced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Cert_enroll Daemon" (PID 2707) isforced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "igmp" (PID 2808) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Radius Daemon" (PID 2806) isforced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "AAA Daemon" (PID 2708) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vshd" (PID 2636) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vlan_mgr" (PID 2737) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vdc_mgr" (PID 2681) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "urib" (PID 2718) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "u6rib" (PID 2717) is forced exit.Jun 10 18:33:17 %TTYD-2-TTYD_ERROR TTYD Error ttyd bad selectJun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "statsclient" (PID 2684) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "smm" (PID 2637) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "res_mgr" (PID 2688) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "licmgr" (PID 2641) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "l3vm" (PID 2715) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "icmpv6" (PID 2781) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "eth_dstats" (PID 2700) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "arp" (PID 2780) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "fs-daemon" (PID 2642) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "ascii-cfg" (PID 2704) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "adjmgr" (PID 2771) is forcedexit.Jun 10 18:33:19 Unexporting directories for NFS kernel daemon...done.Stopping NFS kernel daemon: rpc.mountd rpc.nfsddone.Unexporting directories for NFS kernel daemon...done.Stopping portmap daemon: portmap.Stopping kernel log daemon: klogd.Sending all processes the TERM signal... done.Sending all processes the KILL signal... done.Unmounting remote filesystems... done.Deactivating swap...umount: none busy - remounted read-onlydone.Unmounting local filesystems...umount: none busy - remounted read-onlydone.mount: you must specify the filesystem typeStarting reboot command: rebootRebooting...Restarting system.The switch reboots and restarts with the new image.For detailed information about the install all command, see Using the install all Command.CautionAfter completing the installation, all traffic through the switch is disrupted while theswitch reboots.Step 8
switch# show versionCisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright ) 2002-2010, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained herein are owned byother third parties and are used and distributed under license.Some parts of this software are covered under the GNU PublicLicense. A copy of the license is available athttp://www.gnu.org/licenses/gpl.html.SoftwareBIOS: version 1.2.0loader: version N/Akickstart: version 4.2(1)N1(1) [build 4.2(1)N1(0.96)]system: version 4.2(1)N1(1) [build 4.2(1)N1(0.96)]BIOS compile time: 06/19/09kickstart image file is: bootflash:/n5000-uk9-kickstart.4.2.1.N1.0.96.binkickstart compile time: 7/14/2010 4:00:00 [07/14/2010 04:27:38]system image file is: bootflash:/n5000-uk9.4.2.1.N1.0.96.binsystem compile time: 7/14/2010 4:00:00 [07/14/2010 05:20:12]Hardwarecisco Nexus5020 Chassis ("40x10GE/Supervisor")Intel) Celeron) M CPU with 2074240 kB of memory.Processor Board ID JAB1232002FDevice name: switchbootflash: 1003520 kBKernel uptime is 13 day(s), 23 hour(s), 25 minute(s), 5 second(s)Last reset at 720833 usecs after Tue Jul 14 11:18:32 2010Reason: Reset by installerSystem version: 4.2(1)N1(0.96)Service:pluginCore Plugin, Ethernet PluginMinimizing the Impact of a Disruptive Upgrade
A non-ISSU upgrade is a disruptive upgrade that results in the reload of the Cisco Nexus 5000 Series switch and the Cisco Nexus 2000 Series Fabric Extenders. The reload is a cold reboot that brings down the control plan and the data plane. The reload causes disruptions to the connected servers and hosts. When 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 thereby reducing the impact.
To reduce the disruption of a disruptive upgrade, follow these steps:
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 15 Hosts Directly Connected Directly to vPC Peers
Figure 16 vPC Peered Dual-Supervisor Virtual Modular System Dual-Homed FEXs and Singled-Homed FEXs
Figure 17 Cisco Nexus 5000 Series Switches Connected To Downstream Switches
To upgrade the access layer without a disruption to hosts, follow these tasks:
•
•
•
•
NoteUpgrading A Dual-Homed FEX Access Layer
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 require for the upgrade of the entire access layer. These steps bypass NX-OS installer while upgrading the second switch (details below) and should be used with caution, only when necessary. Additionally, BIOS and power-sequencer components of switch will not be upgraded, owing to this bypassing of NX-OS installer.
The following are the steps:
•
•
•
1. Update the boot variable on the switch to point to reflect the new target image
2. Save configuration with copy running-config startup-config command
•
•
•
•
Detailed Steps
Step 1
NoteAccess the Software Download Center at http://www.cisco.com/public/sw-center/index.shtml. Navigate to the software downloads for Cisco Nexus 5000 Series switches. Links to the download images for the switch are listed.
Step 2
Step 3
switch# dir bootflash:4681 May 24 02:43:52 2010 config13176836 May 24 07:19:36 2010 gdb.149152 Jan 12 18:38:36 2009 lost+found/310556 Dec 23 02:53:28 2008 n120058112 Jun 25 23:17:44 2010 n5000-uk9-kickstart.4.1.3.N1.1.bin20217856 May 09 23:17:11 2010 n5000-uk9-kickstart.4.0.1a.N1.0.62.bin76930262 Jun 25 23:11:47 2010 n5000-uk9.4.1.3.N1.1.bin103484727 May 09 23:10:02 2010 n5000-uk9.4.0.1a.N1.0.62.binUsage for bootflash://sup-local74934272 bytes used5550080 bytes free80484352 bytes totalWe 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
switch# delete bootflash:n5000-uk9-kickstart.4.0.1a.N1.0.62.binswitch# delete bootflash:n5000-uk9.4.0.1a.N1.0.62.binStep 5
switch-1# dir bootflash:21778944 May 25 23:17:44 2010 n5000-uk9-kickstart.4.2.1.N1.1.bin22557184 Jun 09 23:17:11 2010 n5000-uk9-kickstart.4.1.3.N1.1.bin181095489 May 25 23:11:47 2010 n5000-uk9.4.2.1.N1.1.bin181204582 Jun 09 23:10:02 2010 n5000-uk9.4.1.3.N1.1.binStep 6
switch-1# show install all impact kickstart bootflash:n5000-uk9-kickstart.4.2.1.N1.1.binsystem bootflash:n5000-uk9.4.2.1.N1.1.binVerifying image bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin for boot variable"kickstart".[####################] 100% -- SUCCESSVerifying image bootflash:/n5000-uk9.4.2.1.N1.1.bin for boot variable "system".[####################] 100% -- SUCCESSVerifying image type.[########### ] 50%[####################] 100% -- SUCCESSExtracting "system" version from image bootflash:/n5000-uk9.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSExtracting "kickstart" version from image bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSExtracting "bios" version from image bootflash:/n5000-uk9.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSExtracting "fex" version from image bootflash:/n5000-uk9.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSNotifying services about system upgrade.[####################] 100% -- SUCCESSCompatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------1 yes disruptive reset Reset due to single supervisor100 yes disruptive reset Reset due to single supervisorImages will be upgraded according to following table:Module Image Running-Version New-Version Upg-Required------ ---------- ---------------------- ---------------------- ------------1 system 4.1(3)N1(1) 4.2(1)N1(1) yes1 kickstart 4.1(3)N1(1) 4.2(1)N1(1) yes1 bios v1.3.0(09/08/09) no100 fex 4.1(3)N1(1) 4.2(1)N1(1) yesStep 7
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:n5000-uk9-kickstart.4.2.1.N1.1.bin systembootflash:n5000-uk9.4.2.1.N1.1.binVerifying image bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin for boot variable"kickstart".[####################] 100% -- SUCCESSVerifying image bootflash:/n5000-uk9.4.2.1.N1.1.bin for boot variable "system".[####################] 100% -- SUCCESSVerifying image type.[####################] 100% -- SUCCESSExtracting "system" version from image bootflash:/n5000-uk9.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSExtracting "kickstart" version from image bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSExtracting "bios" version from image bootflash:/n5000-uk9.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSExtracting "fex" version from image bootflash:/n5000-uk9.4.2.1.N1.1.bin.[####################] 100% -- SUCCESSNotifying services about system upgrade.[####################] 100% -- SUCCESSCompatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------1 yes disruptive reset Reset due to single supervisor100 yes disruptive reset Reset due to single supervisorImages will be upgraded according to following table:Module Image Running-Version New-Version Upg-Required------ ---------- ---------------------- ---------------------- ------------1 system 4.1(3)N1(1) 4.2(1)N1(1) yes1 kickstart 4.1(3)N1(1) 4.2(1)N1(1) yes1 bios v1.3.0(09/08/09) no100 fex 4.1(3)N1(1) 4.2(1)N1(1) yesSwitch will be reloaded for disruptive upgrade.Do you want to continue with the installation (y/n)? [n] yInstall is in progress, please wait.Setting boot variables.[####################] 100% -- SUCCESSPerforming configuration copy.[####################] 100% -- SUCCESSModule 1: Refreshing compact flash and upgrading bios/loader/bootrom.Warning: please do not remove or power off the module at this time.[####################] 100% -- SUCCESSPre-loading modules.[This step might take upto 20 minutes to complete - please wait.][# ] 0%2010 Jun 10 18:27:25 N5K1 %$ VDC-1 %$ %SATCTRL-2-SATCTRL_IMAGE:FEX100 Image update in progress.[##### ] 20%[###### ] 25%2010 Jun 10 18:32:54 N5K1 %$ VDC-1 %$ %SATCTRL-2-SATCTRL_IMAGE:FEX100 Image update complete. Install pending[####################] 100% -- SUCCESSFinishing the upgrade, switch will reboot in 10 seconds.switch-1#switch-1#switch-1# writing reset reason 31,Broadcast message from root (Thu Jun 10 18:33:16 2010):INIT: Sending processes the TERM signalJun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "stp" (PID 2843) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "netstack" (PID 2782) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Security Daemon" (PID 2706) isforced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Cert_enroll Daemon" (PID 2707) isforced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "igmp" (PID 2808) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Radius Daemon" (PID 2806) isforced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "AAA Daemon" (PID 2708) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vshd" (PID 2636) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vlan_mgr" (PID 2737) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vdc_mgr" (PID 2681) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "urib" (PID 2718) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "u6rib" (PID 2717) is forced exit.Jun 10 18:33:17 %TTYD-2-TTYD_ERROR TTYD Error ttyd bad selectJun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "statsclient" (PID 2684) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "smm" (PID 2637) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "res_mgr" (PID 2688) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "licmgr" (PID 2641) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "l3vm" (PID 2715) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "icmpv6" (PID 2781) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "eth_dstats" (PID 2700) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "arp" (PID 2780) is forced exit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "fs-daemon" (PID 2642) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "ascii-cfg" (PID 2704) is forcedexit.Jun 10 18:33:17 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "adjmgr" (PID 2771) is forcedexit.Jun 10 18:33:19 Unexporting directories for NFS kernel daemon...done.Stopping NFS kernel daemon: rpc.mountd rpc.nfsddone.Unexporting directories for NFS kernel daemon...done.Stopping portmap daemon: portmap.Stopping kernel log daemon: klogd.Sending all processes the TERM signal... done.Sending all processes the KILL signal... done.Unmounting remote filesystems... done.Deactivating swap...umount: none busy - remounted read-onlydone.Unmounting local filesystems...umount: none busy - remounted read-onlydone.mount: you must specify the filesystem typeStarting reboot command: rebootRebooting...Restarting system.The primary switch restarts with the new image.From the primary switch, verify the status of the fabric extender.switch-1# show fex 100FEX: 100 Description: FEX0100 state: AA Version MismatchFEX version: 4.1(3)N1(1) [Switch version: 4.2(1)N1(1)]pinning-mode: static Max-links: 1Fabric port for control traffic: Eth1/37Fabric interface state:Po5 - Interface Up. State: ActiveEth1/37 - Interface Up. State: ActiveDuring the software upgrade on the primary switch, you can view the FEX upgrade progress using the secondary vPC switch:
switch-2# 2010 Jun 10 18:27:25 N5K2 %$ VDC-1 %$ %SATCTRL-2-SATCTRL_IMAGE: FEX100 Imageupdate in progress.switch-2# 2010 Jun 10 18:32:54 N5K2 %$ VDC-1 %$ %SATCTRL-2-SATCTRL_IMAGE: FEX100 Imageupdate complete. Install pendingVerify the status of the fabric extender from the secondary switch.
switch-2# show fex 100FEX: 100 Description: FEX0100 state: OnlineFEX version: 4.1(3)N1(1) [Switch version: 4.1(3)N1(1)]Extender Model: N2K-C2148T-1GE, Extender Serial: JAF1343BHCKPart No: 73-12009-06pinning-mode: static Max-links: 1Fabric port for control traffic: Eth1/37Fabric interface state:Po5 - Interface Up. State: ActiveEth1/37 - Interface Up. State: Active
NoteStep 8
switch-2(config)# boot system bootflash:n5000-uk9.4.2.1.N1.1.binswitch-2(config)# boot kickstart bootflash:n5000-uk9-kickstart.4.2.1.N1.1.binIssue the copy running startup-configuration command.switch-2(config)# copy running startup-configuration[########################################] 100%Step 9
switch-2# reload fex 100WARNING: This command will reboot FEX 100Do you want to continue? (y/n) [n] yswitch-2# 2010 Jun 10 18:49:54 N5K2 %$ VDC-1 %$ %PFMA-2-FEX_STATUS: Fex 100 is offline2010 Jun 10 18:49:54 N5K2 %$ VDC-1 %$ %NOHMS-2-NOHMS_ENV_FEX_OFFLINE: FEX-100 Off-line(Serial Number JAF1343BHCK)
Noteswitch-2# show fex 100FEX: 100 Description: FEX0100 state: Image DownloadFEX version: 4.2(1)N1(1) [Switch version: 4.1(3)N1(1)]Extender Model: N2K-C2148T-1GE, Extender Serial: JAF1343BHCKPart No: 73-12009-06pinning-mode: static Max-links: 1Fabric port for control traffic: Eth1/37Fabric interface state:Po5 - Interface Up. State: ActiveEth1/37 - Interface Up. State: Activeswitch-1# show fex 100FEX: 100 Description: FEX0100 state: OnlineFEX version: 4.2(1)N1(1) [Switch version: 4.2(1)N1(1)]Extender Model: N2K-C2148T-1GE, Extender Serial: JAF1343BHCKPart No: 73-12009-06pinning-mode: static Max-links: 1Fabric port for control traffic: Eth1/37Fabric interface state:Po5 - Interface Up. State: ActiveEth1/37 - Interface Up. State: Active
NoteWhen all fabric extenders are loaded, go to the next step.
Step 10
Noteswitch-2# reloadWARNING: There is unsaved configuration!!!WARNING: This command will reboot the systemDo you want to continue? (y/n) [n] y2010 Jun 10 18:55:52 N5K2 %$ VDC-1 %$ %PFMA-2-PFM_SYSTEM_RESET: Manual system restart fromCommand Line Interface writing reset reason 9,INIT: Sending processes the TERM signalJun 10 18:55:57 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "statsclient" (PID 2684) is forcedexit.Jun 10 18:55:57 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "stp" (PID 2842) is forced exit.Jun 10 18:55:57 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "netstack" (PID 2777) is forcedexit.Jun 10 18:55:57 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Security Daemon" (PID 2706) isforced exit.Jun 10 1Jun 10 18:55:57 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "ascii-cfg" (PID 2704) isforced exit.Jun 10 18:55:57 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "adjmgr" (PID 2767) is forcedexit.Unexporting directories for NFS kernel daemon...done.Stopping NFS kernel daemon: rpc.mountd rpc.nfsddone.Unexporting directories for NFS kernel daemon...done.Stopping portmap daemon: portmap.Stopping kernel log daemon: klogd.Sending all processes the TERM signal... done.Sending all processes the KILL signal... done.Unmounting remote filesystems... done.Deactivating swap...umount: none busy - remounted read-onlydone.Unmounting local filesystems...umount: none busy - remounted read-onlydone.mount: you must specify the filesystem typeStarting reboot command: rebootRebooting...Restarting system.It is beneficial to do certain sanity checks to ensure that the system is ready for ISSU and to understand the impact of ISSU.
Monitoring the Upgrade Status
Table 1-8 lists the show commands that are used to monitor installation upgrades.
Table 1-8 Monitoring the Upgrade Process
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 oldest to newest.
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.SUCCESSSupervisor non-disruptive upgrade successful.Pre-loading modules.SUCCESSModule 198: Non-disruptive upgrading.SUCCESSModule 199: Non-disruptive upgrading.SUCCESSInstall 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 fexFEX FEX FEX FEXNumber Description State Model Serial------------------------------------------------------------------------198 FEX0198 Hitless Upg Idle N2K-C2248TP-1GE JAF1342ANQP199 FEX0199 Online N2K-C2248TP-1GE JAF1342ANRLswitch-2# show fexFEX FEX FEX FEXNumber Description State Model Serial------------------------------------------------------------------------198 FEX0198 FEX AA Upg Idle N2K-C2248TP-1GE JAF1342ANQP199 FEX0199 Online N2K-C2248TP-1GE JAF1342ANRLDowngrading From a Higher Release
The procedure to downgrade the switch is identical to 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. User can use the show incompatibility system command to ensure that there are no feature incompatibilities between current release and the target release. Please note that downgrades disruptive. Please refer to the Release-specific information section to get information about certain downgrades that are non-disruptive.
NoteTroubleshooting ISSUs and Disruptive Installations
Some of the common causes for ISSU failure include
•
•
•
•
•
•
The following commands can be used to query the status of install and reasons for failures, if any show install all failure-reason displays the application that failed during an installation and why the installation failed show install all status displays a high level log of the last 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 5 installation related commands, from oldest to newest.
Related Documentation
Documentation for Cisco Nexus 3000 Series Switches and Cisco Nexus 2000 Series Fabric Extenders is available at the following URL:
http://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.html
The following are related Cisco Nexus 3000 Series and Cisco Nexus 2000 Series Fabric Extender documents:
Release Notes
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes
Cisco Nexus 5000 Series Switch Release Notes
Configuration Guides
Cisco Nexus 5000 Series Configuration Limits for Cisco NX-OS Release 5.0(2)N1(1b)
Cisco Nexus 5000 Series Configuration Limits for Cisco NX-OS Release 4.2(1)N1(1) and Release 4.2(1)N2(1)
Cisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide
Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide
Cisco Nexus 5000 Series NX-OS Multicast Routing Configuration Guide
Cisco Nexus 5000 Series NX-OS Quality of Service Configuration Guide
Cisco Nexus 5000 Series NX-OS SAN Switching Configuration Guide
Cisco Nexus 5000 Series NX-OS Security Configuration Guide
Cisco Nexus 5000 Series NX-OS System Management Configuration Guide
Cisco Nexus 5000 Series NX-OS Unicast Routing Configuration Guide
Cisco Nexus 5000 Series Switch NX-OS Software Configuration Guide
Cisco Nexus 5000 Series Fabric Manager Configuration Guide, Release 3.4(1a)
Cisco Nexus 7000 Series NX-OS Fundamentals Configuration Guide, Release 4.2
Cisco Nexus 2000 Series Fabric Extender Software Configuration Guide
Maintain and Operate Guides
Cisco Nexus 5000 Series NX-OS Operations Guide
Installation and Upgrade Guides
Cisco Nexus 5000 Series and Cisco Nexus 5500 Platform Hardware Installation Guide
Cisco Nexus 2000 Series Hardware Installation Guide
Cisco Nexus 5000 Series NX-OS Software Upgrade and Downgrade Guide, Release 4.2(1)N1(1)
Regulatory Compliance and Safety Information for the Cisco Nexus 5000 Series Switches and Cisco Nexus 2000 Series Fabric Extenders
Licensing Guide
Cisco NX-OS Licensing Guide
Command References
Cisco Nexus 5000 Series Command Reference
Technical References
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Fabric Extender MIBs Reference
Error and System Messages
Cisco NX-OS System Messages Reference
Troubleshooting Guide
Cisco Nexus 5000 Troubleshooting Guide
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
