research(OptiXtrans): the E9600 board datasheet has a vendor link and a document ID - every anonymous route to it is 404 #1808

Merged
jaylouisw merged 1 commit from catalogue/1117-0725 into main 2026-11-17 07:34:00 +00:00
Owner

Refs #807 (not a close: no spec is added, because the one missing field is still missing)

Follow-up to research/optixtrans-board-census.md, which left the E9600 family blocked twice over. This pass narrowed both halves.

1. The board matrix is no longer "unpublished" - it is a named vendor document. The E9605/E9612/E9624 product pages list, under Datasheet, OptiXtrans E9600 Board Datasheet -> EDOC1100163901. Read 2026-11-17 with a crawler UA (200, 436,367 B). Every anonymous route to the document 404s: bare /enterprise/en/doc/EDOC1100163901?idPath=... -> 302 -> view/notFound; the ru locale -> 404; /enterprise/en/datasheet/optixtrans-e9600-board-datasheet-pid-250732995 returns 200 but is the product page again (slug ignored); hedex/hdx.do?docid=EDOC1100163901 returns the 3,728-byte SPA shell, and &format=json returns the same HTML. Control proving the route itself works: EDOC1100318733/4f560405/cabinet-layout-and-connection-planning -> 200, 517,177 B, full document. The current-generation EDOC1100625542 (V100R026C00 HD), EDOC1100622610 (PD) and EDOC1100622612 (FD) fail identically.

2. The port-type blocker was wrong. ciena/6500-s14, adva/fsp-3000, nokia/1830-pss-24x and packetlight/pl-2000m all file WDM/OTN line sides as type: ethernet in QSFP28 cages with a "modelled at this engine's 100G ceiling" caveat. An E9605 (5 x TNG1N210) = 50 x 10G SFP+ line ports can be written in that house style without a new engine type, so the remaining missing field is the board->subrack matrix alone - the contents of EDOC1100163901.

No device spec, no guess: the partner Y/NA mirror stays a lead.

Gates: syntax-check.js 378 files OK; audit-port-types.js "No port contradicts its declared type"; test/hardware-invariants.test.js 26 passed, 0 failed; regen-registry-doc.js --check current at 2,348 models / 258 vendors.

Refs #807 (not a close: no spec is added, because the one missing field is still missing) Follow-up to `research/optixtrans-board-census.md`, which left the E9600 family blocked twice over. This pass narrowed both halves. **1. The board matrix is no longer "unpublished" - it is a named vendor document.** The E9605/E9612/E9624 product pages list, under *Datasheet*, `OptiXtrans E9600 Board Datasheet` -> `EDOC1100163901`. Read 2026-11-17 with a crawler UA (200, 436,367 B). Every anonymous route to the document 404s: bare `/enterprise/en/doc/EDOC1100163901?idPath=...` -> 302 -> `view/notFound`; the `ru` locale -> 404; `/enterprise/en/datasheet/optixtrans-e9600-board-datasheet-pid-250732995` returns 200 but is the product page again (slug ignored); `hedex/hdx.do?docid=EDOC1100163901` returns the 3,728-byte SPA shell, and `&format=json` returns the same HTML. Control proving the route itself works: `EDOC1100318733/4f560405/cabinet-layout-and-connection-planning` -> 200, 517,177 B, full document. The current-generation `EDOC1100625542` (V100R026C00 HD), `EDOC1100622610` (PD) and `EDOC1100622612` (FD) fail identically. **2. The port-type blocker was wrong.** `ciena/6500-s14`, `adva/fsp-3000`, `nokia/1830-pss-24x` and `packetlight/pl-2000m` all file WDM/OTN line sides as `type: ethernet` in QSFP28 cages with a "modelled at this engine's 100G ceiling" caveat. An `E9605 (5 x TNG1N210)` = 50 x 10G SFP+ line ports can be written in that house style without a new engine type, so the remaining missing field is the board->subrack matrix alone - the contents of EDOC1100163901. No device spec, no guess: the partner `Y`/`NA` mirror stays a lead. **Gates:** `syntax-check.js` 378 files OK; `audit-port-types.js` "No port contradicts its declared type"; `test/hardware-invariants.test.js` 26 passed, 0 failed; `regen-registry-doc.js --check` current at 2,348 models / 258 vendors.
research(OptiXtrans): the E9600 board datasheet is named, linked and 404 — and the port-type blocker was wrong (#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 9s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 18) (pull_request) Successful in 52s
CI / Test (Node 20) (pull_request) Successful in 46s
CI / Test (Node 22) (pull_request) Successful in 49s
CI / Arm auto-merge (pull_request) Successful in 24s
dcdbc51162
jaylouisw changed title from research(OptiXtrans): the E9600 board datasheet has a vendor link and a document ID - every anonymous route to it is 404 to CI: bound every network call the rebase maintenance jobs make 2026-11-17 07:31:43 +00:00
jaylouisw changed title from CI: bound every network call the rebase maintenance jobs make to research(OptiXtrans): the E9600 board datasheet has a vendor link and a document ID - every anonymous route to it is 404 2026-11-17 07:32:16 +00:00
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!1808
No description provided.