SA260324R-0351
① SA Source
- Source: 開啟完整 SA 文章
- Section:
NVL288 System - Line hint:
441
Context Before
For the LPX, Amphenol will be a beneficiary for all the connectors for the backplane. Each LPX node requires 16 80DP Paladin connectors for the backplane. There are also board to board connectors required to connect all the various modules within the tray: the main LPU board with the host CPU module and the OSFP/QSFP modules that sit below the CPU module, the front-end NIC module, and the management module. Amphenol will supply the cable backplane too which is 8,160 DP per rack.
NVL288 System
Evidence
For the Vera Rubin Ultra NVL288 System that we discussed above, we would say the cable backplane return for Kyber. If Rubin Ultra is deployed in such a form factor – each of the Rubin Ultra GPUs will have a scale-up bandwidth of 14.4Tbit/s uni-di, requiring 144 DPs of cables to connect to the NVSwitches. 144 DPs times 288 GPUs means a total of 41,472 DPs to connect this larger world size domain. This is a lot of cables, so it is more of an upper bound of how much cable content could be used here. If there is oversubscription or if the inter-rack connection is made through the switches – it is possible fewer DPs would be needed.
Context After
FIT Joining the Party
Backplane cable cartridge and Paladin connector demand is so strong that Amphenol cannot keep up with supply. Amphenol has now completed licensing of the VR NVL72 backplane cable cartridge as well as Paladin HD connectors to FIT, who can now manufacture these components. This has been in the works for a long time but is finally settled. Amphenol will earn licensing fees from FIT’s sales of these licensed components.
② Atomic Claim
若 Rubin Ultra 以此 form factor 部署，每顆 Rubin Ultra GPU 將提供 14.4Tbit/s uni-di scale-up bandwidth，並需要 144 DP cable 連到 NVSwitch。
- Epistemic Mode:
HYPOTHETICAL - Mapping Status:
PARTIAL
③ Semantic Frame
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Rubin Ultra",
"label": "Rubin Ultra"
},
"role": "platform"
},
{
"node": {
"id": "04_knowledge_base/GPU",
"label": "GPU"
},
"role": "device"
},
{
"node": {
"id": "04_knowledge_base/14.4Tbit per second",
"label": "14.4Tbit/s"
},
"role": "bandwidth"
},
{
"node": {
"id": "04_knowledge_base/NVSwitch",
"label": "NVSwitch"
},
"role": "switch"
}
],
"qualifiers": {
"condition_text": "hypothetical deployment; DP cable has no canonical entity",
"numeric_mentions": [
"14.4Tbit/s",
"144"
],
"temporal_mentions": []
},
"relation_type": "RUBIN_ULTRA_GPU_SCALEUP_CABLE_REQUIREMENT"
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| platform | Rubin Ultra | 04_knowledge_base/Rubin Ultra |
| device | GPU | GPU |
| bandwidth | 14.4Tbit/s | 04_knowledge_base/14.4Tbit per second |
| switch | NVSwitch | NVSwitch |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
若 Rubin Ultra 以此 form factor 部署，每顆 Rubin Ultra GPU 將提供 14.4Tbit/s uni-di scale-up bandwidth，並需要 144 DP cable 連到 NVSwitch。
V2 Semantic Frame Draft
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Rubin Ultra",
"label": "Rubin Ultra"
},
"role": "platform"
},
{
"node": {
"id": "04_knowledge_base/GPU",
"label": "GPU"
},
"role": "device"
},
{
"node": {
"id": "04_knowledge_base/14.4Tbit per second",
"label": "14.4Tbit/s"
},
"role": "bandwidth"
},
{
"node": {
"id": "04_knowledge_base/NVSwitch",
"label": "NVSwitch"
},
"role": "switch"
}
],
"qualifiers": {
"condition_text": "hypothetical deployment; DP cable has no canonical entity",
"numeric_mentions": [
"14.4Tbit/s",
"144"
],
"temporal_mentions": []
},
"relation_type": "RUBIN_ULTRA_GPU_SCALEUP_CABLE_REQUIREMENT"
}V2 Revision Metadata Draft
{
"epistemic_mode": "HYPOTHETICAL",
"mapping_status": "PARTIAL"
}⑥ 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 才是正式決策。