VR2R-0586
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Connecting GPUs in the Scale-Out InfiniBand Network - Line hint:
745
Context Before
Connecting GPUs in the Scale-Out InfiniBand Network
Broadly, there are three flavors of scale-out deployments for Vera Rubin NVL72. We have InfiniBand-based clusters which employ the NVIDIA Quantum series of switches, NVIDIA Ethernet-based clusters employing Spectrum series switches and lastly, non-Nvidia Ethernet such as Tomahawk-based, Cisco Silicon One or Teralynx-based Ethernet switches. Some Ethernet-based clusters deployed by hyperscalers will use AECs for NIC-to-TOR and switch-to-switch connections, while other Ethernet-based clusters using only optical interconnects will usually adopt a multi-plane and multi-rail networking architecture. What is particularly noteworthy about Vera Rubin NVL72 deployments, however, is that it is the first Nvidia GPU generation where we will be seeing some Co-Packaged-Optics (CPO) deployments in the scale-out backend network.
Evidence
While there are both InfiniBand and Spectrum-X based clusters, the InfiniBand-based Quantum X800-34XX series of switches is more popular with Neoclouds than with hyperscalers. For InfiniBand, there are two deployment types – the first is the Quantum X800-Q3400 with pluggable optics and the second is the Quantum X800-Q3450 CPO-based switch that use co-packaged Optical Engines (OE) instead of pluggable transceivers.
Context After
The Quantum X800-Q3400 is logically a multi-plane switch combining 4 Quantum-3 ASICs into a single switch box, though we will dive into this equivalence later in the article. This multi-plane “topology” is abstracted away and as far as network engineers are concerned, the Q3400 is a single switch with 144 ports – or a “little boy” switch.

② Atomic Claim
第二種是 Quantum X800-Q3450 CPO-based switch,使用 co-packaged Optical Engines,而不是 pluggable transceivers。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Quantum X800",
"label": "Q3450"
},
"role": "switch_platform"
},
{
"node": {
"id": "04_knowledge_base/CPO",
"label": "CPO"
},
"role": "optical_architecture"
},
{
"node": {
"id": "04_knowledge_base/Optical Engine",
"label": "Optical Engine"
},
"role": "optical_component"
}
],
"qualifiers": {
"condition_text": "second InfiniBand deployment type; uses co-packaged Optical Engines instead of pluggable transceivers; source preserves §9§ reference",
"numeric_mentions": [],
"temporal_mentions": []
},
"relation_type": "Q3450_CPO_USES_COPACKAGED_OPTICAL_ENGINES"
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| switch_platform | Q3450 | 04_knowledge_base/Quantum X800 |
| optical_architecture | CPO | CPO |
| optical_component | Optical Engine | 04_knowledge_base/Optical Engine |
⑤ V2 Draft(需要修正時直接編輯)
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR,再手動執行 Repair Preview。
執行腳本前,Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
第二種是 Quantum X800-Q3450 CPO-based switch,使用 co-packaged Optical Engines,而不是 pluggable transceivers。
V2 Semantic Frame Draft
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Quantum X800",
"label": "Q3450"
},
"role": "switch_platform"
},
{
"node": {
"id": "04_knowledge_base/CPO",
"label": "CPO"
},
"role": "optical_architecture"
},
{
"node": {
"id": "04_knowledge_base/Optical Engine",
"label": "Optical Engine"
},
"role": "optical_component"
}
],
"qualifiers": {
"condition_text": "second InfiniBand deployment type; uses co-packaged Optical Engines instead of pluggable transceivers; source preserves §9§ reference",
"numeric_mentions": [],
"temporal_mentions": []
},
"relation_type": "Q3450_CPO_USES_COPACKAGED_OPTICAL_ENGINES"
}V2 Revision Metadata Draft
{
"epistemic_mode": "ASSERTED",
"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 才是正式決策。