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."