Doca Bf4 Deployment
NVIDIAOfficialCreated by NVIDIA
- Skill
- Workflow
- Cloud and DevOps
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill guides operators through the day-1 platform bring-up of BlueField-4 (BF4) DPUs via the BMC. It covers installing the BlueField/DOCA bundle ISO, performing PLDM platform-firmware updates, and deploying Grace Ubuntu images with optional cloud-init. The skill emphasizes safety by requiring all mutating hardware operations—such as firmware burns, ISO reflashes, and power cycles—to be governed by the doca-hardware-safety skill, ensuring maintenance windows and rollback plans are in place.
What it does
- Guides UEFI HTTP Boot, PXE, and Redfish Virtual Media installation methods.
- Manages PLDM platform-firmware updates via Redfish UpdateService and pldmtool.
- Supports Grace Ubuntu image installation with cloud-init configuration.
- Provides diagnostic workflows for common bring-up issues like boot loops or firmware task failures.
- Enforces strict safety protocols for all irreversible hardware-mutating operations.
- Routes non-BF4 or application-level requests to appropriate specialized skills.
When to use it
- When performing initial day-1 bring-up of a new BlueField-4 DPU.
- When updating platform firmware on a BlueField-4 via the BMC.
- When troubleshooting failed ISO boots, firmware task hangs, or virtual media attachment issues.
- When configuring a Grace Ubuntu environment with cloud-init via Redfish.
Advantages
- Ensures consistent, documented procedures for complex hardware bring-up.
- Integrates safety checks to prevent bricking or corruption during firmware updates.
- Provides a clear taxonomy for diagnosing and resolving deployment errors.
- Maintains a clean separation between platform bring-up and application deployment.
Usage examples
- “I have a brand-new BlueField-4 and need to install the DOCA bundle ISO onto it. What are my options?”
- The agent provides a comparison of UEFI HTTP Boot, PXE, and Redfish Virtual Media, guiding the user to the appropriate task workflow based on their infrastructure.
- “I pushed a firmware bundle through Redfish and the Task just sits at Running. Is it stuck?”
- The agent initiates the debug workflow, checking the firmware-Task layer and advising on whether to wait or intervene, while enforcing safety rules against blind re-pushes.
- “My BlueField-4 keeps re-entering the installer every time it resets. Why?”
- The agent identifies a potential boot-loop caused by attached virtual media and provides instructions to detach the media to allow the system to boot into the installed OS.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/nvidia/doca-bf4-deployment/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip doca-bf4-deployment.zip -d .agents/skills
Documentation by NVIDIA
DOCA BlueField-4 (BF4) deployment
Examples
"I have a BlueField-4 and a BMC — how do I bring Grace up?" — BMC-driven day-1, not the BF3 RShim/BFB path. Do not invent credentials or skip media detach.
"PLDM update finished but the NIC firmware did not move." — treat it as a firmware-Task / activation failure, not a second burn by default.
BlueField-3 or any other generation is not this skill. Name
doca-bf3-deployment and stop; do not read further or run commands.
Preparing a BlueField-4 host (answer from here)
Platform: confirm it is BlueField-4 and that the BMC is reachable out of band; compare the Redfish firmware inventory with the release notes' targets.
Version alignment: run the
doca-versionfour-source chain on the host. Fixing any mismatch changes hardware state and followsdoca-hardware-safety.Safest first smoke test: read-only
doca_caps --list-devs, then one shipped sample perdoca-bare-metal-deployment. No firmware, mode or reset change before that is green.Say it in the answer: every mutating step (PLDM firmware burn, ISO reflash, power cycle, BMC reset) is routed through
doca-hardware-safety: pre-flight inventory, out-of-band access, maintenance window, rollback, then apply and verify.
Instructions
Follow Loading order below. Open the tasks companion for BMC bring-up and recover. Open the capabilities companion for the three install methods and the BF4 safety overlay. Do not open every companion file.
⚠️ WARNING — irreversible hardware operations. This skill guides operators through potentially destructive, irreversible BlueField-4 hardware operations: PLDM firmware burns, ISO reflashes, power cycles, and BMC factory resets. These can brick firmware, corrupt boot media, or cause production outages. Do not proceed without a maintenance window and a tested rollback plan. Every mutating step is governed by
doca-hardware-safety/SKILL.md, which MUST be loaded alongside this skill before any destructive action.Before executing any mutating step — PLDM firmware burn, ISO reflash, power cycle, or BMC factory reset — the agent MUST show the exact command and its blast radius (which device, what becomes unavailable, whether it is reversible) and obtain the user's explicit confirmation for that specific action. Never chain destructive steps or run them speculatively as a side effect of another task.
Where to start: This skill is the bundle's deliberate in-bundle
home for day-1 platform bring-up of a BlueField-4 DPU via the
BMC — getting a powered-but-bare BF4 to "Grace OS installed,
firmware at the target level, ready to deploy a workload." It is the
upstream of the two application-deployment skills
(doca-container-deployment/SKILL.md
and
doca-bare-metal-deployment/SKILL.md):
those skills assume a working BlueField; this skill is how the
BlueField-4 GETS to working. If the user has a fresh BF4 and wants to
install the OS or update firmware, open the tasks companion and
start at ## configure. If the question is
what bring-up methods even exist and what is the contract for each,
start at the capabilities companion.
How to use this skill. Read this file, then search the companion file
for the ## <name> heading the question needs and read that whole section.
Answer completely from it, quoting only its symbols and commands. Do not
browse docs; use the entry points in doca-public-knowledge-map. Give
environment checks as commands for the user's DOCA host. For out-of-scope
requests, name the skill that owns them and stop.
Scope note — BF4 day-1 is in scope. The bundle's
AGENTS.md ## Non-goals(bundleAGENTS.md#non-goals-questions-the-agent-should-recognize-and-refuse-politely) item 7 lists the BlueField BSP / BFB / RShim / TMFIFO layer and the BlueField BMC software as externally-productized. BlueField-4 day-1 bring-up via the BMC is in scope for this skill because day-1 has no other home in the bundle. The carve-out is narrow: this skill teaches the documented BMC-driven install and firmware-update FLOWS (the CLASS), routing every mutating step throughdoca-hardware-safety/SKILL.mdfor the change-application meta-policy. It does NOT redefine that meta-policy, and it does NOT cover BF3 (route todoca-bf3-deployment), application launch, or library APIs.
When to load this skill
Load this skill when the user is doing hands-on day-1 bring-up of a BlueField-4 via the BMC, or asking a cross-cutting BF4-bring-up question that is not specific to a later application-deployment step. Concretely:
Installing the BlueField/DOCA bundle ISO onto the DPU (Grace) for the first time, and choosing between the install methods — UEFI HTTP Boot, PXE Boot, Redfish Virtual Media, or the DOCA Management Service install path.
Running the PLDM firmware-update flow across the BMC, NIC firmware and the other platform components the PLDM package lists: pushing the
.fwpkgbundle through the Redfish UpdateService multipart endpoint, monitoring the returned Task, verifying pending images withpldmtool, and activating with a power cycle.Installing a Grace Ubuntu image (with optional cloud-init via a CIDATA-labelled config ISO) through Redfish Virtual Media, with either local hosting on the BMC eMMC or remote hosting on an HTTPS server.
Reaching the DPU's OOB serial console (BMC SSH plus
obmc-console-client) to watch the installer or UEFI menus.Diagnosing a bring-up that is misbehaving — the ISO will not boot, virtual media will not attach, a firmware Task hangs or reports an Exception, a pending image never activates, cloud-init is ignored, or the DPU is stuck in a boot loop because media was never detached.
Cross-cutting questions: "HTTP Boot or Redfish Virtual Media — which do I use, and when do I actually need PXE?", "how do I know the firmware update actually took effect?", "the ISO landed but the NIC firmware update sub-step seems to have failed — what now?".
Do not load this skill for BF3 bring-up (route to
doca-bf3-deployment); for running an application on an
already-working BlueField (route to
doca-container-deployment/SKILL.md
or
doca-bare-metal-deployment/SKILL.md);
for env preparation on the installed Grace OS such as hugepages /
pkg-config / devlink (use doca-setup/SKILL.md); for
the cross-cutting hardware-change meta-policy (route to
doca-hardware-safety/SKILL.md); or for
fleet-scale orchestrated provisioning (route via
doca-public-knowledge-map/SKILL.md).
What this skill provides
This is a thin loader. Substantive material lives in two companion files:
the capabilities companion — the BF4 day-1 bring-up contract: the three OS install methods (UEFI HTTP Boot, PXE Boot, Redfish Virtual Media) and the Grace-Ubuntu-plus-cloud-init Virtual Media path; the PLDM firmware-update surface across the platform firmware components; the version-compatibility overlay on
doca-version/SKILL.md(the install and firmware targets come from the public release notes, never from memory); the bring-up error taxonomy (boot-source -> virtual-media-attach -> firmware-Task -> activation -> cloud-init -> boot-loop); the observability surface (the OOB console, the Redfish Task resource, the Redfish FirmwareInventory,pldmtoolGetFwParams, and the installed-build checkcat /etc/mlnx-release); and the safety policy (an overlay ondoca-hardware-safety/SKILL.md: every PLDM burn / ISO reflash / power cycle / BMC factory reset is a MUTATING hardware op; never print a real password; always detach virtual media to avoid boot loops; only public hosts for any NVIDIA URL).the tasks companion — step-by-step workflows for the in-scope bring-up verbs:
configure,build(routing stub),modify(routing stub),run(the three install methods plus the PLDM firmware-update flow plus the Grace-Ubuntu cloud-init path, as###sub-anchors),test(the post-install / post-update verification sweep),debug(the layered bring-up diagnosis), and theDeferred task verbsblock routing BF3 / application-launch / library-API / env-prep / hardware-meta-policy / fleet questions out to their owning skills.
The skill assumes a BlueField-4 target where:
the BMC is reachable out-of-band and the operator has BMC credentials ({bmc-user} / {bmc-password}) they supply — never invented here,
the bundle ISO (and any Grace Ubuntu image / cloud-init config ISO) is downloaded from the public NVIDIA download surface and hosted at {iso-uri},
the operator has read the target firmware and OS versions from the public BlueField/DOCA release notes.
It does not cover installing DOCA tooling on the host — that path goes
through doca-setup/SKILL.md — and it does not cover
running a workload once Grace is up — those paths go through the two
application-deployment skills.
Loading order
Read this skill first to confirm the user's question is in scope (BF4 day-1 bring-up via the BMC; NOT BF3, NOT application launch, NOT a library-API question, NOT the hardware-change meta-policy itself).
For the bring-up contract (the three install methods, the Grace-Ubuntu cloud-init path, the PLDM firmware-update surface, the version overlay, the bring-up error taxonomy, the observability surface, and the BF4 safety overlay), see the capabilities companion.
For step-by-step workflows —
configure,build(routing stub),modify(routing stub),run(with the three install methods, the PLDM flow, and the Grace-Ubuntu cloud-init path as###sub-anchors),test,debug, plus theDeferred task verbsblock — see the tasks companion.Load
doca-hardware-safety/SKILL.mdALONGSIDE whenever the question reaches a mutating step (PLDM firmware burn, ISO reflash, power cycle, BMC factory reset).
Related skills
doca-bf3-deployment/SKILL.md— BF3 RShim/BFB day-1.doca-hardware-safety/SKILL.md— PLDM, reflash, power cycle.doca-bare-metal-deployment/SKILL.md— launch after Grace is up.doca-container-deployment/SKILL.md— service container after Grace is up.doca-setup/SKILL.md— env prep on the installed Grace OS.doca-version/SKILL.md— four-way version match.doca-public-knowledge-map/SKILL.md— public docs and release notes.
Files
- ATTRIBUTION.mdAdded by AutoGineer915 B
- BENCHMARK.md9.9 KiB
- CAPABILITIES.md17.0 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md12.0 KiB
- TASKS.md21.0 KiB
- evals/evals.json2.4 KiB
- references/details.md7.0 KiB
- skill-card.md4.7 KiB
- skill.oms.sig5.1 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
The author says: No DOCA install is required to read this skill; it teaches the documented BlueField-4 BMC-driven bring-up flows (UEFI HTTP Boot, PXE, Redfish Virtual Media, PLDM firmware update). Executing the steps requires a BlueField-4 with an out-of-band-reachable BMC, a host or HTTP/HTTPS server to host the bundle ISO, and the target versions from the public BlueField/DOCA release notes. The validation steps require a live DOCA install.
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- NVIDIA
- Publisher
- NVIDIA (Official)
- Source
- NVIDIA/skills · skills/doca-bf4-deployment · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download doca-bf4-deployment.zip