clm_e8e9e48bc37b40f49f4a418383241264_r1

VR2-0579

① SA Source

• Source: 開啟完整 SA 文章
• Section: GB200 Hardware Architecture - Component Supply Chain & BOM
• Line hint: 701

Context Before

2024年7月17日

Read full story ↗

Evidence

This translates to four NVLink Switch chips per tray on 9 switch trays, or 36 NVLink Switch chips in each rack

Context After

Each VR NVL72 Switch tray contains four NVLink 6 Switch ASICs and one system management module. The design of the Rubin NVLink 6 Switch tray is also simpler and relatively seamless compared to the first Oberon NVLink 5 Switch released for GB200 because Rubin NVLink 6 Switch trays will not use flyover cables. As such, all NVLink signals will run over the PCB.

The NVLink 6 Switch board is liquid cooled and will be covered with a cold plate, which is a single module. Connected to the NVSwitch tray is the system management module (SMM) that comes with a CPU and acts as a host to the switch tray. The switch tray to SMM connection uses flyover cables, but this is the only flyover cable connection required in the entire Vera Rubin NVL72 system. Given that the PCIe connection is lower speed and the NVLink Switch tray contains relatively few modules, assembly of the switch tray is unlikely to be challenging.

② Atomic Claim

具體配置為 9 個 switch trays，每 tray 4 顆 NVLink Switch chips，因此每 rack 共 36 顆 NVLink Switch chips。

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "attribute": "COUNT",
  "context_nodes": [],
  "entity": {
    "id": "04_knowledge_base/NVLink",
    "label": "NVLink"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "9",
      "4",
      "36"
    ],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [
      "9",
      "4",
      "36"
    ],
    "value_text": "具體配置為 9 個 switch trays，每 tray 4 顆 NVLink Switch chips，因此每 rack 共 36 顆 NVLink Switch chips。"
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
entity	NVLink	NVLink

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