research(optixtrans): the TNG2DAP slot table is the DAP's own - the E9600 board matrix is not vendor-readable (#810) #1927

Merged
jaylouisw merged 1 commit from catalogue/1118-0226 into main 2026-11-18 02:35:30 +00:00
Owner

Refs #810 (records a provenance correction; closes nothing).

The open-request row for #810 - rendered into docs/DEVICE_REGISTRY.md - said the E9600 family needed "one client board chapter plus the protection mode", naming TNG1N206, TNG1N210, TNG1N401 "which TNG2DAP section 1.9 shows is valid in all four subracks". That sentence put a second-hand claim in the vendor-sourced column, and it is the one line a later pass would use to write E9624 (24x TNG1N210) believing validity was established.

What section 1.9 actually is. https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/e75c775ac71144e6b522d7cef1601604/M3T1A669N1188254864652623965/TNG2DAP%20-.pdf - 200, application/pdf, 871,676 B, 51 pp, V100R024C00. Section 1.9 "Valid Slots", Table 1, is the DAP amplifier board's own placement table: E9605 = IU1-IU5, E9612 = IU1-IU13, E9624 = IU1-IU24, E9624X = IU1-IU24, one occupied slot each.

Text-layer counts across all 51 pages: N206 0, N210 0, N401 0, 10 Gbit/s 0. The codes the chapter does print are optical-layer and control only (TNG2OACU*, TNG3OACU*, TNG3OBCU*, TNG3OACE*, TNG1/3/4CXP, TNG1HCXP, TNG2HSOCXP, TNG3CXCS*), with no TNZ* at all.

Where the names come from. research/optixtrans-board-census.md section 1: a partner mirror (https://www.actfornet.com/solutions/solution/OptiXtrans_E9600_Boards_Overview, 200, 226,637 B) of hedex EDOC1100126589BEJ09047, the OptiXtrans E9600 (E9624/E9612/E9605) Boards Overview. Re-read today it gives the topic titles and counts (TNG1N210: 10 x 10 Gbit/s Line Service Processing Board) and the system-control/cross-connect mapping table for the three subracks, but no per-subrack Y/NA matrix - Not supported occurs 0 times in its 226,637 B.

Vendor copy still shut, measured at two user-agents. .../hedex/pages/EDOC1100126589BEJ09047/03/.../triu64/t212/t212.html: desktop Chrome/120 gives 403 Access Denied (540 B); Googlebot/2.1 gives 302 to the hdx.do viewer shell (0 B).

Consequence. The family is blocked on vendor-stated board-to-subrack validity, not on a missing board part number. Rows for #807, #808 and #810 corrected to say so, checked bumped to 2026-11-18, the mirror added to their sources; registry regenerated from research/open-device-requests.json (2 hunks, no other page touched). Detail: research/optixtrans-dap-slots-are-dap-only.md.

Gates: syntax-check 403 files OK; audit-port-types no port contradicts its type; hardware-invariants 26/26; request-queue 32/32; check-control-bytes clean; regen-registry-doc idempotent on a second run.

Refs #810 (records a provenance correction; closes nothing). The open-request row for #810 - rendered into `docs/DEVICE_REGISTRY.md` - said the E9600 family needed "one client board chapter plus the protection mode", naming `TNG1N206`, `TNG1N210`, `TNG1N401` "which `TNG2DAP` section 1.9 shows is valid in all four subracks". That sentence put a second-hand claim in the vendor-sourced column, and it is the one line a later pass would use to write `E9624 (24x TNG1N210)` believing validity was established. **What section 1.9 actually is.** `https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/e75c775ac71144e6b522d7cef1601604/M3T1A669N1188254864652623965/TNG2DAP%20-.pdf` - 200, `application/pdf`, 871,676 B, 51 pp, V100R024C00. Section 1.9 "Valid Slots", Table 1, is the DAP amplifier board's own placement table: E9605 = IU1-IU5, E9612 = IU1-IU13, E9624 = IU1-IU24, E9624X = IU1-IU24, one occupied slot each. Text-layer counts across all 51 pages: `N206` 0, `N210` 0, `N401` 0, `10 Gbit/s` 0. The codes the chapter does print are optical-layer and control only (`TNG2OACU*`, `TNG3OACU*`, `TNG3OBCU*`, `TNG3OACE*`, `TNG1/3/4CXP`, `TNG1HCXP`, `TNG2HSOCXP`, `TNG3CXCS*`), with no `TNZ*` at all. **Where the names come from.** `research/optixtrans-board-census.md` section 1: a partner mirror (`https://www.actfornet.com/solutions/solution/OptiXtrans_E9600_Boards_Overview`, 200, 226,637 B) of hedex `EDOC1100126589BEJ09047`, the *OptiXtrans E9600 (E9624/E9612/E9605) Boards Overview*. Re-read today it gives the topic titles and counts (`TNG1N210: 10 x 10 Gbit/s Line Service Processing Board`) and the system-control/cross-connect mapping table for the three subracks, but no per-subrack Y/NA matrix - `Not supported` occurs 0 times in its 226,637 B. **Vendor copy still shut, measured at two user-agents.** `.../hedex/pages/EDOC1100126589BEJ09047/03/.../triu64/t212/t212.html`: desktop Chrome/120 gives 403 Access Denied (540 B); `Googlebot/2.1` gives 302 to the `hdx.do` viewer shell (0 B). **Consequence.** The family is blocked on vendor-stated board-to-subrack validity, not on a missing board part number. Rows for #807, #808 and #810 corrected to say so, `checked` bumped to 2026-11-18, the mirror added to their sources; registry regenerated from `research/open-device-requests.json` (2 hunks, no other page touched). Detail: `research/optixtrans-dap-slots-are-dap-only.md`. Gates: `syntax-check` 403 files OK; `audit-port-types` no port contradicts its type; `hardware-invariants` 26/26; `request-queue` 32/32; `check-control-bytes` clean; `regen-registry-doc` idempotent on a second run.
research(optixtrans): TNG2DAP section 1.9 is the DAP board's own slot table, not a board-to-subrack matrix (#810)
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 5s
CI / Server smoke test (pull_request) Successful in 5s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Successful in 47s
CI / Test (Node 18) (pull_request) Successful in 58s
CI / Test (Node 22) (pull_request) Successful in 51s
CI / Arm auto-merge (pull_request) Successful in 5s
9855de6513
The open-request row for #810 said TNG1N206/N210/N401 are "valid in all four
subracks, which TNG2DAP section 1.9 shows". Section 1.9 of the 51-page TNG2DAP
chapter is Table 1 "Valid slots" for the DAP amplifier board itself (E9605
IU1-IU5, E9612 IU1-IU13, E9624/E9624X IU1-IU24), and N206/N210/N401 occur zero
times in the whole text layer. The board names and counts come from the gated
OptiXtrans E9600 Boards Overview (EDOC1100126589/BEJ09047), readable today only
through a partner mirror, whose surviving copy states names and counts but no
Y/NA per-subrack matrix ("Not supported": 0 occurrences in 226,637 B).

So the family is blocked on vendor-stated board-to-subrack validity, not on a
missing board part number. Row corrected for #807/#808/#810; registry
regenerated. No spec added, nothing closed.
jaylouisw force-pushed catalogue/1118-0226 from 9855de6513
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 5s
CI / Server smoke test (pull_request) Successful in 5s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Successful in 47s
CI / Test (Node 18) (pull_request) Successful in 58s
CI / Test (Node 22) (pull_request) Successful in 51s
CI / Arm auto-merge (pull_request) Successful in 5s
to b2935d552e
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 3s
CI / Classify the change (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 49s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Arm auto-merge (pull_request) Successful in 10s
2026-11-18 02:33:37 +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!1927
No description provided.