research: the E9605 page keeps 110 of its 149 documents, and a tributary board is the cheaper ask (#807) #1887

Merged
jaylouisw merged 1 commit from catalogue/1117-1855 into main 2026-11-17 19:02:52 +00:00
Owner

Records #807; it does not close it.

Three new measurements in research/optixtrans-support-portal-census.md:

§6 - the E9605's own page, counted. https://support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9605-pid-250732995 (200, 436,367 B, crawler UA) links 149 unique document IDs. Requested one at a time: 39 answer 200 (24 videos, 12 Optical Basics issues, 3 documents), 110 answer 302 -> /view/notFound - including EDOC1100163901, OptiXtrans E9600 Board Datasheet. Text census across all 39 bodies: TNG1 0, Port Specifications 0, IU1 0. The E9605's own support page prints no board part number in any document it publishes.

§7 - the article URL shape is not the problem. …/en/doc/EDOC1100400005 (a guide on that same page) answers 200 / 492,157 B, and an article inside it (…/EDOC1100400005/bec365f7/network-management) answers 200 / 484,645 B, while EDOC1100625542 (Hardware Description) and EDOC1100163901 (Board Datasheet) 404 on the same host, same user-agent, same minute. Withholding, not URL grammar.

§8 - a tributary board is the cheaper artifact. The line boards named so far (TNG1N206/210/401) terminate on the WDM side, so engine/media.js can only file them as ethernet/sfp+ - a wrong protocol claim on a real socket. A tributary board carries 10GE LAN as a client service. Candidate: TNG1A212 (12 x 10G any-rate) - a lead only; its E9605 validity and port count come from partner mirrors, not from Huawei, and are recorded as a lead for that reason.

Gates: node scripts/syntax-check.js 393 files OK; node scripts/audit-port-types.js clean; node test/hardware-invariants.test.js 26/26; node test/request-queue.test.js 23/23; node scripts/check-control-bytes.js clean. No spec file changed, so no importer tripwire run was needed.

Records #807; it does not close it. Three new measurements in `research/optixtrans-support-portal-census.md`: **§6 - the E9605's own page, counted.** `https://support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9605-pid-250732995` (200, 436,367 B, crawler UA) links 149 unique document IDs. Requested one at a time: 39 answer 200 (24 videos, 12 *Optical Basics* issues, 3 documents), 110 answer `302 -> /view/notFound` - including `EDOC1100163901`, *OptiXtrans E9600 Board Datasheet*. Text census across all 39 bodies: `TNG1` 0, `Port Specifications` 0, `IU1` 0. The E9605's own support page prints no board part number in any document it publishes. **§7 - the article URL shape is not the problem.** `…/en/doc/EDOC1100400005` (a guide on that same page) answers 200 / 492,157 B, and an article inside it (`…/EDOC1100400005/bec365f7/network-management`) answers 200 / 484,645 B, while `EDOC1100625542` (Hardware Description) and `EDOC1100163901` (Board Datasheet) 404 on the same host, same user-agent, same minute. Withholding, not URL grammar. **§8 - a tributary board is the cheaper artifact.** The line boards named so far (`TNG1N206/210/401`) terminate on the WDM side, so `engine/media.js` can only file them as `ethernet`/`sfp+` - a wrong protocol claim on a real socket. A tributary board carries 10GE LAN as a client service. Candidate: `TNG1A212` (12 x 10G any-rate) - a lead only; its E9605 validity and port count come from partner mirrors, not from Huawei, and are recorded as a lead for that reason. Gates: `node scripts/syntax-check.js` 393 files OK; `node scripts/audit-port-types.js` clean; `node test/hardware-invariants.test.js` 26/26; `node test/request-queue.test.js` 23/23; `node scripts/check-control-bytes.js` clean. No spec file changed, so no importer tripwire run was needed.
research: the E9605 page keeps 110 of its 149 documents, and a tributary board is the cheaper ask (#807)
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 25s
CI / Test (Node 20) (pull_request) Successful in 47s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Arm auto-merge (pull_request) Successful in 20s
2b1ae6ec1d
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!1887
No description provided.