clm_e31227256f4d4934a4b0cf19a1ff835e_r1

VR2-0581

① SA Source

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

Context Before

Read full story ↗

Although the NVLink 6 Switch used in the VR NVL72 system delivers the same per switch 28.8T aggregate bandwidth as NVLink 5 Switch, the SerDes speed on the NVLink 6 Switch is double the SerDes speed of NVLink 5 Switch but with the same number of DPs. As such, in order to deliver double the aggregate scale-up bandwidth required for NVLink 6, Vera Rubin NVL72 racks will contain double the number of NVLink Switches as compared to GB200 racks. This translates to four NVLink Switch chips per tray on 9 switch trays, or 36 NVLink Switch chips in each rack.

Evidence

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

Context After

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

Rubin NVLink 6 Switch tray 相較 GB200 首代 Oberon NVLink 5 Switch 更簡化且更 seamless，因 Rubin NVLink 6 Switch trays 不使用 flyover cables。

• Epistemic Mode: ASSERTED
• Mapping Status: PARTIAL

③ Semantic Frame

{
  "comparison_expression": "Rubin NVLink 6 Switch tray 相較 GB200 首代 Oberon NVLink 5 Switch 更簡化且更 seamless，因 Rubin NVLink 6 Switch trays 不使用 flyover cables。",
  "entities": [
    {
      "id": "04_knowledge_base/Vera Rubin",
      "label": "Rubin"
    },
    {
      "id": "04_knowledge_base/NVLink",
      "label": "NVLink"
    },
    {
      "id": "04_knowledge_base/GB200",
      "label": "GB200"
    },
    {
      "id": "04_knowledge_base/NVIDIA Oberon",
      "label": "Oberon"
    },
    {
      "id": "04_knowledge_base/NVLink5",
      "label": "NVLink 5"
    },
    {
      "id": "04_knowledge_base/Flyover cable",
      "label": "flyover cables"
    }
  ],
  "frame_type": "COMPARISON",
  "metric": "UNSPECIFIED_METRIC",
  "operator": "COMPARES_WITH",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "6 S",
      "5 S"
    ],
    "temporal_mentions": []
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
comparison_entity_0	Rubin	04_knowledge_base/Vera Rubin
comparison_entity_1	NVLink	NVLink
comparison_entity_2	GB200	GB200
comparison_entity_3	Oberon	04_knowledge_base/NVIDIA Oberon
comparison_entity_4	NVLink 5	NVLink5
comparison_entity_5	flyover cables	04_knowledge_base/Flyover cable

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