Cisco Nexus 7000 Series FPGA/EPLD Upgrade Release Notes, Release 7.x
Available Languages
Table of Contents
Cisco Nexus 7000 Series FPGA/EPLD Upgrade Release Notes, Release 7.x
Deciding When to Upgrade EPLDs
EPLDs Available for Releases 7.x
Determining Whether to Upgrade EPLD Images
Preparing the EPLD Images for Installation
Manual Upgrading of EPLD Images
Automatic Upgrading of EPLD Images
Enabling or Disabling Automatic Upgrades of EPLD Images
Verifying Automatic Upgrades of EPLD Images
Resetting Automatic Upgrades of EPLD Images
Verifying the EPLD Upgrades and Downgrades
Displaying the Available EPLD Versions
Displaying the Status of EPLD Upgrades
Obtaining Documentation and Submitting a Service Request
Cisco Nexus 7000 Series FPGA/EPLD Upgrade Release Notes, Release 7.x
Release Date: February 12, 2016
Table 1 shows the revision history changes for this document.
This document includes the following sections:
- Introduction
- Deciding When to Upgrade EPLDs
- Switch Requirements
- EPLDs Available for Releases 7.x
- Determining Whether to Upgrade EPLD Images
- Downloading the EPLD Images
- EPLD Images Needed for vPCs
- EPLD Images Needed for LISP
- Installation Guidelines
- Preparing the EPLD Images for Installation
- Manual Upgrading of EPLD Images
- Automatic Upgrading of EPLD Images
- Downgrading EPLD Images
- Verifying the EPLD Upgrades and Downgrades
- Displaying the Available EPLD Versions
- Displaying the Status of EPLD Upgrades
- Limitations
- Related Documentation
- Obtaining Documentation and Submitting a Service Request
Introduction
The Cisco Nexus 7000 Series switches, which include the Cisco Nexus 70 xx and 77 xx switches, contain several programmable logical devices (PLDs) that provide hardware functionalities in all modules. Cisco provides electronic programmable logic device (EPLD) image upgrades to enhance hardware functionality or to resolve known issues. PLDs include electronic programmable logic devices (EPLDs), field programmable gate arrays (FPGAs), and complex programmable logic devices (CPLDs), but they do not include ASICs. In this document, the term EPLD is used for FPGA and CPLDs.
The advantage of having EPLDs for some module functions is that when you need to upgrade those functions, you just upgrade their software images instead of replacing their hardware.
Note EPLD image upgrades for an I/O module disrupt the traffic going through the module because the module must power down briefly during the upgrade. The system performs EPLD upgrades on one module at a time, so at any one time the upgrade disrupts only the traffic going through one module.
Cisco provides the latest EPLD images with each release. Typically, these images are the same as provided in earlier releases but occasionally some of these images are updated. To determine if there are any updated images, see Table 3. These EPLD image updates are not mandatory unless otherwise specified. The EPLD image upgrades are independent from the Cisco NX-OS In Service Software Upgrade (ISSU) process, which upgrades the system and kickstart images with no impact on the network environment.
When Cisco makes an EPLD image upgrade available, these release notes announce their availability, and you can download them from http://www.cisco.com .
Deciding When to Upgrade EPLDs
You do not always need to upgrade EPLD images but the following circumstances do require that you upgrade these images:
- If you are enabling software features (LISP, VPCs, and so on) that require EPLDs
- If you are using M2 Series 100-Gbps Ethernet I/O modules that remain powered down after booting up the switch
When new EPLD images are available, the upgrades are always recommended if your network environment allows for a maintenance period in which some level of traffic disruption is acceptable. If such a disruption is not acceptable at this time, then you might consider postponing the upgrade until a better time.
Note The EPLD upgrade operation is a disruptive operation. You should execute this operation only at a programmed maintenance time. The system/kickstart ISSU upgrade is a nondisruptive upgrade.
Note Do not perform an EPLD upgrade during an ISSU system/kickstart upgrade.
Table 2 provides high-level guidelines to help network administrators determine whether an EPLD upgrade is necessary when upgrading the Cisco NX-OS Release 5.0(1) or later releases. If you are upgrading an earlier release, see one of the following earlier versions of the release notes:
- Cisco Nexus 7000 Series FPGA/EPLD Upgrade Release Notes, Release 4.0
- Cisco Nexus 7000 Series FPGA/EPLD Upgrade Release Notes, Release 4.1
Upgrading Supervisor 2 E from any Cisco Nexus N77xx device to Cisco Nexus N7702 device for For Release 7.2(0)D1(1).
M2 Series I/O modules remain powered down after booting up the switch for Cisco NX-OS Release 6.1(1) or 6.1(2).
Download one of the following EPLD images and use the no poweroff module command for each powered down M2 Series I/O module:
Upgrading the Cisco NX-OS operating system from Release 4.x to Release 5.0 or later releases.
Update all supervisor, I/O, and fabric modules with the latest EPLD images.
Moving 32-port 10-Gbps Ethernet I/O modules from a Cisco Nexus 7010 switch to a Cisco Nexus 7018 switch.
Moving 48-port 10/100/1000 Ethernet I/O modules from a Cisco Nexus 7010 switch to a Cisco Nexus 7018 switch.
Switch Requirements
The Cisco Nexus 7000 Series switch must be running the Cisco NX-OS operating system and include the following hardware:
- Supervisor modules—one or two, each with at least 120 MB of available bootflash or slot0 memory
- I/O modules—at least one
- Fabric modules—at least three (Cisco Nexus 7009, 7010, 7018, 7706, 7710, and 7718 only)
- Fan trays
– For the Cisco Nexus 7004, one fan tray
– For the Cisco Nexus 7009 chassis, one fan tray
– For the Cisco Nexus 7010 chassis, two system fan trays and two fabric fan trays
– For the Cisco Nexus 7018 chassis, two fan trays
– For the Cisco Nexus 7702 chassis, one fan tray
– For the Cisco Nexus 7706, 7710, and 7718 chassis, three fan trays
You must be able to access the switch through a console, SSH, or Telnet.
You must have administrator privileges to work with the Cisco Nexus 7000 Series switch.
EPLDs Available for Releases 7.x
Each EPLD image that you can download from http://www.cisco.com is a bundle of EPLD upgrades. To see the updated EPLD versions for each release, see Table 3 .
Cisco NX-OS Release 7.3(0)D1(1) includes the following new EPLD images:
Cisco NX-OS Release 7.2(0)D1(1) includes new EPLD images for the supervisor 2E module, N77-C7702-FAN, and the F3 series modules as listed below.
- Supervisor 2E module (N77-SUP2E) (from 19.000 to 20.000)
- N77-C7702-FAN (Version 0.016)
- F3 Series 48-port, 1- and 10-Gigabit Ethernet I/O module (N77-F348XP-23) (from 1.007 to 1.008)
- F3 Series 12-port, 100-Gigabit Ethernet I/O module (N77-F312CK-26) (Version 0.019)
- F3 Series 48-port, 1- and 10-Gigabit Ethernet I/O module (N77-F348XP-23) (from 1.004 to 1.007)
- F3 Series 48-port, 1- and 10-Gigabit Ethernet I/O module (N77-F348XP-23) (from 0.026 to 0.031)
- F3 Series 48-port, 1- and 10-Gigabit Ethernet I/O module (N77-F348XP-23) (from 1.002 to 1.003)
Cisco Nexus 7700 switches have an EPLD image that is programmed on the switches. This EPLD image is different than the EPLD image for the Cisco Nexus 7000 switches.
Note The CPAK-100G-ER4L transceiver works in N77-F312CK-26 only when you upgrade EPLD IO SPI to version 0.021. Other transceivers such as CPAK-100G-LR4, CPAK-100G-SR10, and CPAK-100G-SR4 function properly in N77-F312CK-26 with EPLD version 0.019.
The Cisco Nexus 7000 Series Network Analysis Module (Cisco NAM-NX1) also includes an EPLD image that is programmed on the device.
The following modules are supported in Cisco NX-OS 7.3.x and in Cisco NX-OS 7.2.x releases:
Note Table 3 shows EPLD image numbers in X.00y format but the show commands might display these numbers in an older X.y format (without leading zeros) for earlier EPLD images.
Note To list the EPLDs running on your switch, use the show version module module_number epld command. If any of the versions that you list are older than what is listed in Table 3, we recommend that you update the EPLDs.
Determining Whether to Upgrade EPLD Images
As shown in Table 4 , you can use various show commands to determine whether the EPLDs can be upgraded for all the modules or for specific modules on a switch. These commands indicate the current EPLD images, new EPLD images, and whether the upgrades would be disruptive to switch operations.
If there are different EPLD images to use depending on the version ID (VID) of a hardware module (see Table 3), then you must determine the version number of the module by using the show sprom module number command as shown in Example 1.
Example 1 Determining the Version Number of a Supervisor or I/O Module
Downloading the EPLD Images
Before you can prepare the EPLD images for installation, you must download them to the FTP or management server.
To download the EPLD images, follow these steps:
Step 1 From a browser, go to the following URL:
The browser will display the Cisco website.
Step 2 From the Products & Services tab, choose Switches .
Step 3 In the Data Center area, click the arrow next to View Products.
The page lists the Data Center products.
The Cisco Nexus 7000 Series Switches page opens.
Step 5 In the Support area, click Download Software .
The Downloads page opens and lists the Data Center switches.
Step 6 Choose a Cisco Nexus 7000 Series switch from the list under Data Center Switches > Cisco Nexus 7000 Series Switches .
Step 7 If you are an existing user, enter your username in the User Name field and your password in the Password field. If you are a new user, click Register Now and provide the required information before returning to the Log In page and logging in with your new username.
The Downloads page lists the software types that can be downloaded for the switch that you specified.
Step 8 Click NX-OS EPLD Updates .
The Downloads page lists software releases that you can download.
Step 9 Choose Latest Releases > 6.2(10) .
The Downloads page displays image information, including a link to the downloadable Tar file, to the right of the releases.
Note For Releases 6.1(1) or 6.1(2), you must download EPLD image files for 6.1(1a) or 6.1(2a).
Step 10 Click the link for the Tar file.
The Downloads page displays a Download button and lists information for the Tar file.
The Supporting Documents page opens to display the rules for downloading the software.
Step 12 Read the rules and click Agree .
A File Download dialog box opens to ask if you want to open or save the images file.
The Save As dialog box appears.
Step 14 Indicate where to save the Tar file and click Save .
The Tar file saves to the location that you specified.
You are ready to prepare the EPLD images for Installation (see the “Preparing the EPLD Images for Installation” section).
EPLD Images Needed for vPCs
The virtual port channel (vPC) feature is available beginning with Cisco NX-OS Release 4.1(3). When you enable vPC on the chassis, you must have EPLD image 186.3 (or later image) on the 32-port 10-Gigabit Ethernet types of I/O modules (N7K-M132XP-12 and N7K-M132XP-12L).
Note The EPLD upgrade operation is a disruptive operation. You should execute this operation only at a programmed maintenance time. The system/kickstart ISSU upgrade is a nondisruptive upgrade.
Note Do not perform an EPLD upgrade during an ISSU system/kickstart upgrade.
Most of the N7K-M132XP-12 modules in the chassis already meet this minimum EPLD requirement, but if you are working with an N7K-M132XP-12 module that was shipped before June 2008, you might need to upgrade the EPLD version.
To determine the EPLD version for all N7K-M132XP-12 modules, enter the show version module slot_number epld command. If the line FE Bridge( x ) version displays a version earlier than 186.7, you should schedule an EPLD upgrade to a version that is compatible with the target Cisco NX-OS release. For example, if you want to run Cisco NX-OS Release 6.1(2), you should choose Release 6.1(2) EPLDs.
The following example shows Release 186.008 on the FE Bridge line, which is a correct EPLD version:
Nexus-7k(config)# show version module 7 epld
EPLD Device Version
-----------------------------------------
Power Manager 4.008
IO 1.016
Forwarding Engine 1.006
FE Bridge(1) 186.008 << OK!
FE Bridge(2) 186.008 << OK!
Linksec Engine(1) 2.007
Linksec Engine(2) 2.007
Linksec Engine(3) 2.007
Linksec Engine(4) 2.007
Linksec Engine(5) 2.007
Linksec Engine(6) 2.007
Linksec Engine(7) 2.007
Linksec Engine(8) 2.007EPLD Images Needed for LISP
The Locator/ID Separator Protocol ( LISP) feature is available beginning with Cisco NX-OS Release 5.2(1). When you enable LISP on the chassis, you must have EPLD image 186.008 (or later image) on the 32-port 10-Gigabit Ethernet types of I/O modules (N7K-M132XP-12 and N7K-M132XP-12L).
Note The EPLD upgrade operation is a disruptive operation. You should execute this operation only at a programmed maintenance time. The system/kickstart ISSU upgrade is a nondisruptive upgrade.
Note Do not perform an EPLD upgrade during an ISSU system/kickstart upgrade.
If you are working with an N7K-M132XP-12 module that was shipped before July 2011, you might need to upgrade the EPLD version.
To determine the EPLD version for all N7K-M132XP-12 and N7K-M132XP-12L modules, enter the show version module module_id epld . If the line FE Bridge(x) version displays a version earlier than 186.008, you should schedule an EPLD upgrade to a version that is compatible with the target Cisco NX-OS release. For example, if you want to run Cisco NX-OS Release 5.2(1), you should choose Release 5.2(1) EPLDs.
The following example shows Release 186.008 on the FE Bridge line, which is the correct EPLD version:
Nexus-7k(config)# show version module 7 epld
EPLD Device Version
-----------------------------------------
Power Manager 4.008
IO 1.016
Forwarding Engine 1.006
FE Bridge(1) 186.008 << OK!
FE Bridge(2) 186.008 << OK!
Linksec Engine(1) 2.007
Linksec Engine(2) 2.007
Linksec Engine(3) 2.007
Linksec Engine(4) 2.007
Linksec Engine(5) 2.007
Linksec Engine(6) 2.007
Linksec Engine(7) 2.007
Linksec Engine(8) 2.007Installation Guidelines
You can upgrade (or downgrade) EPLDs using CLI commands on the Cisco Nexus 7000 Series switch. By default, EPLD images are not downgraded when you downgrade the NX-OS software release because each EPLD image works with older releases of the software. If you need to downgrade the EPLD version, you must include the allow-downgrade keyword with the install command. Follow these guidelines when you upgrade or downgrade EPLDs:
- Before you upgrade any EPLD images, be sure that you have updated the Cisco NX-OS operating system to the level required for the images and be sure that you have one of the following EPLD image files:
– n7000-s2-epld.6.2.8.img (for Cisco Nexus 7004, 7009, 7010, and 7018 switches with Supervisor 2 or Supervisor 2E modules)
– n7700-s2-epld.6.2.8.img (for Cisco Nexus 7706, 7710, and 7718 switches)
- You can execute an upgrade from the active supervisor module only. This upgrade is for one or all of the modules as follows:
– You can upgrade a module individually.
– You can upgrade all modules sequentially.
– You can upgrade all modules in parallel.
- You can update the images for one or all modules whether the switch is online or offline as follows:
– If the modules are on line, only the EPLD images with version numbers that differ from the new EPLD images are upgraded.
– If the modules are offline, all of the EPLD images are upgraded.
- On a system that has two supervisor modules, upgrade the EPLDs for the standby supervisor and then switch the active supervisor to the standby mode to upgrade its EPLDs (the supervisor switchover is not disruptive to traffic on Cisco Nexus 7000 Series switches). On a switch that has only one supervisor module, you can upgrade the active supervisor, but this will disrupt its operations during the upgrade.
- If you interrupt an upgrade, you must upgrade the module that is being upgraded again.
- The upgrade process disrupts traffic on the targeted module.
- Do not insert or remove any modules while an EPLD upgrade is in progress.
Preparing the EPLD Images for Installation
Before you can update the EPLD images for each of your switch modules, you must determine the Cisco NX-OS version that your switch is using, make sure that there is space for the new EPLD images, and download the images.
To prepare the EPLD images for installation, follow these steps:
Step 1 Log in to the switch through the console port, an SSH session, or a Telnet session.
Step 2 Verify that the switch is using the expected version of the Cisco NX-OS operating system. The kickstart and system lines indicate the Cisco NX-OS version. This step determines the versions of EPLD images that you must download.
Step 3 Verify that you have 120 MB of free space on the active or standby supervisor memory devices for the EPLD images that you will be downloading by using the dir bootflash: or dir slot0: commands.
By default, these commands display the used and free memory for the active supervisor. If your switch has an additional supervisor (a standby supervisor), use the show module command to find the module number for the other supervisor, use the attach module command to attach to the module number, and then use the dir bootflash: or dir slot0: command to determine the amount of used and free memory. See Example 2 to determine the amount of available bootflash memory, and see Example 3 to determine the amount of available slot0 memory.
Example 2 Determining the Amount of Available Bootflash Memory
Example 3 Determining the Amount of Available Slot0 Memory
Step 4 If there is not at least 120 MB of memory free for the EPLD files, delete some unneeded files, such as earlier images, so there is enough free memory.
Step 5 Copy the EPLD image file from the FTP or management server to the bootflash or slot0 memory in the active supervisor module. The following example shows how to copy from the FTP server to the bootflash memory:
Note For NX-OS Release 6.1(1), you must copy the n7000-s2-epld.6.1.1a.img (for supervisor 2 modules) files. For NX-OS Release 6.1(2), you must copy the n7000-s2-epld.6.1.2a.img (for supervisor 2 modules) files.
Step 6 Copy the EPLD image to the standby supervisor.
You are ready to upgrade the EPLD images (see the “Manual Upgrading of EPLD Images” section).
Manual Upgrading of EPLD Images
You can manually upgrade the EPLD images for either all of the modules installed in your switch or specific modules installed in your switch. When you request an upgrade, the Cisco NX-OS software lists the current and new versions for each EPLD image with the following results:
- If a module is installed and online, the software lists the installed and new versions for each EPLD. Where there is a difference in versions, the software indicates an upgrade or downgrade to occur when you confirm the process.
- If a module is installed and offline, the software cannot list its current EPLD versions so all EPLDs will be updated when you confirm the upgrade.
- If a module is not installed, the software displays an error message and does not upgrade the EPLDs.
If you need to know which modules can be updated and which upgrades are disruptive to switch operations, see the “Determining Whether to Upgrade EPLD Images” section.
To upgrade the EPLD images for a Cisco Nexus 7000 Series switch, you use one of the install commands listed in Table 5 . These commands enable you to upgrade the EPLD images for all of the modules on the switch, multiple modules of one or two types, or single modules. When specifying a slot_number , use one number. When specifying slot_numbers , you can specify all for all slots, multiple slots separated by commas ( x , y , z ) or a range of slot numbers ( x - y ).
When you upgrade both supervisor modules in a switch, Cisco NX-OS upgrades the EPLD images for the standby supervisor module and then upgrades the active supervisor module. This action enables the upgrade of supervisor modules to be nondisruptive to switch operations.
Note When upgrading EPLD images for Supervisor 2 or Supervisor 2E modules in a dual-supervisor switch, the standby supervisor will reset twice towards the end of that upgrade but the upgrade continues to completion and the console displays the upgrade status.
When you upgrade supervisor module in a single-supervisor switch, the operation is disruptive to switch operations if the switch is active.
To start the installation of all new EPLD images for all modules in a switch, use the install all epld command as shown in Example 4 (switches with Supervisor 2 or Supervisor 2E modules).
Note When upgrading EPLD images for F3 Series I/O modules, you must upgrade them in parallel by including the parallel keyword with the install command. For example, if you are updating the images for the F3 Series I/O module in slot 2, you use the following command:
switch#install all epld epld_image parallel module 2
Note EPLD and software images for a chassis with Supervisor 2 and Supervisor 2E have “s2” in the image name.
Example 4 Installing EPLD Images in Parallel for Switches with Supervisor 2 or Supervisor 2E Modules
Note For Releases 6.1(1) and 6.1(2), if there are any powered down M2 Series I/O modules, use the no poweroff module command to power up that module.
switch#no poweroff module slot_number
Note For Release 4.0(2) or earlier releases, if you updated the power management EPLD image, you must reset the power for the module so that EPLD can take effect (this is not required for release 4.0(3) or later). You can reset the power in one of the following two ways: reset the power for the module (physically remove the module and reinstall it—a module reload or just pressing the ejector buttons is not sufficient for this reset requirement), or reset the entire switch (power cycle the switch).
Caution Resetting the power disrupts any data traffic going through the affected modules. If you power cycle the entire switch, all data traffic going through the switch at the time of the power cycling is disrupted. This is not necessary for Release 4.0(3) or later releases.
Note For Release 4.0(3) and later releases, the switch automatically loads the new power management EPLD after an upgrade, so it is no longer necessary to reset the power for the module or switch.
To confirm the EPLD upgrades, see the “Verifying the EPLD Upgrades and Downgrades” section.
Automatic Upgrading of EPLD Images
You can enable, disable, and verify automatic upgrading of EPLD images for I/O modules installed in the Cisco Nexus 70 xx (as of Release 6.2[2])and 77 xx (as of Release 6.2[6]) switches. Also, if the upgrade is canceled because it exceeds a maximum number of programmed attempts, you can reset the process to enable the upgrades.
Note You can set automatic upgrading of EPLD images for only I/O modules, not for other modules such as the supervisor modules, fabric modules, or fan trays.
This section includes the following topics:
- Enabling or Disabling Automatic Upgrades of EPLD Images
- Verifying Automatic Upgrades of EPLD Images
- Resetting Automatic Upgrades of EPLD Images
Enabling or Disabling Automatic Upgrades of EPLD Images
You can enable or disable automatic upgrades of EPLD images for I/O modules. When enabled, the switch checks the EPLD image versions on newly installed or powered up I/O modules to see if they are older than the images that were installed on the switch. If the images on the I/O modules are older, the switch automatically upgrades the images to the newer versions.
SUMMARY STEPS
3. show running-config | inc epld
Note Alternatively, to prevent automatic upgrades of EPLD images for I/O modules, use the no system auto-upgrade epld command.
Verifying Automatic Upgrades of EPLD Images
To check on the automatic upgrade status while the upgrades occur or after the upgrades, use the commands listed in Table 1-6 .
Note During automatic upgrades of I/O modules, the status for VDC creation is pending until all of the installed I/O modules are upgraded and online.
Resetting Automatic Upgrades of EPLD Images
If the automatic upgrade function has stopped because it has exceeded the maximum number of allowed update attempts, you will see the following message:
switch# 2013 May 21 13:30:21 switch %$ VDC-1 %$_ %USER-2-SYSTEM_MSG: <<%EPLD_AUTO-2-AUTO_UPGRADE_CHECK>> Automatic EPLD upgrade check for module 15: Max retries reached. Use 'clear auto-upgrade epld flags all' to upgrade. - epld_autoYou can reset the automatic upgrade process in one of the following ways:
Downgrading EPLD Images
By default, you cannot downgrade EPLD images when you downgrade the NX-OS software release because the EPLD images work with downlevel versions of the software. For this reason, we do not recommend downgrading EPLD images. If you need to downgrade EPLD images, you must include the allow-downgrade keyword after the parallel keyword in the install command as shown in Example 5.
Verifying the EPLD Upgrades and Downgrades
You can verify the EPLD upgrades and downgrades for each slot in the switch by using the commands listed in Table 7 .
This example shows how to verify the EPLD images for the Cisco Nexus 7018 supervisor module in slot 9:
This example shows how to verify the EPLD images for the fan-tray module in fan-tray module slot 2:
This example shows how to verify the EPLD images for the fabric module in fabric module slot 4:
Displaying the Available EPLD Versions
To view the available EPLD versions in an EPLD image file, use the show version epld url command as shown in Example 6.
Note If the NX-OS and the EPLD versions do not match, issuing the show version epld url command may cause it to exit with the error message: Could not extract EPLD images, Insufficient space in bootflash, Failed to extract EPLD image versions, Exiting. For example, if a Nexus 7000 switch is running NX-OS 6.1(4) and the EPLD version is 6.2(2), issuing the show version epld url command will return the error message: Could not extract EPLD images, Insufficient space in bootflash, Failed to extract EPLD image versions, Exiting.
Displaying the Status of EPLD Upgrades
To display the status of EPLD upgrades on the switch, use the show install epld status command as shown in Example 7.
Caveats
This section includes the following topics:
Open Caveats
This section lists the EPLD related caveats that are resolved for Cisco NX-OS Release 7.2(0)D1(1).
Limitations
When EPLDs are upgraded or downgraded, the following guidelines and observations apply:
- You cannot upgrade the Local Bus CPLD and CMP CPLD while you are upgrading a supervisor module in the 4.0(1) release only.
- You must upgrade each installed module individually. If the module is online, Cisco NX-OS upgrades only the EPLD images that have different current and new versions. If the module is offline, all EPLDs are upgraded, even if their version numbers are the same.
- The existing FPGA image version should match the new FPGA image version. For Example, the FPGA image version 2.x cannot be downloaded onto cards which already have FPGA image version 1.x, and vice-versa [FPGA images 1.x cannot be downloaded onto the revised cards, which have FPGA images 2.x].
- If you interrupt an upgrade, you must upgrade the module again.
- You can execute an upgrade or downgrade only from the active supervisor module. On switches with two supervisors, upgrade the standby supervisor and then switch the standby supervisor to active to place the previously active supervisor module in standby mode. Upgrade the EPLDs on the standby supervisor. On switches that have only one supervisor, you must upgrade or downgrade the EPLDs on the active supervisor, which will interfere with data traffic during the upgrade.
- Release 4.1(2) does not provide EPLD upgrades for the Cisco Nexus 7018 fan controller.
Related Documentation
Cisco Nexus 7000 Series documentation is available at the following URL:
http://www.cisco.com/en/US/products/ps9402/tsd_products_support_series_home.html
The documentation set includes the following documents:
- Cisco Nexus 7000 Series Site Preparation Guide
- Cisco Nexus 7000 Series Hardware Installation and Reference Guide
- Cisco Nexus 7000 Series Regulatory Compliance and Safety Information
- Cisco Nexus 7000 Series Connectivity Management Processor Configuration Guide
The release notes for upgrading Cisco NX-OS and DCNM are available at the following URL:
http://www.cisco.com/en/US/products/ps9402/prod_release_notes_list.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation , which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the “Related Documentation” section.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)
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)