devices(huawei): the E6616X is modelled on the EGS4, whose chapter names the X in its subrack row (#803) #2373

Merged
jaylouisw merged 1 commit from catalogue/1121-0522 into main 2026-11-21 05:46:46 +00:00
Owner

Fixes #803

The E6616X is not short of a service-board census — the EGS4 chapter states both halves of it, and this PR models the X on that board.

The two tables (TMB3EGS4 chapter, OptiXtrans E6600 Hardware Description, read 2026-11-21 from the verbatim partner copy https://www.szhuaxunjia.com/product/2302.html, HTTP 200, 67,351 B):

  • 表1 单板配套关系: TMB3EGS4 | E6616X | TM65UXCL | V100R022C10SPC010 — the board, the subrack, the cross-connect it needs, and the first release that carries it. The E6608 / E6616 rows in the same table name their own cross-connects, so the X row is not a sibling's.
  • 表3 单板接口说明: silkscreen TX1/RX1~TX4/RX4, 连接器类型 LC或RJ-45, 网管接口序号 1~4 — four cages, optical or electrical module. Port modes: GE electrical 10/100/1000, GE optical 1000M, FE optical 100M. Board 193.80 × 19.80 × 205.90 mm (one slot), 61 W typical / 66 W max.
  • The chapter's 功能特性 opens with 仅适配 E6608/E6616/E6616X时支持.

The build. No Huawei document states a typical E6616X configuration, so the spec follows optixtrans-e6616.json / optixtrans-e9605.json: every service slot filled with one board the vendor lists as valid in the subrack, complement in label, bare model in model. DC chassis 14 service slots (AC 12, and every AC X SKU is 1500 W, so there is no 10-slot AC variant as on the E6616). 14 × 4 = 56 FE/GE ports, named <slot>/<port>.

What it deliberately does not model. The 2M build the Ningbo deployment record shows (B2PD1 + B2DMS, 32× E1/T1 per DMS) still has no home in the engine: there is no E1/T1 port type, and a G.703 tributary declared rj45 would cable at the wrong rate. That is recorded in research/optixtrans-e6616x-port-type-gap.md and restated in the spec's notes, so a future pass can add the TMB2TPS build as a second spec without reopening this one.

Files. devices/huawei/optixtrans-e6616x.json; research/optixtrans-e6616x-stated-build.md (readings, rejected candidates TMB4EGS8 — 8 ports but TX5-TX8 need a 端口扩展 RTU — and TMB4EFS8 — FE only — and why the ActForNet E6600 Boards Overview cannot place a board in the X: no subrack column, zero occurrences of E6616X); research/open-device-requests.json drops #803; docs/DEVICE_REGISTRY.md, README, docs/CONNECTORS.md and the wiki headline regenerated (2,352 models / 29,768 sockets / 974 shapes).

Gates. node scripts/syntax-check.js — 515 files, all OK. node scripts/audit-port-types.js — 0 gated. node scripts/audit-devices.js — 0 hard defects, 0 optics-without-a-fibre-cage. node --test on doc-catalog-counts, request-queue, hardware-invariants, device-aliases, duplicate-models, catalogue-hygiene — 6/6 pass.

Fixes #803 The E6616X is not short of a service-board census — the EGS4 chapter states both halves of it, and this PR models the X on that board. **The two tables (TMB3EGS4 chapter, OptiXtrans E6600 Hardware Description, read 2026-11-21 from the verbatim partner copy https://www.szhuaxunjia.com/product/2302.html, HTTP 200, 67,351 B):** - 表1 单板配套关系: `TMB3EGS4 | E6616X | TM65UXCL | V100R022C10SPC010` — the board, the subrack, the cross-connect it needs, and the first release that carries it. The E6608 / E6616 rows in the same table name their own cross-connects, so the X row is not a sibling's. - 表3 单板接口说明: silkscreen `TX1/RX1~TX4/RX4`, 连接器类型 `LC或RJ-45`, 网管接口序号 `1~4` — four cages, optical or electrical module. Port modes: GE electrical 10/100/1000, GE optical 1000M, FE optical 100M. Board 193.80 × 19.80 × 205.90 mm (one slot), 61 W typical / 66 W max. - The chapter's 功能特性 opens with 仅适配 E6608/E6616/E6616X时支持. **The build.** No Huawei document states a typical E6616X configuration, so the spec follows `optixtrans-e6616.json` / `optixtrans-e9605.json`: every service slot filled with one board the vendor lists as valid in the subrack, complement in `label`, bare model in `model`. DC chassis 14 service slots (AC 12, and every AC X SKU is 1500 W, so there is no 10-slot AC variant as on the E6616). 14 × 4 = 56 FE/GE ports, named `<slot>/<port>`. **What it deliberately does not model.** The 2M build the Ningbo deployment record shows (`B2PD1` + `B2DMS`, 32× E1/T1 per DMS) still has no home in the engine: there is no E1/T1 port type, and a G.703 tributary declared `rj45` would cable at the wrong rate. That is recorded in `research/optixtrans-e6616x-port-type-gap.md` and restated in the spec's notes, so a future pass can add the TMB2TPS build as a second spec without reopening this one. **Files.** `devices/huawei/optixtrans-e6616x.json`; `research/optixtrans-e6616x-stated-build.md` (readings, rejected candidates TMB4EGS8 — 8 ports but TX5-TX8 need a 端口扩展 RTU — and TMB4EFS8 — FE only — and why the ActForNet E6600 Boards Overview cannot place a board in the X: no subrack column, zero occurrences of `E6616X`); `research/open-device-requests.json` drops #803; `docs/DEVICE_REGISTRY.md`, README, `docs/CONNECTORS.md` and the wiki headline regenerated (2,352 models / 29,768 sockets / 974 shapes). **Gates.** `node scripts/syntax-check.js` — 515 files, all OK. `node scripts/audit-port-types.js` — 0 gated. `node scripts/audit-devices.js` — 0 hard defects, 0 optics-without-a-fibre-cage. `node --test` on doc-catalog-counts, request-queue, hardware-invariants, device-aliases, duplicate-models, catalogue-hygiene — 6/6 pass.
devices(huawei): the E6616X is buildable from the EGS4's own subrack row (#803)
All checks were successful
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Test (Node 22) (pull_request) Successful in 1m4s
CI / Test (Node 20) (pull_request) Successful in 1m5s
CI / Test (Node 18) (pull_request) Successful in 1m6s
CI / Server smoke and Docker build (pull_request) Successful in 32s
CI / Arm auto-merge (pull_request) Successful in 5s
800f6c690f
The X's service-board set is published after all: the TMB3EGS4 chapter of the
E6600 Hardware Description prints 表1 单板配套关系 with an E6616X row
(TM65UXCL, V100R022C10SPC010) and 表3 单板接口说明 with four LC-or-RJ-45
cages. Modelled as 14x TMB3EGS4 = 56x FE/GE, the same stated-build convention
as the E6616 and E9605. The 2M build stays out: the engine has no E1/T1 port
type (research/optixtrans-e6616x-port-type-gap.md).

Refs #803
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 05:30:50 +00:00
jaylouisw deleted branch catalogue/1121-0522 2026-11-21 05:46:49 +00:00
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!2373
No description provided.