Upgrading System Firmware

NVOS software package version has a default switch firmware version. When updating the operating system software to a new version, an automatic firmware update process will be attempted by NVOS. This process is described below.

To perform an automatic firmware update by the OS for a different switch firmware version without changing the OS version, import and install the firmware package as described below. The OS sets it as the new default firmware and performs the firmware update automatically.

Default Firmware Change

1. Display the firmware that is currently available.

   Copy

   Copied!

               
   
               
   admin@nvos:~$ nv show platform firmware ASIC
                    operational                applied
   ---------------  -------------------------  -------
   part-number      920-9K36F-00MV-JS0_IPN_Ax
   actual-firmware  35.2014.1482
   auto-update      enabled                    enabled
   fw-source        default                    default
           

2. Import the firmware image (.mfa file) to the switch.

   Copy

   Copied!

               
   
               
   admin@nvos:~$ nv action fetch platform firmware ASIC /path/to/fw-image.mfa
           

   Alternatively, you can upload the FW file from the host to the switch:

   Note

   The firmware file must be copied to the predefined directory: "/host/fw-images/asic"

   Copy

   Copied!

               
   
               
   user@host:~$ scp <path-to-fw-file> <switch-admin-username>@<switch-ip-address>:/host/fw-images/asic/<desired-name>.mfa
           

3. Configure default firmware source from user.

   Copy

   Copied!

               
   
               
   admin@nvos:~$ nv set platform firmware ASIC fw-source custom
           

4. Display system firmware component information.

   Copy

   Copied!

               
   
               
   admin@nvos:~$ nv show platform firmware ASIC
                    operational                applied
   ---------------  -------------------------  -------
   part-number      920-9K36F-00MV-JS0_IPN_Ax
   actual-firmware  35.2014.1482
   auto-update      enabled                    enabled
   fw-source        default                    default
           

5. Apply the configuration

   Copy

   Copied!

               
   
               
   admin@nvos:~$ nv config apply
           

6. Save the configuration.

   Copy

   Copied!

               
   
               
   admin@nvos:~$ nv config save
           

7. Install the firmware image.

   Copy

   Copied!

               
   
               
   admin@nvos:~$ nv action install platform firmware ASIC files fw-image.mfa
   The operation will initiate a component firmware update.
   Type [y] to install the firmware and reboot afterwards.
   Type [N] to install the firmware without reboot.
    
   Do you want to reboot? [y/N]
           

8. Press 'Y' will cause system reboot to install and activate firmware.

9. Press 'N' requires manual reboot from user later on.

   Copy

   Copied!

               
   
               
   admin@nvos:~$ nv action reboot system
           

This section provides step-by-step instructions to manually check and update software and firmware on GB200-NVL NVLink switch tray to ensure the system is up to date with the latest software and firmware versions.

References

Bundles content and upgrade sequence

Bundles List

Upgrade Sequence

1. BMC

2. FPGA

3. ERoT

4. CPLD

5. BIOS

6. NVOS

Component Image Update Using NVOS CLI

Firmware updates can be done by NVOS CLI commands. CLI commands are blocking, meaning each command must be finished before another one can be.

There are two stages to upgrade each component:

1. Fetching a file from the unpacked bundle.

   Copy

   Copied!

               
   
               
   admin@nvos:~$ nv action fetch platform firmware <component-id> <remote-url>
           

   For details, see nv action fetch platform firmware.

2. Installing a component:

   Copy

   Copied!

               
   
               
   admin@nvos:~$ nv action install platform firmware <component-id> files <file-name>
           

   For details, see nv action install platform firmware files.

To save time, it it recommended to update one-by-one component and then to choose a power cycle.

1. Power cycle should be triggered if it was chosen after install command but if manual power cycle required, run the following:

   Copy

   Copied!

               
   
               
   admin@nvos:~$ nv action power-cycle system
           

2. To verify firmware versions after power cycle, run the following:

   For details, see nv show platform firmware.

Transceiver Firmware Upgrade

Firmware updates can be done by NVOS CLI commands. CLI commands are blocking, meaning each command must be finished before another one can be.

There are two stages to upgrade each component:

1. Fetching a file from the unpacked bundle.

   Copy

   Copied!

               
   
               
   admin@nvos:~$ nv action fetch platform firmware transceiver <file-path>
           

   For details, see nv action fetch platform firmware.

2. Installing transceiver firmware.

   Copy

   Copied!

               
   
               
   admin@nvos:~$ nv action install platform transceiver <transceiver-id> firmware files <file-name>
           

   For details, see nv action install platform transceiver firmware files.

In order to activate the transceiver firmware, NVOS will reset the transceiver as part of the install action.

To verify firmware version, run the following:

            

            
admin@nvos:~$ nv show platform transceiver <transceiver-id> firmware
        

For details, see nv show platform transceiver firmware.

Component Image Update Using RestAPI

RestAPI can be used from remote server to perform operations on the switch.

RestAPI is not blocking, meaning command can be sent before the previous finished. To deal with this nature, each command returns Task ID, use the Task ID to query for the result between the commands. State of “action_success” means the operation ended successfully.

Upgrades consist of fetch, install, and power cycle at the end of the entire process.

REST API Commands

Query command, should be executed between commands:

            

            
admin@nvos:~$ curl -k --user <nvos-user>:<nvos-password> --request GET 'https://<switch-ip>/nvue_v1/action/<task-id>'
        

1. Fetching component image file:

   Copy

   Copied!

               
   
               
   admin@nvos:~$ curl -k --user <nvos-user>:<nvos-password> --request POST 'https://<switch-ip>/nvue_v1/platform/firmware/<component>' -H 'Content-Type: application/json' -d '{"@fetch": {"state": "start", "parameters": {"remote-url": "scp://<server-user>:<<server-password> >@<PATH_TO_FILE>"}}}'
           

2. Install the component file:

   Copy

   Copied!

               
   
               
   admin@nvos:~$ curl -k --user <nvos-user>:<nvos-password> --request POST 'https://<switch-ip>/nvue_v1/platform/firmware/<component>/files/</<file-name>' -H 'Content-Type: application/json' -d '{"@install": {"state": "start", "parameters": {"force": false}}}'
           

3. Power cycle:

   Copy

   Copied!

               
   
               
   admin@nvos:~$ curl -k --user <nvos-user>:<nvos-password>--request POST 'https://<switch-ip>/nvue_v1/system' -H 'Content-Type: application/json' -d '{"@power-cycle": {"state": "start", "parameters": {"force": true}}}'
           

4. After power cycle, check firmware version:

   Copy

   Copied!

               
   
               
   admin@nvos:~$ curl -k --user <nvos-user>:<nvos-password> --request GET 'https://<nvos-ip>/nvue_v1/platform/firmware'
           

Error Status Catalog

Use the table below to identify the errors and their meaning.

Bundles List