Skip to content
#2702 Overall#374 in DevOpsVerified SKILL.md

Doca Bf3 Deployment

Use this skill for BlueField-3 (BF3) day-1 platform bring-up via the classic RShim/BFB path: pushing a BlueField bundle (BFB) to the DPU over RShim with bfb-install from the host, the host-to-DPU TMFIFO management channel (tmfifo_net0, the 192.168.100.x convention), RShim daemon state and console-over-rshim, DPU mode selection (DPU/embedded-function vs separated-host/NIC mode) via mlxconfig, post-BFB recovery, a six-state BlueField-state classifier, and verifying the install (cat /etc/mlnx-release plus version checks). Trigger even when the user does not say "BF3" — typical phrasings include {push a BFB to my BlueField-3}, {bfb-install exited 0 but the DPU never came back}, {ping 192.168.100.2 works but ssh fails}, or {is DOCA on the host or the Arm side?}. BFB reflash, mlxconfig set, mode changes, and firmware burns are destructive: require explicit target-bound confirmation and load doca-hardware-safety. App launch, container deploy, env install, and the BF4 BMC-Redfish path route elsewhere.

Claude CodeCodexSKILL.md Official publisher
0Total downloads
0Active installs
3,046Community stars
Momentum rank

Overview

What It Does

Doca Bf3 Deployment packages a focused devops & cloud workflow for an AI agent. Use this skill for BlueField-3 (BF3) day-1 platform bring-up via the classic RShim/BFB path: pushing a BlueField bundle (BFB) to the DPU over RShim with bfb-install from the host, the host-to-DPU TMFIFO management channel (tmfifo_net0, the 192.168.100.x convention), RShim daemon state and console-over-rshim, DPU mode selection (DPU/embedded-function vs separated-host/NIC mode) via mlxconfig, post-BFB recovery, a six-state BlueField-state classifier, and verifying the install (cat /etc/mlnx-release plus version checks). Trigger even when the user does not say "BF3" — typical phrasings include {push a BFB to my BlueField-3}, {bfb-install exited 0 but the DPU never came back}, {ping 192.168.100.2 works but ssh fails}, or {is DOCA on the host or the Arm side?}. BFB reflash, mlxconfig set, mode changes, and firmware burns are destructive: require explicit target-bound confirmation and load doca-hardware-safety. App launch, container deploy, env install, and the BF4 BMC-Redfish path route elsewhere. It is best suited to users who can review the resulting actions and provide only the accounts, files, or command access needed for the task. It is not a substitute for human approval on destructive, financial, security-sensitive, or public-facing actions.

Task ideas

Popular Use Cases

  • Inspect deployment or infrastructure state
  • Automate a repeatable operations task
  • Troubleshoot configuration and runtime issues
  • Apply documented production practices

Installation

Install this Agent Skill

Claude Code

npx skills add https://github.com/NVIDIA/skills --skill doca-bf3-deployment

Commands derived from the public GitHub SKILL.md record. Checked 2026-09-02. Review the source before running them.

Before you start

Requirements

Claude CodeRequired / review
CodexRequired / review
Public SKILL.md sourceRequired / review
Review instructions and requested permissions before installationRequired / review
Paid serviceCheck source
Supported systemCheck source

Popularity context

Why It’s Popular

Doca Bf3 Deployment is a verified Agent Skill from NVIDIA with a public SKILL.md, compatible with Claude Code, Codex.

Alternatives

Similar Skills