research(optixtrans): the TNG2DAP slot table is the DAP's own - the E9600 board matrix is not vendor-readable (#810) #1927
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1927
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1118-0226"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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", namingTNG1N206,TNG1N210,TNG1N401"whichTNG2DAPsection 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 writeE9624 (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:
N2060,N2100,N4010,10 Gbit/s0. The codes the chapter does print are optical-layer and control only (TNG2OACU*,TNG3OACU*,TNG3OBCU*,TNG3OACE*,TNG1/3/4CXP,TNG1HCXP,TNG2HSOCXP,TNG3CXCS*), with noTNZ*at all.Where the names come from.
research/optixtrans-board-census.mdsection 1: a partner mirror (https://www.actfornet.com/solutions/solution/OptiXtrans_E9600_Boards_Overview, 200, 226,637 B) of hedexEDOC1100126589BEJ09047, 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 supportedoccurs 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.1gives 302 to thehdx.doviewer 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,
checkedbumped to 2026-11-18, the mirror added to their sources; registry regenerated fromresearch/open-device-requests.json(2 hunks, no other page touched). Detail:research/optixtrans-dap-slots-are-dap-only.md.Gates:
syntax-check403 files OK;audit-port-typesno port contradicts its type;hardware-invariants26/26;request-queue32/32;check-control-bytesclean;regen-registry-docidempotent on a second run.9855de6513b2935d552e