clm_2e974f8706064b0880e2454a9da9cc9a_r1

NIEK2-0350

① SA Source

• Source: 開啟完整 SA 文章
• Section: Cables and Connectors: Amphenol Continues to Benefit
• Line hint: 437

Context Before

Next, we mentioned that a very high spec PCB is required for the LPX compute tray. We estimate that each compute tray main board PCB will carry $7k ASP. The suppliers for this are Victory Giant and WUS. Of course, there are several other PCB modules in the compute tray, but they do not need a high spec. Nvidia is continuing with their cable-less philosophy similar to the Vera Rubin compute tray which requires a lot of board-to-board connectors, which brings us to the next big beneficiary.

Cables and Connectors: Amphenol Continues to Benefit

Evidence

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

Context After

NVL288 System

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.

② Atomic Claim

tray 內各模組之間也需要 board-to-board connectors，包括主 LPU board、host CPU module、位於 CPU module 下方的 OSFP／QSFP modules、front-end NIC module 與 management module。

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/Groq LPU",
        "label": "LPU"
      },
      "role": "endpoint_or_system"
    },
    {
      "node": {
        "id": "04_knowledge_base/CPU",
        "label": "CPU"
      },
      "role": "connected_entity"
    },
    {
      "node": {
        "id": "04_knowledge_base/OSFP (Octal Small Form-factor Pluggable)",
        "label": "OSFP"
      },
      "role": "connected_entity"
    },
    {
      "node": {
        "id": "04_knowledge_base/QSFP",
        "label": "QSFP"
      },
      "role": "connected_entity"
    },
    {
      "node": {
        "id": "04_knowledge_base/NIC",
        "label": "NIC"
      },
      "role": "connected_entity"
    }
  ],
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "relation_type": "CONNECTS_TO"
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
endpoint_or_system	LPU	04_knowledge_base/Groq LPU
connected_entity	CPU	CPU
connected_entity	OSFP	04_knowledge_base/OSFP (Octal Small Form-factor Pluggable)
connected_entity	QSFP	QSFP
connected_entity	NIC	NIC

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