huawei: model the OptiXtrans E9624 as the stated 1:1 24x TNG1N210 build #1969

Merged
jaylouisw merged 2 commits from catalogue/1118-0956 into main 2026-11-18 10:11:43 +00:00
Owner

Fixes #810

devices/huawei/optixtrans-e9624.json — OptiXtrans E9624 OTN subrack, 1:1 cross-connect mode, fully populated with 24x TNG1N210 = 240x 10G OTU2/OTU2e line ports (IU1-IU24, ports named iuN/pM so the 24 boards are visible rather than flattened into line1..line240).

The blocker was in the request. Issue #810's port line reads "12/24 service slots (1:1 cross-connect mode: 12 large or 24 small slots)" — the mode the open-request row asked for. 1:1 + small slots = IU1-IU24 = 24 single-slot boards x 10 ports = 240. The 1:3 alternative (20 slots, IU6/IU7/IU18/IU19 unusable) is a different box and is named in notes, not averaged in.

Sources (all recorded in the spec's sourceUrl / notes)

  • Frame and slot arithmetic: OptiXtrans E9600 Family brochure PDF (sourceUrl), E9624 column — 1:1: 12 large or 24 small slots; 1:3: 10 or 20; "One 11 U slot of the E9624 subrack can be split into two 5.5 U slots".
  • Slot map and the 1:3 caveat: TNG2DAP section 1.9 Valid Slots, Table 1, E9624 row — IU1-IU24, footnote excludes IU6/IU7/IU18/IU19 in 1:3 (e-file PDF, 871,676 B).
  • Board validity and port count: OptiXtrans E9600 (E9624/E9612/E9605) Boards Overview, Table 3 (TNG1N206/TNG1N210 under E9624: 1:1 Y / 1:3 Y) and Table 1 ("TNG1N210: 10 x 10 Gbit/s Line Service Processing Board"). The vendor copy (EDOC1100163901) still answers 302 to the login gate, so — as in the merged E9605 (#1955) and E9612 (#1962) entries — the text was read from the verbatim partner copy whose 127 hedex links identify the vendor chapter.
  • Cross-connect placement and the brand join: EUCC-3089-2026-004 Security Target, Table 1-1 — "OptiX OSN 9800 M24 / OptiXtrans E9624", SCC in CXP IU71/IU72, i.e. outside IU1-IU24; that row is also what makes the N210 chapter's OSN 9800 M24 valid-slot line describe this subrack.

Not modelled: the CXP cross-connect boards (no client ports, and the engine has no cross-connect concept); the E9624X, a separate fourth subrack; and the OTN tributary / packet board builds the E9624 column also admits (listed in notes so this file is not reused for a tributary shelf).

Caveats carried in the spec: the port count is the 1:1 stated build, not a fixed chassis figure; the line side is OTU2/OTU2e filed as ethernet/sfp+ (house convention — no OTN type in the engine).

Also in this PR: research/open-device-requests.json drops the #810 row and docs/DEVICE_REGISTRY.md is regenerated (2,356 models, 29,721 sockets, 972 port shapes; two requests left open); new research/optixtrans-e9624-stated-build.md; the E9612 note's "the mode is not stated" paragraph is corrected, since the request does state it.

Duplicate warning: open PR #1934 already contains an E9624 spec from the same matrix (240 ports, 1:1) — plus E9605 and E9612 specs that have since landed on main as #1955 and #1962, which is why it is add/add-conflicted and red. This PR is the single-device replacement for its E9624 third; do not merge both.

Gates: scripts/syntax-check.js 412 files OK · audit-port-types.js no port contradicts its declared type · test/hardware-invariants.test.js 26/26 · test/request-queue.test.js 32/32 · check-control-bytes.js clean · regen-registry-doc.js no drift · check-doc-citations.js only the three pre-existing BGP/CLI drift suspects.

Fixes #810 `devices/huawei/optixtrans-e9624.json` — OptiXtrans E9624 OTN subrack, 1:1 cross-connect mode, fully populated with 24x TNG1N210 = **240x 10G OTU2/OTU2e line ports** (IU1-IU24, ports named `iuN/pM` so the 24 boards are visible rather than flattened into `line1..line240`). **The blocker was in the request.** Issue #810's port line reads "12/24 service slots (1:1 cross-connect mode: 12 large or 24 small slots)" — the mode the open-request row asked for. 1:1 + small slots = IU1-IU24 = 24 single-slot boards x 10 ports = 240. The 1:3 alternative (20 slots, IU6/IU7/IU18/IU19 unusable) is a different box and is named in `notes`, not averaged in. **Sources** (all recorded in the spec's `sourceUrl` / `notes`) - Frame and slot arithmetic: *OptiXtrans E9600 Family* brochure PDF (`sourceUrl`), E9624 column — 1:1: 12 large or 24 small slots; 1:3: 10 or 20; "One 11 U slot of the E9624 subrack can be split into two 5.5 U slots". - Slot map and the 1:3 caveat: TNG2DAP section 1.9 Valid Slots, Table 1, E9624 row — IU1-IU24, footnote excludes IU6/IU7/IU18/IU19 in 1:3 (e-file PDF, 871,676 B). - Board validity and port count: *OptiXtrans E9600 (E9624/E9612/E9605) Boards Overview*, Table 3 (TNG1N206/TNG1N210 under E9624: 1:1 Y / 1:3 Y) and Table 1 ("TNG1N210: 10 x 10 Gbit/s Line Service Processing Board"). The vendor copy (EDOC1100163901) still answers 302 to the login gate, so — as in the merged E9605 (#1955) and E9612 (#1962) entries — the text was read from the verbatim partner copy whose 127 hedex links identify the vendor chapter. - Cross-connect placement and the brand join: EUCC-3089-2026-004 Security Target, Table 1-1 — "OptiX OSN 9800 M24 / OptiXtrans E9624", SCC in CXP IU71/IU72, i.e. outside IU1-IU24; that row is also what makes the N210 chapter's `OSN 9800 M24` valid-slot line describe this subrack. **Not modelled:** the CXP cross-connect boards (no client ports, and the engine has no cross-connect concept); the E9624X, a separate fourth subrack; and the OTN tributary / packet board builds the E9624 column also admits (listed in `notes` so this file is not reused for a tributary shelf). **Caveats carried in the spec:** the port count is the 1:1 stated build, not a fixed chassis figure; the line side is OTU2/OTU2e filed as `ethernet`/`sfp+` (house convention — no OTN type in the engine). **Also in this PR:** `research/open-device-requests.json` drops the #810 row and `docs/DEVICE_REGISTRY.md` is regenerated (2,356 models, 29,721 sockets, 972 port shapes; two requests left open); new `research/optixtrans-e9624-stated-build.md`; the E9612 note's "the mode is not stated" paragraph is corrected, since the request does state it. **Duplicate warning:** open PR #1934 already contains an E9624 spec from the same matrix (240 ports, 1:1) — plus E9605 and E9612 specs that have since landed on main as #1955 and #1962, which is why it is add/add-conflicted and red. This PR is the single-device replacement for its E9624 third; do not merge both. **Gates:** `scripts/syntax-check.js` 412 files OK · `audit-port-types.js` no port contradicts its declared type · `test/hardware-invariants.test.js` 26/26 · `test/request-queue.test.js` 32/32 · `check-control-bytes.js` clean · `regen-registry-doc.js` no drift · `check-doc-citations.js` only the three pre-existing BGP/CLI drift suspects.
huawei: model the OptiXtrans E9624 as the stated 1:1 24x TNG1N210 build (#810)
Some checks failed
CI / Classify the change (pull_request) Successful in 6s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Failing after 49s
CI / Test (Node 18) (pull_request) Failing after 56s
CI / Test (Node 22) (pull_request) Failing after 53s
CI / Arm auto-merge (pull_request) Successful in 2s
c7da358fb3
The request states the cross-connect mode in its own port line ("1:1 cross-connect
mode: 12 large or 24 small slots"), which is the one field the open-request row
said was missing. 1:1 + small slots = IU1-IU24 = 24 single-slot TNG1N210 line
boards = 240 x 10G OTU2/OTU2e line ports.

Frame: OptiXtrans E9600 Family brochure PDF, E9624 column (24 small / 12 large in
1:1; 20 / 10 in 1:3; one 11 U slot splits into two 5.5 U). Slot map and the 1:3
caveat: TNG2DAP section 1.9 Valid Slots, E9624 row (IU1-IU24, footnote excludes
IU6/IU7/IU18/IU19 in 1:3). Board validity and port count: E9600 Boards Overview
Table 3 (N210 Y under E9624 in both modes) and Table 1 (10 x 10 Gbit/s Line
Service Processing Board). Cross-connect TNG4CXP in IU71/IU72 outside IU1-IU24,
and the OSN 9800 M24 brand join: EUCC-3089-2026-004 Security Target Table 1-1.

What differs from its siblings: real cross-connect boards, and OTN tributary and
packet boards the E9612 and E9605 columns mark NA - both named in notes so this
file is not reused for a tributary shelf.
test(close-merged-issues): #810 now resolves, and E9624X is the near miss
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
CI / Classify the change (pull_request) Successful in 6s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Successful in 53s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Arm auto-merge (pull_request) Successful in 10s
9b5ab0e00c
The device sweep asserts that no open request is already in the catalogue, and it
carries a literal snapshot of the queue so a spec landing without updating the list
is caught. E9624 left the queue in research/open-device-requests.json with this
branch, so it leaves the snapshot too - five rows, and the positive assertion that
the request resolves to devices/huawei/optixtrans-e9624.json.

The near miss is E9624X: a fourth subrack Huawei sells beside the E9624, with its
own product page and its own SCC board, and the sweep must keep calling it
unmatched rather than reading it as "E9624 with a suffix". Same shape as #1955
(E9605) and #1962 (E9612).
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1969
No description provided.