"Plugged in" is not "verified." This domain is about proving every link meets spec — with inspection, loss testing, and the Cable Validation Tool — and leaving documentation the operations team can actually trust.
A cluster with thousands of links can't be trusted on faith. Domain 6 proves you can confirm each connection performs to spec and hand the operations team an accurate as-built record. Skip verification and marginal links surface later as random training-job failures no one can explain.
The verification workflow has a natural order: inspect the connectors, validate the links (loss + connectivity), run the Cable Validation Tool at the fabric level, then document everything.
Verification starts before the connector is even mated. Because contamination is the top cause of fiber problems (Domain 4), every end-face is inspected with a fiber inspection scope and graded against a cleanliness standard (the industry uses IEC end-face criteria) before mating.
Inspect → clean if needed → re-inspect → connect. Never mate a connector you haven't verified is clean, and cap unused connectors so they stay that way.
Once mated, links are tested to confirm they'll actually carry traffic. Know what each tool proves.
| Test / tool | What it verifies | Why it matters |
|---|---|---|
| Fiber inspection scope | End-face cleanliness & damage | Catches the #1 failure cause before it's in service |
| Insertion-loss test (light source + power meter / OLTS) | Total optical loss (dB) vs the loss budget | Confirms the channel is within tolerance end to end |
| Continuity / polarity check | Every fiber maps TX→RX correctly | Catches polarity and mis-wiring errors |
| Link-up & error counters | Transceiver trains and runs clean (no errors) | A link that comes up can still be marginal — counters reveal it |
Link-up ≠ healthy. A connection can negotiate and appear "up" while quietly logging errors or sitting near its loss limit. Verification means testing against the spec (loss budget, clean counters), not just seeing a green light.
Testing single links is necessary but not sufficient — a large fabric also has to be validated as a whole. That's what the Cable Validation Tool (CVT) does. It's NVIDIA's tool (associated with UFM, Unified Fabric Manager) for validating and monitoring the cabling of high-speed interconnects, particularly in DGX SuperPOD-class deployments.
Confirms cables land where the design says — catching mis-cabled or swapped connections across the fabric.
Surfaces cable/port health so marginal links are found before they cause job failures.
Exposes a Prometheus-compatible metrics endpoint, so results plug into monitoring stacks (Prometheus/Grafana).
Can be deployed and managed as a service for persistent, automated validation.
NVIDIA offers a free, self-paced Cable Validation Tool (CVT) Fundamentals course. It maps directly onto this domain — take it.
The deployment isn't done until it's documented. The operations team inherits whatever record you leave — and troubleshoots against it for years.
Undocumented or inconsistently labeled cabling is treated as an incomplete install. In a fabric of thousands of links, an unlabeled cable is nearly impossible to trace — labeling and as-built docs are part of the job, not an afterthought.
Verification questions reward knowing what each test proves and why documentation matters. Rehearse with explained answers.
Practice Testing & Verification →NCP-ARI-style questions on Domain 6. Choose an answer to see the explanation.
Pick the verification topic you want to shore up.
Tap a card to flip it.
For educational use only · Not affiliated with or endorsed by NVIDIA Corporation. Tooling and standards references (CVT, IEC end-face grading, TIA-606 labeling) follow published NVIDIA and industry documentation and can change; confirm specifics in the CVT documentation and applicable standards.
