research: the OptiXtrans support portal serves 146 of 174 documents to nobody (#807) #1884

Merged
jaylouisw merged 1 commit from catalogue/1117-1825 into main 2026-11-17 18:38:25 +00:00
Owner

Refs #807

No spec is written: the field #807 needs is still one client-board Port Specifications table, and this PR closes two more routes rather than guessing one.

1. The support portal answers 146 of the 174 document ids on the OSN 9800 M24 page with notFound. https://support.huawei.com/enterprise/en/optical-transmission/optix-osn-9800-m24-pid-22048459 (200, 442,970 B, crawler UA) links 174 unique ids; requested one by one, 146 return 302 -> /view/notFound and 28 return 200. That includes the page own Datasheet entry, OptiX OSN 9800 Board Datasheet -> EDOC1000074739, so the 2014-era EDOC1000 numbering is as closed as the current EDOC11006 one.

2. The 28 that open carry no ports. 24 are videos; the two documents are EDOC1100605036 (User Guide, 550,913 B) and EDOC1100605336 (EUCC statement, 462,529 B). In the User Guide, TNG1N, Port Specifications, IU1 and line service processing occur zero times.

3. One vendor sentence worth keeping. Both documents scope themselves as: "The hardware models covered by this guidance are: The OSN 9800 series (U64E/U32E/M24/M12/M05/P32/P32C) and E9600 series (E9605/E9612/E9624/E9624X)." That makes the E9600 subracks the same hardware family as the OSN 9800 M subracks, so an OSN 9800 board chapter would be acceptable for #807/#808/#810 - but the sentence prints no E9605->M05 pairing, so it is not a licence to borrow the M05 census.

4. carrier.huawei.com closed. 103 archived URLs in its networks/ PDF folder, 8 WDM/OTN, all brochures or datasheets; the OSN 9800 M datasheet text layer (14,161 chars, 6 pp) has 0 TNG1N and 0 N210. The live host 403s every UA tried.

Recorded in research/optixtrans-support-portal-census.md; research/open-device-requests.json #807 row and docs/DEVICE_REGISTRY.md regenerated by npm run regen:registry-doc.

Gates: node scripts/syntax-check.js 393 files OK; node scripts/audit-port-types.js no port contradicts its declared type; node test/hardware-invariants.test.js 26 passed, 0 failed.

Refs #807 No spec is written: the field #807 needs is still one client-board Port Specifications table, and this PR closes two more routes rather than guessing one. **1. The support portal answers 146 of the 174 document ids on the OSN 9800 M24 page with `notFound`.** `https://support.huawei.com/enterprise/en/optical-transmission/optix-osn-9800-m24-pid-22048459` (200, 442,970 B, crawler UA) links 174 unique ids; requested one by one, 146 return 302 -> `/view/notFound` and 28 return 200. That includes the page own Datasheet entry, *OptiX OSN 9800 Board Datasheet* -> `EDOC1000074739`, so the 2014-era `EDOC1000` numbering is as closed as the current `EDOC11006` one. **2. The 28 that open carry no ports.** 24 are videos; the two documents are `EDOC1100605036` (User Guide, 550,913 B) and `EDOC1100605336` (EUCC statement, 462,529 B). In the User Guide, `TNG1N`, `Port Specifications`, `IU1` and `line service processing` occur zero times. **3. One vendor sentence worth keeping.** Both documents scope themselves as: *"The hardware models covered by this guidance are: The OSN 9800 series (U64E/U32E/M24/M12/M05/P32/P32C) and E9600 series (E9605/E9612/E9624/E9624X)."* That makes the E9600 subracks the same hardware family as the OSN 9800 M subracks, so an OSN 9800 board chapter would be acceptable for #807/#808/#810 - but the sentence prints no E9605->M05 pairing, so it is not a licence to borrow the M05 census. **4. carrier.huawei.com closed.** 103 archived URLs in its `networks/` PDF folder, 8 WDM/OTN, all brochures or datasheets; the OSN 9800 M datasheet text layer (14,161 chars, 6 pp) has 0 `TNG1N` and 0 `N210`. The live host 403s every UA tried. Recorded in `research/optixtrans-support-portal-census.md`; `research/open-device-requests.json` #807 row and `docs/DEVICE_REGISTRY.md` regenerated by `npm run regen:registry-doc`. Gates: `node scripts/syntax-check.js` 393 files OK; `node scripts/audit-port-types.js` no port contradicts its declared type; `node test/hardware-invariants.test.js` 26 passed, 0 failed.
research: the OptiXtrans support portal serves 146 of 174 documents to nobody (#807)
All checks were successful
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 54s
CI / Arm auto-merge (pull_request) Successful in 9s
755f0e688e
The OSN 9800 M24 support page links 174 document ids; 146 answer 302 ->
/view/notFound, including its own Datasheet entry (OptiX OSN 9800 Board
Datasheet, EDOC1000074739), so the 2014-era EDOC1000 numbering is as
closed as the current one. Of the 28 that open, 24 are videos and the two
documents (User Guide EDOC1100605036, EUCC EDOC1100605336) contain zero
occurrences of "Port Specifications", "IU1" or TNG1N.

That pair does carry Huawei's scope sentence putting the E9600 series
(E9605/E9612/E9624/E9624X) beside the OSN 9800 M subracks as one hardware
family - so an OSN 9800 board chapter would be acceptable for this family,
but the sentence prints no E9605->M05 pairing and is not a licence to
borrow the M05 census.

Also closed: carrier.huawei.com (103 archived PDFs in its networks folder,
8 WDM/OTN, all brochures; the M datasheet text layer has 0 x TNG1N and
0 x N210), and the crawler-UA requirement this portal needs to render at all.

No spec written: the field is still one client-board Port Specifications
table. Registry row for #807 regenerated from research/open-device-requests.json.
jaylouisw force-pushed catalogue/1117-1825 from 755f0e688e
All checks were successful
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 54s
CI / Arm auto-merge (pull_request) Successful in 9s
to b0960e3e1c
All checks were successful
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 23s
CI / Test (Node 20) (pull_request) Successful in 48s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Arm auto-merge (pull_request) Successful in 20s
2026-11-17 18:36:16 +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!1884
No description provided.