VR-COV-VR-CON-COMPARE
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Replacing Internal Cables with Board-to-Board Connectors - Line hint:
395
Context Before
For the GB200/300, the most valuable cable that is exclusively supplied by Amphenol is the DensiLink OverPass cable set within the compute tray. This cable provides the ethernet connection between the CX-7/8 NIC and the OSFP cages. However, this cable is extremely vulnerable to scratches and damage of the cable termination during assembly, thereby creating many points of failure. There are also several other lower-end PCIe cables in use (MCIO and SlimSAS) that also suffer from the same points of failure. These cables involve many other suppliers as well – complicating procurement and vendor management. Given the delicate nature of the cable, workers must be extremely careful while placing the cables in a very dense and compact chassis, which prolongs assembly time.
Although a cableless design might initially appear unfavorable for Amphenol, it is in fact a positive. Signals between the Strata module and the daughter modules still need a physical interconnect. In this architecture, those signals exit the Strata board through Amphenol’s PaladinHD2 board-to-board connectors. The signal is then routed through a PCB midplane sitting in the middle of the chassis. On the other side of the PCB midplane, the daughter modules connect to the PCB midplane via another set of Paladin HD2 B2B connectors. In our VR NVL72 Component BoM and Power Budget Model ↗ we have a detailed breakdown of Amphenol’s compute tray content in Vera Rubin NVL72. This is also discussed in more detail in our article on **Amphenol’s AI Content. ↗ **
Evidence
Context After
Source: Nvidia VR NVL72 Component BoM and Power Budget Model ↗
Relocating ConnectX-9
② Atomic Claim
The Amphenol content table specifies 22 Paladin HD2 board-to-board connectors per VR NVL72 compute tray.
- Epistemic Mode:
ATTRIBUTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "PALADIN_HD2_CONNECTORS_PER_TRAY",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/VR NVL72",
"label": "VR NVL72"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [
"22"
],
"value_text": "22"
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | VR NVL72 | 04_knowledge_base/VR NVL72 |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
The Amphenol content table specifies 22 Paladin HD2 board-to-board connectors per VR NVL72 compute tray.
V2 Semantic Frame Draft
{
"attribute": "PALADIN_HD2_CONNECTORS_PER_TRAY",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/VR NVL72",
"label": "VR NVL72"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [
"22"
],
"value_text": "22"
}
}V2 Revision Metadata Draft
{
"epistemic_mode": "ATTRIBUTED",
"mapping_status": "COMPLETE"
}⑥ Human Review
請在 Properties 逐項確認：
- 原文 → Atomic Claim 是否忠實
- Atomic Claim → Semantic Frame 是否忠實
- Canonical Entity mapping 是否正確
- Epistemic mode 是否保留原文語氣
- 最後選擇
review_action
Review state
Markdown 內文不是正式 approval。只有 Apply bridge 寫入的 Decision Ledger event 才是正式決策。