research: E6600 chassis chapters download anonymously, and hold no board census (#803) #1826
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1826
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1117-0955"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #803 (does not close it: the port census is still missing).
New route, verified today. The per-chapter product documentation is reachable without a login once the 32-hex material hash is known:
https://e.huawei.com/en/documents/others/<hash>is server-rendered and prints thee-file.huawei.comasset path in its HTML, so the 19-digit asset token never has to be guessed.What that fetched.
(2)-OptiXtrans E6616-Datasheet= OptiXtrans E6600 V100R025C10 Product Documentation, 20 pp, 1,535,511 B, issue 2026-03-31. Chapter 1 gives the slot layout verbatim:TMB1APIU; fan 19.The trap it closes. The public spec table prints "AC chassis: 12"; the 2400 W AC chassis actually has 10 service slots, because four slots carry
TMB1APIUboards. Any future E6616/E6616X label must name the power configuration.What it does not contain. No service-board census: the only boards named are system control/cross-connect (
TMK5SXCH,TMK5XCH,TMK6XCH,TMK5UXCME,TMK5XCS), fgOTN (TMK1FXCL,TMK1XCL), powerTMB1APIUand fanTMK5FAN. Section 1.5 is per-slot backplane capacity, not ports. The E6600 partner mirror covers E6608T/E6608/E6616 only - not the X. So #803 still needs the service-board part number per slot plus its front-panel port census.scripts/huawei-material-fetch.jsmakes that lookup repeatable (hash in, PDF out), so the next pass needs one search hit for aTMB1*/TMK1*chapter rather than a full re-walk.Gates:
syntax-check384 files OK;audit-port-typesno contradictions;check-node-surfaceclean;check-control-bytesclean;hardware-invariants1/1 pass; registry doc regenerates with no diff.