Generated banner for Doca Dms
Generated logo for Doca Dms

Doca Dms

NVIDIAOfficialCreated by NVIDIA

  • Skill
  • Tool integration
  • Cloud and DevOps
  • Apache-2.0
  • Medium risk

From the author

Operate NVIDIA DOCA Management Service on a BlueField, Arm/x86 host, or Kubernetes pod: from DOCA 3.5 the local `dms-cli` (one command per YANG path, no server), and the `dmsd` + `dmspe` service: choose deployment and authentication, configure `-allowed_users` and `dmsgroup`, use gNMI Get/Set, run supported gNOI workflows, and debug frontend/backend failures. Trigger even without "DMS" for "manage a remote BlueField over gRPC", "gNOI reboot from orchestrator", or fleet-management requests. SAFETY: reboot, OS install, factory-reset, and managed-file deletion are destructive and require target-bound explicit confirmation; never invoke them speculatively. Route installation and library/API build questions elsewhere, and route telemetry streaming and aggregation to doca-dts (DOCA Telemetry Service).
— the description by NVIDIA

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The doca-dms skill provides operational guidance for the NVIDIA DOCA Management Service (DMS). It covers the deployment, configuration, and management of the dmsd and dmspe services on host systems, BlueField DPUs, or Kubernetes pods. The skill focuses on using gNMI for configuration and gNOI for lifecycle management, while emphasizing strict safety protocols for destructive operations like reboots and factory resets. It is designed for operators managing networking platforms from a centralized control plane.

What it does

  • Guides the configuration of dmsd and dmspe services for various deployment topologies.
  • Supports gNMI Get/Set operations for managing device settings via YANG paths.
  • Facilitates gNOI workflows including reboots, OS installs, and factory resets.
  • Provides debugging procedures for frontend and backend service failures.
  • Enforces mandatory safety confirmation protocols for destructive hardware operations.
  • Assists in setting up authentication modes and managing user access boundaries.

When to use it

  • When deploying or configuring the DMS daemon on a management endpoint.
  • When performing remote management of BlueField or ConnectX devices via gRPC.
  • When executing gNOI lifecycle operations like system reboots or firmware updates.
  • When troubleshooting errors between the DMS frontend and backend components.
  • When determining the appropriate authentication and security posture for DMS.

Advantages

  • Provides a structured approach to managing complex DPU/SmartNIC environments.
  • Ensures operational safety through explicit confirmation requirements for destructive tasks.
  • Standardizes interaction with hardware via industry-standard gNMI/gNOI protocols.
  • Clearly separates operational tasks from development or library-level programming.

Usage examples

“How do I read a BlueField setting locally using dms-cli?”
The agent will guide you to use dms-cli with the appropriate YANG path, suggesting the use of --tree to explore available paths before reading or modifying values.
“Trigger a clean reboot of the target via gNOI.”
The agent will identify the gNOI reboot operation as destructive, require target-bound explicit confirmation, and then provide the necessary gNOI command sequence.
“My DMS request failed; how do I debug it?”
The agent will walk you through the layered debug process to determine if the error originated in the dmsd frontend or the dmspe backend.
“Which authentication mode should I pick for a multi-tenant environment?”
The agent will reference the auth-mode trade-off table to help you select the appropriate security configuration for your specific environment.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/nvidia/doca-dms/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip doca-dms.zip -d .agents/skills

Documentation by NVIDIA

DOCA Management Service (DMS)

Examples

  • "Read or change a BlueField setting locally." — use dms-cli (DOCA 3.5+); explore the path with --tree first.

  • "Manage a remote BlueField over gRPC." — this is in scope. Use dmsd + dmspe with the chosen auth; do not drop to ad-hoc SSH for the management plane.

  • "gNOI reboot from orchestrator." — treat reboot / OS install / factory-reset as destructive: require target-bound explicit confirmation first.

Instructions

Follow Loading order below. Open the tasks companion for configure / gNMI / debug. Open the capabilities companion for auth and gNOI scope. Do not open every companion file.

⚠️ Destructive operations. The gNOI reboot, OS install, factory-reset, and managed-file deletion operations are irreversible and service-impacting — they can take a production BlueField or ConnectX offline or wipe its configuration. Before issuing any of them the agent MUST: (1) verify the target device identity, and (2) obtain explicit confirmation bound to that target and action. In an interactive session this is an explicit user reply naming/accepting both; in unattended execution it must be an approved-system authorization artifact bound to both. Otherwise stop with confirmation_required. Never invoke them speculatively or as a side effect of another task. See the public DMS guide's safety guidance for these operations.

Where to start: This skill is for operating DMS, not for linking against a library. If the user wants to deploy or run the daemon, open the tasks companion and start at ## configure. If the question is what shape of service is DMS and what protocols does it speak, start at the capabilities companion. If DOCA is not installed on the management endpoint yet, route to doca-setup/SKILL.md first.

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.

DOCA 3.5 and later: start with dms-cli. The DMS guide now centres on /opt/mellanox/doca/services/dms/dms-cli, run directly on the host or BlueField Arm with no server or daemon. One syntax per YANG path: dms-cli -t pci/<BDF> /nvidia/mode/operating-mode reads a value, the same path plus a value sets it, and action paths run operations. Explore before writing: --tree /nvidia, --describe <path> and list-xpaths <path>; script with --json; validate with --dry-run. VFs and SFs take -t pci/<BDF>,pf<N>vf<M> or pf<N>sf<M>. On DOCA 3.5: as a normal user it fails with backend fork/exec .../dmspe: permission denied — run it with sudo or add the user to dmsgroup; some example paths do not exist on every device (for example congestion-control slots are under /nvidia/cc/algo/slot there), so confirm every path with --tree / list-xpaths before using it. Firmware or BFB installs (/nvidia/provisioning/install), resets and mode changes are hardware-state changes: follow doca-hardware-safety. The dmsd + dmspe gRPC (gNMI / gNOI) service below remains for remote and fleet management.

Example questions this skill answers well

Never invent the image tag. It comes from the NGC catalog's DOCA org or the DMS page on docs.nvidia.com, not from memory — a plausible tag reads as authoritative and mismatches the installed DOCA. Cite where it came from, or send the user to look it up.

The CLASSES of DMS questions this skill is built to answer, each with one worked example. The class is the load-bearing piece; the worked example is one instance.

  • "Where should DMS run for my target topology?" — worked example: "I have a host without a DPU; can I still manage a remote ConnectX?". Answered by the deployment-shape decision in the capabilities companion

    • the tasks companion.

  • "Which authentication mode should I pick for my security posture?" — worked example: "a multi-tenant production env vs a single-tenant lab". Answered by the auth-mode trade-off table in the capabilities companion

    • the auth-wiring step in the tasks companion.

  • "How do I issue a gNMI Get / Set against a modeled path?" — worked example: "set /interfaces/interface/config/mtu on a remote interface". Answered by the gNMI/gNOI surface in the capabilities companion

    • the request-shape workflow in the tasks companion.

  • "How do I run a gNOI operation (reboot, OS install, file transfer)?" — worked example: "trigger a clean reboot of the target via gNOI". Answered by the gNOI catalog in the capabilities companion

    • the run workflow in the tasks companion.

  • "My DMS request returned an error — was it the frontend or the backend?" — worked example: "mlxconfig failed under DMS but works on the shell". Answered by the frontend-vs-backend split in the capabilities companion

    • the layered ladder in the tasks companion.

  • "Where do I read DMS logs and how do I rotate them?" — worked example: "persistent log directory + journald + log-rotation policy". Answered by the logging surface in the capabilities companion

    • the log-rotation step in the tasks companion.

Audience

This skill serves external operators and platform teams who deploy and operate DMS to manage NVIDIA® BlueField® networking platforms or NVIDIA® ConnectX® SmartNICs from a centralized control plane. Concretely: people running dmsd, integrating gNMI/gNOI clients against it, choosing an authentication mode, or wiring DMS into a Kubernetes deployment.

It is not for NVIDIA developers contributing to DMS itself, and it is not a programming guide for building applications on top of DOCA libraries (that is doca-programming-guide plus the matching library skill under libs/). DMS is a service, not a library: the user invokes it as a daemon and talks to it over gRPC; they do not link against libdms.so to write their own program.

Status note. Per the public DMS guide, DMS is currently in beta, with General Availability scoped to SPC-X use cases. The skill reflects the public guide's posture: prescribe the documented launch / auth / deployment paths, follow the documented security best practices, and defer roadmap and GA-scope questions to the live public guide rather than guessing.

When to load this skill

Load this skill when the user is doing hands-on DMS operation work against a BlueField or ConnectX target where DOCA is already installed on the management endpoint (host, DPU, or pod). Concretely:

  • Deciding where DMS should run (host non-DPU / BlueField Arm / Kubernetes pod) for a given target topology.

  • Bringing up the dmsd daemon — choosing SystemD vs manual launch, selecting an authentication mode, wiring -allowed_users (the gRPC client authorization boundary) and, if needed, dmsgroup (the dmspe backend-helper Unix group).

  • Issuing gNMI Get / Set requests against modeled paths (e.g. /interfaces/interface/config/mtu).

  • Issuing gNOI operations: OS install, reboot, file transfer, factory-reset, mlxconfig, containerz.

  • Choosing an authentication mode (localhost / PAM / credentials / mTLS) and understanding the security trade-offs the public guide calls out.

  • Reading or rotating DMS logs, configuring config persistency, or recovering from a crashed daemon.

  • Debugging a DMS request that returned an error — separating "frontend rejected before reaching backend" from "backend executed and the underlying tool (e.g. mlxconfig) failed".

Do not load this skill for general DOCA orientation, install of DOCA itself, or library-API questions. For those, route via doca-public-knowledge-map/SKILL.md, doca-setup/SKILL.md, or the matching libs/<library> skill.

What this skill provides

This is a thin loader. Substantive material lives in two companion files:

  • the capabilities companion — DMS architecture (frontend dmsd / privileged backend dmspe), management protocols (gNMI, gNOI), the YANG-based unified configuration dictionary, deployment shapes, authentication modes with their security trade-offs, the configuration-persistency model, the logging surface, and DMS's documented security posture.

  • the tasks companion — step-by-step workflows for the in-scope DMS verbs: configure, build, modify, run, test, debug, plus a Deferred task verbs block routing out-of-scope questions.

The skill assumes a host where DOCA is already installed and the operator has root / sudo access where the public guide says it is required. It does not cover installing DOCA — that path goes through doca-setup/SKILL.md.

What this skill deliberately does not ship

This skill is agent guidance, not a templates or sample-config bundle. To keep the boundary clean, it deliberately does not contain — and pull requests should not add:

  • Pre-baked DMS configuration files (YANG instance documents, full-stack example configs, ready-to-run dmsd flag bundles) intended to be copy-pasted into production. Configs are deployment- specific and the safe answer for an external operator is to derive them from the public guide against their own target. The agent's job is to prescribe the procedure and quote the documented flags and paths, not to ship a config the user might run unmodified.

  • Pre-written gNMI / gNOI client programs in any language. The client surface is standard gNMI / gNOI (publicly documented); the skill describes which paths and operations DMS supports, not how to build a gRPC client in language X.

  • TLS material, credentials, or PAM stanzas. These are user-environment artifacts; the skill points at the documented configuration knobs and the documented security best practices and stops there.

  • A samples/, templates/, or reference/ subtree of any kind. A mock or incomplete artifact in this skill's tree, even one labeled "reference", is misleading: operators will read it as production-ready.

Loading order

  1. Read this skill first to confirm the user's question is in scope.

  2. For the DMS architecture, deployment shapes, auth modes, protocol/path inventory, persistency, logging, and security posture, see the capabilities companion.

  3. For step-by-step workflows — configure, build, modify, run, test, debug — see the tasks companion.

  4. Apply the destructive-operation gate in every phase. Before any gNOI OS install, reboot, factory reset, or managed-file deletion — including a test or debug action — verify the exact target and obtain explicit confirmation for that specific operation using the interactive or approved-system mechanism defined in the warning above. No earlier confirmation or workflow phase carries authorization forward.

  • doca-public-knowledge-map/SKILL.md — the routing table to the public DMS guide and the rest of the public DOCA documentation set.

  • doca-setup/SKILL.md — env preparation and install verification on the host where dmsd will run, including the I have no install yet path via the public NGC DOCA container. This skill assumes its preconditions are satisfied at the management endpoint.

  • doca-programming-guide/SKILL.md — general DOCA patterns. DMS is service-shaped not library-shaped, so the build / modify / first-app pattern there does not apply directly, but the cross-library DOCA_ERROR_* taxonomy and the layered-debug order remain useful when DMS reports errors that originated in a DOCA library it called.

Files

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: DOCA service shipped with the DOCA install at /opt/mellanox/doca on the management endpoint (x86 host (non-DPU), BlueField Arm, or Kubernetes pod) on Linux (Ubuntu 22.04/24.04 or RHEL/SLES); `dmsd` + `dmspe` run there, and DMS is also pulled as an NGC container image. Verify the public DMS guide version matches the installed DOCA release before quoting flags or YANG paths. 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-dms · 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-dms.zip