NVIDIA DOCA Installation Guide for Linux
This guide details the necessary steps to set up NVIDIA DOCA in your Linux environment.
Installation of the NVIDIA® BlueField® networking platform (DPU or SuperNIC) software requires following the following step-by-step procedure.
Supported Platforms
Supported BlueField Platforms
The following NVIDIA® BlueField® Platforms are supported with DOCA:
NVIDIA SKU |
Legacy OPN |
PSID |
Description |
900-9D3B6-00CV-AA0 |
N/A |
MT_0000000884 |
BlueField-3 B3220 P-Series FHHL DPU; 200GbE (default mode) / NDR200 IB; Dual-port QSFP112; PCIe Gen5.0 x16 with x16 PCIe extension option; 16 Arm cores; 32GB on-board DDR; integrated BMC; Crypto Enabled |
900-9D3B6-00SV-AA0 |
N/A |
MT_0000000965 |
BlueField-3 B3220 P-Series FHHL DPU; 200GbE (default mode) / NDR200 IB; Dual-port QSFP112; PCIe Gen5.0 x16 with x16 PCIe extension option; 16 Arm cores; 32GB on-board DDR; integrated BMC; Crypto Disabled |
900-9D3B6-00CC-AA0 |
N/A |
MT_0000001024 |
BlueField-3 B3210 P-Series FHHL DPU; 100GbE (default mode) / HDR100 IB; Dual-port QSFP112; PCIe Gen5.0 x16 with x16 PCIe extension option; 16 Arm cores; 32GB on-board DDR; integrated BMC; Crypto Enabled |
900-9D3B6-00SC-AA0 |
N/A |
MT_0000001025 |
BlueField-3 B3210 P-Series FHHL DPU; 100GbE (default mode) / HDR100 IB; Dual-port QSFP112; PCIe Gen5.0 x16 with x16 PCIe extension option; 16 Arm cores; 32GB on-board DDR; integrated BMC; Crypto Disabled |
900-9D219-0086-ST1 |
MBF2M516A-CECOT |
MT_0000000375 |
BlueField-2 E-Series DPU 100GbE Dual-Port QSFP56; PCIe Gen4 x16; Crypto and Secure Boot Enabled; 16GB on-board DDR; 1GbE OOB management; FHHL |
900-9D219-0086-ST0 |
MBF2M516A-EECOT |
MT_0000000376 |
BlueField-2 E-Series DPU 100GbE/EDR/HDR100 VPI Dual-Port QSFP56; PCIe Gen4 x16; Crypto and Secure Boot Enabled; 16GB on-board DDR; 1GbE OOB management; FHHL |
900-9D219-0056-ST1 |
MBF2M516A-EENOT |
MT_0000000377 |
BlueField-2 E-Series DPU 100GbE/EDR/HDR100 VPI Dual-Port QSFP56; PCIe Gen4 x16; Crypto Disabled; 16GB on-board DDR; 1GbE OOB management; FHHL |
900-9D206-0053-SQ0 |
MBF2H332A-AENOT |
MT_0000000539 |
BlueField-2 P-Series DPU 25GbE Dual-Port SFP56; PCIe Gen4 x8; Crypto Disabled; 16GB on-board DDR; 1GbE OOB management; HHHL |
900-9D206-0063-ST2 |
MBF2H332A-AEEOT |
MT_0000000540 |
BlueField-2 P-Series DPU 25GbE Dual-Port SFP56; PCIe Gen4 x8; Crypto Enabled; 16GB on-board DDR; 1GbE OOB management; HHHL |
900-9D206-0083-ST3 |
MBF2H332A-AECOT |
MT_0000000541 |
BlueField-2 P-Series DPU 25GbE Dual-Port SFP56; PCIe Gen4 x8; Crypto and Secure Boot Enabled; 16GB on-board DDR; 1GbE OOB management; HHHL |
900-9D206-0083-ST1 |
MBF2H322A-AECOT |
MT_0000000542 |
BlueField-2 P-Series DPU 25GbE Dual-Port SFP56; PCIe Gen4 x8; Crypto and Secure Boot Enabled; 8GB on-board DDR; 1GbE OOB management; HHHL |
900-9D206-0063-ST1 |
MBF2H322A-AEEOT |
MT_0000000543 |
BlueField-2 P-Series DPU 25GbE Dual-Port SFP56; PCIe Gen4 x8; Crypto Enabled; 8GB on-board DDR; 1GbE OOB management; HHHL |
900-9D219-0066-ST0 |
MBF2M516A-EEEOT |
MT_0000000559 |
BlueField-2 E-Series DPU 100GbE/EDR/HDR100 VPI Dual-Port QSFP56; PCIe Gen4 x16; Crypto Enabled; 16GB on-board DDR; 1GbE OOB management; FHHL |
900-9D219-0056-SN1 |
MBF2M516A-CENOT |
MT_0000000560 |
BlueField-2 E-Series DPU 100GbE Dual-Port QSFP56; PCIe Gen4 x16; Crypto Disabled; 16GB on-board DDR; 1GbE OOB management; FHHL |
900-9D219-0066-ST2 |
MBF2M516A-CEEOT |
MT_0000000561 |
BlueField-2 E-Series DPU 100GbE Dual-Port QSFP56; PCIe Gen4 x16; Crypto Enabled; 16GB on-board DDR; 1GbE OOB management; FHHL |
900-9D219-0006-ST0 |
MBF2H516A-CEEOT |
MT_0000000702 |
BlueField-2 DPU 100GbE Dual-Port QSFP56; PCIe Gen4 x16; Crypto; 16GB on-board DDR; 1GbE OOB management; FHHL |
900-9D219-0056-ST2 |
MBF2H516A-CENOT |
MT_0000000703 |
BlueField-2 DPU 100GbE Dual-Port QSFP56; PCIe Gen4 x16; Crypto Disabled; 16GB on-board DDR; 1GbE OOB management; FHHL |
900-9D219-0066-ST3 |
MBF2H516A-EEEOT |
MT_0000000704 |
BlueField-2 DPU 100GbE/EDR/HDR100 VPI Dual-Port QSFP56; PCIe Gen4 x16; Crypto Enabled; 16GB on-board DDR; 1GbE OOB management; FHHL |
900-9D219-0056-SQ0 |
MBF2H516A-EENOT |
MT_0000000705 |
BlueField-2 DPU 100GbE/EDR/HDR100 VPI Dual-Port QSFP56; PCIe Gen4 x16; Crypto Disabled; 16GB on-board DDR; 1GbE OOB management; FHHL |
900-9D250-0038-ST1 |
MBF2M345A-HESOT |
MT_0000000715 |
BlueField-2 E-Series DPU; 200GbE/HDR single-port QSFP56; PCIe Gen4 x16; Secure Boot Enabled; Crypto Disabled; 16GB on-board DDR; 1GbE OOB management; HHHL |
900-9D250-0048-ST1 |
MBF2M345A-HECOT |
MT_0000000716 |
BlueField-2 E-Series DPU; 200GbE/HDR single-port QSFP56; PCIe Gen4 x16; Secure Boot Enabled; Crypto Enabled; 16GB on-board DDR; 1GbE OOB management; HHHL |
900-9D218-0073-ST1 |
MBF2H512C-AESOT |
MT_0000000723 |
BlueField-2 P-Series DPU 25GbE Dual-Port SFP56; integrated BMC; PCIe Gen4 x8; Secure Boot Enabled; Crypto Disabled; 16GB on-board DDR; 1GbE OOB management; FHHL |
900-9D218-0083-ST2 |
MBF2H512C-AECOT |
MT_0000000724 |
BlueField-2 P-Series DPU 25GbE Dual-Port SFP56; integrated BMC; PCIe Gen4 x8; Secure Boot Enabled; Crypto Enabled; 16GB on-board DDR; 1GbE OOB management; FHHL |
900-9D208-0086-ST4 |
MBF2M516C-EECOT |
MT_0000000728 |
BlueField-2 E-Series DPU 100GbE/EDR/HDR100 VPI Dual-Port QSFP56; integrated BMC; PCIe Gen4 x16; Secure Boot Enabled; Crypto Enabled; 16GB on-board DDR; 1GbE OOB management; Tall Bracket; FHHL |
900-9D208-0086-SQ0 |
MBF2H516C-CECOT |
MT_0000000729 |
BlueField-2 P-Series DPU 100GbE Dual-Port QSFP56; integrated BMC; PCIe Gen4 x16; Secure Boot Enabled; Crypto Enabled; 16GB on-board DDR; 1GbE OOB management; Tall Bracket; FHHL |
900-9D208-0076-ST5 |
MBF2M516C-CESOT |
MT_0000000731 |
BlueField-2 E-Series DPU 100GbE Dual-Port QSFP56; integrated BMC; PCIe Gen4 x16; Secure Boot Enabled; Crypto Disabled; 16GB on-board DDR; 1GbE OOB management; Tall Bracket; FHHL |
900-9D208-0076-ST6 |
MBF2M516C-EESOT |
MT_0000000732 |
BlueField-2 E-Series DPU 100GbE/EDR/HDR100 VPI Dual-Port QSFP56; integrated BMC; PCIe Gen4 x16; Secure Boot Enabled; Crypto Disabled; 16GB on-board DDR; 1GbE OOB management; Tall Bracket; FHHL |
900-9D208-0086-ST3 |
MBF2M516C-CECOT |
MT_0000000733 |
BlueField-2 E-Series DPU 100GbE Dual-Port QSFP56; integrated BMC; PCIe Gen4 x16; Secure Boot Enabled; Crypto Enabled; 16GB on-board DDR; 1GbE OOB management; Tall Bracket; FHHL |
900-9D208-0076-ST2 |
MBF2H516C-EESOT |
MT_0000000737 |
BlueField-2 P-Series DPU 100GbE/EDR/HDR100 VPI Dual-Port QSFP56; integrated BMC; PCIe Gen4 x16; Secure Boot Enabled; Crypto Disabled; 16GB on-board DDR; 1GbE OOB management; Tall Bracket; FHHL |
900-9D208-0076-ST1 |
MBF2H516C-CESOT |
MT_0000000738 |
BlueField-2 P-Series DPU 100GbE Dual-Port QSFP56; integrated BMC; PCIe Gen4 x16; Secure Boot Enabled; Crypto Disabled; 16GB on-board DDR; 1GbE OOB management; Tall Bracket; FHHL |
900-9D218-0083-ST4 |
MBF2H532C-AECOT |
MT_0000000765 |
BlueField-2 P-Series DPU 25GbE Dual-Port SFP56; integrated BMC; PCIe Gen4 x8; Secure Boot Enabled; Crypto Enabled; 32GB on-board DDR; 1GbE OOB management; FHHL |
900-9D218-0073-ST0 |
MBF2H532C-AESOT |
MT_0000000766 |
BlueField-2 P-Series DPU 25GbE Dual-Port SFP56; integrated BMC; PCIe Gen4 x8; Secure Boot Enabled; Crypto Disabled; 32GB on-board DDR; 1GbE OOB management; FHHL |
900-9D208-0076-ST3 |
MBF2H536C-CESOT |
MT_0000000767 |
BlueField-2 P-Series DPU 100GbE Dual-Port QSFP56; integrated BMC; PCIe Gen4 x16; Secure Boot Enabled; Crypto Disabled; 32GB on-board DDR; 1GbE OOB management; FHHL |
900-9D208-0086-ST2 |
MBF2H536C-CECOT |
MT_0000000768 |
BlueField-2 P-Series DPU 100GbE Dual-Port QSFP56; integrated BMC; PCIe Gen4 x16; Secure Boot Enabled; Crypto Enabled; 32GB on-board DDR; 1GbE OOB management; FHHL |
900-9D218-0073-ST4 |
MBF2H512C-AEUOT |
MT_0000000972 |
BlueField-2 P-Series DPU 25GbE Dual-Port SFP56; integrated BMC; PCIe Gen4 x8; Secure Boot Enabled with UEFI disabled; Crypto Disabled; 16GB on-board DDR; 1GbE OOB management |
900-9D208-0076-STA |
MBF2H516C-CEUOT |
MT_0000000973 |
BlueField-2 P-Series DPU 100GbE Dual-Port QSFP56; integrated BMC; PCIe Gen4 x16; Secure Boot Enabled with UEFI disabled; Crypto Disabled; 16GB on-board DDR; 1GbE OOB management |
900-9D208-0076-STB |
MBF2H536C-CEUOT |
MT_0000001008 |
BlueField-2 P-Series DPU 100GbE Dual-Port QSFP56, integrated BMC, PCIe Gen4 x16, Secure Boot Enabled with UEFI Disabled, Crypto Disabled, 32GB on-board DDR, 1GbE OOB management, Tall Bracket, FHHL |
P1004/699210040230 |
N/A |
NVD0000000015 |
BlueField-2 A30X, P1004 SKU 205, Generic, GA100, 24GB HBM2e, PCIe passive Dual Slot 230W GEN4, DPU Crypto ON W/ Bkt, 1 Dongle, Black, HF, VCPD |
P4028/699140280000 |
N/A |
NVD0000000020 |
ZAM / NAS |
Supported ConnectX NICs
The NVIDIA® ConnectX® NICs supported with DOCA-Host can be found in: NVIDIA DOCA Profiles
Hardware Prerequisites
For BlueField Platform users, this guide assumes that a BlueField device has been installed in a server according to the instructions detailed in your DPU's hardware user guide .
DOCA Packages
Device |
Component |
Version |
Description |
Host |
DOCA Devel |
2.7.0 |
Software development kit package and tools for developing host software |
DOCA Runtime |
2.7.0 |
Runtime libraries and tools required to run DOCA-based software applications on host |
|
DOCA Extra |
2.7.0 |
Contains helper scripts (doca-info, doca-kernel-support) |
|
DOCA OFED |
2.7.0 |
Software stack which operates across all NVIDIA network adapter solutions |
|
Arm emulated (QEMU) development container |
4.7.0 |
Linux-based BlueField Arm emulated container for developers |
|
Target BlueField DPU (Arm) |
BlueField BSP |
4.7.0 |
BlueField image and firmware |
DOCA SDK |
2.7.0 |
Software development kit packages and tools for developing Arm software |
|
DOCA Runtime |
2.7.0 |
Runtime libraries and tools required to run DOCA-based software applications on Arm |
Supported Host OS per DOCA-Host Installation Profile
The default operating system included with the BlueField Bundle (for DPU and SuperNIC) is Ubuntu 22.04.
The supported operating systems on the host machine per DOCA-Host installation profile are the following:
Only the following generic kernel versions are supported for DOCA local repo package for host installation.
OS |
OS Version |
Default Kernel Version |
Arch |
DOCA Profile |
||
doca-all |
doca-networking |
doca-ofed |
||||
Alinux |
3.2 |
5.10.134-13.al8.x86_64 |
x86 |
✔ |
✔ |
✔ |
Anolis |
8.6 |
5.10.134+ |
aarch64 |
✔ |
||
x86 |
✔ |
|||||
BCLinux |
21.10SP2 |
4.19.90-2107.6.0.0098.oe1.bclinux.aarch64 |
aarch64 |
✔ |
||
4.19.90-2107.6.0.0100.oe1.bclinux.x86_64 |
x86 |
✔ |
||||
CTYunOS |
2.0 |
4.19.90-2102.2.0.0062.ctl2.aarch64 |
aarch64 |
✔ |
||
4.19.90-2102.2.0.0062.ctl2.x86_64 |
x86 |
✔ |
||||
3.0 (23.01) |
5.10.0-136.12.0.86.ctl3.aarch64 |
aarch64 |
✔ |
✔ |
✔ |
|
5.10.0-136.12.0.86.ctl3.x86_64 |
x86 |
✔ |
✔ |
✔ |
||
Debian |
10.13 |
4.19.0-21-arm64 |
aarch64 |
✔ |
||
4.19.0-21-amd64 |
x86 |
✔ |
||||
10.8 |
4.19.0-14-arm64 |
aarch64 |
✔ |
|||
4.19.0-14-amd64 |
x86 |
✔ |
✔ |
✔ |
||
10.9 |
4.19.0-16-amd64 |
x86 |
✔ |
|||
11.3 |
5.10.0-13-arm64 |
aarch64 |
✔ |
|||
5.10.0-13-amd64 |
x86 |
✔ |
||||
12.1 |
6.1.0-10-arm64 |
aarch64 |
✔ |
|||
6.1.0-10-amd64 |
x86 |
✔ |
||||
EulerOS |
2.0sp11 |
5.10.0-60.18.0.50.h323.eulerosv2r11.aarch64 |
aarch64 |
✔ |
||
5.10.0-60.18.0.50.h323.eulerosv2r11.x86_64 |
x86 |
✔ |
||||
2.0sp12 |
5.10.0-136.12.0.86.h1032.eulerosv2r12.aarch64 |
aarch64 |
✔ |
|||
5.10.0-136.12.0.86.h1032.eulerosv2r12.x86_64 |
x86 |
✔ |
||||
Kylin |
10sp2 |
4.19.90-24.4.v2101.ky10.aarch64 |
aarch64 |
✔ |
||
4.19.90-24.4.v2101.ky10.x86_64 |
x86 |
✔ |
||||
10sp3 |
4.19.90-52.22.v2207.ky10.aarch64 |
aarch64 |
✔ |
|||
4.19.90-52.22.v2207.ky10.x86_64 |
x86 |
✔ |
||||
Mariner |
2.0 |
5.15.118.1-1.cm2.x86_64 |
x86 |
✔ |
||
Oracle Linux |
7.9 |
5.4.17-2011.6.2.el7uek.x86_64 |
x86 |
✔ |
||
8.4 |
5.4.17-2102.201.3.el8uek.x86_64 |
x86 |
✔ |
|||
8.6 |
5.4.17-2136.307.3.1.el8uek.x86_64 |
x86 |
✔ |
|||
8.7 |
5.15.0-3.60.5.1.el8uek.x86_64 |
x86 |
✔ |
✔ |
✔ |
|
8.8 |
5.15.0-101.103.2.1.el8uek.x86_64 |
x86 |
✔ |
|||
9.1 |
5.15.0-3.60.5.1.el9uek.x86_64 |
x86 |
✔ |
|||
9.2 |
5.15.0-101.103.2.1.el9uek.x86_64 |
x86 |
✔ |
|||
openEuler |
20.03sp3 |
4.19.90-2112.8.0.0131.oe1.aarch64 |
aarch64 |
✔ |
||
4.19.90-2112.8.0.0131.oe1.x86_64 |
x86 |
✔ |
||||
22.03 |
5.10.0-60.18.0.50.oe2203.aarch64 |
aarch64 |
✔ |
|||
5.10.0-60.18.0.50.oe2203.x86_64 |
x86 |
✔ |
||||
RHEL/CentOS |
8.0 |
4.18.0-80.el8.aarch64 |
aarch64 |
✔ |
||
4.18.0-80.el8.x86_64 |
x86 |
✔ |
||||
8.1 |
4.18.0-147.el8.aarch64 |
aarch64 |
✔ |
|||
4.18.0-147.el8.x86_64 |
x86 |
✔ |
||||
8.2 |
4.18.0-193.el8.aarch64 |
aarch64 |
✔ |
|||
4.18.0-193.el8.x86_64 |
x86 |
✔ |
✔ |
✔ |
||
8.3 |
4.18.0-240.el8.aarch64 |
aarch64 |
✔ |
|||
4.18.0-240.el8.x86_64 |
x86 |
✔ |
||||
8.4 |
4.18.0-305.el8.aarch64 |
aarch64 |
✔ |
|||
4.18.0-305.el8.x86_64 |
x86 |
✔ |
||||
RHEL/Rocky |
8.5 |
4.18.0-348.el8.aarch64 |
aarch64 |
✔ |
||
4.18.0-348.el8.x86_64 |
x86 |
✔ |
||||
8.6 |
4.18.0-372.41.1.el8_6.aarch64 |
aarch64 |
✔ |
|||
4.18.0-372.41.1.el8_6.x86_64 |
x86 |
✔ |
✔ |
✔ |
||
8.7 |
4.18.0-425.14.1.el8_7.aarch64 |
aarch64 |
✔ |
|||
4.18.0-425.14.1.el8_7.x86_64 |
x86 |
✔ |
||||
8.8 |
4.18.0-477.10.1.el8_8.aarch64 |
aarch64 |
✔ |
✔ |
✔ |
|
4.18.0-477.10.1.el8_8.x86_64 |
x86 |
✔ |
✔ |
✔ |
||
8.9 |
4.18.0-513.5.1.el8_9.aarch64 |
aarch64 |
✔ |
✔ |
✔ |
|
4.18.0-513.5.1.el8_9.x86_64 |
x86 |
✔ |
✔ |
✔ |
||
9.0 |
5.14.0-70.46.1.el9_0.aarch64 |
aarch64 |
✔ |
|||
5.14.0-70.46.1.el9_0.x86_64 |
x86 |
✔ |
||||
9.1 |
5.14.0-162.19.1.el9_1.aarch64 |
aarch64 |
✔ |
|||
5.14.0-162.19.1.el9_1.x86_64 |
x86 |
✔ |
✔ |
✔ |
||
9.2 |
5.14.0-284.11.1.el9_2.aarch64 |
aarch64 |
✔ |
|||
5.14.0-284.11.1.el9_2.x86_64 |
x86 |
✔ |
||||
9.3 |
5.14.0-362.8.1.el9_3.aarch64 |
aarch64 |
✔ |
|||
5.14.0-362.8.1.el9_3.x86_64 |
x86 |
✔ |
||||
SLES |
15sp2 |
5.3.18-22-default |
aarch64 |
✔ |
||
x86 |
✔ |
|||||
15sp3 |
5.3.18-57-default |
aarch64 |
✔ |
|||
x86 |
✔ |
|||||
15sp4 |
5.14.21-150400.22-default |
aarch64 |
✔ |
|||
x86 |
✔ |
|||||
15sp5 |
5.14.21-150500.53-default |
aarch64 |
✔ |
|||
x86 |
✔ |
|||||
TKLinux |
3.3 |
5.4.119-19.0009.39 |
aarch64 |
✔ |
||
5.4.119-19.0009.39 |
x86 |
✔ |
||||
Ubuntu |
20.04 |
5.4.0-26-generic |
aarch64 |
✔ |
||
x86 |
✔ |
✔ |
✔ |
|||
22.04 |
5.15.0-25-generic |
aarch64 |
✔ |
✔ |
✔ |
|
x86 |
✔ |
✔ |
✔ |
|||
24.04 |
6.8.0-31-generic |
aarch64 |
✔ |
|||
x86 |
✔ |
|||||
UOS |
20.1060a |
5.10.0-46.uelc20.aarch64 |
aarch64 |
✔ |
||
5.10.0-46.uelc20.x86_64 |
x86 |
✔ |
||||
20.1060e |
5.10.0-46.uel20.aarch64 |
aarch64 |
✔ |
|||
5.10.0-46.uel20.x86_64 |
x86 |
✔ |
||||
XenServer |
8.2 |
4.19.0+1 |
x86 |
✔ |
This guide provides the minimal instructions for setting up DOCA on a standard system.
Make sure to follow the instructions in this section sequentially. Make sure to update DOCA on the host side first before installing the BFB Bundle on the BlueField.
Installation Files
Device |
Component |
OS |
Arch |
Link |
Host |
These files contain the following components suitable for their respective OS version.
|
Alinux 3.2 |
x86 |
|
Anolis |
aarch64 |
|||
x86 |
||||
BCLinux 21.10 SP2 |
aarch64 |
|||
x86 |
||||
CTyunOS 2.0 |
aarch64 |
|||
x86 |
||||
CTyunOS 23.01 |
aarch64 |
|||
x86 |
||||
Debian 10.13 |
aarch64 |
|||
x86 |
||||
Debian 10.8 |
aarch64 |
|||
x86 |
||||
Debian 10.9 |
x86 |
|||
Debian 11.3 |
aarch64 |
|||
x86 |
||||
Debian 12.1 |
aarch64 |
|||
x86 |
||||
EulerOS 20 SP11 |
aarch64 |
|||
x86 |
||||
EulerOS 20 SP12 |
aarch64 |
|||
x86 |
||||
Kylin 1.0 SP2 |
aarch64 |
|||
x86 |
||||
Kylin 1.0 SP3 |
aarch64 |
|||
x86 |
||||
Mariner 2.0 |
x86 |
|||
Oracle Linux 7.9 |
x86 |
|||
Oracle Linux 8.4 |
x86 |
|||
Oracle Linux 8.6 |
x86 |
|||
Oracle Linux 8.7 |
x86 |
|||
Oracle Linux 8.8 |
x86 |
|||
Oracle Linux 9.0 |
x86 |
|||
Oracle Linux 9.1 |
x86 |
|||
Oracle Linux 9.2 |
x86 |
|||
openEuler 20.03 SP3 |
aarch64 |
|||
x86 |
||||
openEuler 22.03 |
aarch64 |
|||
x86 |
||||
RHEL/CentOS 8.0 |
aarch64 |
|||
x86 |
||||
RHEL/CentOS 8.2 |
aarch64 |
|||
x86 |
||||
RHEL/CentOS 8.3 |
aarch64 |
|||
x86 |
||||
RHEL/CentOS 8.4 |
aarch64 |
|||
x86 |
||||
RHEL/CentOS 8.5 |
aarch64 |
|||
x86 |
||||
RHEL/Rocky 8.6 |
aarch64 |
|||
x86 |
||||
RHEL/Rocky 8.7 |
aarch64 |
|||
x86 |
||||
RHEL/Rocky 8.8 |
aarch64 |
|||
x86 |
||||
RHEL/Rocky 8.9 |
aarch64 |
|||
x86 |
||||
RHEL/Rocky 8.10 |
aarch64 |
|||
x86 |
||||
RHEL/Rocky 9.0 |
aarch64 |
|||
x86 |
||||
RHEL/Rocky 9.1 |
aarch64 |
|||
x86 |
||||
RHEL/Rocky 9.2 |
aarch64 |
|||
x86 |
||||
RHEL/Rocky 9.3 |
aarch64 |
|||
x86 |
||||
RHEL/Rocky 9.4 |
aarch64 |
|||
x86 |
||||
SLES 15 SP2 |
aarch64 |
|||
x86 |
||||
SLES 15 SP3 |
aarch64 |
|||
x86 |
||||
SLES 15 SP4 |
aarch64 |
|||
x86 |
||||
SLES 15 SP5 |
aarch64 |
|||
x86 |
||||
TencentOS 3.3 |
aarch64 |
|||
x86 |
||||
Ubuntu 20.04 |
aarch64 |
|||
x86 |
||||
Ubuntu 22.04 |
aarch64 |
|||
x86 |
||||
Ubuntu 24.04 |
aarch64 |
|||
x86 |
||||
UOS20.1060 |
aarch64 |
|||
x86 |
||||
UOS20.1060A |
aarch64 |
|||
x86 |
||||
Target BlueField Platform (Arm) |
BlueField Software v4.7.0 |
Ubuntu 22.04 |
aarch64 |
|
DOCA SDK v2.7.0 |
Ubuntu 22.04 |
aarch64 |
doca-dpu-repo-ubuntu2204-local_2.7.0085-1.24.04.0.6.6.0.bf.4.7.0.13127_arm64.deb |
|
DOCA Runtime v2.7.0 |
Uninstalling Software from Host
If an older DOCA (or MLNX_OFED) software version is installed on your host, make sure to uninstall it before proceeding with the installation of the new version:
Deb-based |
|
RPM-based |
|
Then perform the following steps:
Download NVIDIA's RPM-GPG-KEY-Mellanox-SHA256 key:
# wget http://www.mellanox.com/downloads/ofed/RPM-GPG-KEY-Mellanox-SHA256 --2018-01-25 13:52:30-- http://www.mellanox.com/downloads/ofed/RPM-GPG-KEY-Mellanox-SHA256 Resolving www.mellanox.com... 72.3.194.0 Connecting to www.mellanox.com|72.3.194.0|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1354 (1.3K) [text/plain] Saving to: ?RPM-GPG-KEY-Mellanox-SHA256? 100%[=================================================>] 1,354 --.-K/s in 0s 2018-01-25 13:52:30 (247 MB/s) - ?RPM-GPG-KEY-Mellanox-SHA256? saved [1354/1354]
Install the key:
# sudo rpm --import RPM-GPG-KEY-Mellanox-SHA256 warning: rpmts_HdrFromFdno: Header V3 DSA/SHA1 Signature, key ID 6224c050: NOKEY Retrieving key from file:///repos/MLNX_OFED//RPM-GPG-KEY-Mellanox Importing GPG key 0x6224C050: Userid: "Mellanox Technologies (Mellanox Technologies - Signing Key v2) " From : /repos/MLNX_OFED//RPM-GPG-KEY-Mellanox-SHA256 Is this ok [y/N]:
Verify that the key was successfully imported:
# rpm -q gpg-pubkey --qf '%{NAME}-%{VERSION}-%{RELEASE}\t%{SUMMARY}\n' | grep Mellanox gpg-pubkey-a9e4b643-520791ba gpg(Mellanox Technologies )
Installing Prerequisites on Host for Target BlueField
Install RShim to manage and flash the BlueField Platform.
OS |
Procedure |
Deb-based |
|
RPM-based |
|
Skip section "Installing Software on Host" to proceed without the DOCA local repo package for host.
Determining BlueField Device ID
It is important to learn your BlueField's device-id to perform some of the software installations or upgrades in this guide.
To determine the device ID of the BlueField Platform on your setup, run:
host# mst start
host# mst status -v
Example output:
MST modules:
------------
MST PCI module is not loaded
MST PCI configuration module loaded
PCI devices:
------------
DEVICE_TYPE MST PCI RDMA NET NUMA
BlueField2(rev:1
) /dev/mst/mt41686_pciconf0.1
3b:00.1
mlx5_1 net-ens1f1 0
BlueField2(rev:1
) /dev/mst/mt41686_pciconf0 3b:00.0
mlx5_0 net-ens1f0 0
BlueField3(rev:1
) /dev/mst/mt41692_pciconf0.1
e2:00.1
mlx5_1 net-ens7f1np1 4
BlueField3(rev:1
) /dev/mst/mt41692_pciconf0 e2:00.0
mlx5_0 net-ens7f0np0 4
The device IDs for the BlueField-2 and BlueField-3 networking platforms in this example are /dev/mst/mt41686_pciconf0 and /dev/mst/mt41692_pciconf0 respectively.
Installing Software on Host
Skip this section if you intend to update only the BlueField software (*.bfb).
Make sure to have followed the instructions under "Installing Prerequisites on Host for Target DPU".
Install DOCA local repo package for host:
InfoThe following table provides instructions for installing the DOCA host repo on your device depending on your OS and desired profile.
OS
Profile
Instructions
Deb-based
doca-all
Download the DOCA host repo from section "Installation Files" for the host.
Unpack the deb repo. Run:
host# dpkg -i <repo_file>
Perform apt update. Run:
host# apt-get update
If the kernel version on your host is not supported (not shown under "Supported Operating System Distributions"), refer to section "DOCA Extra Package".
Ensure that the kernel headers installed match the version of the currently running kernel.
InfoIf the build directory exists in under /lib/modules/$(uname -r)/build, then the kernel headers are installed.
Run apt install for DOCA SDK and DOCA runtime:
host# sudo apt install -y doca-all mlnx-fw-updater
doca-networking
Download the DOCA host repo from section "Installation Files" for the host.
Unpack the deb repo. Run:
host# dpkg -i <repo_file>
Perform apt update. Run:
host# apt-get update
If the kernel version on your host is not supported (not shown under "Supported Operating System Distributions"), refer to section "DOCA Extra Package".
Ensure that the kernel headers installed match the version of the currently running kernel.
InfoIf the build directory exists in under /lib/modules/$(uname -r)/build, then the kernel headers are installed.
Run apt install for DOCA SDK and DOCA runtime:
host# sudo apt install -y doca-networking mlnx-fw-updater
doca-ofed
Download the DOCA host repo from section "Installation Files" for the host.
Unpack the deb repo. Run:
host# sudo dpkg -i <repo_file>
Perform apt update. Run:
host# sudo apt-get update
If the kernel version on your host is not supported (not shown under "Supported Operating System Distributions"), refer to section "DOCA Extra Package".
Ensure that the kernel headers installed match the version of the currently running kernel.
InfoIf the build directory exists in under /lib/modules/$(uname -r)/build, then the kernel headers are installed.
Install doca-ofed. Run:
host# sudo apt install -y doca-ofed mlnx-fw-updater
RPM-based
doca-all
Download the DOCA host repo from section "Installation Files" for the host .
Unpack the rpm repo. Run:
host# rpm -Uvh <repo_file>.rpm
Perform yum update. Run:
host# sudo yum makecache
If the kernel version on your host is not supported (not shown under "Supported Operating System Distributions"), refer to section "DOCA Extra Package".
Run yum install for DOCA SDK and DOCA runtime:
host# sudo yum install -y doca-all mlnx-fw-updater
doca-networking
Download the DOCA host repo from section "Installation Files" for the host .
Unpack the rpm repo. Run:
host# rpm -Uvh <repo_file>.rpm
Perform yum update. Run:
host# sudo yum makecache
If the kernel version on your host is not supported (not shown under "Supported Operating System Distributions"), refer to section "DOCA Extra Package".
Run yum install for DOCA SDK and DOCA runtime:
host# sudo yum install -y doca-networking mlnx-fw-updater
doca-ofed
Download the DOCA host repo from section "Installation Files" for the host.
Unpack the RPM repo. Run:
host# sudo rpm -Uvh <repo_file>.rpm
Perform yum update. Run:
host# sudo yum makecache
If the kernel version on your host is not supported (not shown under "Supported Operating System Distributions"), refer to section "DOCA Extra Package".
Install doca-ofed. Run:
host# sudo yum install -y doca-ofed mlnx-fw-updater
Load the drivers:
host# sudo /etc/init.d/openibd restart
Initialize MST. Run:
host# sudo mst restart
Skip this step if your BlueField Platform is Ethernet only. Please refer to Supported Platforms to learn your Bluefield type.
If you have a VPI-capable BlueField, the default link type of the ports will be configured to IB. To verify your link type, run:
host# sudo mst start host# sudo mlxconfig -d <device-id> -e q | grep -i link_type Configurations: Default Current Next Boot * LINK_TYPE_P1 IB(
1
) ETH(2
) IB(1
) * LINK_TYPE_P2 IB(1
) ETH(2
) IB(1
)NoteIf your BlueField is Ethernet capable only, then the sudo mlxconfig -d <device> command will not provide an output.
If the current link type is set to IB, run the following command to change it to Ethernet:
host# sudo mlxconfig -d <device-id> s LINK_TYPE_P1=
2
LINK_TYPE_P2=2
Verify that RShim is active.
host# sudo systemctl status rshim
This command is expected to display active (running). If RShim service does not launch automatically, run:
host# sudo systemctl enable rshim host# sudo systemctl start rshim
Assign a dynamic IP to tmfifo_net0 interface (RShim host interface).
NoteSkip this step if you are installing the DOCA image on multiple DPUs.
host# ifconfig tmfifo_net0
192.168
.100.1
netmask255.255
.255.252
up
DOCA Extra Package
If the kernel version on on your host is not supported (not shown under "Supported Operating System Distributions"), two options are available:
Switch to a compatible kernel.
Install doca-extra package:
Run:
host# sudo apt/yum install -y doca-extra
Execute the doca-kernel-support script which rebuilds and installs the DOCA-Host kernel modules with the running kernel:
host# sudo /opt/mellanox/doca/tools/doca-kernel-support
Install user-space packages:
host# sudo apt/yum install -y doca-ofed-userspace
Notedoca-kernel-support does not support customized or unofficial kernels.
Installing Software on DPU
Users have two options for installing DOCA on BlueField DPU or SuperNIC:
Upgrading the full DOCA image on BlueField (recommended) – this option overwrites the entire boot partition with an Ubuntu 22.04 installation and updates BlueField and NIC firmware.
Upgrading DOCA local repo package on BlueField – this option upgrades DOCA components without overwriting the boot partition. Use this option to preserve configurations or files on BlueField itself.
Installing Full DOCA Image on DPU via Host
This step overwrites the entire boot partition.
This installation sets up the OVS bridge.
If you are installing DOCA on multiple BlueField platforms, skip to section Installing Full DOCA Image on Multiple BlueField Platforms.
Option 1 – No Pre-defined Password
To change the default Ubuntu password during the BFB bundle installation, proceed to Option 2.
BFB installation is executed as follows:
host# sudo bfb-install --rshim rshim<N> --bfb <image_path.bfb>
Where rshim<N> is rshim0 if you only have one Bluefield. You may run the following command to verify:
host# ls -la /dev/ | grep rshim
Option 2 – Set Pre-defined Password
Ubuntu users can provide a unique password that will be applied at the end of the BlueField BFB bundle installation. This password needs to be defined in a bf.cfg configuration file.
To set the password for the "ubuntu" user:
Create password hash. Run:
host# openssl passwd -
1
Password: Verifying - Password: $1
$3B0RIrfX$TlHry93NFUJzg3Nya00rE1Add the password hash in quotes to the bf.cfg file:
host# sudo vim bf.cfg ubuntu_PASSWORD=
'$1$3B0RIrfX$TlHry93NFUJzg3Nya00rE1'
When running the installation command, use the --config flag to provide the file containing the password:
host# sudo bfb-install --rshim rshim<N> --bfb <image_path.bfb> --config bf.cfg
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.
NoteIf --config is not used, then upon first login to the BlueField device, users will be prompted to update the default 'ubuntu' password.
The following is an example of Ubuntu-22.04 BFB bundle installation (Release 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 bfb1
.41GiB0
: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, status0
INFO[UEFI]: PCIeenum
start INFO[UEFI]: PCIeenum
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 thedefault
passwordfor
user ubuntu INFO[MISC]: Ubuntu installation completed INFO[MISC]: Updating NIC firmware... INFO[MISC]: NIC firmware update done INFO[MISC]: Installation finishedTo verify the BlueField has completed booting up, allow additional 90 seconds then perform the following:
host# sudo cat /dev/rshim<N>/misc ... INFO[MISC]: Linux up INFO[MISC]: DPU is ready
Installing Full DOCA Image on Multiple BlueField Platforms
On a host with multiple BlueField devices, the BFB image can be installed on all of them using the multi-bfb-install script.
host# ./multi-bfb-install --bfb <image_path.bfb> --password <password>
This script detects the number of RShim devices and configures them statically.
For Ubuntu – the script creates a configuration file /etc/netplan/20-tmfifo.yaml
For CentOS/RH 8.0 and 8.2 – the script installs the bridge-utils package to use the brctl command, creates the tm-br bridge, and connects all RShim interfaces to it
After the installation is complete, the configuration of the bridge and each RShim interface can be observed using ifconfig. The expected result is to see the IP on the tm-br bridge configured to 192.168.100.1 with subnet 255.255.255.0.
To log into BlueField with rshim0, run:
ssh ubuntu@192
.168.100.2
For each RShim after that, add 1 to the fourth octet of the IP address (e.g., ubuntu@192.168.100.3 for rshim1, ubuntu@192.168.100.4 for rshim2, etc).
The script burns a new MAC address to each BlueField and configures a new IP, 192.168.100.x, as described earlier.
Installing DOCA Local Repo Package on BlueField
If you have already installed BlueField image, be aware that the DOCA SDK, Runtime, and Tools are already contained in the BFB, and this installation is not mandatory. If you have not installed the BlueField image and wish to update DOCA Local Repo package, proceed with the following procedure.
Before installing DOCA on the target BlueField, make sure the out-of-band interface (mgmt) is connected to the internet.
Download the DOCA SDK and DOCA Runtime package from section Installation Files.
Copy deb repo package into BlueField. Run:
host# sudo scp -r doca-repo-aarch64-ubuntu2204-local_<version>_arm64.deb ubuntu
@192
.168.100.2
:/tmp/Unpack the deb repo. Run:
dpu# sudo dpkg -i doca-dpu-repo-ubuntu2204-local_<version>_arm64.deb
Run apt update.
dpu# sudo apt-get update
Run apt install for DOCA Runtime and DOCA SDK:
dpu# sudo apt install doca-runtime doca-sdk
Upgrading Firmware
This operation is only required if the user skipped NIC firmware update during BFB bundle installation using the parameter WITH_NIC_FW_UPDATE=no in the bf.cfg file.
This section explains how to update the NIC firmware on a DOCA installed BlueField OS.
If multiple BlueFields are installed, the following steps must be performed on all of them after BFB installation.
An up-to-date NIC firmware image is provided in BlueField BFB bundle and copied to the BlueField filesystem during BFB installation.
To upgrade firmware in the BlueField Arm OS:
SSH to your BlueField Arm OS by any means available.
The following instructions enable to login to the BlueField Arm OS from the host OS over the RShim virtual interface, tmfifo_net<N> and do not require LAN connectivity with the BlueField OOB network port.
NoteThis operation can be performed over the host's tmfifo_net0 IPv4, 192.168.100.1 (preconfigured) with BlueField Arm OS at 192.168.100.2 (default).
If multiple BlueField DPUs were updated using the multi-bfb-install script, as explained above, then each target BlueField OS IPv4 address changes in its last octate according to the underlaying RShim interface number: 192.168.100.3 for rshim1, 192.168.100.4 for rshim2, etc.
The default credentials for Ubuntu are as follows:
Username
Password
ubuntu
ubuntu
For example, to log into BlueField Arm OS over IPv6:
host]# systemctl restart rshim
// Wait 10 seconds
host]# ssh -6
fe80::21a:caff:feff:ff01%tmfifo_net<N> Password: <configured-password>Upgrade firmware in BlueField. Run:
dpu# sudo /opt/mellanox/mlnx-fw-updater/mlnx_fw_updater.pl --force-fw-update
Example output:
Device #
1
: ---------- Device Type: BlueField-2
[...] Versions: Current Available FW <Old_FW> <New_FW>For the firmware upgrade to take effect perform a BlueField system reboot.
Post-installation Procedure
Restart the driver. Run:
host# sudo /etc/init.d/openibd restart Unloading HCA driver: [ OK ] Loading HCA driver and Access Layer: [ OK ]
Configure the physical function (PF) interfaces.
host# sudo ifconfig <
interface
-1
> <network-1
/mask> up host# sudo ifconfig <interface
-2
> <network-2
/mask> upFor example:
host# sudo ifconfig p2p1
192.168
.200.32
/24
up host# sudo ifconfig p2p2192.168
.201.32
/24
upPings between the source and destination should now be operational.
This upgrade procedure enables upgrading DOCA components using standard Linux tools (e.g., apt update and yum update). This process utilizes native package manager repositories to upgrade BlueField networking platforms (DPUs or SuperNICs) without the need for a full installation.
This process has the following benefits :
Only updates components that include modifications
Configurable – user can select specific components (e.g., UEFI-ATF, NIC-FW)
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
Does not:
Impact user binaries
Upgrade non-Ubuntu OS kernels
Upgrade BlueField BMC firmware
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
OS |
Action |
Instructions |
Ubuntu/ Debian |
Remove mlxbf-bootimages package |
|
Install the the GPG key |
|
|
Export the desired distribution |
Export DOCA_REPO with the relevant URL. The following is an example for Ubuntu 22.04:
|
|
Add GPG key to APT trusted keyring |
|
|
Add DOCA online repository |
|
|
Update index |
|
|
Upgrade UEFI/ATF firmware |
Run:
Then i nitiate upgrade for UEFI/ATF firmware:
|
|
Upgrade BlueField NIC firmware |
Run:
Note
This immediately starts NIC firmware upgrade.
To prevent automatic upgrade, run:
|
|
Remove old metapackages |
|
|
Install new metapackages |
|
|
Upgrade system |
|
|
Apply the new changes, NIC firmware, and UEFI/ATF |
For the upgrade to take effect, perform BlueField system reboot as explained in the "NVIDIA BlueField Reset and Reboot Procedures" troubleshooting page. Note
This step triggers immediate reboot of the BlueField Arm cores.
|
|
CentOS/RHEL/ Anolis/Rocky |
Remove mlxbf-bootimages package |
|
Export the desired distribution |
Export DOCA_REPO with the relevant URL. The following is an example for Rocky Linux 8.6:
|
|
Add DOCA online repository |
A file is created under /etc/yum.repos.d/doca.repo . |
|
Update index |
|
|
Upgrade UEFI/ATF firmware |
Run:
Then i nitiate the upgrade for UEFI/ATF firmware:
|
|
Upgrade BlueField NIC firmware |
The following command updates the firmware package and automatically attempts to flash the firmware to the NIC:
Info
This step can be used as a standalone firmware update. In any case, it is performed as part of the upgrade flow.
Note
To prevent automatic flashing of the firmware to the NIC, run the following first:
Info
Flashing the firmware to the NIC can be performed manually by running the following command, after the firmware package had been updated:
|
|
Remove old metapackages |
|
|
Install new metapackages |
|
|
Upgrade system |
|
|
Apply the new changes, NIC firmware, and UEFI/ATF |
For the upgrade to take effect, perform BlueField system reboot as explained in the "NVIDIA BlueField Reset and Reboot Procedures" troubleshooting page. Note
This step triggers immediate reboot of the BlueField Arm cores.
|
Users wishing to build their own customized BlueField OS image can use the BFB build environment. Please refer to the bfb-build project in this GitHub webpage for more information.
For a customized BlueField OS image to boot on the UEFI secure-boot-enabled BlueField (default BlueField secure boot setting), the OS must be either signed with an existing key in the UEFI DB (e.g., the Microsoft key), or UEFI secure boot must be disabled. Please refer to the "Secure Boot" page under NVIDIA BlueField DPU Platform Operating System Documentation for more details.
For full instructions about setting up a development environment, refer to the NVIDIA DOCA Developer Guide.
Installing CUDA on NVIDIA Converged Accelerator
NVIDIA® CUDA® is a parallel computing platform and programming model developed by NVIDIA for general computing GPUs.
This section details the necessary steps to set up CUDA on your environment. This section assumes that a BFB image has already been installed on your environment.
To install CUDA on your converged accelerator:
Download and install the latest NVIDIA Data Center GPU driver.
Download and install CUDA
NoteThe CUDA version tested to work with DOCA SDK is 11.8.0.
Downloading CUDA includes the latest NVIDIA Data Center GPU driver and CUDA toolkit. For more information about CUDA and driver compatibility, refer to the NVIDIA CUDA Toolkit Release Notes.
Configuring Operation Mode
There are two modes that the NVIDIA Converged Accelerator may operate in:
Standard mode (default) – the BlueField and the GPU operate separately
BlueField-X mode – the GPU is exposed to BlueField and is no longer visible on the host
To verify which mode the system is operating in, run:
host# sudo mst start
host# sudo mlxconfig -d <device-id> q PCI_DOWNSTREAM_PORT_OWNER[4
]
To learn your BlueField Platform's device ID, refer to section "Determining BlueField Device ID".
Standard mode output:
Device #
1
: […] Configurations: Next Boot PCI_DOWNSTREAM_PORT_OWNER[4
] DEVICE_DEFAULT(0
)
BlueField-X mode output:
Device #
1
: […] Configurations: Next Boot PCI_DOWNSTREAM_PORT_OWNER[4
] EMBEDDED_CPU(15
)
To configure BlueField-X mode, run:
host# mlxconfig -d <device-id> s PCI_DOWNSTREAM_PORT_OWNER[4
]=0xF
To configure standard mode, run:
host# mlxconfig -d <device-id> s PCI_DOWNSTREAM_PORT_OWNER[4
]=0x0
To learn your BlueField Platform's device ID, refer to section "Determining BlueField Device ID".
Power cycle is required for configuration to take effect. For power cycle the host run:
host# ipmitool power cycle
Downloading and Installing CUDA Toolkit and Driver
This section details the necessary steps to set up CUDA on your environment. It assumes that a BFB image has already been installed on your environment.
Install CUDA by visiting the CUDA Toolkit Downloads webpage.
NoteSelect the Linux distribution and version relevant for your environment.
NoteThis section shows the native compilation option either on x86 or aarch64 hosts.
Test that the driver installation completed successfully. Run:
dpu# nvidia-smi Tue Apr
5
13
:37
:59
2022
+-----------------------------------------------------------------------------+ | NVIDIA-SMI510.47
.03
Driver Version:510.47
.03
CUDA Version:11.8
| |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===============================+======================+======================| |0
NVIDIA BF A10 Off |00000000
:06
:00.0
Off |0
| |0
% 43C P0 N/A / 225W | 0MiB / 23028MiB |0
% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=============================================================================| | No running processes found | +-----------------------------------------------------------------------------+Verify that the installation completed successfully.
Download CUDA samples repo. Run:
dpu# git clone https:
//github.com/NVIDIA/cuda-samples.git
Build and run vectorAdd CUDA sample. Run:
dpu# cd cuda-samples/Samples/0_Introduction/vectorAdd dpu# make dpu# ./vectorAdd
NoteIf the vectorAdd sample works as expected, it should output "Test Passed".
NoteIf it seems that the GPU is slow or stuck, stop execution and run:
dpu# sudo setpci -v -d ::
0302
800
.L=201
# CPL_VC0 =32
GPUDirect RDMA
For information on GPUDirect RMDA and more, refer to DOCA GPUNetIO documentation.
Installing Rivermax on BlueField
NVIDIA Rivermax offers a unique IP-based solution for any media and data streaming use case.
This section provides the steps to install Rivermax assuming that a BFB image has already been installed on your environment.
Downloading Rivermax Driver
Navigate to the NVIDIA Rivermax SDK product page.
Register to be able to download the driver package using the JOIN button at the top of the page.
D ownload the appropriate driver package according to your BFB under the "Linux" subsection. For example, for Ubuntu 22.04 BFB, download rivermax_ubuntu2204_<version>.tar.gz.
Installing Rivermax Driver
Copy the .tgz file to BlueField:
host# sudo scp -r rivermax_ubuntu2204_<version>.tar.gz ubuntu@192.168.100.2:/tmp/
Extract the Rivermax file:
dpu# sudo tar xzf rivermax_ubuntu2204_<version>.tar.gz
Install the Rivermax driver package:
dpu# cd <rivermax-version>/Ubuntu.22.04/deb-dist/aarch64/ dpu# sudo dpkg -i rivermax_<version>.deb
Installing Rivermax Libraries from DOCA
Rivermax libraries are compatibles with DOCA components and can be found inside the doca-dpu-repo.
Unpack the doca-dpu-repo:
dpu# sudo dpkg -i doca-dpu-repo-ubuntu2204-local_<version>_arm64.deb
Run apt update:
dpu# sudo apt-get update
Install the Rivermax libraries:
dpu# sudo apt install doca-rmax-libs dpu# sudo apt install libdoca-rmax-libs-dev
For additional details and guidelines, please visit the NVIDIA Rivermax SDK product page.
For questions, comments, and feedback, please contact us at DOCA-Feedback@exchange.nvidia.com.