B Cisco Nexus 3000 NX Os Software Upgrade Downgrade Guide 92x
B Cisco Nexus 3000 NX Os Software Upgrade Downgrade Guide 92x
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of
the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com
go trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any
other company. (1721R)
© 2018 Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface vii
Audience viii
Document Conventions ix
Documentation Feedback xi
CHAPTER 2 Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software 3
Information About Software Images 3
Supported Hardware 4
About ISSU 5
ISSU Prerequisites 5
Guidelines and Limitations for ISSU 5
Configuring Enhanced ISSU 7
Compact Image for Cisco Nexus 3000 8
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
iii
Contents
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
iv
Contents
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
v
Contents
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
vi
Preface
This preface includes the following sections:
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
vii
Audience
Audience
Audience
This publication is for network administrators who install, configure, and maintain Cisco Nexus switches.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
viii
Document Conventions
Command descriptions use the following conventions:
Convention Description
bold Bold text indicates the commands and keywords that you enter literally
as shown.
Italic Italic text indicates arguments for which you supply the values.
variable Indicates a variable for which you supply values, in context where italics
cannot be used.
string A nonquoted set of characters. Do not use quotation marks around the
string or the string includes the quotation marks.
Convention Description
screen font Terminal sessions and information the switch displays are in screen font.
boldface screen font Information that you must enter is in boldface screen font.
italic screen font Arguments for which you supply values are in italic screen font.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
ix
Related Documentation for Cisco Nexus 9000 Series Switches
Related Documentation for Cisco Nexus 9000 Series Switches
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
x
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, please send your comments
to [email protected]. We appreciate your feedback.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
xi
Communications, Services, and Additional Information
Communications, Services, and Additional Information
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
xii
CHAPTER 1
New and Changed Information
This chapter provides release-specific information for each new and changed feature in the Cisco Nexus 3000
Series NX-OS Software Upgrade and Downgrade Guide, Release 9.x.
• New and Changed Information, on page 1
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
1
New and Changed Information
New and Changed Information
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
2
CHAPTER 2
Upgrading or Downgrading the Cisco Nexus 3000
Series NX-OS Software
This document describes how to reboot the Cisco Nexus 3000 and 3100 Series switches and upgrade or
downgrade the Cisco NX-OS software on these switches:
• Information About Software Images, on page 3
• Supported Hardware, on page 4
• About ISSU, on page 5
• Compact Image for Cisco Nexus 3000, on page 8
• Booting the Switch from the USB, on page 9
• Upgrading the BIOS and Power Sequencer Images, on page 9
• Guidelines for Upgrading in Fast-Reload Scenarios, on page 11
• Guidelines for Upgrading in Non-Fast Reload Scenarios, on page 11
• Upgrade Prerequisites, on page 12
• Pre-Installation Checks, on page 13
• Information About Fast Reboot, on page 14
• Using the Fast-Reload Command, on page 17
• Upgrading and Downgrading Using Fast Reboot, on page 19
• Upgrading Procedures, on page 21
• Guidelines for vPC Upgrades, on page 26
• Monitoring the Upgrade Status, on page 27
• Downgrading from a Higher Release, on page 27
• Troubleshooting Installations, on page 28
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
3
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Supported Hardware
Cisco Nexus 3000 and 3100 Series switches. Using fast-reload after the BIOS upgrade or using install all
commands are the only supported methods of upgrading to the new releases.
Note There is a single image for booting the Cisco Nexus 3000 Series platforms. The kickstart and system images
are not required. The single image binary now boots up on Cisco Nexus 3000 and 3100 Series switches. Due
to a single image binary, the following commands are updated:
• boot nxos single_image_binary
• fast-reload nxos single_image_binary
• install all nxos single_image_binary
Supported Hardware
Cisco Nexus 3000 and Nexus 3100 Series switches are shipped with the Cisco NX-OS software preinstalled.
Cisco NX-OS upgrades and downgrades are supported on the hardware listed in the following sections:
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
4
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
About ISSU
About ISSU
You can perform an in-service software upgrade (ISSU), also known as a non-disruptive upgrade. An ISSU
allows you to upgrade the device software while the switch continues to forward traffic. An ISSU reduces or
eliminates the downtime typically caused by software upgrades.
Enhanced ISSUs are supported for Cisco Nexus 31108PC-V, 31108TC-V, and 3132Q-V switches. The Cisco
NX-OS software normally runs directly on the hardware. However, with enhanced ISSU, the software runs
inside a separate Linux container (LXC) for the supervisor and line cards, and a third container is created as
part of the ISSU procedure and is brought up as a standby supervisor. During a software upgrade, the supervisor
control plane stays up with minimal switchover downtime disruption, and the forwarding state of the network
is maintained more accurately during the upgrade window. The supervisor is upgraded first, and the line cards
are upgraded either one at a time or in a batch.
Note A non-disruptive standard ISSU is supported from Cisco NX-OS Release 7.0(3)I7(4) or 7.0(3)I7(5) to a Cisco
NX-OS 9.x release. Enhanced ISSU to Cisco NX-OS Release 9.2(1) or 9.2(2) is not supported as there are
kernel fixes that cannot take effect without reloading the underlying kernel. For more information, see the
ISSU Support Matrix.
ISSU Prerequisites
All the upgrade guidelines listed in the Cisco NX-OS Upgrade Guidelines section should be strictly adhered
to for the ISSU to work smoothly. In particular, it is important to make sure that the network is stable and no
changes are made while the ISSU is in progress. It is also necessary to ensure feature compatibility between
the current running release and the target release.
The CLI and the SNMP configuration change requests are denied during the ISSU operations.
The STP topology changes are not expected during ISSU.
There should be no interface that is in a spanning-tree designated forwarding state. Also, the bridge assurance
should not be configured on any interface of the switch. The vPC peer-link is an exception to these requirements.
Verify that the current STP topology is consistent with the ISSU requirements. Use the show spanning-tree
issu-impact command to display the STP configuration and whether or not there are potential STP issues.
The ISSU process is aborted if the system has any LACP fast timers configured.
Use the show lacp issu-impact command to display if any port or a peer switch is configured in the rate fast
mode.
The Guest Shell is disabled during an ISSU and it is reactivated after the upgrade. During an ISSU on Cisco
Nexus 3000 Series switches, all First-Hop Redundancy Protocols (FHRPs) cause the other peer to become
active if the node undergoing the ISSU is active.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
5
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Guidelines and Limitations for ISSU
as there are kernel fixes that cannot take effect without reloading the underlying kernel. For more
information, see the ISSU Support Matrix.
• You can perform an ISSU for VXLAN.
• ISSUs for segment routing are supported on Cisco Nexus 3000 Series switches.
• Standard ISSUs are supported on the following platforms:
• Cisco Nexus 3232C and 3264Q switches
• Cisco Nexus 3172PQ, 3172TQ, 3172PQ-XL, and 3172TQ-XL switches
• Cisco Nexus 3164Q and 31128PQ switches
• Cisco Nexus 3132Q, 3132Q-X, and 3132Q-XL switches
• Cisco Nexus 31108PC-V, 31108TC-V, and 3132Q-V switches
• Cisco Nexus 3064, 3064-X, and 3064-T switches
• Cisco Nexus 3048 switches
• Cisco Nexus 3016 switches
• The minimum free bootflash space required to perform ISSU is 550 MB.
• Beginning with Cisco NX-OS Release 9.2(1), a simplified NX-OS numbering format is used for the
platforms that are supported in the release. In order to support a software upgrade from releases prior to
Release 7.0(3)I7(4) that have the old release format, an installer feature supplies an I9(1) label as a suffix
to the actual release during the install all operation. This label is printed as part of the image during the
install operation from any release prior to 7.0(3)I7(4) to Release 9.2(1), and it can be ignored. See the
following example.
switch# install all nxos bootflash:nxos.9.2.1.bin
Installer will perform compatibility check first. Please wait.
Installer is forced disruptive
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
6
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Configuring Enhanced ISSU
Note Enhanced ISSU to Cisco NX-OS Release 9.2(1) or 9.2(2) is not supported as there are kernel fixes that cannot
take effect without reloading the underlying kernel.
Procedure
Step 2 [no] boot mode lxc Enables or disables enhanced (LXC) ISSU.
Example:
switch(config)# boot mode lxc
Using LXC boot mode
Example:
switch(config)# no boot mode lxc
Using normal native boot mode
Step 3 (Optional) show boot mode Shows whether enhanced (LXC) ISSU is
enabled or disabled.
Example:
switch(config)# show boot mode
LXC boot mode is enabled
Example:
switch(config)# show boot mode
LXC boot mode is disabled
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
7
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Compact Image for Cisco Nexus 3000
What to do next
Follow the instructions to upgrade the Cisco NX-OS Software. Make sure to choose the non-disruptive option
if you want to perform an enhanced ISSU or regular ISSU.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
8
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Booting the Switch from the USB
Note The compacted image on Cisco Nexus 30xx, Cisco Nexus 3172, or Cisco Nexus 3172-XL switches should
be used only on the respective switches.
The sequence of compacting the images is also important. You cannot compact the currently loaded image if
you have another image copied on the bootflash.
Use the CLI command install all nxos bootflash: nxos-image-name compact to compact the image.
Note The install all nxos bootflash: nxos-image-namecompact CLI option is applicable for the images with Release
(7.0.3.I3.*) version or later. Do not compact the older Cisco Nexus 3000 Series images with this CLI option.
Image compacting overwrites the earlier image. If the image compacting fails for the currently booted image,
the image is kept intact.
An image compacted can be reused within the below mentioned platform groups only:
Group 1:
• Cisco Nexus 3172 Switch
• Cisco Nexus 3172TQ Switch
• Cisco Nexus 3132Q Switch
Group 2:
• Cisco Nexus 3064 Switch
• Cisco Nexus 3064-T Switch
• Cisco Nexus 3048 Switch
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
9
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
BIOS Upgrade
Note After a successful power sequence upgrade, you must switch off the power to the system and then power it
up.
BIOS Upgrade
See the following guidelines for the BIOS upgrade:
Cisco Nexus 3000 Series platforms require a BIOS upgrade to load Release 7.0(3)I2(1) or later images. Only
BIOS versions 3.x.x are compatible with Release 7.0(3)I2(1) and later releases on all Cisco Nexus 3000 Series
switches. This is taken care in the regular install all method of upgrade but it needs to be explicitly upgraded
prior to the fast-reload upgrade.
Only after the BIOS upgrade is complete, it allows the system to perform fast-reload to the newer releases.
Table 2: BIOS Versions Table for Each Cisco Nexus 3000 Series Platform
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
10
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Guidelines for Upgrading in Fast-Reload Scenarios
Procedure
Upgrade to a new release using fast-reload. Using fast-reload after the BIOS upgrade or using install all are
the only supported methods of upgrading to Cisco NX-OS Release 7.0(3)I3(1). For example:
switch#fast-reload nxos bootflash:nxos.9.2.1.bin
Example:
Note The configuration must be backed up prior to upgrading to a new release as the configuration is
required for the downgrade later.
Procedure
Perform install all to upgrade BIOS and also upgrade the NX-OS image to Cisco NX-OS Release 9.x. Upgrade
the Cisco NX-OS software using the install all nxos bootflash:filename [no-reload | non-disruptive |
non-interruptive | serial] command.
Example:
switch# install all nxos bootflash:nxos.9.2.1.bin
• non-interruptive—Upgrades the software without any prompts. This option skips all error and sanity
checks.
• serial—Upgrades the line cards in the system one at a time. (By default, the line cards are upgraded in
batches to save time.)
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
11
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Upgrade Prerequisites
The configuration must be backed up prior to upgrading to a new release as the configuration is required for
the downgrade later.
Upgrade Prerequisites
• Ensure that the network is stable and no changes are made while an upgrade is in progress.
• Ensure that you check for feature compatibility between the current running release and the target release.
Table 3: Inband and Management Ports Services Impacted During Upgrade Reset
Service Description
Telnet/SSH When an upgrade resets the system to load the target Cisco NX-OS version,
all Telnet/SSH sessions are disconnected and need to be reestablished after the
upgrade completes.
AAA/RADIUS Applications that leverage the AAA Service (such as login) are disabled during
an upgrade, because all Network Management services are disabled during this
time, this behavior is consistent.
HTTP HTTP sessions to the switch are disconnected during an upgrade reboot. After
the reboot, the HTTP is restarted and the switch will accept an HTTP sessions.
NTP NTP sessions to and from the switch are disrupted during an upgrade reboot.
After the reboot, NTP session are reestablished based on the saved startup
configuration.
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. Upgrade should
not impact peers that rely on LACP because the recovery time is less than 90
seconds.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
12
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Ethernet Interfaces on the Switch
Protocol Description
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 upgrade completes. New
router ports or changes to router ports are not detected during this time.
DCBX and LLDP DCBX uses LLDP to exchange parameters between peer devices. Because DCBX
is a link-local protocol, when the switch undergoes an upgrade, the age time is
increased on all ports on the switches that are being upgraded.
Manual configurations are ignored during this time.
CDP During an upgrade, 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 upgrade, the switch transmits L2 IS-IS hellos on all
interfaces to prevent neighbor switches from marking routes to the upgrade switch
as down. Any topology changes during this time are also not acted upon until the
upgrade completes.
Pre-Installation Checks
You should do certain sanity checks to ensure that the system is ready for an upgrade and to understand the
impact of the upgrade:
• 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.
• A BIOS incompatibility issue has been discovered on specific Cisco Nexus 3000 and 3100 Series switches.
When you upgrade these switches from Cisco NX-OS Release 6.0(2)U6(8) or an earlier release to Cisco
NX-OS Release 7.0(x), an MD5 mismatch error might occur and leave the switch at the loader prompt.
We recommend that you view the field notice for this release to see if your software or hardware platforms
are affected. You can find the field notice at the following URL
http://www.cisco.com/c/en/us/support/docs/field-notices/642/fn64233.html
• Enter the install all command to update to the latest Cisco NX-OS software.
• Review the installer impact analysis and choose to continue.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
13
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Information About Fast Reboot
Note The switch might reload at this time and cause a traffic disruption.
The following table lists the show commands that identify the impact or potential problems that may occur
when performing an upgrade.
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 upgrade. Processes with a logging level greater than 5 are not displayed
when you enter the show install all impact command.
show install all impact Displays information that describes the impact of the upgrade. This
command also displays if the upgrade is disruptive or not and if the switch
needs to be rebooted and the reason why.
You 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 pcco.s
No incompatible configurations
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
14
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Fast Reboot Timing Requirements
restart (GR) for compatible peers. You can trigger a fast reboot with graceful restart by using the trigger-gr
option.
Note Only the Cisco Nexus 3164Q and 3264C-E switches support fast reload. Fast reload is supported from Cisco
NX-OS Release 7.0(3)I7(4) or 7.0(3)I7(5) to a Cisco NX-OS 9.x release.
Currently, fast reboot is supported only with limited configurations and topologies. Some of supported
configurations and guidelines are listed in this section. When reloading system software by using the fast-reload
command, use the supported follow these guidelines:
• Configuration changes
You cannot enter configuration mode during a reload or 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
Ensure that you check the compatibility of configurations before using the fast-reload command.
Note Do not use the fast-reload command for upgrades that may lead to kernel or
BIOS changes.
For more information on configuration sessions, see the Cisco Nexus 3000 Series NX-OS System
Management Configuration Guide.
Note The CLI and SNMP configuration change requests are denied.
• Topology—You should make topology changes such as Spanning Tree Protocol (STP) before you perform
an upgrade. You should perform module installations or removals only before or after an upgrade.
However, you should not make changes to the Layer 2 and routing topologies, and the default root bridge
should not be configured.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
15
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Fast Reboot Guidelines
• 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 650 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.
• Link Aggregation Control Protocol (LACP) fast timers—To allow fast-reload, ensure that LACP fast
timers are not configured.
• 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 also
displays whether the upgrade is disruptive or the reason why the upgrade is disruptive, whether the
switch needs to be rebooted, and the reason why it needs to be rebooted.
Note We recommended that you log in to the console port to begin the upgrade process.
• Between control plane disruption and data plane disruption, the CPU stops responding.
• Configuration—Fast reboot currently supports the following configuration:
• BGP v4 and v6
• 16-way ECMP
• 48 downlink L2 ports
• 4 SVIs
• Less than 10 VLANs
• 2000 v4 routes and 2000 v6 routes
• RACLs
• ARPs
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
16
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Using the Fast-Reload Command
• Repaved fast-reload also supports the change in configurations that earlier required a complete reload,
for example, portmode profile, URPF enable/disable, and TCAM re-carving.
• Do not use the fast-reload option for upgrade to/from a version that has reached EOL.
• The fast reload feature also supports the change in the configurations that earlier required a complete
reload, for example, portmode profile, URPF enable/disable, and TCAM re-carving.
• Fast reload does not upgrade the BIOS.
• If you downgrade to a release lower than Cisco NXOS release 6.0(2)U2(1) using the install-all command,
fast reload does not work.
Note Ensure that you have a working image and that you analyze the impact of the fast reboot operation before
using this command.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
17
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Fast Reload in PSS/Binary Configuration
Note The copy file startup and fast reload are supported only for specific configurations, namely Layer 3 ports with
port channels, eBGP, and a few physical l2 ports having SVI only towards the hosts.
Note To ensure that subsequent fast reboot operations, use the NXOS software image as the boot variables, specify
the save-config option while running the fast-reload command. If the save-config option is not specified, the
fast-reload command does not save the boot variables.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
18
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Enabling BGP Graceful Restart with Fast Reboot
Caution The fast-reload to Release 7.0(3)I2(1) is supported only from Release 6.0(2)U6(3a) or later releases, after the
BIOS has been upgraded. Using fast-reload from Release 6.0(2)U6(3a) to Release 7.0(3)I2(1) without upgrading
the BIOS will result in the switch not booting up. See BIOS upgrade for more information.
Note If guest shell or any virtual-services are enabled, the install all command should be used. Use the show
virtual-service list command to verify the presence or the state of the guest shell or any virtual services..
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
19
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Using the Install All Non-Interruptive Command
• System BIOS
• Power sequencers on the system
• You can also use the install all non-interruptive command to install a new image without any prompts.
• The command automatically checks the image integrity, which includes the NXOS software image.
• The command performs a platform validity check to verify that a 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.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
20
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Upgrading Procedures
• Cisco Nexus N3K-C3048TP-1GE-SUP Series switches that use software versions older than Cisco
NX-OS Release 6.0(2)U6(2) need to be updated to Cisco NX-OS Release 6.0(2)U6(2a) before they are
upgraded to Cisco NX-OS Release 6.0(2)U6(3) or later releases.
• Cisco NX-OS Release 5.0(3)U3(1) does not support a software upgrade from Cisco NX-OS Release
5.0(3)U2(2c). If you want to upgrade through this path, see CSCty75328 for details about how to work
around this issue.
• In Cisco NX-OS Release 5.0(3)U3(1), support for IPv6 was added in Control Plane Policing (CoPP). To
enable redirection of IPv6 control packets to the CPU, you must configure IPv6 CoPP on the system.
Running the write erase command on a device that runs Release 5.0(3)U3(1) automatically applies CoPP
on the device and ensures that all IPv4 and IPv6-related CoPP configuration is set up correctly.
• If you upgrade from a Cisco NX-OS release that does not support the CoPP feature to a release that does
support the CoPP feature, you must run the setup utility after the upgrade to enable CoPP on the device.
• If you upgrade from Cisco NX-OS Release 5.0(3)U2(2), which supports the CoPP feature, to Cisco
NX-OS Release 5.0(3)U3(1), which adds CoPP classes for IPv6 support, you must run the setup script
to enable the IPv6 CoPP feature on the device.
• In Cisco NX-OS Release 6.0(2)U2(2), the default interface name in LLDP MIB is in short form. To make
it long form, you must set lldp portid-subtype to 1. In Cisco NX-OS Release 6.0(2)U2(3), this behavior
was reversed. The default interface name in LLDP MIB is now in long form. To make it short form, you
must set lldp portid-subtype to 0.
• If you have set lldp port-subtype to 1 and you are upgrading to Cisco NX-OS Release 6.0(2)U2(4), ensure
that you set lldp port-subtype to 0.
Upgrading Procedures
The upgrade 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 3000 Series switch.
Note If you have a release prior to Release 7.0(3)I2(1), upgrade to Cisco Nexus 3000 Release 6.0.2.U6(3a) first
and then upgrade to Release 7.0(3)I2(1) or later releases.
Note During the compatibility check, the following ISSU-related messages might appear in the Reason field:
Incompatible image Incompatible image for ISSU The Cisco NX-OS image to which
you are attempting to upgrade does
not support ISSU.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
21
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Installation At-A-Glance
Hitless upgrade is not supported Default upgrade is not hitless By default, the software upgrade
process is disruptive. You must
configure the non-disruptive option
to perform an ISSU.
Installation At-A-Glance
The following table shows an overview of the upgrade process.:
Upgrade Preparation 1. Log in to the first Cisco Nexus 3000 Series switch. We recommend that you log
in to the console port. In vPC topologies, the first upgrade can be performed on
either the primary or secondary switch in the topology.
2. Log in to Cisco.com to access the Software Download Center. To log in to
Cisco.com, go to https://www.cisco.com and click Log In at the top of the page.
Enter your Cisco username and password.
3. Choose and download the software image 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 software image to the bootflash using a transfer protocol
such as ftp:, http:, https:, 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 https://www.cisco.com
and the image sizes of the transferred files should be the same.
8. Complete the above Step 1 through Step 7 for each Cisco Nexus 3000 Series
switch in the topology.
Pre-upgrade 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. A BIOS incompatibility issue has been discovered on specific Cisco Nexus 3000
and 3100 Series switches. When you upgrade these switches from Cisco NX-OS
Release 6.0(2)U6(8) or an earlier release to Cisco NX-OS Release 7.0(x), an
MD5 mismatch error might occur and leave the switch at the loader prompt. We
recommend that you view the field notice for this release to see if your software
or hardware platforms are affected. You can find the field notice at the following
URL http://www.cisco.com/c/en/us/support/docs/field-notices/642/fn64233.html
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
22
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Copying the Running Configuration from an External Flash Memory Device
Upgrade Begins 1. Enter the install all command to update to the latest Cisco NX-OS software.
2. Peruse the installer impact analysis and accept to proceed.
3. Installer on Nexus 3000 upgrades the software – the switch will now run new
version of the software.
Upgrade Verification 1. Enter the show install all status command to verify the status of the installation.
Note This procedure applies to the Cisco Nexus 3000 Platform running Cisco NX-OS Release 6.0.2 and later
releases.
Procedure
Step 4 (Optional) copy{usb1:|usb2:}[directory/] You can copy the running configuration from
filename running-config an external flash memory device to the
bootflash.
Example:
switch# copy usb1:dsn-config.cfg
running-config
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
23
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Copying the Startup Configuration from an External Flash Memory Device
Step 6 (Optional) copy running-config startup-config Copies the running configuration to the startup
configuration.
Example:
switch# copy running-config
startup-config
Note This procedure applies to the Cisco Nexus 3000 Platform running Cisco NX-OS Release 6.0.2 and later
releases.
Procedure
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
24
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Upgrade Process in a Non-vPC Topology
Step 6 (Optional) copy running-config startup-config Copies the running configuration to the startup
configuration.
Example:
switch# copy running-config
startup-config
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
25
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Guidelines for vPC Upgrades
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 installation is complete.
Note The vPC primary switch is running the upgraded version and the vPC secondary switch is running the original
software version.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
26
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Monitoring the Upgrade Status
Command Definition
show install all failure-reason Displays the applications that failed during an installation and why the
installation failed.
show system internal log install Displays the detailed logs of the last installation-related command.
details
show system internal log install Displays the detailed logs of the last five installation-related commands,
history 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.
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. See the Cisco Nexus 3000 Series
Switch Release Notes for details.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
27
Upgrading or Downgrading the Cisco Nexus 3000 Series NX-OS Software
Downgrading from a Higher Release to a Lower Release
Caution Make sure that you store the configuration file for later use.
Procedure
Step 4 Enter the install all kickstart img.kick system img.sys no-save bios-force command
Step 5 To verify whether the boot variables exist, enter the show boot command. If the boot variables do not exist,
enter the following set of commands to update the boot variables manually:
switch# configure t
switch (config)# boot kickstart <img.kick>
switch (config)# boot system <img.sys>
switch (config)# write run start
Troubleshooting Installations
Some common causes for upgrade failure are as follows:
• The bootflash: does not have enough space to accept the updated image.
• The hardware is installed or removed while the upgrade is in process.
• A power disruption occurs while an upgrade is in progress.
• The entire path for the remote server location is not specified accurately.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
28
CHAPTER 3
Optionality in Cisco NX-OS Software
This chapter describes optionality in Cisco NX-OS software.
• Optionality in Cisco NX-OS Software, on page 29
• Using Modular Packages, on page 30
• List of Cisco NX-OS Software Packages, on page 31
• Booting the NX-OS Image in Base or Full Mode, on page 33
• Support for ISSU, on page 34
• Information About RPMs, on page 34
• Information About YUM Commands, on page 49
• Creating User Roles for Install Operation, on page 67
Cisco NX-OS software is provisioned to boot the NX-OS software in two modes as described in the following
illustration:
• Base NX-OS mode
• Full NX-OS mode
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
29
Optionality in Cisco NX-OS Software
Using Modular Packages
In base NX-OS mode, basic Layer 2 and Layer 3 features are available. All dynamic routing features (for
example, BGP, OSPF, EIGRP, RIP, and ISIS ) and other optional feature RPMs are not available by default.
You have to install the optional feature RPMs on top of the base image.
In full NX-OS mode, all feature RPMs are installed during boot time when Ethernet plugin is activated by
the plugin manager. There is no change in the user behavior as compared to the previous releases.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
30
Optionality in Cisco NX-OS Software
List of Cisco NX-OS Software Packages
This section describes a new package management for the Cisco NX-OS software image. Beginning with
Cisco NX-OS Release 9.2(1), some NXOS features are considered as optional, for example, BGP, OSPF,
VXLAN, MPLS, Segment Routing.
Each modular package has the following important characteristics:
• Upgrade functionality: The modular packages can be independently upgraded. The modular packages
should be used from the same release as performing upgrades on these packages across multiple releases
is not supported.
• Optionality: The modular packages are optional, for example, these packages can be removed or uninstalled
at run time. The removal of the modular packages does not affect bringing-up the system and it does not
affect any other functionality of the switches.
Note All APIs exported by the modular package should be used only after the installation of the feature.
Note that rpm is the command name for the main command used with RPM, while .rpm is the extension used
for the RPM files.
YUM (Yellowdog Updater, Modified) is an open source command-line tool for RPM based Linux systems.
It allows users and system administrators to easily install, update, remove, or search software packages on
the systems. YUM adds the automatic updates and the package management, including dependency
management, to the RPM systems. In addition to understanding the installed packages on a system, YUM
works with the repositories that are collections of the packages and they are typically accessible over a network
connection.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
31
Optionality in Cisco NX-OS Software
List of Cisco NX-OS Software Packages
• These packages are optional, for example, these packages can be removed or uninstalled at runtime. The
removal of the upgradable optional packages does not affect bringing-up the system and it does not affect
any other functionality on the switches.
Note Use all the APIs that are exported by the optional package only after detecting
the presence of the feature.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
32
Optionality in Cisco NX-OS Software
Booting the NX-OS Image in Base or Full Mode
• LACP
• LLDP
• MTX
• nb-proxy
• NTP
• SNMP
• SSH
• SVI
• TACACS
• VTP
Patchable Packages
The patchable packages contain the following:
• Kernel
• LC
• Network-infra (aka Eth)
• Platform
• Rootfs
• System-infra (aka Core)
For more information, see Using Install CLIs for Feature RPM Operation section.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
33
Optionality in Cisco NX-OS Software
Support for ISSU
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
34
Optionality in Cisco NX-OS Software
Guidelines for NX-OS Feature RPM Installation
Virtualization NA
Note Avoid manually copying the RPMs to system repositories. Instead use the install or YUM commands.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
35
Optionality in Cisco NX-OS Software
Guidelines for NX-OS Feature RPM Installation
The groups-repo and localdb repositories hold the NX-OS feature RPMs that should be installed during the
system boot or during activation. YUM commands or install command can be used for the installation or the
removal of these RPMs.
The following rules are applied to the feature RPM installation procedure during boot or install time:
• Only RPMs with the same NX-OS release number should be selected for the installation.
• Base RPMs cannot be added to the localdb repository.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
36
Optionality in Cisco NX-OS Software
List of NX-OS Mandatory RPMs That Can Be Patched
Table 11: List of the NX-OS Mandatory RPMs that can be Patched
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
37
Optionality in Cisco NX-OS Software
Using Install CLIs for Feature RPM Operation
Table 12: Reference for Install CLIs for the Feature RPM Operations
CLI Description
install reset nxos base This operation installs NXOS in base mode by
removing all patches, upgraded packages, persisted
etc configurations, third party packages installed,
startup configuration (write erase), and reloads the
switch with the default packages.
install reset nxos full This operation installs NXOS with full mode by
removing all patches, upgraded packages, persisted
etc configs, third party packages installed, startup
configuration (write erase), and reloads the switch
with the default packages (with mandatory and
optional RPMs).
install add <> Adds an RPM file to respective repository and updates
the repository (patch/feature/third-party).
install activate <rpm name> Installs an RPM that is present in the repository.
install commit <rpm name> Used for the patch RPMs. Makes the patch persist
during reload.
install remove <rpm name> Removes an RPM file from the repository and updates
the repository.
sh install active Displays the list of the installed RPMs in the system
apart from base rootfs RPMs.
(features/patch/third-party).
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
38
Optionality in Cisco NX-OS Software
Using Install CLIs for Digital Signature Support
CLI Description
sh install inactive Displays the list of the RPMs that are present in the
repository but they are not installed.
sh install packages Lists all the RPMs that are installed including rootfs
RPMs.
Procedure
Cisco release RPMs are signed with Cisco GPG (GNU Privacy Guard) key. The public GPG key is present
at /etc/pki/rpm-gpg/arm-Nexus9k-rel.gpg. To add other public keys from different sources, use the steps
in this section.
RSA signed
switch#
Displays the CLI to verify whether the RPM file is a signed or non-signed file.
----------------------------------------------------
Installed Packages
attr.x86_64 2.4.47-r0.0 installed Unsigned
aufs-util.x86_64 3.14+git0+b59a2167a1-r0.0 installed Unsigned
base-files.n9000 3.0.14-r89.0 installed Unsigned
base-passwd.lib32_x86 3.5.29-r0.1.0 installed Unsigned
bash.lib32_x86 4.3.30-r0.0 installed Unsigned
bfd.lib32_n9000 2.0.0.0-9.2.1 installed Signed
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
39
Optionality in Cisco NX-OS Software
Querying All Installed RPMs
Procedure
----------------------------------------------------
Installed Packages
attr.x86_64 2.4.47-r0.0 installed
Unsigned
aufs-util.x86_64
3.14+git0+b59a2167a1-r0.0 installed
Unsigned
base-files.n9000 3.0.14-r89.0 installed
Unsigned
base-passwd.lib32_x86 3.5.29-r0.1.0
installed Unsigned
bash.lib32_x86 4.3.30-r0.0 installed
Unsigned
bfd.lib32_n9000 2.0.0.0-9.2.1 installed
Signed
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
40
Optionality in Cisco NX-OS Software
Querying Only Installed Featured NX-OS RPMs
Procedure
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
41
Optionality in Cisco NX-OS Software
Querying Only Installed Featured NX-OS RPMs
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
42
Optionality in Cisco NX-OS Software
Querying Only Installed Third Party RPMs
Procedure
Procedure
install add
switch# bootflash:chef.rpm
activate
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
43
Optionality in Cisco NX-OS Software
Installing the RPMs Using Two Steps Procedure
Example
Active Packages:
bgp-2.0.1.0-9.2.1.lib32_n9000
chef-12.0.0alpha.2+20150319234423.git.1608.b6eb10f-1.el5.x86_64
Procedure
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
44
Optionality in Cisco NX-OS Software
Upgrading the RPMs Using One Step
[####################] 100%
Install operation 892 completed
successfully at Thu Jun 7 13:56:38 2018
sh install inactive
switch(config)#
| grep vxlan
vxlan-2.0.1.0-9.2.1.lib32_n9000
Example
[####################] 100%
Install operation 891 completed successfully at Thu Jun 7 13:53:07 2018
switch#
Procedure
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
45
Optionality in Cisco NX-OS Software
Downgrading the RPMs
Example
switch(config)# show install active
Boot Image:
NXOS Image: bootflash:/nxos.9.2.1.bin
Active Packages:
bgp-2.0.2.0-9.2.1.lib32_n9000
chef-12.0.0alpha.2+20150319234423.git.1608.b6eb10f-1.el5.x86_64
Procedure
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
46
Optionality in Cisco NX-OS Software
Removing the RPMs
Example
Active Packages:
bgp-2.0.1.0-9.2.1.lib32_n9000
chef-12.0.0alpha.2+20150319234423.git.1608.b6eb10f-1.el5.x86_64
Procedure
show install
switch(config)#
inactive | grep vxlan
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
47
Optionality in Cisco NX-OS Software
Format of the RPM
vxlan-2.0.0.0-9.2.1.lib32_n9000
switch(config)# install remove vxlan
See the following table for more information on the naming convention, for example,
fex-2.0.0.0-9.2.1.lib32_n9000.rpm:
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
48
Optionality in Cisco NX-OS Software
Rules for Managing RPM Version During Installation
Note Avoid manually copying the RPMs to the system repositories. Instead, use the install or YUM commands.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
49
Optionality in Cisco NX-OS Software
Performing Package Operations Using the YUM Commands
Note YUM commands are accessed only from the BASH shell on the box and they are not allowed from the NXOS
VSH terminal.
Note Make sure that as a sudo user, you have access to the super user privileges.
#ls /rpms
bfd-2.0.0.0-9.2.1.lib32_n9000.rpm
ins_tor_sdk_t2-1.0.0.0-9.2.0.77.lib32_n9000.rpm
mtx-netconf-agent-2.0.0.0-9.2.1.lib32_n9000.rpm snmp-2.0.0.0-9.2.1.lib32_n9000.rpm
bgp-2.0.0.0-9.2.1.lib32_n9000.rpm
ins_tor_sdk_t3-1.0.0.0-9.2.0.77.lib32_n9000.rpm
mtx-restconf-agent-2.0.0.0-9.2.1.lib32_n9000.rpm sr-2.0.0.0-9.2.1.lib32_n9000.rpm
container-tracker-2.0.0.0-9.2.1.lib32_n9000.rpm isis-2.0.0.0-9.2.1.lib32_n9000.rpm
mtx-telemetry-2.0.0.0-9.2.1.lib32_n9000.rpm svi-2.0.0.0-9.2.1.lib32_n9000.rpm
eigrp-2.0.0.0-9.2.1.lib32_n9000.rpm lacp-2.0.0.0-9.2.1.lib32_n9000.rpm
nbproxy-2.0.0.0-9.2.1.lib32_n9000.rpm
tacacs-2.0.0.0-9.2.1.lib32_n9000.rpm
ext-eth-2.0.0.0-9.2.1.lib32_n9000.rpm lldp-2.0.0.0-9.2.1.lib32_n9000.rpm
ntp-2.0.0.0-9.2.1.lib32_n9000.rpm
telemetry-2.3.4.0-9.2.1.lib32_n9000.rpm
fcoe-2.0.0.0-9.2.1.lib32_n9000.rpm mcast-2.0.0.0-9.2.1.lib32_n9000.rpm
nxos-ssh-2.0.0.0-9.2.1.lib32_n9000.rpm
virtualization-2.0.0.0-9.2.1.lib32_n9000.rpm
fex-2.0.0.0-9.2.1.lib32_n9000.rpm mpls-2.0.0.0-9.2.1.lib32_n9000.rpm
ospf-2.0.0.0-9.2.1.lib32_n9000.rpm vtp-2.0.0.0-9.2.1.lib32_n9000.rpm
fhrp-2.0.0.0-9.2.1.lib32_n9000.rpm mtx-device-2.0.0.0-9.2.1.lib32_n9000.rpm
repodata
vxlan-2.0.0.0-9.2.1.lib32_n9000.rpm
guestshell-2.0.0.0-9.2.1.lib32_n9000.rpm mtx-grpc-agent-2.0.0.0-9.2.1.lib32_n9000.rpm
rip-2.0.0.0-9.2.1.lib32_n9000.rpm
icam-2.0.0.0-9.2.1.lib32_n9000.rpm mtx-infra-2.0.0.0-9.2.1.lib32_n9000.rpm
services-2.0.0.0-9.2.1.lib32_n9000.rpm
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
50
Optionality in Cisco NX-OS Software
Getting Details of the Installed RPMs
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
51
Optionality in Cisco NX-OS Software
Installing the RPMs
yum install
bash-4.3#
http://10.0.0.2/modularity/rpms/vxlan-2.0.1.0-9.2.1.lib32_n9000.rpm
Dependencies Resolved
=====================================================================================================================================================================
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
52
Optionality in Cisco NX-OS Software
Installing the RPMs
Installed:
vxlan.lib32_n9000 0:2.0.1.0-9.2.1
Complete!
See the following example for installing the RPMs from local bootflash:
Dependencies Resolved
================================================================================================================================================================================================================================
Package Arch
Version Repository
Size
================================================================================================================================================================================================================================
Updating:
vxlan lib32_n9000
2.0.1.0-9.2.1 /vxlan-2.0.1.0-9.2.1.lib32_n9000
6.4 M
Transaction Summary
================================================================================================================================================================================================================================
Upgrade 1 Package
1/2
starting pre-install package version mgmt for vxlan
pre-install for vxlan complete
starting post-install package version mgmt for vxlan
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
53
Optionality in Cisco NX-OS Software
Upgrading the RPMs
2/2
Updated:
vxlan.lib32_n9000 0:2.0.1.0-9.2.1
Complete!
See the following example for installing the RPM if it is available in a repository:
yum upgrade
bash-4.3#
http://10.0.0.2/modularity/rpms/vxlan-2.0.1.0-9.2.1.lib32_n9000.rpm
Loaded plugins: downloadonly, importpubkey, localrpmDB, patchaction, patching,
protect-packages
groups-repo
| 1.1 kB 00:00 ...
localdb
| 951 B 00:00 ...
patching
| 951 B 00:00 ...
thirdparty
| 951 B 00:00 ...
Setting up Upgrade Process
vxlan-2.0.1.0-9.2.1.lib32_n9000.rpm
| 1.6 MB 00:00
Examining /var/tmp/yum-root-RaANgb/vxlan-2.0.1.0-9.2.1.lib32_n9000.rpm:
vxlan-2.0.1.0-9.2.1.lib32_n9000
Marking /var/tmp/yum-root-RaANgb/vxlan-2.0.1.0-9.2.1.lib32_n9000.rpm as an update to
vxlan-2.0.0.0-9.2.1.lib32_n9000
Resolving Dependencies
--> Running transaction check
---> Package vxlan.lib32_n9000 0:2.0.0.0-9.2.1 will be updated
---> Package vxlan.lib32_n9000 0:2.0.1.0-9.2.1 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
=====================================================================================================================================================================
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
54
Optionality in Cisco NX-OS Software
Upgrading the RPMs
Is this ok [y/N]: y
Downloading Packages:
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
busybox-1.23.2-r0.0.x86_64 has missing requires of busybox-syslog
Updating : vxlan-2.0.1.0-9.2.1.lib32_n9000
1/2
starting pre-install package version mgmt for vxlan
pre-install for vxlan complete
starting post-install package version mgmt for vxlan
post-install for vxlan complete
Cleanup : vxlan-2.0.0.0-9.2.1.lib32_n9000
2/2
Updated:
vxlan.lib32_n9000 0:2.0.1.0-9.2.1
Complete!
See the following example for upgrading the RPMs from local bootflash:
Dependencies Resolved
================================================================================================================================================================================================================================
Package Arch
Version Repository
Size
================================================================================================================================================================================================================================
Updating:
vxlan lib32_n9000
2.0.1.0-9.2.1 /vxlan-2.0.1.0-9.2.1.lib32_n9000
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
55
Optionality in Cisco NX-OS Software
Downgrading the RPMs
6.4 M
Transaction Summary
================================================================================================================================================================================================================================
Upgrade 1 Package
1/2
starting pre-install package version mgmt for vxlan
pre-install for vxlan complete
starting post-install package version mgmt for vxlan
post-install for vxlan complete
Cleanup : vxlan-2.0.0.0-9.2.1.lib32_n9000
2/2
Updated:
vxlan.lib32_n9000 0:2.0.1.0-9.2.1
Complete!
See the following example for upgrading the RPMs if it is available in any repository:
2/2
patching
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
56
Optionality in Cisco NX-OS Software
Downgrading the RPMs
thirdparty
Dependencies Resolved
================================================================================================================================================================================================================================
Package Arch
Version Repository
Size
================================================================================================================================================================================================================================
Downgrading:
vxlan lib32_n9000
2.0.0.0-9.2.1 groups-repo
1.6 M
Transaction Summary
================================================================================================================================================================================================================================
Downgrade 1 Package
1/2
starting pre-install package version mgmt for vxlan
pre-install for vxlan complete
starting post-install package version mgmt for vxlan
post-install for vxlan complete
Cleanup : vxlan-2.0.1.0-9.2.1.lib32_n9000
2/2
Removed:
vxlan.lib32_n9000 0:2.0.1.0-9.2.1
Installed:
vxlan.lib32_n9000 0:2.0.0.0-9.2.1
Complete!
See the following example for downgrading the RPMs from local bootflash:
See the following example for downgrading the RPMs if it is available in any repository:
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
57
Optionality in Cisco NX-OS Software
Deleting the RPMs
Dependencies Resolved
================================================================================================================================================================================================================================
1/1
starting pre-remove package version mgmt for vxlan
pre-remove for vxlan complete
Removed:
vxlan.lib32_n9000 0:2.0.1.0-9.2.1
Complete!
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
58
Optionality in Cisco NX-OS Software
Using the grouplist Command
• grouplist
• groupinfo
• groupinstall
• groupremove
• groupupdate
YUM groups can be broadly classified as L2, L3, routing, and management.
bash-4.3$
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
59
Optionality in Cisco NX-OS Software
Using the groupinstall Command
Group: L2
Mandatory Packages:
lacp
lldp
svi
vtp
Dependencies Resolved
================================================================================================================================================================================================================================
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
60
Optionality in Cisco NX-OS Software
Using the groupinstall Command
1/4
starting pre-install package version mgmt for rip
pre-install for rip complete
starting post-install package version mgmt for rip
post-install for rip complete
Installing : isis-2.0.0.0-9.2.1.lib32_n9000
2/4
starting pre-install package version mgmt for isis
pre-install for isis complete
starting post-install package version mgmt for isis
post-install for isis complete
Installing : eigrp-2.0.0.0-9.2.1.lib32_n9000
3/4
starting pre-install package version mgmt for eigrp
pre-install for eigrp complete
starting post-install package version mgmt for eigrp
post-install for eigrp complete
Installing : bgp-2.0.0.0-9.2.1.lib32_n9000
4/4
starting pre-install package version mgmt for bgp
pre-install for bgp complete
starting post-install package version mgmt for bgp
post-install for bgp complete
Installed:
bgp.lib32_n9000 0:2.0.0.0-9.2.1 eigrp.lib32_n9000 0:2.0.0.0-9.2.1
isis.lib32_n9000 0:2.0.0.0-9.2.1 rip.lib32_n9000
0:2.0.0.0-9.2.1
Complete!
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
61
Optionality in Cisco NX-OS Software
Using the groupupdate Command
6/6
patching
Dependencies Resolved
================================================================================================================================================================================================================================
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
62
Optionality in Cisco NX-OS Software
Using the groupupdate Command
1/10
starting pre-install package version mgmt for eigrp
pre-install for eigrp complete
starting post-install package version mgmt for eigrp
post-install for eigrp complete
Updating : ospf-2.0.1.0-9.2.1.lib32_n9000
2/10
starting pre-install package version mgmt for ospf
pre-install for ospf complete
starting post-install package version mgmt for ospf
post-install for ospf complete
Updating : rip-2.0.1.0-9.2.1.lib32_n9000
3/10
starting pre-install package version mgmt for rip
pre-install for rip complete
starting post-install package version mgmt for rip
post-install for rip complete
Updating : isis-2.0.1.0-9.2.1.lib32_n9000
4/10
starting pre-install package version mgmt for isis
pre-install for isis complete
starting post-install package version mgmt for isis
post-install for isis complete
Updating : bgp-2.0.1.0-9.2.1.lib32_n9000
5/10
starting pre-install package version mgmt for bgp
pre-install for bgp complete
starting post-install package version mgmt for bgp
post-install for bgp complete
Cleanup : bgp-2.0.0.0-9.2.1.lib32_n9000
6/10
Cleanup : isis-2.0.0.0-9.2.1.lib32_n9000
7/10
Cleanup : rip-2.0.0.0-9.2.1.lib32_n9000
8/10
Cleanup : ospf-2.0.0.0-9.2.1.lib32_n9000
9/10
Cleanup : eigrp-2.0.0.0-9.2.1.lib32_n9000
10/10
Updated:
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
63
Optionality in Cisco NX-OS Software
Using the grouperase Command
Complete!
Dependencies Resolved
================================================================================================================================================================================================================================
Transaction Summary
================================================================================================================================================================================================================================
Remove 5 Packages
Installed size: 34 M
Is this ok [y/N]: y
Downloading Packages:
Running Transaction Check
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
64
Optionality in Cisco NX-OS Software
Finding Repositories
1/5
starting pre-remove package version mgmt for isis
pre-remove for isis complete
Erasing : ospf-2.0.0.0-9.2.1.lib32_n9000
2/5
starting post-remove package version mgmt for isis
post-remove for isis complete
starting pre-remove package version mgmt for ospf
pre-remove for ospf complete
Erasing : eigrp-2.0.0.0-9.2.1.lib32_n9000
3/5
starting post-remove package version mgmt for ospf
post-remove for ospf complete
starting pre-remove package version mgmt for eigrp
pre-remove for eigrp complete
Erasing : rip-2.0.0.0-9.2.1.lib32_n9000
4/5
starting post-remove package version mgmt for eigrp
post-remove for eigrp complete
starting pre-remove package version mgmt for rip
pre-remove for rip complete
Erasing : bgp-2.0.0.0-9.2.1.lib32_n9000
5/5
starting post-remove package version mgmt for rip
post-remove for rip complete
starting pre-remove package version mgmt for bgp
pre-remove for bgp complete
Removed:
bgp.lib32_n9000 0:2.0.0.0-9.2.1 eigrp.lib32_n9000 0:2.0.0.0-9.2.1
isis.lib32_n9000 0:2.0.0.0-9.2.1 ospf.lib32_n9000 0:2.0.0.0-9.2.1 rip.lib32_n9000
0:2.0.0.0-9.2.1
Complete!
Finding Repositories
This command lists the repositories that the switch has along with the number of RPMs it has to those
repositories.
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
65
Optionality in Cisco NX-OS Software
Finding the Installed YUM Version
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
66
Optionality in Cisco NX-OS Software
Creating User Roles for Install Operation
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
67
Optionality in Cisco NX-OS Software
Creating User Roles for Install Operation
Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
68