huawei: model the OptiXtrans E9605 as a stated 5x TNG1N210 build #1955
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!1955
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1118-0756"
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?
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(plusresearch/optixtrans-e9605-stated-build.md; #807 removed fromresearch/open-device-requests.jsonwith the registry doc regenerated).Sources read this run (2026-11-18):
TNG1N206 TNG1N210 | 1:1 Y 1:3 Y | Y | Y- valid in the E9605 subrack; Table 1 namesTNG1N210: 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.TNG2DAPsection 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.js408 files OK;node scripts/audit-port-types.jsno contradiction;npm run test:hardware26/26;npm run test:requests32/32;npm run check:citations0 suspects;npm test335 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.61f85d9571845057c757