docs(open-requests): the E9600 trio is blocked on a client board chapter, not on a withheld matrix #1849

Merged
jaylouisw merged 1 commit from catalogue/1117-1325 into main 2026-11-17 13:32:25 +00:00
Owner

Refs #807, #808, #810 — records the corrected blocker for the OptiXtrans E9600 family; it closes nothing, because a spec still cannot be written.

The stale claim this fixes. research/open-device-requests.json said all three were blocked on the board-to-subrack matrix in EDOC1100163901, and #807 called that matrix "withheld, not unpublished". It is published. Verified today from the vendor file itself:

  • https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/e75c775ac71144e6b522d7cef1601604/M3T1A669N1188254864652623965/TNG2DAP%20-.pdf — HTTP 200, application/pdf, 871,676 B, 51 pp. pdftotext -layout → §1.9 "Valid Slots", Table 1: OptiXtrans E9605 | 1 | IU1, IU2, IU3, IU4, IU5, E9612 | IU1 to IU13, E9624 | IU1 to IU24, E9624X | IU1 to IU24, plus "In the 1:3 mode of an E9624 subrack, service boards cannot be installed in slots IU6, IU7, IU18, and IU19."

So the frame arithmetic for #807/#808/#810 is vendor-sourced and the registry now says so. What is actually missing is one client board chapter: every indexed e-file chapter is an optical-layer board (TNG2DAP is a 5x LC EDFA), and searches for TNG1N206, TNG1N210, TNG1N401, TNG1M* return the family brochure, the partner mirror or nothing — no chapter PDF.

Why no spec is added. The remaining half is the board's Port Specifications table. Board names print their own counts (TNG1N210: 10 x 10 Gbit/s line service processing board, per the partner mirror and the HCIP-Transmission board table), but the vendor port table is what the evidence rule wants, and the only index of which board fits which subrack outside the partner mirror is the account-walled EDOC1100621488 / EDOC1100163901. Writing E9605 (5x TNG1N210) from a partner mirror plus a board-name convention is the family-sibling guess this catalogue has already corrected three times.

Changes. research/open-device-requests.json entries 807/808/810 rewritten (missing field, unblock condition, sources now include the vendor TNG2DAP chapter); docs/DEVICE_REGISTRY.md regenerated with npm run regen:registry-doc — not hand-edited.

Gates. node scripts/syntax-check.js → 387 files, all OK. node scripts/audit-port-types.js → "No port contradicts its declared type." node scripts/check-control-bytes.js → clean. node scripts/run-tests.js --filter=hardware → 26 assertions, 0 failed. Registry regen reports 2,348 models / 29,235 sockets unchanged.

Refs #807, #808, #810 — records the corrected blocker for the OptiXtrans E9600 family; it closes nothing, because a spec still cannot be written. **The stale claim this fixes.** `research/open-device-requests.json` said all three were blocked on the board-to-subrack matrix in `EDOC1100163901`, and #807 called that matrix "withheld, not unpublished". It is published. Verified today from the vendor file itself: - `https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/e75c775ac71144e6b522d7cef1601604/M3T1A669N1188254864652623965/TNG2DAP%20-.pdf` — HTTP 200, `application/pdf`, 871,676 B, 51 pp. `pdftotext -layout` → §1.9 "Valid Slots", Table 1: `OptiXtrans E9605 | 1 | IU1, IU2, IU3, IU4, IU5`, `E9612 | IU1 to IU13`, `E9624 | IU1 to IU24`, `E9624X | IU1 to IU24`, plus "In the 1:3 mode of an E9624 subrack, service boards cannot be installed in slots IU6, IU7, IU18, and IU19." So the frame arithmetic for #807/#808/#810 is vendor-sourced and the registry now says so. What is actually missing is one **client** board chapter: every indexed e-file chapter is an optical-layer board (`TNG2DAP` is a 5x LC EDFA), and searches for `TNG1N206`, `TNG1N210`, `TNG1N401`, `TNG1M*` return the family brochure, the partner mirror or nothing — no chapter PDF. **Why no spec is added.** The remaining half is the board's Port Specifications table. Board names print their own counts (`TNG1N210: 10 x 10 Gbit/s line service processing board`, per the partner mirror and the HCIP-Transmission board table), but the vendor port table is what the evidence rule wants, and the only index of which board fits which subrack outside the partner mirror is the account-walled `EDOC1100621488` / `EDOC1100163901`. Writing `E9605 (5x TNG1N210)` from a partner mirror plus a board-name convention is the family-sibling guess this catalogue has already corrected three times. **Changes.** `research/open-device-requests.json` entries 807/808/810 rewritten (missing field, unblock condition, sources now include the vendor TNG2DAP chapter); `docs/DEVICE_REGISTRY.md` regenerated with `npm run regen:registry-doc` — not hand-edited. **Gates.** `node scripts/syntax-check.js` → 387 files, all OK. `node scripts/audit-port-types.js` → "No port contradicts its declared type." `node scripts/check-control-bytes.js` → clean. `node scripts/run-tests.js --filter=hardware` → 26 assertions, 0 failed. Registry regen reports 2,348 models / 29,235 sockets unchanged.
docs(open-requests): the E9600 trio is blocked on a client board chapter, not on a withheld matrix
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 13s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Arm auto-merge (pull_request) Successful in 9s
835487c9e8
jaylouisw force-pushed catalogue/1117-1325 from 835487c9e8
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 13s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Arm auto-merge (pull_request) Successful in 9s
to 33cc732153
All checks were successful
CI / Classify the change (pull_request) Successful in 16s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 13s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Arm auto-merge (pull_request) Successful in 15s
2026-11-17 13:30:19 +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!1849
No description provided.