advertisement
• Ensure that the required space is available on both the active and standby supervisor modules for the image files to be copied using the dir command.
• Use the one-step install all command to upgrade your software. This command upgrades all modules in any Cisco NX-OS device.
• Run only one installation on a device at a time.
Note
During vPC setup, the configuration is locked on the peer switch while ISSU is in progress.
• ISSU is not supported when the vPC peers are on a single physical device but are across VDCs.
• Do not enter another command while running the installation.
• Do the installation on the active supervisor module, not the standby supervisor module.
Note
If the I/O modules are not compatible with the software image you install on the supervisor module, some traffic disruption might occur in those modules, depending on your configuration. The install all command output identifies these commands. You can choose to proceed with the upgrade or end at this point.
• The configuration is locked during the upgrade process.
• You can have only one instance of the install all command running.
Cisco NX-OS Software Downgrade Guidelines
• Any features introduced in a release must be disabled before downgrading to a release that does not support those features. See the release notes for information on the new features introduced in each release.
• In Cisco NX-OS Release 8.0(1), ISSD is not supported. You will have to perform a cold boot of the switch.
• VPC peers can only operate dissimilar versions of the Cisco NX-OS software during the upgrade or downgrade process. Operating
VPC peers with dissimilar versions, after the upgrade or downgrade process is complete, is not supported.
• To determine incompatibility before you downgrade your software, use the following commands:
• For hardware incompatibility—
sh install all impact system system_name
• For software incompatibility—
show incompatibility-all system image_filename
Upgrading a Device with Dual Supervisor Modules
The install all command supports in-service software upgrades (ISSUs) on devices that have dual supervisor modules and performs the following actions:
15
• Determines whether the upgrade will be disruptive and asks if you want to continue.
• Ensure that you have enough space in the standby bootflash.
• Copies the kickstart and system images to the standby supervisor module.
• Sets the KICKSTART and SYSTEM boot variables.
• Reloads the standby supervisor module with the new Cisco NX-OS software.
• Reloads the active supervisor module with the new Cisco NX-OS software, which causes a switchover to the newly upgraded standby supervisor module.
• Upgrades the line cards.
• The Connectivity Management Processor (CMP) on both supervisors will get upgraded.
Benefits of Using the install all Command
The install all command provides the following benefits:
• You can upgrade the entire device using just one command.
• You can receive descriptive information on the intended changes to your system before you continue with the installation.
• You have the option to cancel the command. You can continue or cancel when you see this question (the default is no):
Do you want to continue (y/n) [n] :
y
• You can upgrade the entire device using the least disruptive procedure.
• You can see the progress of this command on the console, Telnet, and SSH screens:
◦Before a switchover process, you can only see the progress from the active supervisor module.
◦After a switchover process, you can see the progress from both the supervisor modules.
• The install all command automatically checks the image integrity, which includes the running kickstart and system images.
• The install all command performs a platform validity check to verify that a wrong image is not used—for example, to check if a Nexus 7000 device image is used inadvertently to upgrade a Nexus 5000 device.
• The Ctrl-c escape sequence gracefully ends the install all command. You are prompted to confirm your decision to abort the
ISSU process. If you proceed, the command sequence completes the update step in progress and returns to the device prompt.
(Other upgrade steps cannot be ended using Ctrl-c.)
• After entering the install all command, if any step in the sequence fails, the command completes the step in progress and ends.
For example, if an I/O module fails to be updated for any reason (for example, due to an unstable network state), the command sequence disruptively updates that module and ends. In such cases, you can verify the problem on the affected switching module and upgrade the other I/O modules.
• The
show install all impact image-name command runs pre-upgrade checks against a given image and informs the user if the images are compatible for an upgrade or a downgrade.
16
Note
Refer to the " Supported Upgrade and Downgrade Paths " section of the Cisco Nexus 7000 Series NX-OS
Release Notes to get details on the supported Cisco NX-OS release versions to which you can upgrade to.
ISSU Failure Conditions
The following situations cause the installation to fail to complete:
• If the standby supervisor module bootflash: file system does not have sufficient space to accept the updated image.
• If the specified system and kickstart images are not compatible.
• If the network or device is configured while the upgrade is in progress.
• If a Spanning Tree Protocol (STP) topology change occurs while the upgrade is in progress.
• If the install all command is entered on the standby supervisor module.
• If the install all command does not reference the default bootflash: in a dual supervisor module configuration.
• If a module is removed while the upgrade is in progress.
• If the device has any power disruption while the upgrade is in progress.
• If the entire path for the remote server location is not specified accurately.
• If some FEX ports are operating in LACP fast rate mode.
• If images are incompatible after an upgrade. For example, an I/O module image may be incompatible with the system image, or a kickstart image may be incompatible with a system image. This is also identified by the show install all impact command in the compatibility check section of the output (under the Bootable column).
• If a linecard is in failure state, the ISSU will abort.
The Cisco NX-OS software prevents most configuration changes while the install all command is in progress. However, the Cisco
NX-OS software allows configuration changes from Cisco Fabric Services (CFS) and those changes may affect the ISSU.
Upgrade Procedure Summary
The following summary procedure describes how to upgrade a device that has dual supervisor modules to the latest Cisco NX-OS software.
Procedure
Step 1
Log in to the console port on both of the active and standby supervisor modules.
Step 2
Log in to Cisco.com and download the latest Cisco NX-OS kickstart and system images to a server.
Step 3
Download the Cisco NX-OS kickstart and system images from the server to your device using the copy command.
Step 4
Save the device configuration using the copy running-config startup-config vdc-all command.
Step 5
Enter the install all command at the active supervisor command prompt to upgrade the Cisco NX-OS software on your device.
17
Note
A supervisor module switchover occurs during the software installation.
Detailed Upgrade Procedure
This section describes the detailed procedure to upgrade to the latest Cisco NX-OS software on a device with dual supervisor modules.
Procedure
Step 1
Log in to the device on the console port connection on both of the active and standby supervisor modules.
Step 2
Log in to Cisco.com to access the links provided in this document. To log in to Cisco.com, go to the URL http:// www.cisco.com/ and click Log In at the top of the page. Enter your Cisco username and password.
Note
Unregistered Cisco.com users cannot access the links provided in this document.
Step 3
Access the Software Download Center using this URL: http://www.cisco.com/public/sw-center/index.shtml
Step 4
Navigate to the download site for your device.
You see links to the download images for your device.
Step 5
Select and download the kickstart and system software files to a server.
Step 6
Ensure that the required space is available for the image file(s) to be copied.
switch#
dir bootflash:
4096 Oct 24 18:06:54 2016 lost+found/
146701191
30674944
Aug 09 15:18:05 2016
Apr 25 15:51:13 2016 n7000-s1-dk9.7.2.0.D1.1.bin.CCO
n7000-s1-kickstart.7.2.0.D1.1.bin.CCO
Usage for bootflash://sup-local
1260208128 bytes used
579682304 bytes free
1839890432 bytes total switch#
Tip
We recommend that you have the kickstart and system image files for at least one previous release of the Cisco
NX-OS software on the device to use if the new image files do not load successfully.
Step 7
If you need more space on the active supervisor module, delete unnecessary files to make space available.
switch#
delete bootflash:n7000-s1-kickstart.7.2.0.D1.1.bin.CCO
switch#
delete bootflash:n7000-s1-dk9.7.2.0.D1.1.bin.CCO
Step 8
Verify that there is space available on the standby supervisor module.
switch#
dir bootflash://sup-standby/
49152 Oct 16 14:43:39 2016 lost+found
80850712
22593024
Oct 04 15:57:44 2016
Oct 04 15:52:56 2016 n7000-s2-dk9.8.0.1.bin.CCO
n7000-s2-kickstart.8.0.1.bin.CCO
Usage for bootflash://sup-standby
103492888 bytes used
18
800604904 bytes free
904097792 bytes total
Step 9
If you need more space on the standby supervisor module, delete any unnecessary files to make space available.
switch#
delete bootflash://sup-standby/n7000-s2-kickstart.8.0.1.bin.CCO
switch#
delete bootflash://sup-standby/n7000-s2-dk9.8.0.1.bin.CCO
Step 10
Copy the NX-OS kickstart and system images to the active supervisor module using a transfer protocol. You can use
ftp:,tftp:, scp:, or sftp:. The examples in this procedure use scp:.
Note
When you download an image file, change to your FTP environment IP address or DNS name and the path where the files are located.
switch#
copy scp://[email protected]/downloads/n7000-s2-kickstart.8.0.1.bin
n7000-s2-kickstart.8.0.1.bin
switch#
copy scp://[email protected]/downloads/n7000-s2-dk9.8.0.1.bin n7000-s2-dk9.8.0.1.bin
Step 11
Read the release notes for the related image file. See the Cisco Nexus 7000 Series NX-OS Release Notes.
Step 12
Save the running configuration to the startup configuration.
switch#
copy running-config startup-config vdc-all
Step 13
Perform the upgrade using the install all command at the command prompt on the active supervisor module.
switch#
install all kickstart n7000-s2-kickstart.8.0.1.bin system n7000-s2-dk9.8.0.1.bin
Note
If the upgrade is disruptive, you can either resolve the issues that cause the disruption and repeat this step, or you can continue with the disruptive upgrade.
Step 14
After the installation operation completes, log in and verify that the device is running the required software version using the show version command.
switch#
show version
Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_serie s_home.html
Copyright (c) 2002-2016, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license.
Certain components of this software are licensed under the GNU General Public License (GPL) version
2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1.
A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php
Software
BIOS: version 3.1.0
kickstart: version 8.0(1) system: version 8.0(1)
BIOS compile time: 02/27/2016 kickstart image file is: bootflash:///n7000-s2-kickstart.8.0.1.bin.S28
kickstart compile time: 5/19/2016 11:00:00 [06/14/2016 21:46:24] system image file is: bootflash:///n7000-s2-dk9.8.0.1.bin.S28
19
advertisement