research(optixtrans): the E9600 board chapters are public on e-file, and Valid Slots is the frame census (#807) #1816

Merged
jaylouisw merged 1 commit from catalogue/1117-0825 into main 2026-11-17 08:43:11 +00:00
Owner

Refs #807, #808, #810 — evidence only, no spec (the client-board chapter is still missing).

The E9600 board census is not behind the EDOC1100163901 login wall after all: Huawei publishes the whole OptiXtrans E9600 Product Documentation as one PDF per board on e-file.huawei.com, anonymously, and each chapter carries a Valid Slots table naming the subrack and slot range.

Vendor-hosted, fetched 2026-11-17, HTTP 200 application/pdf:

Re-probed so the next pass does not repeat it: EDOC1100163901 stays 404 on trailing-slash, zh and idPath shapes (452,479 B not-found page); /carrier/en/doc/EDOC1100163901 returns a 3,740 B Vue SPA shell with no anonymous content API; EDOC1100625542 (V100R026C00 HD) is 404 too.

Still missing: one client-port board chapter (TNG1N206/N210/N401, TNG1T*, TNG1M*, TNV1T210U). Search reaches only OA boards and a transceiver module, and an OA board is the wrong panel to hang a lab node on, so no spec is written.

Gates: node scripts/syntax-check.js (380 files OK); node scripts/audit-port-types.js (no contradiction); npm run test:hardware (26 passed, 0 failed); node test/request-queue.test.js (23 passed); node scripts/check-doc-citations.js (pre-existing drift only).

Refs #807, #808, #810 — evidence only, no spec (the client-board chapter is still missing). The E9600 board census is not behind the EDOC1100163901 login wall after all: Huawei publishes the whole *OptiXtrans E9600 Product Documentation* as one PDF per board on e-file.huawei.com, anonymously, and each chapter carries a **Valid Slots** table naming the subrack and slot range. Vendor-hosted, fetched 2026-11-17, HTTP 200 application/pdf: - https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/e75c775ac71144e6b522d7cef1601604/M3T1A669N1188254864652623965/TNG2DAP%20-.pdf (871,676 B, 51 pp) — 1.9 Valid Slots: E9605 IU1-IU5, E9612 IU1-IU13, E9624 IU1-IU24, E9624X IU1-IU24, one slot each; plus: In the 1:3 mode of an E9624 subrack, service boards cannot be installed in slots IU6, IU7, IU18, and IU19 (24-4 = 20, matching the brochure). - https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/08ed3c9aa1274b2c84d9a591d467aaba/M3T1A669N1178216511632400475/OptiXtrans%20E9600%20TNG2SRAPXF.pdf (1,104,102 B, 45 pp) Re-probed so the next pass does not repeat it: EDOC1100163901 stays 404 on trailing-slash, zh and idPath shapes (452,479 B not-found page); /carrier/en/doc/EDOC1100163901 returns a 3,740 B Vue SPA shell with no anonymous content API; EDOC1100625542 (V100R026C00 HD) is 404 too. Still missing: one **client-port** board chapter (TNG1N206/N210/N401, TNG1T*, TNG1M*, TNV1T210U). Search reaches only OA boards and a transceiver module, and an OA board is the wrong panel to hang a lab node on, so no spec is written. Gates: node scripts/syntax-check.js (380 files OK); node scripts/audit-port-types.js (no contradiction); npm run test:hardware (26 passed, 0 failed); node test/request-queue.test.js (23 passed); node scripts/check-doc-citations.js (pre-existing drift only).
research(optixtrans): the E9600 board chapters are public on e-file, and Valid Slots is the frame census (#807)
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Classify the change (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 18) (pull_request) Successful in 58s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Arm auto-merge (pull_request) Successful in 4s
8fe321ecc2
jaylouisw force-pushed catalogue/1117-0825 from 8fe321ecc2
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Classify the change (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 18) (pull_request) Successful in 58s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Arm auto-merge (pull_request) Successful in 4s
to ebb5bc843b
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 / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 48s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Arm auto-merge (pull_request) Successful in 23s
2026-11-17 08:37:51 +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!1816
No description provided.