Housing authority cluster documentation covers Spectrum-X leaf configs but omits DPU software. What install steps should the runbook add?
Select an answer to reveal the explanation.
Short Explanation
Leaf configs without DOCA steps leave the DPU half of the story blank. Housing authority runbooks should put NVIDIA DOCA install right next to the Spectrum-X leaf procedures.
Full Explanation
Housing authority cluster documentation that covers Spectrum-X leaf configs but omits DPU software should add NVIDIA DOCA installation steps beside the Spectrum-X leaf configuration procedures. Runbooks must treat leaf and DPU software as one civic bring-up story: Spectrum-X alone does not configure BlueField, and operators following only leaf steps will leave DPU networking incomplete. MLNX_OFED host driver installation steps for servers attached to Spectrum-X leaves fail by concept: those steps target host NIC drivers on attached servers, not Spectrum-X leaf configuration or DOCA install on DPUs, so adding them checks the wrong layer entirely. Manual re-provisioning of NetQ agents after each leaf software update fails because it is a NetQ agent maintenance task, not a DOCA installation step—re-provisioning monitoring agents does not put DOCA on the DPU. DOCA SDK sample deployment steps for custom DPU streaming functions fail: deploying SDK samples is an optional custom task, not the required DOCA installation the runbook lacks, so it guarantees incomplete housing-authority AI host offload. Exam caveat: Spectrum-X leaf procedures and DOCA install steps belong together in the runbook when BlueField DPUs front Spectrum-attached hosts; MLNX_OFED host driver steps for attached servers and NetQ agent re-provisioning are not DOCA substitutes. Operational check: update the housing authority runbook with ordered DOCA install/verify steps next to Spectrum-X leaf config, dry-run on one rack, confirm DPU version and services, then roll the combined procedure to remaining civic racks.