research(optixtrans): the E9600 board census is public, the port type is not (#807) #1788

Merged
jaylouisw merged 1 commit from catalogue/1117-0425 into main 2026-11-17 04:37:09 +00:00
Owner

Refs #807 — records evidence, does not close it.

Follow-up to research/optixtrans-slot-census.md. The missing field named on #803/#804/#807/#808/#810 ("board part number per slot") is now found, and under it a second blocker that is not a document.

1. Board census, per subrack

Huawei's OptiXtrans E9600 board matrix (reprinted by ActForNet, https://www.actfornet.com/solutions/solution/OptiXtrans_E9600_Boards_Overview ; vendor landing page https://support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9605-pid-250732995 , Datasheet "OptiXtrans E9600 Board Datasheet") splits the frame much harder than the slot count suggests. For the E9605 (5 service slots): OTN line boards TNG1N206 (6x10G), TNG1N210 (10x10G), TNG1N401 (1x100G) = Y; every tributary, packet, TDM and turbo-WDM board = NA; transponder units TNG1M*, general TNG1A212, mux/demux and ROADM boards = Y. So the E9605's client ports can only arrive as a TNG1M* transponder or as a line board's ports — 10 board rows against the E9624's ~40.

Port counts are printed in the board names: TNG1N206 6x10G, TNG1N210 10x10G, TNG1N401 1x100G, TNG1T212 12x10G, TNV1T410 10x100G, TNV2T601 1x400GE, TNG1M210D 10x any-rate + 2xOTU2, TNG2M604SM 4x100G -> 1x400G/200G. OptiXtrans E9605 (5x TNG1N210) = 50 x 10G with no guessed number.

2. The blocker underneath it

engine/media.js knows ethernet, wireless, console, usb, coax, dsl, powerline, serial, pon and Ethernet/storage cages (rj45 .. qsfpdd, xfp, cfp2, fibre connectors). A TNG1N210 front-panel port is an OTU2/OTU2e WDM-side optical port (published SFP+ module list: 10/40/80 km, DWDM 100 GHz and 50 GHz tunable, CWDM). The only filable combination today is type: ethernet, connector: sfp+, which makes it an Ethernet socket that CAGE_MEDIA['sfp+'] will happily join to a 10G Ethernet peer — the exact "lab refuses to cable" failure the catalogue guards against. There is no otn/wdm type, and adding one is an engine/media.js change this stream must not make.

3. URLs checked 2026-11-17

  • https://e.huawei.com/marketingcloud/pep/asset/20000001/Material/0f9e00e3f2ca431693884a01667d7ec6/M3T1A669N1188254857740624027/OptiXtrans E9600 Family -.pdf — 200, 277,705 B. Brochure: slots 1:1 12 large / 24 small, 1:3 10 large / 20 small (E9624), 13 (E9612), 5 (E9605). No board list.
  • https://support.huawei.com/hedex/pages/EDOC1100126589BEJ09047/03/EDOC1100126589BEJ09047/03/resources/help/wdm/9800/hd/line/n210/n210.html — 403 to a crawler UA: the board description that would settle client-vs-WDM sides.
  • https://support.huawei.com/enterprise/en/doc/EDOC1100624531 — 404, unchanged since 2026-11-16.
  • https://www.actfornet.com/solutions/solution/OptiXtrans_E9600_Boards_Overview — 200, partner mirror of the matrix (lead, not evidence).

What would unblock #807

A project decision on an optical-line port type (an otn/wdm entry in engine/media.js and the faceplate renderer). The board statement is ready the moment one exists: E9605 (5x TNG1N210) -> 50 x 10G OTU2 line ports. Until then this PR adds research only — no spec, because a mislabelled port is worse than a missing device.

Gates: node scripts/syntax-check.js OK (374 files); audit-port-types 0 offenders; audit-devices no hard defects; test/hardware-invariants 26 passed; regen-registry-doc --check current; check-control-bytes clean.

Refs #807 — **records evidence, does not close it.** Follow-up to `research/optixtrans-slot-census.md`. The missing field named on #803/#804/#807/#808/#810 ("board part number per slot") is now **found**, and under it a second blocker that is **not a document**. ## 1. Board census, per subrack Huawei's OptiXtrans E9600 board matrix (reprinted by ActForNet, https://www.actfornet.com/solutions/solution/OptiXtrans_E9600_Boards_Overview ; vendor landing page https://support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9605-pid-250732995 , Datasheet "OptiXtrans E9600 Board Datasheet") splits the frame much harder than the slot count suggests. For the E9605 (5 service slots): OTN line boards `TNG1N206` (6x10G), `TNG1N210` (10x10G), `TNG1N401` (1x100G) = **Y**; every tributary, packet, TDM and turbo-WDM board = **NA**; transponder units `TNG1M*`, general `TNG1A212`, mux/demux and ROADM boards = **Y**. So the E9605's client ports can only arrive as a `TNG1M*` transponder or as a line board's ports — 10 board rows against the E9624's ~40. Port counts are printed in the board names: `TNG1N206` 6x10G, `TNG1N210` 10x10G, `TNG1N401` 1x100G, `TNG1T212` 12x10G, `TNV1T410` 10x100G, `TNV2T601` 1x400GE, `TNG1M210D` 10x any-rate + 2xOTU2, `TNG2M604SM` 4x100G -> 1x400G/200G. `OptiXtrans E9605 (5x TNG1N210)` = 50 x 10G with no guessed number. ## 2. The blocker underneath it `engine/media.js` knows `ethernet, wireless, console, usb, coax, dsl, powerline, serial, pon` and Ethernet/storage cages (`rj45` .. `qsfpdd`, `xfp`, `cfp2`, fibre connectors). A `TNG1N210` front-panel port is an **OTU2/OTU2e WDM-side optical port** (published SFP+ module list: 10/40/80 km, DWDM 100 GHz and 50 GHz tunable, CWDM). The only filable combination today is `type: ethernet, connector: sfp+`, which makes it an Ethernet socket that `CAGE_MEDIA['sfp+']` will happily join to a 10G Ethernet peer — the exact "lab refuses to cable" failure the catalogue guards against. There is no `otn`/`wdm` type, and adding one is an `engine/media.js` change this stream must not make. ## 3. URLs checked 2026-11-17 - `https://e.huawei.com/marketingcloud/pep/asset/20000001/Material/0f9e00e3f2ca431693884a01667d7ec6/M3T1A669N1188254857740624027/OptiXtrans E9600 Family -.pdf` — 200, 277,705 B. Brochure: slots 1:1 12 large / 24 small, 1:3 10 large / 20 small (E9624), 13 (E9612), 5 (E9605). No board list. - `https://support.huawei.com/hedex/pages/EDOC1100126589BEJ09047/03/EDOC1100126589BEJ09047/03/resources/help/wdm/9800/hd/line/n210/n210.html` — **403** to a crawler UA: the board description that would settle client-vs-WDM sides. - `https://support.huawei.com/enterprise/en/doc/EDOC1100624531` — 404, unchanged since 2026-11-16. - `https://www.actfornet.com/solutions/solution/OptiXtrans_E9600_Boards_Overview` — 200, partner mirror of the matrix (lead, not evidence). ## What would unblock #807 A project decision on an optical-line port type (an `otn`/`wdm` entry in `engine/media.js` and the faceplate renderer). The board statement is ready the moment one exists: `E9605 (5x TNG1N210)` -> 50 x 10G OTU2 line ports. Until then this PR adds research only — no spec, because a mislabelled port is worse than a missing device. Gates: `node scripts/syntax-check.js` OK (374 files); `audit-port-types` 0 offenders; `audit-devices` no hard defects; `test/hardware-invariants` 26 passed; `regen-registry-doc --check` current; `check-control-bytes` clean.
research(optixtrans): the E9600 board census is public, the port type is not (#807)
All checks were successful
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 11s
CI / Server smoke test (pull_request) Successful in 11s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Successful in 50s
CI / Test (Node 18) (pull_request) Successful in 59s
CI / Test (Node 22) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 5s
b84123dead
jaylouisw force-pushed catalogue/1117-0425 from b84123dead
All checks were successful
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 11s
CI / Server smoke test (pull_request) Successful in 11s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Successful in 50s
CI / Test (Node 18) (pull_request) Successful in 59s
CI / Test (Node 22) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 5s
to 64785d6650
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 11s
CI / Server smoke test (pull_request) Successful in 11s
CI / Docker build (pull_request) Successful in 26s
CI / Test (Node 20) (pull_request) Successful in 56s
CI / Test (Node 18) (pull_request) Successful in 1m5s
CI / Test (Node 22) (pull_request) Successful in 1m5s
CI / Arm auto-merge (pull_request) Successful in 18s
2026-11-17 04:33:39 +00:00
Compare
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!1788
No description provided.