doca-comm-channel-admin

Enumerate host-DPU DOCA comch servers and connections via the doca_comm_channel_admin binary.

3.2k|370|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/NVIDIA/skills --skill doca-comm-channel-admin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doca-comm-channel-admin
Source: https://github.com/NVIDIA/skills/tree/main/skills/doca-comm-channel-admin
Command: npx skills add https://github.com/NVIDIA/skills --skill doca-comm-channel-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Operators and developers working with NVIDIA DOCA on BlueField DPUs need a reliable way to see which comch (Comm Channel) servers and connections are active on a host or DPU, and to verify that the admin tool's view matches what their program reports. This Skill teaches an agent to use the shipped read-only doca_comm_channel_admin binary correctly, avoiding invented subcommands and misdiagnosis of empty output.

Core Features & Use Cases

  • Single-shot channel inventory: Run the zero-argument scan-and-print binary to list every comch-capable device and decode the SERVERS and CONNECTIONS tables (server name, PID, in-use/max counts, PCIe address).
  • Cross-side verification: Cross-check the admin tool's printed rows against the program-side doca_comch connection callback, and run the same scan on the other side of the host↔DPU pair when views disagree.
  • Layered diagnosis: Walk a six-layer error taxonomy (tool-not-installed, resourcedump/MFT prerequisite, device-binding, row-discovery, version mismatch, cross-cutting) before interpreting empty or mismatched output.
  • Use Case: A developer sees their Comch program report CONNECTED but wants external confirmation; the agent runs the zero-argument scan, quotes the matching row, and confirms both sides agree before any code change.

Quick Start

Ask your agent to list the active comch servers and connections on this BlueField using the doca_comm_channel_admin tool.

Frequently Asked Questions about doca-comm-channel-admin

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list active DOCA comch servers and connections on a BlueField DPU?

Run /opt/mellanox/doca/tools/doca_comm_channel_admin with zero application arguments. It scans every comch-capable device on the current side via resourcedump and prints SERVERS and CONNECTIONS tables with server name, PID, in-use/max counts, and PCIe address.

How do I verify the admin tool sees the same channel as my comch program?

Run the zero-argument scan, locate the expected row in the printed tables, and compare it against the program-side doca_comch connection callback state. If the row is absent after a clean exit, run the same scan on the other side of the host-DPU pair.

Does doca_comm_channel_admin support list, inspect, drain, or restart subcommands?

No. The binary is a single-shot scan-and-print tool with no registered application arguments beyond ARGP defaults like --help and --version. Channel reset or drain belongs to the doca-comch program side or driver reload workflows, not this tool.

Why does the DOCA Comm Channel Admin Tool print empty tables?

Empty output is often a setup failure, not an empty inventory. Check that MFT is installed, resourcedump resolves through PATH, and privileges are sufficient; any non-zero child exit or stderr must be resolved before interpreting the tables as showing no channels.

Can I use the Comm Channel Admin Tool on DOCA 2.5 or newer?

Yes. The tool still ships under the Comm Channel name even though the companion library was renamed to doca-comch in DOCA 2.5. Confirm the tool version matches the comch library it inspects to avoid partial-install mismatches.

When should I use doca-comch instead of the Comm Channel Admin Tool?

Use doca-comch for anything programmatic: creating channels, the comch API, protocol design, or changing channel state. The admin tool is read-only inventory only and cannot modify, reset, or configure channels.