Talon1 + Talon2 cabling: current links and the bridge cable
Version 7 · 2026-11-10 · Bridge cable measured on both ends: talon1 PCIE8 (bus cf) cage 1 ↔ talon2 PCIE6 (bus 99) cage 1 [module presence, hq-operations 07:31Z and box1-qwen-junior 08:05Z]. No cable was unplugged. talon2 card 99 cage 1 is not driven by its current image, so the link is not up yet.
Two ASUS ESC8000-E11 servers, 8 PCIe slots each. Grey = cable in place today. Orange dashed = the one bridge cable to add. No existing cable is unplugged. Edit the data box at the bottom to change any link; the picture redraws.
- Physical left-to-right order is an assumption, from the user's note that the H200 sits in the leftmost slot (PCIE8) of talon2. Both servers are drawn PCIE8 → PCIE1 left to right, as seen from the side where the cables plug in. Check the slot labels on the chassis before plugging.
- Cage numbers c0–c3 are the link layer's cage index. Their top-to-bottom position on the V80 bracket is not verified. On talon1 this does not matter for card cf: its two cabled cages are exactly c0 and c3.
- Talon1 cable ends: the ring order is measured; which end of each cable sits in c0 and which in c3 is drawn as c0 → c3 along the ring order and is not verified per cable.
- Bridge cage: the rebuilt image 0xE4B71354 drives c1 (bank 210) and c2 (bank 112) [D, from the board pin file; confirmed from the routed design when it lands]. Both are empty on talon1 PCIE8 (cf) and talon2 PCIE6 (99).
- The bridge image is being rebuilt as 0xE4B71354 to drive an empty cage (c1 and/or c2). It drives both middle cages, c1 and c2; either one works on each end. The picture shows c1 on both.
- Read the slot label printed on the chassis. The left-to-right order on this page is an assumption.
- Cage positions on the bracket are not verified. After plugging, a module-presence read per cage confirms which printed cage is which.
- Flash status: the old image 0xE4B71352 (cages 0 and 3) passed QM and is not flashed. The new image is building. A flash needs a cold AC on both servers.
existing cable (measured)bridge cable (plug in)unplug this end firstempty cage
What to do
| # | Server | Action | Why |
|---|
Slots and roles
| Server | Slot | PCIe bus | Card | Role today |
|---|
Existing cables
| Server | Card · cage | Card · cage | Use |
|---|
Edit the map
JSON. cab rows are [server, card, cage, card, cage, use]. bridge rows are [server, card, cage, server, card, cage, label]. pull rows are [server, card, cage] for cable ends to unplug. Changes stay in this browser tab only.
Sources [M unless noted]: talon1 slot ↔ bus from the BMC inventory and /sys/bus/pci/slots (2026-11-10); talon1 ring order 17-3d-50-63-cf-e1-99-bd, cage 0 ↔ cage 3 (2026-11-09/BRIDGE/SCOPE.md:12; TALON_FLASH_0x1250_20261014.md:22); talon1 cf and e1: cages 0 and 3 hold a module, 1 and 2 empty (hq-operations read, 2026-11-10 07:4xZ); talon2 slots and cables from box1's talon2 cabling map (talon2_cabling_20261110.html: link beacons 2026-10-23, module presence 2026-11-09). Bridge image 0xE4B71352 drives cages 0 and 3 only (2026-11-09/BRIDGE/FLASH_PLAN.md). The demo chain uses 63 phys 1 and 99 phys 0 only (G0 postboot [L] lines: 63 rank 0 need phys [1], 99 rank 5 need phys [0]), so 63 cage 0 and 99 cage 3 on talon1 are idle. 2026-11-10, hq-research track 2.