Skip to main content
Challenge

Build an Accelerator Interconnect Diagnosis and Packet Loss Reviewer

Analyze multi-GPU node interconnect counters and fabric error flags. Isolate degraded PCIe and NVLink links causing distributed all-reduce slowdowns and propose hardware repair actions.

EngineeringHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Analyze multi-GPU node interconnect counters and fabric error flags. Isolate degraded PCIe and NVLink links causing distributed all-reduce slowdowns and propose hardware repair actions.

Cluster Network Engineer

Ingest normalized interconnect counter logs, CRC error rates, and replay counts.

Correlate interconnect packet drops with collective all-reduce latency degradation.

Prompt hosted Claude to inspect fabric topology anomalies and pinpoint failing lanes.

Synthesize a hardware maintenance ticket with port isolation and replacement guidance.

Network topology graph visualizer highlighting degraded links with click-to-generate repair tickets.

Construct synthetic interconnect telemetry tables recording link CRC errors, replay events, and NVLink/PCIe port states across 8-GPU nodes. Starter examples below are synthetic. They are not downloaded records.

NVIDIA DCGM exporter Extracts DCGM NVLink error metrics, replay counters, and bandwidth saturation indicators from the DCGM exporter counters.

anthropic-claude, pydantic-ai. Interprets multi-hop interconnect error patterns and drafts clear, actionable physical maintenance steps. Hosted Claude API for topological reasoning and maintenance ticket drafting. No access to proprietary cloud network routing.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Identifies failing interconnect links based on replay threshold exceedance (>1000/hr).

Correlates link errors with distributed collective step latency degradation.

Outputs structured repair tickets specifying switch port, GPU index, and replacement part.

```json [ { "input": { "node_id": "hpc-gpu-node-12", "fabric_errors": [ { "gpu_src": 2, "gpu_dst": 3, "link_id": "nvlink-1", "crc_errors": 45120, "replay_count": 8900 }, { "gpu_src": 0, "gpu_dst": 1, "link_id": "nvlink-0", "crc_errors": 0, "replay_count": 0 } ], "step_time_ms": 340.5, "baseline_step_time_ms": 180 }, "expected_output": { "fault_detected": true, "isolated_component": "GPU 2 -> GPU 3 NVLink 1", "degradation_pct": 89.2, "repair_action": "Reseat high-speed mezzanine interconnect or replace interposer ribbon cable on slot 2-3", "ticket_priority": "urgent" } }, { "input": { "node_id": "hpc-gpu-node-03", "fabric_errors": [ { "gpu_src": 0, "gpu_dst": 1, "link_id": "nvlink-0", "crc_errors": 2, "replay_count": 1 } ], "step_time_ms": 181.2, "baseline_step_time_ms": 180 }, "expected_output": { "fault_detected": false, "isolated_component": "None", "degradation_pct": 0.6, "repair_action": "Maintain routine monitoring; error rate within allowable transient threshold", "ticket_priority": "low" } } ] ```

Diagnostic analysis only; does not reset physical PCIe registers or disable cluster switch fabrics. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Diagnostic analysis only; does not reset physical PCIe registers or disable cluster switch fabrics. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Identifies failing interconnect links based on replay threshold exceedance (>1000/hr). Correlates link errors with distributed collective step latency degradation. Outputs structured repair tickets specifying switch port, GPU index, and replacement part.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest normalized interconnect counter logs, CRC error rates, and replay counts. Correlate interconnect packet drops with collective all-reduce latency degradation. Prompt hosted Claude to inspect fabric topology anomalies and pinpoint failing lanes. Synthesize a hardware maintenance ticket with port isolation and replacement guidance.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Identifies failing interconnect links based on replay threshold exceedance (>1000/hr). Correlates link errors with distributed collective step latency degradation. Outputs structured repair tickets specifying switch port, GPU index, and replacement part.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Network topology graph visualizer highlighting degraded links with click-to-generate repair tickets.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Diagnostic analysis only; does not reset physical PCIe registers or disable cluster switch fabrics.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest normalized interconnect counter logs, CRC error rates, and replay counts.

  • Correlate interconnect packet drops with collective all-reduce latency degradation.

  • Prompt hosted Claude to inspect fabric topology anomalies and pinpoint failing lanes.

  • Synthesize a hardware maintenance ticket with port isolation and replacement guidance.

Resources and assets

Reference links and supporting material

Dataset notes

Construct synthetic interconnect telemetry tables recording link CRC errors, replay events, and NVLink/PCIe port states across 8-GPU nodes. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Anthropic Claude

LLM for code generation & more

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest normalized interconnect counter logs, CRC error rates, and replay counts. Correlate interconnect pac...
  • Identifies failing interconnect links based on replay threshold exceedance (>1000/hr). Correlates link erro...
  • Network topology graph visualizer highlighting degraded links with click-to-generate repair tickets.
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 1 configured tool

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • Anthropic Claude · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build an Accelerator Interconnect Diagnosis and Packet Loss Reviewer