DOCA Firefly Time-Synchronization Operations
Operate, configure, and troubleshoot DOCA Firefly PTP time synchronization on BlueField.
The material scopes the skill to BlueField Arm, a container, selected interfaces, and paired workloads; it requires deciding whether PTP is needed, emphasizes the end-to-end clock chain, prohibits speculative deployment, and shows no malware, credential theft, or covert exfiltration. Points are deducted because PHC, host-clock, container, and network changes can have external effects without an explicit confirmation gate, least-privilege checklist, or complete rollback procedure. License and provenance metadata also conflict across the supplied files.
SKILL.md, CAPABILITIES.md, and TASKS.md provide a generally coherent configure, run, test, and layered-debug workflow with symptom-to-owner mapping. Points are deducted because this is static-only review with no executed reproduction, no committed executable deployment configuration or complete key-path test suite, and substantial dependence on external documentation. The six-subsystem statement is contradicted by a later reference to all five subsystems, and the supplied TASKS evidence is truncated at the end.
Audience, positive triggers, implicit examples, and non-fit boundaries are unusually explicit, and the material separates Firefly from the host follower, consumer workload, and other DOCA skills. Points are deducted because Chinese-language support is not documented, mainland-China reachability of NGC and public documentation is unverified, and deployment compatibility still depends on user-specific versions, runtimes, and PTP topology.
The layered SKILL.md, CAPABILITIES.md, TASKS.md, benchmark, and skill-card structure supports progressive disclosure and includes version guidance, related skills, limitations, maintenance contacts, and evaluation material. Points are deducted for missing recommended Instructions and Examples sections, unresolved schema findings in the benchmark, TBD signature/version fields, inconsistent repository/license declarations, and no clear changelog or stable maintenance commitment.
The skill offers directly useful decision and troubleshooting flows for determining whether Firefly is needed, selecting PTP axes, diagnosing host-clock drift, and isolating failures by layer. Points are deducted because it intentionally omits image tags, complete configuration files, exact deployment commands, and host-follower configuration, requiring external guides and other skills. Static evidence therefore does not establish directly usable completion of the operator's task.
The files identify a public DOCA Firefly Service Guide, name concrete symbols and command classes, and include an internal benchmark report. Points are deducted because the public source URL is not supplied directly, the benchmark dataset is unavailable and cannot be reproduced here, and no inspectable CI workflow, committed test suite, or independent corroboration covers the key paths.
- Do not treat the internal benchmark PASS result or NVIDIA identity as a substitute for evidence of this skill's reliability, safety, or effectiveness.
- Before deployment, verify the version-matched official Firefly guide, image tag, configuration schema, permissions, and host follower; the supplied files contain subsystem-count and license/provenance inconsistencies.
- Obtain confirmation before changes affecting the PHC, host clock, PTP interface, or network path, and prepare verifiable recovery steps.
What does this skill do, and when should you use it?
This skill is for external operators and platform teams running the DOCA Firefly Service container on BlueField Arm. It helps choose the PTP role, profile, domain, and interface, then connect the BlueField PHC to a host-side follower and a timing-sensitive workload. It covers Firefly’s PTP, PTP Monitor, internal PHC2SYS, PPS, SyncE, and Firefly Servo subsystems, along with observability and troubleshooting. Firefly is a poor fit when chrony or NTP already meets the workload’s precision budget or when the network path is not PTP-aware.
Guides installation from the NVIDIA skills collection; assesses whether PTP-grade time is needed; configures and operates the Firefly container on BlueField Arm; checks configuration files, environment variables, container logs, PHC offset, and port state; diagnoses role, profile, domain, interface, host-follower, PTP-path, and container-runtime problems; and explains pairing Firefly with Rivermax SMPTE workloads.
- A BlueField platform team needs PTP-grade time for a Rivermax SMPTE ST 2110 workload.
- An operator has a healthy Firefly container whose PTP state remains LISTENING.
- Firefly reports synchronization, but the host clock continues to drift.
- PTP is locked, but offset or jitter is in the tens of microseconds.
- A team is deciding whether existing chrony/NTP is sufficient for a distributed database, 5G UPF, or financial workload.
What are this skill's strengths and limitations?
- Covers six Firefly PTP-stack subsystems instead of treating Firefly as only a PTP daemon.
- Clearly separates Firefly, the BlueField PHC, the host-side follower, and the consumer workload.
- Organizes deployment and debugging around role, profile, domain, and interface decisions.
- Explicitly routes users away when chrony/NTP is sufficient or the path lacks PTP support.
- Requires DOCA, BlueField Arm, a container runtime, and a PTP-aware network path.
- Does not ship production-ready Firefly configuration files, image tags, or host-side time-sync configuration bodies.
- Does not replace DOCA installation, PTP topology design, host chrony/ptp4l configuration, or application-development guidance.
How do you install this skill?
Install it from the NVIDIA skills collection with: npx skills add nvidia/skills --skill doca-firefly --yes. The source does not require a separate manual folder-copy procedure.
How do you use this skill?
Load the skill in an Agent Skills-compatible client and ask a concrete operations question, such as: “Firefly says it is synced, but the host clock still drifts—what should I check?” Before deployment, confirm that DOCA is installed on BlueField Arm and prepare the Firefly configuration, a reachable PTP master or master role, a PTP-aware network path, and a host-side time follower. The source does not provide exact container image tags, complete configuration blocks, or host chrony/ptp4l/phc2sys configuration bodies.
How does this skill compare with similar options?
The skill compares Firefly with host-side NTP/chrony for path selection: keep the existing NTP/chrony setup when it meets the workload’s precision budget; consider Firefly when PTP-grade precision is required.