Figure 14 shows a dual-homed FEX that is connected to stub switches. Make sure that the network is stable and no changes are made while an ISSU is in progress. Make sure that you check for feature compatibility between the current running release and the target release. Figure 15 shows upgrade restrictions. Figure 15 Upgrade Restrictions. The specific requirements for a nondisruptive upgrade ISSU are as follows:. If the fabric is not stable, the installation aborts.
If any application is holding a CFS lock, the installation aborts. Services that depend on the inband and management ports are impacted during this time. Table 3 lists the services that are impacted during an ISSU reset. After the reboot, NTP session are reestablished based on the saved startup configuration.
During an ISSU, the control plane is offline for up to 80 seconds. Any state changes in the network during this time are not processed.
Depending on the change, the impact might vary. We recommend that you ensure a stable fabric during an ISSU. See the following table for other ISSU impacts. A peer switch zone change request is not answered by the switch undergoing an ISSU. Any topology changes during this time are also not acted upon until the ISSU completes.
Enter the disable-fka command on the core switch VFC parameters to ensure that the core switch ignores any FKA events. IEEE IGMP does not disrupt existing flows of multicast traffic that are already present, but new flows are not learned and are dropped until an ISSU completes. New router ports or changes to router ports are not detected during this time. Manual configurations are ignored during this time. During an ISSU, the time-to-live value is increased seconds if it is less than the recommended timeout value.
The configuration is ignored if manually specified. To avoid link-down to link-up transitions during the control plane outage time, the laser is turned off for administratively up ports that are operationally down. This situation occurs during the ISSU reboot starting state when the switch and the FEX applications stop communicating with each other. After the ISSU reboot and a stateful restart, the laser is turned back on.
This action prevents the link state from transitioning from down to up during an ISSU. Note The switch might reload at this time and cause a traffic disruption if the upgrade i s not an ISSU.
The following table lists the show commands that identify the impact or potential problems that might occur when performing an ISSU. Displays incompatible configurations on the current system that impact the upgrade version.
You must use the system image file. Displays the facility logging severity level configuration. Logging levels for all processes must be set at 5 or below when performing an ISSU. Processes with a logging level greater than 5 do not appear when you enter the show install all impact command. Displays information that describes the impact of the upgrade on each Fabric Extender, including the current and upgrade-image versions.
This command also displays if the upgrade is disruptive or not and if the Fabric Extender needs to be rebooted and the reason why. Displays the spanning-tree configuration and whether or not there are potential STP issues. Displays the port priority information and whether or not there are potential issues.
You can also perform the following tasks to identify potential problems before they occur:. Use the show lacp issu-impact command to display if any port or a peer switch is configured in rate fast mode. The ISSU process is triggered when you enter the install all command. This section describes the sequence of events that occur when you upgrade a single Cisco Nexus device or a single Cisco Nexus device that is connected to one or more FEXs. After that, use the ISSU process to upgrade from 5.
Table 7 shows an overview of the upgrade process. Table 7 Upgrade Process At-a-Glance. Log in to the first Cisco Nexus device. We recommend that you log in to the console port. In vPC topologies, the first upgrade can be performed on either the primary or secondary switch in the topology.
Log in to Cisco. To log in to Cisco. Enter your Cisco username and password. Choose and download the kickstart and system software files to the server. Verify that the required space is available in the bootflash: directory for the image file s to be copied.
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 for each Cisco Nexus device 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. The Installer for the Cisco Nexus upgrades the software. The switch will now run a 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 Copies 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 that was saved on an external flash memory device.
Copies a saved configuration from an external flash memory device to the startup configuration. Optional Copies a saved 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. Doing a disruptive upgrade between incompatible images will result in loss of certain configurations such as unified ports, breakout, and FEX configurations.
For FEX configurations, prior to the downgrade, the configuration must be converted if not already used to use FEX pre-provisioning configuration. The following lists the situations where a nondisruptive ISSU might not be possible when upgrading a Cisco Nexus device:. 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 the force keyword at the end of the install all command as follows:. An upgrade from these releases is disruptive. Step 1 Log in to Cisco.
Note Unregistered Cisco. Navigate to the software downloads for Cisco Nexus devices. Links to the download images for the switch are listed. Step 2 Choose and download the kickstart and system software files to a local server. Step 3 Verify that the required space is available in the bootflash: directory for the image file s to be copied. 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. No need to delete that folder first , especially if you want your configs and payloads. Nyx v1. Now hekate can also show them in text form, plus their error code. Changed description of boot2 fatal error to better reflect possible causes Notice about Atmosphere 1. Sept is now completely removed Boot process on Erista 7. Even if they were not prepared for that. Now that's cleared by default and HOS never goes out of bounds anymore.
All tools and procedures that depend on BIS keys can now be done in single session. That's because Sept that was important for Erista 7. Fixed an issue where big labels in Launch would cause other labels to not show up. Add info on ram chip modules that use 1. SD cards that miss Manufacturer ID will now be reported as fake. Previously it would do that only in decrypting errors. That's subject to change on "how it works" if panel mods for earlier Switch appear.
Display Interface driver now ensures that display properly replies with display id. Added all new dram ids for preparation of new units that use them because of chip shortages. If you updated while in Nyx then just hit Reload Nyx and it will check if update.
Or if in HOS, you can r2p into newer hekate. New Sept will need to run at least once on Erista models. Added proper error messages when restore folder is empty Added missing old touch firmware version info BDK Added support for Sandisk eMMC device health report for modded switches.
Just don't forget to drag n drop bootloader folder, because that's where the updated emuMMC code is. How to update: Drag n drop bootloader folder into sd card root and hit replace.
A Growing Number of Enthusiasts We understand that the number of enthusiasts are looking for the fastest, safest way to install their titles on their Switch. Tinfoil v Added support for "blocked" NSZ installation. Automatically resets required version upon install and uninstall. Added Help section.
Added "Recommended" section. Added "Parental Mode" for filtering content and features for young children. Added Retroarch ROM launching. Added game cartridge installation.
Added USB hard drive support.
0コメント