huawei: model the OptiXtrans E9624 as the stated 1:1 24x TNG1N210 build #1969
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!1969
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1118-0956"
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 #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 namediuN/pMso the 24 boards are visible rather than flattened intoline1..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)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".OSN 9800 M24valid-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
notesso 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.jsondrops the #810 row anddocs/DEVICE_REGISTRY.mdis regenerated (2,356 models, 29,721 sockets, 972 port shapes; two requests left open); newresearch/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.js412 files OK ·audit-port-types.jsno port contradicts its declared type ·test/hardware-invariants.test.js26/26 ·test/request-queue.test.js32/32 ·check-control-bytes.jsclean ·regen-registry-doc.jsno drift ·check-doc-citations.jsonly the three pre-existing BGP/CLI drift suspects.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.