huawei: model the OptiXtrans E9612 as a stated 13x TNG1N210 build (#808) #1962
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!1962
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1118-0856"
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?
Fixes #808
Device: Huawei OptiXtrans E9612 —
devices/huawei/optixtrans-e9612.jsonBuild modelled: 13x TNG1N210 = 130x 10G line ports (stated complement, same convention as E9605 #1955, E6608, E6616).
Census, field by field
TNG1N206/TNG1N210: Y (E9624 is mode-dependent Y/Y; E9612 takes no mode qualifier)TNG1N210: 10 x 10 Gbit/s Line Service Processing Board13 x 10 = 130. No guessed port, rate, cage or part number.
Why a partner copy is cited, and what it is used for. The chapter is
EDOC1100126589BEJ09047; its vendor copy (E9600 Board DatasheetEDOC1100163901) answers302 -> /view/notFoundfor every user-agent tried, as doEDOC1100214449,EDOC1100621488,EDOC1100622610,EDOC1100622612. The Table 1/3 rows were read from the verbatim reproduction at https://www.actfornet.com/solutions/solution/OptiXtrans_E9600_Boards_Overview (200, 226,637 B, 127 hedex links). The spec notes say which fields are mirror-read and which are vendor-page-read; the reseller reprint of the N210 chapter (https://www.thunder-link.com/tng1n210.html) agrees on 10 ports, all SFP+ -10G, M12 IU1-IU13.The 13 is conditional, and the label says it. Subrack chapter (2026-11-17): DC 13 (IU1-IU13), DC master 12, AC/HVDC 10 or 11 — one APIU occupies physical IU1+IU2. So this entry is the DC 13-slot layout; an AC shelf is 20-30 line ports smaller. Recorded in
notes, not only in the thread.Also in this PR
research/optixtrans-e9612-stated-build.md— the reading, the Table 3 rows, the gated ids.research/open-device-requests.json— #808 removed; #810 narrowed: validity is now stated (Table 3 Y in both modes), so only the cross-connect mode is missing (1:1 -> 240 ports, 1:3 -> 200).regen:registry-doc): 2,355 models / 258 vendors / 29,481 sockets / 971 shapes.Gates:
syntax-check411 files OK ·audit-port-typesno contradiction ·hardware-invariants26/26 ·import-devices-capabilities34/34 ·catalogue-hygiene25/25 ·faceplate-catalogue14/14 ·fuzz-importer14/14 ·importer-roundtrip26/26 ·doc-catalog-counts43/43 ·check-control-bytesclean ·regen-registry-doc --checkcurrent.8a314bbc60ec3b431fecSurgery loop 08:55 — the red is one guard line, not this spec. Reproduced on
ec3b431f.Head
ec3b431f, 0 behindorigin/main(9d852ed8),mergeable=true, 8 files (+894/-30). Docker build, smoke, classify, rebase and arm-auto-merge all success. The three Node legs fail on the same assertion:test/close-merged-issues.test.js:305-318still carries the literal queue thatorigin/mainhas, including:and asserts none of the six has a spec. This PR correctly gives #808 one, so the premise the guard encodes is now false — the spec is right, the expectation is stale.
The fix is the two-line edit #1955 already made for #807 in
1304b0bd: drop the[808, ...]row and add the positive assertion that #808 resolves todevices/huawei/optixtrans-e9612.json(that commit is the exact template — same file, same shape). With that, this PR is mergeable and green; nothing in the spec needs to change.Not mine to make:
test/is off-limits to this loop, so this needs the author or Jay.Two things worth knowing before that lands.
#1934also models an E9612 (same 13x TNG1N210 / 130x 10G, different metadata:modelTitle-Case, pluscolor/icon, different prose andsourceUrl) — whichever of the two merges first leaves the other a duplicate of the same box. And this guard is a hand-maintained mirror ofresearch/open-device-requests.json, so every device PR that resolves a queued request trips it; #1955 edited it, this PR and #1934 did not. Making that assertion read the queue and the catalogue instead of a literal list would retire the trap.Re-verified at
ec3b431fmerged withorigin/main9d852ed8(2026-11-18 09:1x):node test/close-merged-issues.test.js→ 72 passed, 1 failed, the single failure beingNothing else in the suite fails, and this PR is still 0 commits behind main with
mergeable: true— so the guard literal is the only thing between it and a green run. The blocker is now tracked as #1963 rather than living only in this thread, so it survives this PR. No action needed here beyond that.19e13932e6dfb22e0ae9Surgery loop 09:23 — the blocker is now a five-line patch, verified green. It is Jay's call to apply, not mine.
I re-ran this at the current head against
origin/main=3aa97d60(#1964 merged 09:1x).ec3b431fmerged with main: same single failure, nothing else.Why the guard fails is not a defect in this spec, and not a decision about behaviour.
test/close-merged-issues.test.js:306-317hardcodes the open-request queue and asserts the catalogue answers none of it. Landing E9612 makes#808answerable, so the assertion is supposed to fail — exactly as#807/E9605 did, and exactly how#1961handled it (moved E9605 out of the queue into an "answered" assertion). This PR just never carried its half of that bookkeeping.The patch, applied locally and reverted — not pushed:
With it applied in a scratch worktree at
ec3b431f+3aa97d60:node test/close-merged-issues.test.js→ 74 passed, 0 failednpm test→ 338 suites in 473.9 s, 11,759 assertions, 0 failed (EXIT=0)That is the entire distance between this PR and a green head — no source change, no semantic conflict, no other failing suite.
Jay: one word and I push this onto
catalogue/1118-0856(as a separate commit, authored by me,test/-only,--force-with-lease), which should turn all three Node legs green and let the standing automerge rule take it. I have not touchedtest/on my own initiative — that block is still yours from the 08:55 escalation. The same patch is what#1934will need, but only after the E9605 source-of-truth call.The durable fix is still open as
#1963(derive the queue fromresearch/open-device-requests.json); this patch is the stopgap for the two PRs in front of us.