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.

Calculations and hypothesis:
Plan changed (2026-11-10): no cable is unplugged.

existing cable (measured)bridge cable (plug in)unplug this end firstempty cage

What to do

#ServerActionWhy

Slots and roles

ServerSlotPCIe busCardRole today

Existing cables

ServerCard · cageCard · cageUse

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.