If you need more space in the bootflash: directory, delete unnecessary files to make space available. Copy the Cisco NX-OS kickstart and system images to the bootflash using a transfer protocol such as ftp:, tftp:, scp:, or sftp. Compare the file sizes of the images that were transferred using the dir bootflash command. The file sizes of the images obtained from Cisco. Complete the above steps through Step 9 for each Cisco Nexus Series switch in the topology. Enter the show incompatibility command to verify that the target image is feature-wise compatible with the current image.
Enter the show install all impact command to identify the upgrade impact. Enter the show spanning-tree issu-impact command to display the impact of the upgrae impact. Enter the show lacp issue-impact command to display the impact of the upgrade. Enter the show fex command to verify that all the FEXs are online. Enter the show vpc role command to verify the vPC switch role. Peruse the installer impact analysis and accept to proceed.
Installer on Nexus upgrades the software — the switch will now run new version of the software. Enter the show install all status command to verify the status of the installation. You can copy configuration files from an external flash memory device. Insert the external flash memory device into the active supervisor module.
Optional Displays the files on the external flash memory device. Copies the image from an external flash memory device into the bootflash. The filename argument is case sensitive. Copies the running configuration from an external flash memory device. Optional You can copy the running configuration from an external flash memory device to the bootflash. Optional Copies the running configuration to the startup configuration. 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.
Copies the startup configuration from an external flash memory device. Optional You can copy the startup configuration from an external flash memory device to the bootflash.
The following list summarizes the upgrade process in a non-vPC topology:. The install all command triggers the installation upgrade. The compatibility checks display the impact of the upgrade. The installation proceeds or not based on the upgrade impact. The stateful restart of the system software and application occurs.
The following list summarizes the upgrade process on a primary switch in a vPC topology. Steps that differ from a switch upgrade in a non-vPC topology are in bold. Note In vPC topologies, the two peer switches must be upgraded individually. An upgrade on one peer switch does not automatically update the vPC peer switch. The install all command issued on the vPC primary switch triggers the installation upgrade. The configuration is locked on both vPC peer switches.
When the installation is complete, the vPC primary switch and the FEXs that are connected to the primary switch are upgraded. The vPC primary switch is running the upgraded version and the vPC secondary switch is running the original software version. The following list summarizes the upgrade process on a secondary switch in a vPC topology.
The install all command issued on the vPC second switch triggers the installation upgrade. The FEXs are upgraded sequentially. Note The dual-homed FEXs were upgraded by the primary switch. The configuration is unlocked on the primary and secondary switches. The following lists conditions where a nondisruptive ISSU might not be possible when upgrading a Cisco Nexus Series access layer switch:. Perform the following steps to restore the configuration if the configurations contain interface breakout or unified port configurations:.
Use the default interface command to restore the default configurations of the breakout interfaces. Save the running configuration to startup configuration using the copy running-config startup-config command. In case of VPC, downgrade the primary switch first and then the secondary switch. After the switch is up, power-off and power-on the module for the interface breakout to be effective. If the breakout is configured on Baseboard module, save the running configuration to startup configuration using the copy running-config startup-config command and then reload the switch again.
If breakout is not configured on the Baseboard, then an additional reload is required if running configuration contains hardware profile route resource service-template.
Verify if all the interfaces are up and traffic is resumed. You can choose to do a disruptive upgrade if one of the ISSU conditions are not met. One additional reason where you might choose to do a disruptive upgrade is when FEXs are upgraded in a rolling fashion one FEX at a time , which requires a longer maintenance window.
With a disruptive upgrade, all the connected FEXs are upgraded simultaneously, so the maintenance window can be shorter. If you need a shorter maintenance window with traffic disruption , you can force a disruptive upgrade even if an ISSU can be leveraged.
It is important to note the possibility of an outage if you do a disruptive upgrade. You can also add force at the end of the install all command as follows:. An upgrade from these releases will be disruptive. Step 1 Log in to Cisco. Note Unregistered Cisco.
Navigate to the software downloads for Cisco Nexus Series switches. Links to the download images for the switch are listed. Step 2 Choose and download the kickstart and system software files to a local server. Step 3 Verify that the required space is available in the bootflash: directory for the image file s to be copied.
We recommend that you keep the kickstart and system image files for at least one previous software release to use if the new image files do not load successfully. Step 4 Optional If you need more space on the bootflash, delete unnecessary files to make space available.
The examples in this procedure use SCP. Step 7 Install the new images, specifying the new image names that you downloaded in the previous step. Step 8 Verify that the switch is running the required software release. 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 one of the vPC switches is being reset during the upgrade process, all the server traffic can flow through its vPC peer. The following figures show topologies in which the access layer includes a vPC configuration to hosts or downstream switches. To upgrade the access layer without a disruption to hosts, follow these tasks:. Note Flows that are forwarded to a switch during an upgrade on the switch, will failover to the second switch.
Also, flows are redistributed when vPC peers are active. The traffic disruption is limited to the time required for the server or host to detect the link-down and link-up events and to redistribute the flows.
This may result in loss of configuration and forwarding issues. A disruptive upgrade causes a switch and connected FEXs to reload. The time required for a FEX to reload is less 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 of the hosts to same time as required by FEX to reload approximately seconds , instead of the time required for an upgrade of the entire access layer.
The following figure shows a dual-homed FEX topology in which the access layer includes a vPC configuration to hosts or downstream switches. Note The following dual-homed FEX procedure is supported only for an upgrade and not for a downgrade. Upgrade the vPC primary switch with the new image using the install all kickstart image system image command.
During the upgrade process, the switch is reloaded. When the switch is reloaded, only singled-homed FEXs connected to the switch are reloaded and dual-homed FEXs are not reloaded.
Servers connected to the dual-homed FEXs retain network connectivity through the vPC secondary switch. Step 2 Verify that the upgrade of the vPC primary switch is completed successfully. At the completion of the upgrade, the vPC primary switch restores vPC peering. The servers connected to the dual-homed FEXs will lose connectivity. Step 4 Wait for the FEXs to reload. Step 5 Upgrade the vPC secondary switch with the new image using the install all kickstart image system image command.
Step 6 Verify that the upgrade of the vPC secondary switch is completed successfully. At the completion of the upgrade, the vPC secondary switch restores vPC peering.
Dual-homed FEXs connect to both the peer switches and start forwarding traffic. Navigate to the software downloads for Cisco Nexus devices. Perform this step on both the switches in a vPC pair. Step 7 Enter the show install all impact command to validate the upgrade process and the components being upgraded.
Step 8 Enter the install all kickstart image system image command on the vPC primary switch. During the software upgrade on the primary switch, you can view the FEX upgrade progress using the vPC secondary switch see the bold output :.
Step 9 Ensure that the upgrade on vPC primary switch is completed. Use the show version command to verify the upgrade on vPC primary switch. Note Only the vPC primary switch shows that the Fabric Extender is online because the vPC secondary switch does not have the new image. When all the Fabric Extenders are loaded, go to the next step. To upgrade the vPC secondary switch, follow Step 2 to Step 9.
Use the show fex command to view the FEX status. Table lists the show commands that are used to monitor installation upgrades. Table Monitoring the Upgrade Process. Displays the applications that failed during an installation and why the installation failed. Displays detailed logs of the last installation-related command. Displays detailed logs of the last five installation-related commands, from the oldest to the newest logs.
Displays the system and configuration information that you can provide to the Cisco Technical Assistance Center when reporting a problem.
The following example shows the output from the show install all status command:. Note that the downgrades are disruptive. You can use the show incompatibility system command to ensure that there are no feature incompatibilities between the current release and the target release.
After FEX pre-provisioning is done, perform the following steps to restore the configuration if the configurations contain interface breakout or unified port configurations:. In case of vPC, downgrade the primary switch first and then the secondary switch. If breakout is not configured on the Baseboard module, then an additional reload is required if running configuration contains hardware profile route resource service-template.
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 Release Notes for your platform for details. Some common causes for ISSU failure are as follows:.
The documentation set includes the following types of documents:. To provide technical feedback on this document or to report an error or omission, please send your comments to nexus5k-docfeedback cisco. We appreciate your feedback. The RSS feeds are a free service.
Upgrade Guidelines When upgrading system software, follow these guidelines: Configuration changes You cannot enter configuration mode during an upgrade. Hi Robert,I'm afraid it's currently not possible to do this, but it's being evaluated by the develop Upgrade files for DMM 5.
Hi Michael,The upgrade from version 5. Play all videos from the folder DMP G. Hi Ivan,It's not possible to do it directly.
The only way to achieve this is to create a playlist wi Stream video for DMP G. ANM 5. Hi Paul,I think I was not clear enough on my answer. You will not get access to the filesystem, the Hi Paul,I'm afraid it's not easy. There is a patch that TAC can provide you will need to open a cas Understanding GSS proximity decisions.
Hi Brandon,The first thing in this case is to check your configuration, but, that's too complex to b Available Languages.
Download Options. Updated: September 23, Overview The following instructions explain how to download the various components of the Service Control Solution from the Cisco software download center.
Compatibility Matrix The following tables provides the compatibility information for the various components of the Service Control Solution: Table 2 —5. Table 1 Release 5.
Downloading Software Table 5 summarizes the contents of each software package. To view a list of Cisco trademarks, go to this URL: www.
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.
Any Internet Protocol IP addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
All rights reserved. Was this Document Helpful?
0コメント