doca-firefly

Configure and debug the DOCA Firefly PTP time-synchronization container on BlueField.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying PTP-grade time synchronization on NVIDIA BlueField is error-prone: operators must pick the correct PTP role, profile, domain, and interface, wire the host clock follower to the BlueField PHC, and diagnose layered failures where the container runs but time never syncs. This Skill guides agents through operating the DOCA Firefly Service container correctly end to end.

Core Features & Use Cases

  • Four-axis PTP configuration: Decide role (master/slave/boundary/transparent clock), profile (default/media/telco-l2/custom), domain number, and network interface before starting the container.
  • End-to-end discipline wiring: Connect the three mandatory legs — Firefly-disciplined BlueField PHC, host-side follower (chrony/ptp4l/phc2sys), and the consumer workload (Rivermax SMPTE, 5G UPF, finance, distributed databases).
  • Layered debug taxonomy: Diagnose failures across five layers — container runtime, four-axis config mismatch, host follower, non-PTP-aware network path, and consumer workload.
  • Use Case: A broadcast engineer deploying SMPTE ST 2110 over Rivermax gets guided through choosing the media profile, confirming PTP reaches SLAVE state, wiring chrony to the PHC, and smoke-testing before going live.

Quick Start

Ask your agent: "My Firefly container is running but PTP never advances past LISTENING — walk me through the four-axis configuration check."

Frequently Asked Questions about doca-firefly

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

FAQPage Schema
How do I configure DOCA Firefly PTP on BlueField?

Decide four axes before starting the container: PTP role (master, slave, boundary, or transparent clock), profile (default, media, telco-l2, or custom), domain number matching the upstream master, and a wire-side interface with hardware timestamping. Derive the config file from the public DOCA Firefly Service Guide.

When should I use Firefly PTP instead of chrony or NTP?

Use Firefly only when the workload needs sub-microsecond PTP-grade precision, such as SMPTE ST 2110 broadcast, 5G UPF, or financial trading, and a PTP-aware network path exists. If chrony or NTP already meets your precision budget, keep it and do not deploy Firefly.

Why does Firefly say synced but the host clock still drifts?

Firefly only disciplines the BlueField PHC; it does not discipline the host clock. You must configure a host-side follower such as chrony with the PHC source or ptp4l/phc2sys reading the PHC, then verify with chronyc tracking.

Why is my Firefly container green but PTP stuck at LISTENING?

This indicates a four-axis configuration mismatch: role, profile, domain, or interface disagrees with the upstream PTP infrastructure. Walk each axis against the upstream master and use tcpdump on the configured interface to confirm PTP frames and matching domain numbers.

Does Firefly work with Rivermax SMPTE ST 2110 workloads?

Yes, Firefly is the time-source side of the Rivermax pairing. It disciplines the BlueField PHC with the media profile (SMPTE 2059-2), while the Rivermax workload reads the disciplined PHC; both skills load together for broadcast deployments.

Can Firefly fix high jitter caused by a non-PTP-aware switch?

No. If sync is acquired but offset and jitter exceed the profile spec due to a non-PTP-aware switch, the fix is network-side: insert boundary clocks or replace the switch with a PTP-aware one. No Firefly config knob can correct path latency.