Cisco Nexus 9000 Series FPGA/EPLD Upgrade Release Notes, Release 10.6(1)

 

Note:      Beginning with Release 10.5(3), Cisco provides a single image for NXOS and EPLD images. There will no longer be separate images. Instead, the EPLD image is bundled with all NXOS images and so the image sizes are correspondingly larger.

Here’s the link to the Cisco Nexus 9000 Series NX-OS Software Upgrade and Downgrade Guide, Release 10.5(x).

Starting with Release 10.5(3), these three 64-bit images are supported:

·       The 64-bit Cisco NX-OS image file name with nxos64-cs as the prefix (for example, nxos64-cs.10.6.1.F.bin) is supported on all Cisco Nexus 9000 series switches except Cisco Nexus 9500 -R and -R2 switches and line cards and Nexus 9800 switches.

·       The 64-bit Cisco NXOS image file name with nxos64-s1 as the prefix (for example, nxos64-s1.10.6.1.bin) is mandatory on Nexus 9800 switches and N9364E-SG2 switches and is supported from Cisco NXOS Release 10.5(3)F.

·       The 64-bit Cisco NXOS image file name with nxos64-msll as the prefix (for example, nxos64-msll.10.6.1.F.bin) is supported on Cisco Nexus 9000 Series -R and -R2 modular switches.

This document lists the current and past versions of EPLD images and describes how to update them for use with the Cisco Nexus 9000 Series switches.

This document also covers later releases. If a new Cisco Nexus 9000 Series FPGA/EPLD Upgrade Release Notes document isn’t available, that means that these are the latest available numbers for upgrade.

This table lists the changes to this document.

Table 1.        Changes to this Document

Introduction

The Cisco Nexus 9000 Series NX-OS mode 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 a line card 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. These EPLD image updates are not mandatory unless otherwise specified. The EPLD image upgrades are independent from the Cisco In Service Software Upgrade (ISSU) process, which upgrades the system image 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 the EPLD images from https://software.cisco.com/download/navigator.html.

When choosing an EPLD version for upgrade, ensure you have already installed the corresponding NXOS software version first. It is generally not supported to upgrade to a newer EPLD image built for a future version of NXOS while running on an older NXOS version, unless explicitly supported as per the specific EPLD Release Notes. NXOS and EPLD images are labeled for their related version to avoid any unsupported upgrades.

When to Upgrade EPLDs

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, then consider postponing the upgrade until a better time.

Note:      The EPLD upgrade operation is a disruptive operation. Execute this operation only at a programmed maintenance time. The system ISSU upgrade is a nondisruptive upgrade.

Note:      The EPLD version is backward compatible. The NXOS software can be downgraded for the switch and the EPLD version does not have to be downgraded to match the older NXOS version.

Switch Requirements

·       The Cisco Nexus 9000 Series switch must be running the Cisco NX-OS operating system.

·       You must be able to access the switch through a console, SSH, or Telnet (required for setting up a switch running in NX-OS mode).

·       You must have administrator privileges to work with the Cisco Nexus 9000 Series switch.

EPLD Upgrades Available for NX-OS Mode Releases 10.4(3) through 10.6(1)

Each EPLD image that you can download from Software Download page is a bundle of EPLD upgrades packaged into a single EPLD image file. Beginning with NXOS Release 10.5(3), this EPLD image file is bundled with NXOS images. There will no longer be separate images. To see the available EPLD versions for the Nexus 9000 standalone and module switches on this release, see the tables.

Note:      All updates to an image are shown in boldface. If more than one release is shown for a column, the boldface applies to the first release listed for the column.

Note:      This release of EPLD addresses the Secure Boot Hardware Tampering vulnerability for Nexus 9000 Series switches. Please refer to this Security Advisory for more information - https://www.cisco.com/c/en/us/support/docs/csa/cisco-sa-20190513-secureboot.html.

Table 2.        Available EPLD Images for the Cisco Nexus 9200, 9300, 9300-EX, and 9300-FX Platform Switches

 

Table 3.        Available EPLD Images for the Cisco Nexus 9400 Switches

Table 4.        Available EPLD Images for the Cisco Nexus 9500 Platform Switches

Table 5.        Available EPLD Images for the Cisco Nexus 9500 Switches with R Line Card

 

Table 6.        Available EPLD Images for the Cisco Nexus 9800 Platform Switches

Determining Whether to Upgrade EPLD Images

If the current EPLD image number for a card is greater than or matches the version expected for your current NXOS software version, you can skip the upgrade.

·       To determine the EPLD upgrades needed for a Cisco Nexus 9000 Series switch running 10.6(1) software, use the show install impact epld bootflash:<image-name> command on that switch, where the image-name given is nxos64-cs.10.6.1.F.bin or nxos64-msll.10.6.1.F.bin or nxos64-s1.10.6.1.F.bin. First, copy this file to the bootflash to proceed. In this example, the MIFPGA and IOFPGA EPLD images do not need to be upgraded.

Note:      The CLI content in this document is only an example. The CLI output might change depending on the hardware/software.

switch# show install all impact epld nxos64-cs.10.6.1.F.bin

Retrieving EPLD versions.... Please wait.

Images will be upgraded according to following table:

Module     Type        EPLD          Running-Version    Flashed-Version     New-Version        Upg-Required

------      ----        -----          --------------          ---------- -                -- -------------------

         1      SUP       MI FPGA             0x09                      0x09                       0x09                       No

         1      SUP       IO FPGA             0x18                      0x18                       0x18                        No

       27      SUP       MI FPGA             0x09                      0x09                       0x09                        No

       27      SUP       IO FPGA             0x18                       0x18                       0x18                       No

Compatibility check:

Module         Type          Upgradable               Impact                       Reason              

 -----           ----          ----------               -------                   ----------------

         27          SUP            Yes                       disruptive              Module Upgradable

switch#

EPLD Upgrade Using Install EPLD Command

To install the EPLD upgrades needed for a Cisco Nexus 9000 Series switch running 10.5(3) software, use the install epld bootflash:<image-name> module all command on that switch. Where the image-name given is nxos64-cs.10.6.1.F.bin or nxos64-msll.10.6.1.F.bin or nxos64-s1.10.6.1.F.bin. First, copy this file to the bootflash to proceed. In this example, the MIFPGA and IOFPGA EPLD images need to be upgraded.

Note:      The CLI content in this document is only an example. The CLI output might change depending on the hardware/software.

switch# install epld bootflash:nxos64-cs.10.6.1.F.bin module all

Compatibility check:

Module           Type             Upgradable               Impact                 Reason  

------             ----             ---------                ------                 -------

      27             SUP              Yes                          disruptive             Module Upgradable

Retrieving EPLD versions.... Please wait.

Images will be upgraded according to the following table:

Module       Type       EPLD          Running-Version       Flashed-Version     New-Version         Upg-Required

       27        SUP       MI FPGA         0x09                     0x09                        0x09                          No

       27        SUP       IO FPGA          0x15                    0x15                         0x18                         Yes

The above modules require upgrade. EPLD Upgrade may result in multiple modules going offline. The switch will be reloaded at the end of the upgrade.

Do you want to continue   (y/n)    ?     [n]   y

Proceeding to upgrade Modules.

Starting Module 27 EPLD Upgrade

Module 27 :      IO FPGA      [Programming] :  100.00%     (           64 of            64 sectors)

Module 27 EPLD upgrade is successful…

Module               Type                  Upgrade-Result

-------               -----                --------------

         27               SUP                  Success

Module 27 EPLD upgrade is successful.

Module               Type                   Upgrade-Result

------                ----                    ----------------

          27           SUP                        Success

 

Reseting Active SUP (Module 27) FPGAs.  
Please wait...

Reload in 10 seconds......

switch#

 

EPLD Upgrade During Install All

Beginning with Release 10.5(3), the EPLD image can be upgraded along with the nxos image during install all. To upgrade your EPLD image using the install all command, use install all nxos <image-name>. This command will upgrade both NXOS and EPLD, if required.

switch# install all nxos bootflash:nxos64-cs.10.6.1.F.bin

Installer will perform compatibility check first. Please wait.

Installer is forced disruptive    

Verifying image bootflash:/nxos64-cs.10.6.1.F.bin for boot variable "nxos".

[####################] 100% -- SUCCESS

Verifying EPLD/FPGA image //bootflash/nxos64-cs.10.6.1.F.bin.

[####################] 100% -- SUCCESS

Verifying image type.

[####################] 100% -- SUCCESS

Preparing "nxos" version info using image bootflash:/nxos64-cs.10.6.1.F.bin.

[####################] 100% -- SUCCESS

Preparing "bios" version info using image bootflash:/nxos64-cs.10.6.1.F.bin.

[####################] 100% -- SUCCESS

Performing module support checks.

[####################] 100% -- SUCCESS

Notifying services about system upgrade.

[####################] 100% -- SUCCESS

 

 

 

 

 

Compatibility check is done:

Module         bootable           Impact                Install-type          Reason                              

------          -------            --------            ----------          ---------------------

         1          yes                  disruptive            reset                     default upgrade is not hitless

       27          yes                  disruptive            none                     default upgrade is not hitless

 

 

Images will be upgraded according to the following table:

Module          Image         Running-Version(pri:alt)                          New-Version                   Upg-Required 

          1          lcn9k                                    10.5(3)                          10.6(1)                                             Yes

        27          nxos                                     10.5(3)                          10.6(1)                                              Yes

        27           bios     v05.53(01/22/2025):v05.43(11/22/2020)     v05.53(01/22/2025)                          No

 

FPGA microcode will be upgraded according to the following table:

Module       Type        EPLD            Running-Version     Flashed-Version    New-Version        Upg-Required

        27       SUP        MI FPGA        0x09                          0x09                      0x09                        No

        27       SUP        IO FPGA        0x15                      0x15                          0x18                        Yes

 

EPLD Upgrade may result in multiple modules going offline.

 

Switch will be reloaded for disruptive upgrade.

Do you want to continue with the installation   (y/n) ?   [n]   y

 

Install is in progress, please wait.

[#          ] 0%

Setting boot variables.

[####################] 100%

Performing configuration copy.

[####################] 100% -- SUCCESS

Performing configuration copy.

[####################] 100% -- SUCCESS

 

Module 1: Refreshing compact flash and upgrading bios/loader/bootrom.

Warning: please do not remove or power off the module at this time.

[#         ]  0%

 

Module 1: Refreshing compact flash and upgrading bios/loader/bootrom.

Warning: please do not remove or power off the module at this time.

[####################] 100% -- SUCCESS

 

Module 27: Refreshing compact flash and upgrading bios/loader/bootrom.

Warning: please do not remove or power off the module at this time.

[#      ]  0%

 

Module 27: Refreshing compact flash and upgrading bios/loader/bootrom.

Warning: please do not remove or power off the module at this time.

[####################] 100% -- SUCCESS

 

Performing EPLD/FPGA upgrade .

[#      ] 0%

 

Performing EPLD/FPGA upgrade.

[####################] 100% -- SUCCESS

 

Finishing the upgrade, switch will reboot in 10 seconds.

switch#

 

EPLD upgrades are disruptive. For non-disruptive NXOS system upgrade, use the install all nxos <image-name> non-disruptive command. This command will upgrade and load a new NXOS version and program the EPLD. However, explicit power cycle or reload of the switch is required for the new EPLD image to take effect.

To upgrade only NXOS, you can use the skip-epld option. Use this command:  install all nxos <image-name> skip-epld

For additional information about ISSU, please see the Cisco Nexus 9000 Series NX-OS Software Upgrade and Downgrade Guide.

Displaying the Status of EPLD Upgrades

To display the status of EPLD upgrades on the switch, use the show install epld status command.

Limitations

When EPLDs are upgraded, apply these guidelines and observations:

●     If a module is not online, you cannot upgrade its EPLD images.

●     If there are two supervisors that are installed in the switch (Cisco Nexus 9504, 9508, and 9516 switches only), you can either upgrade only the standby or upgrade all modules (including both supervisor modules) by using these commands:

◦    install epld bootflash:<image-name> module standby-supervisor-slot-number (upgrades only the standby supervisor module)

Note:      After you use this command, you can switchover the active and standby supervisor modules and then upgrade the other supervisor.

◦    install epld bootflash:<image-name> module all (upgrades all of the modules)

●     If there is only one supervisor installed in the switch, the upgrade or downgrade of the EPLD images is disruptive.

Cisco Secure Boot Hardware Tampering Vulnerability

This section details updating your EPLD version for affected switches listed in the link below. The table provides the PIDs exposed to the issue, as well as the fixed IO FPGA version for each PID, for validation purposes.

Secure Boot Hardware Tampering Vulnerability advisory: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190513-secureboot

Vulnerable Products

These are the vulnerable products addressed in the Secure Boot Tampering Security Advisory (cisco-sa-20190513-secureboot).

Table 7.        Nexus 9000 Series Switches affected by the Secure Boot Hardware Tampering Vulnerability

Cisco Secure Boot Hardware Tampering Vulnerability - Remediation Steps

Nexus 9000 Modular chassis with dual supervisor

Note:      Requirement–Update both Golden and Primary regions of FPGA to address this particular vulnerability. It is by design that we don't allow updating both primary and golden at the same time (to avoid programming errors that may cause switch to not boot, so only one region is allowed to be programmed per reload).

Note:      Beginning with Release 10.5(3), Cisco provides a single image for NXOS and EPLD images. There will no longer be separate images. Instead, the EPLD image is bundled with all NXOS images and so the image sizes are correspondingly larger.

Please do not attempt to upgrade Golden region of the FPGA once it is on a fixed version.

1.     Copy the EPLD image to bootflash (e.g., this document will use the nxos64-cs.10.6.1.F.bin image).

2.     If you have dual supervisors, determine which is the standby supervisor by doing 'show module' to verify the status of the supervisors, and start upgrading the standby first. On the Nexus 9500, only supervisors need to be upgraded to address this vulnerability. Line cards/fabric modules/system controllers are not affected.

3.     Assuming the standby supervisor is slot 28, update the Primary FPGA region of the standby supervisor.

install epld bootflash: nxos64-cs.10.6.1.F.bin module 28

Expected result: The switch will update the primary EPLD of the standby supervisor and will reload the standby supervisor module automatically. Please don't interrupt, power cycle, or reload when EPLD update is happening. Once the standby is rebooted, it will again come up as the standby supervisor.  The command show version module 28 epld will continue to show the old version.

Note:    The CLI sequence used in this document is just an example. Your CLI sequence can be confirmed directly on the switch.

switch# show mod | grep SUP

27   0    Supervisor Module                     N9K-SUP-A             active *

28   0    Supervisor Module                     N9K-SUP-A             ha-standby           <<< standby supervisor

27   10.3(5)               1.0    SUP1

28   10.3(5)               0.3011 SUP2

switch# show version module 28 epld

EPLD Device                     Version

---------------------------------------

IO FPGA                          0x27

This is expected, as the switch would have booted from Golden FPGA which is still not updated. You can verify this from the syslog which would say:

%CARDCLIENT-5-MOD_BOOT_GOLDEN: Module 28 IOFPGA booted from Golden

4.     Update the Golden (also called backup) FPGA region of the standby supervisor.

install epld bootflash: nxos64-cs.10.6.1.F.bin module 28 golden

Module 28 : IO FPGA [Programming ] : 100.00% ( 64 of 64 total sectors)

Module 28 EPLD upgrade is successful.

Module        Type  Upgrade-Result

------  ------------------  --------------

28         SUP         Success

Expected result: Switch will update the golden EPLD of the standby supervisor and will reload the standby supervisor module automatically. Please don't interrupt, power cycle, or reload when EPLD update is happening. Once standby is booted, it will again come up as the standby supervisor.

Once this is done, check show version module 28 epld to confirm the FPGA version is greater than or equal to the fixed version for the standby supervisor.  Your switch has the fixed version for standby supervisor.

 

switch# show version module 28 epld

EPLD Device                     Version

---------------------------------------

IO FPGA                          0x30

Repeat Steps 3 and 4 for the active supervisor. At the end of Step 3, the supervisor in slot 27 will reload and so now will become the standby supervisor. The active supervisor will be the supervisor in slot 28.

For the situation where the active supervisor is in the other slot, considering SUP 27 is active to begin with, for the above activity, such as Steps 3 and 4, commands would have swapped 27 in place of 28.

Log below shows what happens when the EPLD upgrade happens for the active supervisor:

Module 27 : IO FPGA [Programming] : 100.00% (64 of 64 sectors)

Module 27 EPLD upgrade is successful.

Module        Type  Upgrade-Result

------  ------------------  --------------

27         SUP         Success 

EPLDs upgraded. Performing switchover.

Once the supervisor in Slot 27 becomes ha-standby, complete Step 4 for Slot 27 and it will again boot and become the ha-standby.  Both the supervisors now have the vulnerability fixed version of the FPGA.

At the end of the upgrades, the switch should boot with the primary EPLD image for both SUPs, as seen in the logs below:

switch# show logging log | grep -i fpga | grep -i 27

2019 Jul 10 07:55:04 switch %CARDCLIENT-5-MOD_BOOT_PRIMARY: Module 27 IOFPGA booted from Primary

switch# show logging log | grep -i fpga | grep -i 28

2019 Jul 10 07:58:01 switch %CARDCLIENT-5-MOD_BOOT_PRIMARY: Module 28 IOFPGA booted from Primary

Nexus 9000 Modular chassis with single supervisor

Note:      Requirement–Update both Golden and Primary regions of FPGA to address this vulnerability. It is by design that we don't allow updating both primary and golden at the same time (to avoid programming errors that may cause switch to not boot, so only one region is allowed to be programmed per reload).

Please do not attempt to upgrade Golden region of FPGA once it is on a fixed version.

1.     Copy the NXOS image to bootflash (e.g., this document will use the nxos64-cs.10.6.1.F.bin image).

2.     Assuming the supervisor is in slot 27, update the Primary FPGA region.

install epld bootflash: nxos64-cs.10.6.1.F.bin module 27

Expected result: Switch will update the primary EPLD of the supervisor and will reload the switch automatically. Please don't interrupt, power cycle, or reload when EPLD update is happening. Once the supervisor is booted, the command show version module 27 epld will continue to show the old version.

Note:    The CLI sequence used in this document is just an example. Your CLI sequence can be confirmed directly on the switch.

Switch#show version module 27 epld

-------------------------------------------------------------------

Name                     InstanceNum           Version        Date

-------------------------------------------------------------------

IO FPGA                          0              0x27       20160111

BIOS version                     v08.35(08/31/2018)

Alternate BIOS version           v08.32(10/18/2016)

This is expected, as the switch would have booted from the Golden FPGA which is still not updated. You can verify this from the syslog which would say:

%CARDCLIENT-5-MOD_BOOT_GOLDEN: Module 27 IOFPGA booted from Golden

3.     Since in this case there is only one supervisor, next update the Golden (also called the backup) FPGA region.

install epld bootflash: nxos64-cs.10.6.1.F.bin module 27 golden

Module 27 : IO FPGA [Programming] : 100.00% (64 of 64 total sectors)

Module 27 EPLD upgrade is successful.

Module        Type  Upgrade-Result

------  ------------------  --------------

  27         SUP         Success

Expected result: The switch will update the golden EPLD of the supervisor and will reload the switch automatically. Please don't interrupt, power cycle, or reload the device while the EPLD update is in progress.

Once this is done, when you check the command show version module 27 epld to confirm that the FPGA version is greater than or equal to the fixed version for the supervisor. Your supervisor now has the vulnerability fixed version of FPGA.

 

Switch# show version module 27 epld

-------------------------------------------------------------------

Name                     InstanceNum           Version        Date

-------------------------------------------------------------------

IO FPGA                          0              0x30       20190625

BIOS version                     v08.35(08/31/2018)

Alternate BIOS version           v08.32(10/18/2016)

At the end of the upgrades, the switch should boot with the primary EPLD for the supervisor. The log to check is seen below:

switch# show logging log | grep -i fpga | grep -i 27

2019 Jul 10 07:55:04 switch %CARDCLIENT-5-MOD_BOOT_PRIMARY: Module 27 IOFPGA booted from Primary

 

IMPORTANT NOTE:

If you attempt to upgrade the Golden region of the FPGA once it is on the fixed version, the system will not automatically allow you to upgrade the Golden region of the supervisor and will provide the prompt seen below:

 

switch# install epld bootflash: nxos64-cs.10.6.1.F.bin module all golden

Digital signature verification is successful                        

Compatibility check:                                                

Module        Type         Upgradable        Impact   Reason        

------  -----------------  ----------    ----------   ------        

    22             FM           Yes       disruptive   Module Upgradable

    24             FM           Yes       disruptive   Module Upgradable

    27            SUP            No             none   Golden Not Upgradable

    28            SUP            No             none   Golden Not Upgradable

    29             SC           Yes       disruptive   Module Upgradable   

    30             SC           Yes       disruptive   Module Upgradable   

 

Retrieving EPLD versions.... Please wait.

Images will be upgraded according to this table:

Module  Type   EPLD              Running-Version   New-Version  Upg-Required

------  ----  -------------      ---------------   -----------  ------------

    22    FM  IO FPGA                   0x19        0x19            Yes    

    24    FM  IO FPGA                   0x19        0x19            Yes    

    29    SC  IO FPGA                   0x17        0x20            Yes    

    30    SC  IO FPGA                   0x17        0x20            Yes    

Module 27 (EPLD ver 0x29) Golden upgrade not supported                     

Module 28 (EPLD ver 0x30) Golden upgrade not supported                     

The above modules require upgrade.                                         

Since both System Controller modules need an upgrade,a chassis reload will happen at the end of the upgrade.

Do you want to continue (y/n) ?  [n] y

Nexus 9000 TOR (standalone chassis) switch

Note:      It is required to update both the Golden and Primary regions of the FPGA to address this vulnerability. It is by design that we don't allow updating both primary and golden at the same time (to avoid programming errors that may lead to switch boot failure), so only one FPGA region is allowed to be programmed per reload.

Please do not attempt to upgrade Golden region of FPGA once it is on a fixed version.

1.     Copy the EPLD image to bootflash (e.g., this document will use the nxos64-cs.10.6.1.F.bin image).

2.     Update the Primary FPGA region.

install epld bootflash: nxos64-cs.10.6.1.F.bin module all

Expected result: The switch will update the EPLD and will reload automatically. Please don't interrupt, power cycle, or reload the switch while the EPLD update is in progress.  The switch will boot up with the golden FPGA. The command show version module 1 epld will show the old IO FPGA version at this time. This is expected.

Note:    The CLI sequence used in this document is just an example. Your CLI sequence can be confirmed directly on the switch.

Switch# show version module 1 epld

-------------------------------------------------------------------

Name                     InstanceNum           Version        Date

-------------------------------------------------------------------

IO FPGA                          0              0x06       20180920

MI FPGA                          0              0x01       20170609

BIOS version                     v01.14(06/15/2019)

Alternate BIOS version           v01.12(07/25/2018)

You can verify this from syslog which would say:

%CARDCLIENT-5-MOD_BOOT_GOLDEN: Module 1 IOFPGA booted from Golden

%CARDCLIENT-2-FPGA_BOOT_GOLDEN: IOFPGA booted from Golden

3.     Update the Golden (also called backup) FPGA region.

install epld bootflash: nxos64-cs.10.6.1.F.bin module all golden

Expected result: The switch will update the EPLD image and will reload automatically. Please don't interrupt, power cycle, or further reload the switch when the EPLD update is in progress.

Once this is done, when you check show version module 1 epld, you will see an FPGA version that is greater than or equal to the fixed version.

Switch# show version module 1 epld

-------------------------------------------------------------------

Name                     InstanceNum           Version        Date

-------------------------------------------------------------------

IO FPGA                          0              0x07      20180920

MI FPGA                          0              0x01       20170609

BIOS version                     v01.14(06/15/2019)

Alternate BIOS version           v01.12(07/25/2018)

After the upgrade is complete, the switch should boot up with the primary EPLD image as shown in the logs below:

Switch# show logging log | grep -i fpga

2019 Jul  9 19:46:11 switch %CARDCLIENT-2-FPGA_BOOT_PRIMARY: IOFPGA booted from Primary

2019 Jul  9 19:46:11 switch %CARDCLIENT-2-FPGA_BOOT_PRIMARY: MIFPGA booted from Primary

2019 Jul  9 19:46:11 switch %CARDCLIENT-5-MOD_BOOT_PRIMARY: Module 1 IOFPGA booted from Primary

2019 Jul  9 19:46:11 switch %CARDCLIENT-5-MOD_BOOT_PRIMARY: Module 1 MIFPGA booted from Primary

Related Documentation

The entire Cisco NX-OS 9000 Series documentation set.

Release Notes

The entire Cisco NX-OS 9000 Series release notes set.

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to nexus9k-docfeedback@cisco.com. We appreciate your feedback.

Legal Information

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: https://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. (1110R)

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.

© 2025 Cisco Systems, Inc. All rights reserved.