clm_c38664adbfab43c0839acfb2d61dd1b9_r1

VR2-0617

① SA Source

• Source: 開啟完整 SA 文章
• Section: Connecting GPUs in the Scale-Out InfiniBand Network
• Line hint: 743

Context Before

Source: Nvidia VR NVL72 Component BoM and Power Budget Model

Connecting GPUs in the Scale-Out InfiniBand Network

Evidence

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

Context After

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.

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

第三類則是非 Nvidia Ethernet 方案。

• Epistemic Mode: ASSERTED
• Mapping Status: PARTIAL

③ Semantic Frame

{
  "attribute": "UNSPECIFIED_ATTRIBUTE",
  "context_nodes": [
    {
      "id": "04_knowledge_base/Ethernet",
      "label": "Ethernet"
    }
  ],
  "entity": {
    "id": "02_companies/NVDA",
    "label": "Nvidia"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [],
    "value_text": "第三類則是非 Nvidia Ethernet 方案。"
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
entity	Nvidia	NVDA
context_0	Ethernet	Ethernet

⑤ 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 才是正式決策。