huawei: model the OptiXtrans E9605 as a stated 5x TNG1N210 build #1955

Merged
jaylouisw merged 1 commit from catalogue/1118-0756 into main 2026-11-18 08:16:12 +00:00
Owner

Fixes #807

Device: Huawei OptiXtrans E9605, modelled as the stated build 5x TNG1N210 - 50x 10G WDM-side line ports, each carrying one OTU2/OTU2e wavelength.
Spec: devices/huawei/optixtrans-e9605.json (plus research/optixtrans-e9605-stated-build.md; #807 removed from research/open-device-requests.json with the registry doc regenerated).

Sources read this run (2026-11-18):

Why this is not a guess: validity and port count are one reading of one chapter, not two inferences - five slots x ten line ports. The vendor copy (EDOC1100163901, OptiXtrans E9600 Board Datasheet) is still 302 -> /view/notFound, so the notes record which fields were read from the partner copy and which from huawei.com; the E6616/E6608 specs already carry the same disclosure for their board census. TNG2DAP section 1.9 is used only for the IU numbering, never for validity (research/optixtrans-dap-slots-are-dap-only.md). #808 and #810 stay open: their slot counts move with the power configuration and are not settled by this reading.

Gates: node scripts/syntax-check.js 408 files OK; node scripts/audit-port-types.js no contradiction; npm run test:hardware 26/26; npm run test:requests 32/32; npm run check:citations 0 suspects; npm test 335 suites, 11,596 assertions, 0 failed. The close-merged-issues queue guard was updated: #807 is no longer an open request, and the test now asserts its model resolves to the new spec file.

Fixes #807 **Device:** Huawei OptiXtrans E9605, modelled as the stated build `5x TNG1N210` - 50x 10G WDM-side line ports, each carrying one OTU2/OTU2e wavelength. **Spec:** `devices/huawei/optixtrans-e9605.json` (plus `research/optixtrans-e9605-stated-build.md`; #807 removed from `research/open-device-requests.json` with the registry doc regenerated). **Sources read this run (2026-11-18):** - https://e.huawei.com/en/products/optical-transmission/optixtrans-e9600 - HTTP 200, 344,532 B: 442 x 295 x 177 mm, **Number of Service Slots 5**, Cross-connect Type **NA**, 120 wavelengths at 50 GHz, line rates 10G-1.2T. - https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/e75c775ac71144e6b522d7cef1601604/M3T1A669N1188254864652623965/TNG2DAP%20-.pdf - 871,676 B, 51 pp: section 1.9 Valid Slots, E9605 = IU1-IU5 for a single-slot board. - https://www.actfornet.com/solutions/solution/OptiXtrans_E9600_Boards_Overview - HTTP 200, 226,637 B: verbatim copy of the OptiXtrans E9600 (E9624/E9612/E9605) Boards Overview chapter (EDOC1100126589BEJ09047; its 127 support.huawei.com/hedex topic links identify the chapter). Table 3 prints `TNG1N206 TNG1N210 | 1:1 Y 1:3 Y | Y | Y` - valid in the E9605 subrack; Table 1 names `TNG1N210: 10 x 10 Gbit/s Line Service Processing Board`. **Why this is not a guess:** validity and port count are one reading of one chapter, not two inferences - five slots x ten line ports. The vendor copy (`EDOC1100163901`, OptiXtrans E9600 Board Datasheet) is still 302 -> /view/notFound, so the notes record which fields were read from the partner copy and which from huawei.com; the E6616/E6608 specs already carry the same disclosure for their board census. `TNG2DAP` section 1.9 is used only for the IU numbering, never for validity (`research/optixtrans-dap-slots-are-dap-only.md`). #808 and #810 stay open: their slot counts move with the power configuration and are not settled by this reading. **Gates:** `node scripts/syntax-check.js` 408 files OK; `node scripts/audit-port-types.js` no contradiction; `npm run test:hardware` 26/26; `npm run test:requests` 32/32; `npm run check:citations` 0 suspects; `npm test` 335 suites, 11,596 assertions, 0 failed. The close-merged-issues queue guard was updated: #807 is no longer an open request, and the test now asserts its model resolves to the new spec file.
huawei: model the OptiXtrans E9605 as a stated 5x TNG1N210 build (Fixes #807)
All checks were successful
CI / Classify the change (pull_request) Successful in 5s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 10s
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Successful in 48s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Arm auto-merge (pull_request) Successful in 19s
61f85d9571
The E9605 leaves the open-request queue. Its two missing fields arrive in one
vendor chapter rather than two inferences: the OptiXtrans E9600 (E9624/E9612/
E9605) Boards Overview prints TNG1N206/TNG1N210 as valid in the E9605 subrack
(Table 3, 'Y') and names the board '10 x 10 Gbit/s Line Service Processing
Board' (Table 1). Five service slots (vendor product page) x 10 line ports =
50 x 10G WDM-side ports, each an OTU2/OTU2e wavelength.

The chapter is behind the support wall, so the notes say which fields were read
from the verbatim partner copy and which from huawei.com - the same disclosure
the E6616/E6608 specs carry for their board census. No field is taken from a
sibling frame: TNG2DAP 1.9 supplies the IU1-IU5 numbering only.

Line ports are filed ethernet/sfp+ as the house convention for OTN optics
(e6616, waveserver-ai, fsp-3000, pl-2000m); the protocol compromise is stated in
notes. #808 and #810 stay open - their slot counts move with power configuration.
jaylouisw force-pushed catalogue/1118-0756 from 61f85d9571
All checks were successful
CI / Classify the change (pull_request) Successful in 5s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 10s
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Successful in 48s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Arm auto-merge (pull_request) Successful in 19s
to 845057c757
All checks were successful
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Successful in 46s
CI / Test (Node 18) (pull_request) Successful in 53s
CI / Test (Node 22) (pull_request) Successful in 50s
CI / Arm auto-merge (pull_request) Successful in 11s
2026-11-18 08:14:18 +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!1955
No description provided.