AI & HPC networks
What belongs in a BlueField-3 DPU management and integration BOM?
Separate data ports, OOB access, RShim and server power requirements.
A DPU adds a managed computing endpoint as well as network interfaces. Buying only the card and high-speed links leaves unanswered how it is powered, provisioned, monitored and recovered when the host or production network is unavailable.
The short answer
Document three paths separately: production data, independent OOB management and the supported provisioning or recovery method. Qualify the exact BlueField-3 model, operating mode, server power connection and software before choosing accessories.
Production data, 1GbE out-of-band management and RShim provisioning/recovery serve different roles. The RShim line represents a logical path. Conceptual illustration; equipment shapes are illustrative.
Official technical sources · Independent analysis by SwitchInfra
This is a documented design analysis, not a customer deployment claim. Candidate roles require verification for your configuration.
QSFP112 — documented data interface
1GbE — OOB management interface
PCIe — host integration path
RShim — separate management mechanism
What the technical reference establishes
The BlueField-3 guide documents QSFP112 data interfaces and a 1GbE OOB interface. The software overview describes RShim console and virtual networking over supported host connections, distinct from production data traffic.
For a comparable deployment, assign an owner to the DPU software and recovery path. A card that passes network packets but cannot be updated or recovered under the agreed failure scenario is not an operationally complete delivery.
BlueField-3 supported interfaces
Data — High-speed network traffic uses the documented data interfaces.
OOB — The guide identifies separate 1GbE management connectivity.
Host access — RShim depends on supported access and operating mode.
Power — Specified DPU OPNs require supplementary server power.
Scope of the analysis: Independent selection analysis of official NVIDIA documentation. Proposed examples are not a deployed customer project or a SwitchInfra delivery.
Work through the engineering choices
Start with the documented constraint, then state the conditions for the proposed equipment role.
Define what the DPU will do and who will operate it
The platform combines network and embedded software resources.
Design exercise: Proposed task: name the DPU services and their management owner.
Write the intended operating mode and services into the specification. Identify which software runs on the embedded environment and which responsibilities remain on the host. Do not purchase a DPU solely from its headline port rate when a conventional adapter might meet a different requirement.
Agree the firmware and software baseline, update responsibility and support route. Record how credentials, logs and configuration will be maintained. These are delivery requirements, not evidence that a particular security or offload function has already been enabled and tested on the proposed server.
BlueField-3 networking platform guide · BlueField BSP 4.14 software overview
B3220 DPU integration inquiry
Exact crypto-enabled B3220 OPN; do not substitute the 00SV variant without review.
Keep recovery connectivity independent of production assumptions
The documentation separates OOB and RShim access from data interfaces.
Design exercise: Proposed acceptance question: can operators reach the DPU under each agreed failure scenario?
Map the OOB connection to a management switch and address plan. Separately document whether provisioning uses a supported PCIe or USB RShim path. Host-mediated access should not be assumed available after a host failure, and a functioning data link does not demonstrate independent management access.
The software overview notes that RShim PCIe access is unavailable in isolation mode. Confirm the behavior for the chosen release and trust model. Test the intended recovery procedure before handover, keeping production traffic off the management virtual interface and preserving an approved alternative where needed.
BlueField-3 supported interfaces · BlueField BSP 4.14 software overview
SN2201 family
OOB switch inquiry
Plan actual 1GbE management endpoints and required uplinks.
Include power and accessories in the offered server configuration
The hardware guide gives model-specific auxiliary power and accessory requirements.
Design exercise: Proposed task: reconcile the exact DPU OPN with the server integration kit.
For applicable models such as the documented B3220 configurations, confirm the required supplementary PCIe power connection. The guide distinguishes the permitted PCIe ATX connection from CPU EPS12V wiring. Obtain the server vendor’s integration instructions; a visually similar connector is not an acceptable substitute.
List management leads, any approved accessory kit and service clearance alongside the data interconnects. Confirm what the offered package actually contains. An accessory shown in a hardware manual does not prove that it ships with every card, or that its use is appropriate for the selected server.
BlueField-3 supported interfaces
MBF35-DKIT
Accessory kit inquiry
Confirm exact included accessories and server use; not a generic host USB cable.
Quote an operable DPU, not just a card
The RFQ should reconcile the data-plane role with power, software ownership and a tested recovery path. This turns hidden integration assumptions into reviewable delivery requirements.
BlueField-3 supported interfaces
Platform
Exact OPN, server approval, operating mode and firmware/software baseline.
Access
Data peers, OOB ports, management addressing and supported recovery method.
Integration
Approved power kit, accessories, package contents and recovery acceptance test.
Candidate models and selection boundaries
These are conditional model or product-family inquiries for the documented equipment roles. Confirm the required rate and complete channel before finalizing any line.
| Model / family and status | Role and condition |
|---|---|
| 900-9D3B6-00CV-AA0 Listed OPN; conditional candidate | B3220 DPU integration inquiry Exact crypto-enabled B3220 OPN; do not substitute the 00SV variant without review. BlueField-3 networking platform guide · BlueField-3 exact ordering configurations |
| SN2201 family Conditional model / family inquiry | OOB switch inquiry Plan actual 1GbE management endpoints and required uplinks. H100 SuperPOD key components |
| MBF35-DKIT Conditional model / family inquiry | Accessory kit inquiry Confirm exact included accessories and server use; not a generic host USB cable. BlueField-3 supported interfaces |
Rows with product IDs are mapped to the exact listed model or ordering variant checked on 19 October 2026. Remaining rows are model or family inquiries. A public listing does not establish stock, offered condition, supply or project compatibility.
Continue in the relevant product family
Use the analysis to define the role before comparing catalog options.
Discuss this project
Carry the route, media, endpoint and loss requirements into the inquiry. Leave unknown quantities blank; reference port and fiber counts are not an equipment BOM.
Follow the next selection question.
Compare related decisions while keeping each source’s scope, hardware and link conditions separate.
Browse more engineering analyses →
H100 SuperPOD: four fabrics, four connection schedules
Keep compute, storage, service access and OOB management distinct before counting equipment.
Read the engineering analysisOfficial technical source
HGX Spectrum-X: separate SuperNIC and DPU duties
Keep GPU communication, converged services and management distinct in the node and fabric BOM.
Read the engineering analysisOfficial technical source
ConnectX-6 Dx: qualify the card at both interfaces
Compare OPN, PCIe resources and complete Ethernet channels for a 25G or 100G refresh.
Read the engineering analysisOfficial technical source
Before you finalize the channel
Is the OOB interface a second production data port?
It has a management role and must be planned separately.
Can RShim always replace OOB access?
No. Availability depends on access, operating mode and the host path.
Does a supplied DPU include every required cable?
Do not assume so. Reconcile the package and server integration kit.
Does buying the DPU establish tested offload performance?
No. Configure and test the intended services on the complete system.
Trace the project facts and technical limits
- BlueField-3 supported interfaces
- BlueField-3 networking platform guide
- BlueField BSP 4.14 software overview
- H100 SuperPOD key components
Source check: 19 October 2026. Catalog status is stated per candidate.
Official sources read 19 October 2026. Project-specific engineering review, firmware support, exact offered parts and supply remain unconfirmed.