BF-Bundle Installation and Upgrade
Important! Make sure to update DOCA on the host side before installing the BF-bundle on the BlueField.
Users have three options for installing or upgrading DOCA on BlueField DPU or SuperNIC:
Method | Option Name | Description |
Installation | This option overwrites the entire boot partition with an Ubuntu 22.04 installation and updates BlueField and NIC firmware | |
Upgrade | This option upgrades DOCA components without overwriting the boot partition. Use this option to preserve configurations or files on BlueField itself | |
Installation | This option overwrites the entire boot partition with an Ubuntu 22.04 installation |
Find the DOCA installation files for BlueField from the NVIDIA DOCA Downloads page.
Make sure to update DOCA on the host side before installing the BF-bundle on the BlueField.
The ATF will not boot 150W BlueField-3 platforms if the ATX +12V power supply is not connected. This requirement ensures the proper operation of the BlueField device. For detailed instructions on connecting the external power supply connector, refer to the NVIDIA BlueField-3 Networking Platform User Guide.
Users can install DOCA on BlueField DPU or SuperNIC by upgrading the full DOCA image on BlueField.
This overwrites the entire boot partition with an Ubuntu 22.04 installation and updates BlueField and NIC firmware.
This installation sets up the OVS bridge.
Upgrading DOCA components on BlueField networking platforms, such as DPUs or SuperNICs, using standard Linux tools will install the new doca-eula
package located at /etc/NVIDIA/doca-license/DOCA-EULA.txt
. By installing this package, you accept the NVIDIA DOCA SDK end-user license agreement.
Option 1 – No Pre-defined Password
To change the default Ubuntu password during the BFB bundle installation, proceed to Option 2.
To install a BFB, use the following command:
host# sudo bfb-install --rshim rshim<N> --bfb <image_path.bfb>
Where:
<N>
– the appropriate RShim device identifier. If you have only one BlueField device, usershim0
.<image_path.bfb>
– Replace this with the path to the BFB image file.
To list the RShim devices present on your system, run the following command:
host# ls -la /dev/ | grep rshim
By default bfb-install
will clear the RShim log in /dev/rshim<N>/misc
and save it as tmp/bfb-install-rshim[N].log
instead. To preserve the RShim log in /dev/rshim<N>/misc
, provide the --keep-log
argument to the bfb-install
command line.
Option 2 – Set Pre-defined Password
Ubuntu users can set a unique password for the ubuntu
user in the bf.cfg
configuration file
, which will be applied automatically at the end of the BlueField BFB bundle installation.
To do this, follow these steps:
Generate the hashed password:
host# openssl passwd -
1
Password: Verifying - Password: $1
$3B0RIrfX$TlHry93NFUJzg3Nya00rE1Add the password hash to the
bf.cfg
configuration file:host# echo ubuntu_PASSWORD=
'$1$3B0RIrfX$TlHry93NFUJzg3Nya00rE1'
> bf.cfgUse the
--config
flag to specify the configuration file when running the installation command:host# sudo bfb-install --rshim rshim<N> --bfb <image_path.bfb> --config bf.cfg
NoteIf
--config
is not used, then upon first login to the BlueField device, users will be prompted to update the defaultubuntu
password.NoteOptionally, to upgrade the BlueField integrated BMC firmware using BFB bundle, please provide the current BMC root credentials in a
bf.cfg
file, as shown in the following:BMC_PASSWORD=
"<root password>"
BMC_USER="root"
BMC_REBOOT="yes"
Unless previously changed, the default BMC root password is
0penBmc
.The following is an example output of Ubuntu-22.04 BFB bundle installation (version may vary in the future):
host# sudo bfb-install --rshim rshim0 --bfb bf-bundle-2.7.0_24.04_ubuntu-22.04_prod.bfb --config bf.cfg Pushing bfb 1.41GiB 0:02:02 [11.7MiB/s] [ <=> ] Collecting BlueField booting status. Press Ctrl+C to stop INFO[PSC]: PSC BL1 START INFO[BL2]: start INFO[BL2]: boot mode (rshim) INFO[BL2]: VDDQ: 1120 mV INFO[BL2]: DDR POST passed INFO[BL2]: UEFI loaded INFO[BL31]: start INFO[BL31]: lifecycle GA Secured INFO[BL31]: VDD: 850 mV INFO[BL31]: runtime INFO[BL31]: MB ping success INFO[UEFI]: eMMC init INFO[UEFI]: eMMC probed INFO[UEFI]: UPVS valid INFO[UEFI]: PMI: updates started INFO[UEFI]: PMI: total updates: 1 INFO[UEFI]: PMI: updates completed, status 0 INFO[UEFI]: PCIe enum start INFO[UEFI]: PCIe enum end INFO[UEFI]: UEFI Secure Boot INFO[UEFI]: PK configured INFO[UEFI]: Redfish enabled INFO[UEFI]: exit Boot Service INFO[MISC]: Found bf.cfg INFO[MISC]: Ubuntu installation started INFO[MISC]: Installing OS image INFO[MISC]: Changing the default password for user ubuntu INFO[MISC]: Ubuntu installation completed INFO[MISC]: Updating NIC firmware... INFO[MISC]: NIC firmware update done INFO[MISC]: Installation finished
To verify that the BlueField device has completed booting, wait 90 seconds after the installation process finishes and run the following command:
host# sudo cat /dev/rshim<N>/misc ... INFO[MISC]: Linux up INFO[MISC]: DPU is ready
Retrieve installed packages and their versions as part of BF-Bundle installation:
Log into BlueField.
Run the following:
bf# sudo bf-info
Example output:
Firmware: - ATF: v2.2(release):4.11.0-31-g3cc9f6506 - UEFI: 4.11.0-44-gb67dfb4a53 - BSP: 4.11.0.13582 - NIC Firmware: 32.45.0350 - BMC Firmware: 25.04-3 - CEC Firmware: 00.02.0195.0000 Drivers: - mlnx-dpdk: 'MLNX_DPDK 22.11.2504.0.2' - Kernel: 5.15.0-1064-bluefield Tools: - MFT: 4.32.0-94 - mstflint: 4.29.0-1 Storage: - mlnx-libsnap 1.6.0-1 - spdk 23.01.5-24 - virtio-net-controller 24.10.15-1 DOCA: - doca-apsh-config 2.9.0064-1 - libdoca-sdk-urom-dev 2.9.0064-1 ... FlexIO: - flexio-samples 24.10.2447 - flexio-sdk 24.10.2447 ... SoC Platform: - mlxbf-gige-modules 1.0-0.kver.6.1.0-11-arm64 - sdhci-of-dwcmshc-modules 1.0-0.kver.6.1.0-11-arm64 ... OFED: rdma-core 2410mlnx54-1.2410051 ucx 1.18.0-1.2410051 ...
To configure the
tmfifo_net0
interface over IPv4 for SSH access to the BlueField Arm OS:host# ifconfig tmfifo_net0
192.168
.100.1
/24
InfoSSH into the BlueField Arm OS with 192.168.100.2 (preconfigured default):
host# ssh ubuntu
@192
.168.100.2
This procedure allows for upgrading DOCA components on BlueField networking platforms (DPUs or SuperNICs) using standard Linux tools (e.g., apt update
and yum update
). It leverages native package manager repositories to update components without requiring a full reinstallation.
While this approach enables updating specific DOCA components, the combinations created by selective updates are not validated by NVIDIA. NVIDIA only validates the full installation of the BF-Bundle package.
Upgrading DOCA components on BlueField networking platforms using standard Linux tools will install the new doca-eula
package located at /etc/NVIDIA/doca-license/DOCA-EULA.txt
. By installing this package, you accept the NVIDIA DOCA SDK end-user license agreement.
This process has the following benefits :
Only updates components that include modifications
Includes upgrade of:
DOCA drivers and libraries
DOCA reference applications
BSP (UEFI/ATF) upgrade while maintaining the configuration
NIC firmware upgrade while maintaining the configuration
BMC components upgrade
Does not:
Impact user binaries
Upgrade non-Ubuntu OS kernels
After completion of BlueField upgrade:
If NIC firmware was not updated, perform BlueField Arm reset (software reset/reboot BlueField )
If NIC firmware was updated, perform firmware reset (
mlxfwreset
) or perform a graceful shutdown and power cycle
DEB-based
Action | Instructions |
Export the desired distribution | Export
|
Add GPG key to APT trusted keyring |
|
Add DOCA online repository |
|
Update index |
|
Choose one of the two options for packages upgrade | Option-1 Upgrade BlueField FW Bundle package ( including ATF-UEFI, NIC firmware, and BMC firmware ):
|
Option-2 System upgrade (install all packages):
| |
Configure BMC parameters | Add the BMC user and password to config file
|
Components activation |
Info
The upgrade process should take up to 20 minutes. |
Apply the new changes, NIC firmware, and UEFI/ATF | For the upgrade to take effect, perform BlueField system reboot. Note
This step triggers immediate reboot of the BlueField Arm cores. |
RPM-based
Action | Instructions |
Export the desired distribution | Export
|
Add DOCA online repository |
A file is created under |
Update index |
|
Choose one of the two options for packages upgrade | Option-1 Upgrade BlueField FW Bundle package ( including ATF-UEFI, NIC firmware, and BMC firmware ):
|
Option-2
| |
Configure BMC parameters | Add the BMC user and password to config file
|
Components activation |
Info
The upgrade process should take up to 20 minutes. |
Apply the new changes, NIC firmware, and UEFI/ATF | For the upgrade to take effect, perform BlueField system reboot. Note
This step triggers immediate reboot of the BlueField Arm cores. |
In order to be able to use DOCA installer, Make sure to update DOCA on the host side 3.0.0 before installing the doca-installer.
DEB-based |
| |
RPM-based |
|
DOCA installer is a utility designed to install and upgrade BFB and BlueField firmware bundle images across multiple DPUs in parallel.
It supports multiple DPU operation modes, including NIC mode, DPU mode, and both modes on the same host. It offers extensive customization through configuration files in INI and YAML formats.
This overwrites the entire boot partition with an Ubuntu 22.04 installation and updates BlueField and NIC firmware.
This installation sets up the OVS bridge.
DOCA Installer Running Modes
DOCA installer supports 3 installation running modes:
Mode | Command |
Global run |
|
Per PSID group |
|
Per RShim device |
|
Where:
-
<N>
– the appropriate RShim device identifier. If your environment has only one BlueField device, use0
. <image_path.bfb>
– Replace this with the path to the BFB image file<PSID>
– the group shared PSID identifierNoteOther cards who do not share this PSID will not be upgraded.
Run DOCA Installer with Configuration File
DOCA installer supports 2 configuration files in the format of either INI or YAML.
To upgrade BMC/CEC/Golden Image version, the BMC_USER
and BMC_PASSWORD
variables must be defined in the bf.cfg
configuration file.
Running DOCA installer with configuration file requires providing -c <path-to-config>
or --config-file <path-to-config>
.
Mode | Command |
Global run |
|
Per PSID group |
|
Per RShim device |
|
Where:
-
<N>
– the appropriate RShim device identifier. If your environment has only one BlueField device, use0
. <image_path.bfb>
– Replace this with the path to the BFB image file<PSID>
– the group shared PSID identifierNoteOther cards who do not share this PSID will not be upgraded.
<path-to-config>
– Path to configuration file (INI or YAML)NoteThe YAML configuration file uses a few key sections to organize settings:
global_configs
– Defines variables that are common to all devices. Under this key, thevariables
sub-key is used to specify shared parameters such asBMC_USER
andBMC_PASSWORD
. These settings apply globally unless overridden by device-specific configurations.rshim
– Contains configuration for individual devices. Within thershim
section, each key (e.g.,rshim1
,rshim2
) represents a specific device's configuration.NoteWhen
rshim<N>
andglobal_configs
share the same configuration, the script prioritizesrshim<X>
settings.variables
– Specifies device-specific configuration parameters (e.g.,UPDATE_DPU_OS
,WITH_NIC_FW_UPDATE
) that control the installation and upgrade process for that devicemethods
– Contains commands or steps (often multi-line shell commands) that are executed to customize the device. YAML anchors (e.g.,&default_post_install
) can be used here to reuse common command blocks across multiple devices.
INI Configuration File Customization
Customization Type | Example |
Customizing a single device | To enable per-device configuration, it is necessary to specify the RSHIM device for each variable or method targets.
|
Customizing all devices | To customize all your devices and they share the same parameters (for those that can be shared), customization can be done as follows:
|
YAML Configuration File Customization
Customization type | Example |
Customizing a single device with no global configs | To enable per-device configuration, it is necessary to specify the RSHIM device for each variable or method targets.
|
Customizing all devices using global configs only | To customize all of your devices and they all shared same parameters (on those who can be shared) customization can be done as follow
|
Customizing all devices using global configs, and specific configs per device |
To share global configurations for multiple devices along with specific device configurations, this can be achieved by providing
|
Advanced example with reusing methods using anchors | The YAML configuration file will also allow users to utilize YAML tools, such as anchors, in order to reuse methods. For example, here we can see the reuse of the
|
Logs and Debuggability
The DOCA installer tool will provide extended logs and enhanced debuggability compared to the existing options available with the bfb-install
tool.
For each execution of the doca-installer
tool, a new directory will be generated at the specified path:
/var/log/doca_installer_logs/doca_installer_<time stamp>
Under the logs directory, you'll find the following:
Full run of the doca installer tool
rshim misc per device
lspci - per device and of the entier system
bfb-install output
mlxconfig
mlxprivhost
mstdump (optional)
flint image retrive (optional)
The following is an example output of Ubuntu-22.04 BFB bundle installation on top of a host with 4 devices (version may vary in the future):
host# doca-installer -b /root/bf-bundle-3.0.0-91_25.04_ubuntu-22.04_prod.bfb -c /root/bf.cfg
╒════════════════╤═══════════╕
│ Service name │ Version │
╞════════════════╪═══════════╡
│ Tool version │ 1.1.5 │
├────────────────┼───────────┤
│ rshim │ 2.2.4 │
├────────────────┼───────────┤
│ mft │ 4.32.0-41 │
├────────────────┼───────────┤
│ python │ 3.9.18 │
╘════════════════╧═══════════╛
Extracting firmware versions from /root/bf-bundle-3.0.0-91_25.04_ubuntu-22.04_prod.bfb
Target Firmware Versions of the provided image:
╒═════════════╤═══════════════════════╤═══════════════════════╕
│ Component │ BlueField-2 │ BlueField-3 │
╞═════════════╪═══════════════════════╪═══════════════════════╡
│ DOCA │ 3.0.0034 │ 3.0.0034 │
├─────────────┼───────────────────────┼───────────────────────┤
│ BSP │ 4.11.0.13582 │ 4.11.0.13582 │
├─────────────┼───────────────────────┼───────────────────────┤
│ ATF │ 4.11.0-31-g3cc9f6506 │ 4.11.0-31-g3cc9f6506 │
├─────────────┼───────────────────────┼───────────────────────┤
│ UEFI │ 4.11.0-44-gb67dfb4a53 │ 4.11.0-44-gb67dfb4a53 │
├─────────────┼───────────────────────┼───────────────────────┤
│ NIC_FW │ 24.45.0326 │ 32.45.0326 │
├─────────────┼───────────────────────┼───────────────────────┤
│ BMC_FW │ 25.04-2 │ 25.04-2 │
├─────────────┼───────────────────────┼───────────────────────┤
│ CEC_FW │ 4.15 │ 00.02.0195.0000 │
├─────────────┼───────────────────────┼───────────────────────┤
│ DPU_GI │ Not Supported │ 4.11.0.13582 │
├─────────────┼───────────────────────┼───────────────────────┤
│ NIC_FW_GI │ Not Supported │ 32_43_1014 │
╘═════════════╧═══════════════════════╧═══════════════════════╛
Bundle install of /root/bf-bundle-3.0.0-91_25.04_ubuntu-22.04_prod.bfb image
Logs will be saved to /var/log/doca_installer_logs/doca_installer_20250401_104535 directory
INFO: Searching for interfering processes: minicom, screen
Available DPUs on host:
4 BF DPUs:
╒═══════════════╤════════════════════╤══════════════╤══════════════╤════════╤══════════════╕
│ PSID │ Part Num │ Serial Num │ PCI Addr │ Mode │ Privileged │
╞═══════════════╪════════════════════╪══════════════╪══════════════╪════════╪══════════════╡
│ MT_0000000884 │ 900-9D3B6-00CV-AA0 │ MT2421601NKM │ 0000:03:00.0 │ NIC │ True │
├───────────────┼────────────────────┼──────────────┼──────────────┼────────┼──────────────┤
│ MT_0000000884 │ 900-9D3B6-00CV-AA0 │ MT2421601NHB │ 0000:27:00.0 │ DPU │ True │
├───────────────┼────────────────────┼──────────────┼──────────────┼────────┼──────────────┤
│ MT_0000000884 │ 900-9D3B6-00CV-AA0 │ MT2421601NHE │ 0000:83:00.0 │ DPU │ True │
├───────────────┼────────────────────┼──────────────┼──────────────┼────────┼──────────────┤
│ MT_0000000884 │ 900-9D3B6-00CV-AA0 │ MT242260008X │ 0000:a3:00.0 │ DPU │ True │
╘═══════════════╧════════════════════╧══════════════╧══════════════╧════════╧══════════════╛
The following DPUs are about to be upgrade:
4 BF DPUs:
╒═══════════════╤════════════════════╤══════════════╤══════════════╤═════════════╤════════╤══════════════╤═══════════════════╤════════════════════╤══════════════════════╤═══════════════════╤═══════════════════╕
│ PSID │ Part Num │ Serial Num │ PCI Addr │ RSHIM Dev │ Mode │ Privileged │ Pre Upgrade ATF │ Pre Upgrade UEFI │ Pre Upgrade NIC-FW │ Pre Upgrade BMC │ Pre Upgrade CEC │
╞═══════════════╪════════════════════╪══════════════╪══════════════╪═════════════╪════════╪══════════════╪═══════════════════╪════════════════════╪══════════════════════╪═══════════════════╪═══════════════════╡
│ MT_0000000884 │ 900-9D3B6-00CV-AA0 │ MT2421601NKM │ 0000:03:00.0 │ rshim0 │ NIC │ True │ 4.9.2-15-g302b394 │ 4.9.2-27-ga30d209 │ 32.45.0256 │ N/A │ N/A │
├───────────────┼────────────────────┼──────────────┼──────────────┼─────────────┼────────┼──────────────┼───────────────────┼────────────────────┼──────────────────────┼───────────────────┼───────────────────┤
│ MT_0000000884 │ 900-9D3B6-00CV-AA0 │ MT2421601NHB │ 0000:27:00.0 │ rshim1 │ DPU │ True │ 4.9.2-15-g302b394 │ 4.9.2-27-ga30d209 │ 32.45.0256 │ N/A │ N/A │
├───────────────┼────────────────────┼──────────────┼──────────────┼─────────────┼────────┼──────────────┼───────────────────┼────────────────────┼──────────────────────┼───────────────────┼───────────────────┤
│ MT_0000000884 │ 900-9D3B6-00CV-AA0 │ MT2421601NHE │ 0000:83:00.0 │ rshim3 │ DPU │ True │ 4.9.2-15-g302b394 │ 4.9.2-27-ga30d209 │ 32.45.0256 │ N/A │ N/A │
├───────────────┼────────────────────┼──────────────┼──────────────┼─────────────┼────────┼──────────────┼───────────────────┼────────────────────┼──────────────────────┼───────────────────┼───────────────────┤
│ MT_0000000884 │ 900-9D3B6-00CV-AA0 │ MT242260008X │ 0000:a3:00.0 │ rshim2 │ DPU │ True │ 4.9.2-15-g302b394 │ 4.9.2-27-ga30d209 │ 32.45.0256 │ N/A │ N/A │
╘═══════════════╧════════════════════╧══════════════╧══════════════╧═════════════╧════════╧══════════════╧═══════════════════╧════════════════════╧══════════════════════╧═══════════════════╧═══════════════════╛
Generated configuration for 0000:03:00.0 at /tmp/rshim0-bf.cfg
Generated configuration for 0000:27:00.0 at /tmp/rshim1-bf.cfg
Generated configuration for 0000:83:00.0 at /tmp/rshim3-bf.cfg
Generated configuration for 0000:a3:00.0 at /tmp/rshim2-bf.cfg
4 BF install DPU(s): 0%| | 0/4 [33:55<?, ?it/s]
1/4 done: Device 0000:83:00.0 is ready
4 BF install DPU(s): 25%|█████████████████████████ | 1/4 [34:58<1:41:49, 2036.58s/it]
2/4 done: Device 0000:27:00.0 is ready
4 BF install DPU(s): 50%|██████████████████████████████████████████████████ | 2/4 [35:32<29:11, 875.71s/it]
3/4 done: Device 0000:a3:00.0 is ready
4 BF install DPU(s): 75%|███████████████████████████████████████████████████████████████████████████ | 3/4 [43:07<08:11, 491.40s/it]
4/4 done: Device 0000:03:00.0 is ready
4 BF install DPU(s): 100%|████████████████████████████████████████████████████████████████████████████████████████████████████| 4/4 [43:10<00:00, 707.23s/it]
Validating new FW on DPUs...
Post-installation verification results:
Verification for device: 0000:27:00.0 (PSID: MT_0000000884)
╒═════════════╤═══════════════════╤═══════════════════════╤═══════════════════╕
│ Component │ Pre Upgrade │ Target │ Post Upgrade │
╞═════════════╪═══════════════════╪═══════════════════════╪═══════════════════╡
│ ATF │ 4.9.2-15-g302b394 │ 4.11.0-31-g3cc9f6506 │ 4.11.0-31-g3cc9f6 │
├─────────────┼───────────────────┼───────────────────────┼───────────────────┤
│ UEFI │ 4.9.2-27-ga30d209 │ 4.11.0-44-gb67dfb4a53 │ 4.11.0-44-gb67dfb │
├─────────────┼───────────────────┼───────────────────────┼───────────────────┤
│ NIC_FW │ 32.45.0256 │ 32.45.0326 │ 32.45.0326 │
├─────────────┼───────────────────┼───────────────────────┼───────────────────┤
│ BMC_FW │ N/A │ 25.04-2 │ 25.04-2 │
╘═════════════╧═══════════════════╧═══════════════════════╧═══════════════════╛
--------------------------------------------------------------------------------
Verification for device: 0000:83:00.0 (PSID: MT_0000000884)
╒═════════════╤═══════════════════╤═══════════════════════╤═══════════════════╕
│ Component │ Pre Upgrade │ Target │ Post Upgrade │
╞═════════════╪═══════════════════╪═══════════════════════╪═══════════════════╡
│ ATF │ 4.9.2-15-g302b394 │ 4.11.0-31-g3cc9f6506 │ 4.11.0-31-g3cc9f6 │
├─────────────┼───────────────────┼───────────────────────┼───────────────────┤
│ UEFI │ 4.9.2-27-ga30d209 │ 4.11.0-44-gb67dfb4a53 │ 4.11.0-44-gb67dfb │
├─────────────┼───────────────────┼───────────────────────┼───────────────────┤
│ NIC_FW │ 32.45.0256 │ 32.45.0326 │ 32.45.0326 │
├─────────────┼───────────────────┼───────────────────────┼───────────────────┤
│ BMC_FW │ N/A │ 25.04-2 │ 25.04-2 │
╘═════════════╧═══════════════════╧═══════════════════════╧═══════════════════╛
--------------------------------------------------------------------------------
Verification for device: 0000:a3:00.0 (PSID: MT_0000000884)
╒═════════════╤═══════════════════╤═══════════════════════╤═══════════════════╕
│ Component │ Pre Upgrade │ Target │ Post Upgrade │
╞═════════════╪═══════════════════╪═══════════════════════╪═══════════════════╡
│ ATF │ 4.9.2-15-g302b394 │ 4.11.0-31-g3cc9f6506 │ 4.11.0-31-g3cc9f6 │
├─────────────┼───────────────────┼───────────────────────┼───────────────────┤
│ UEFI │ 4.9.2-27-ga30d209 │ 4.11.0-44-gb67dfb4a53 │ 4.11.0-44-gb67dfb │
├─────────────┼───────────────────┼───────────────────────┼───────────────────┤
│ NIC_FW │ 32.45.0256 │ 32.45.0326 │ 32.45.0326 │
├─────────────┼───────────────────┼───────────────────────┼───────────────────┤
│ BMC_FW │ N/A │ 25.04-2 │ 25.04-2 │
╘═════════════╧═══════════════════╧═══════════════════════╧═══════════════════╛
--------------------------------------------------------------------------------
Verification for device: 0000:03:00.0 (PSID: MT_0000000884)
╒═════════════╤═══════════════════╤═══════════════════════╤═══════════════════╕
│ Component │ Pre Upgrade │ Target │ Post Upgrade │
╞═════════════╪═══════════════════╪═══════════════════════╪═══════════════════╡
│ ATF │ 4.9.2-15-g302b394 │ 4.11.0-31-g3cc9f6506 │ 4.11.0-31-g3cc9f6 │
├─────────────┼───────────────────┼───────────────────────┼───────────────────┤
│ UEFI │ 4.9.2-27-ga30d209 │ 4.11.0-44-gb67dfb4a53 │ 4.11.0-44-gb67dfb │
├─────────────┼───────────────────┼───────────────────────┼───────────────────┤
│ NIC_FW │ 32.45.0256 │ 32.45.0326 │ 32.45.0326 │
├─────────────┼───────────────────┼───────────────────────┼───────────────────┤
│ BMC_FW │ N/A │ 25.04-2 │ 25.04-2 │
╘═════════════╧═══════════════════╧═══════════════════════╧═══════════════════╛
================================================================================
UPGRADE SUMMARY REPORT
================================================================================
The following devices passed upgrade successfully:
1. 0000:27:00.0 (PSID: MT_0000000884)
2. 0000:83:00.0 (PSID: MT_0000000884)
3. 0000:a3:00.0 (PSID: MT_0000000884)
4. 0000:03:00.0 (PSID: MT_0000000884)
The following devices did not pass upgrades successfully:
None
Important! The script will try to load the new NIC firmware automatically, but in case it will fail to do so, it will notify the user with the following message:INFO: At least one device requires a host power cycle for new NIC Firmware to be loaded.
Important! In case the script will find that one or more of the devices did not had BMC_REBOOT set to 'yes' as part of the configuration file, it will notify the user with the following message:WARNING: BMC_REBOOT is not configured for all devices or is not set to 'yes'.
BMC firmware updates will only take effect after a BMC reboot.
Supported DOCA-Host OS for doca-installer
The following OSs on the host machine are supported for doca-installer
:
Operating System | Architecture |
debian10.13 | x86_64 |
aarch64 | |
debian12.1 | x86_64 |
aarch64 | |
debian12.5 | x86_64 |
aarch64 | |
openeuler24.03 | x86_64 |
aarch64 | |
ol8.4 | x86_64 |
ol8.6 | x86_64 |
ol8.7 | x86_64 |
ol8.8 | x86_64 |
ol8.10 | x86_64 |
ol9.1 | x86_64 |
ol9.2 | x86_64 |
ol9.4 | aarch64 |
rhel8.2 | x86_64 |
aarch64 | |
rhel8.4 | x86_64 |
aarch64 | |
rhel8.6 | x86_64 |
ppc64le | |
aarch64 | |
rhel8.8 | x86_64 |
ppc64le | |
aarch64 | |
rhel8.9 | x86_64 |
ppc64le | |
aarch64 | |
rhel8.10 | x86_64 |
ppc64le | |
aarch64 | |
rhel9.0 | x86_64 |
ppc64le | |
aarch64 | |
rhel9.2 | x86_64 |
ppc64le | |
aarch64 | |
rhel9.4 | x86_64 |
ppc64le | |
aarch64 | |
rhel9.5 | x86_64 |
aarch64 | |
ppc64le | |
rhel9.6 | x86_64 |
aarch64 | |
ppc64le | |
ubuntu20.04 | x86_64 |
ppc64le | |
aarch64 | |
ubuntu22.04 | x86_64 |
ppc64le | |
aarch64 | |
ubuntu24.04 | x86_64 |
aarch64 | |
ppc64le | |
ubuntu24.10 | x86_64 |
ubuntu25.04 | x86_64 |
aarch64 | |
azurelinux3.0 | x86_64 |
aarch64 |
Users wishing to build their own customized BlueField OS image can use the BFB build environment. For more details, refer to the bfb-build project in this GitHub webpage.
To boot a customized BlueField OS image on a UEFI secure-boot-enabled BlueField (the default secure boot setting), the following conditions must be met:
The OS image must be signed with a key already present in the UEFI DB (e.g., the Microsoft key)
If the above is not possible, UEFI secure boot must be disabled to allow booting of an unsigned or differently signed image
For detailed instructions on managing UEFI secure boot, refer to the "Secure Boot" page in the BlueField Platform SW Documentation.