research: Info-Finder's third tool has no OptiXtrans hardware, and support.huawei.com only answers Googlebot #1959

Merged
jaylouisw merged 1 commit from catalogue/1118-0826 into main 2026-11-18 08:38:16 +00:00
Owner

Refs #810 (does not close it).

Extends research/optixtrans-infofinder-api.md with the tool the earlier pass never asked — Info-Finder Hardware Center (/info-finder/hardware/v4/queryModels), which answers anonymously at domain:"0":

keyword total
"" 8,137
OSN 9800 32, all hardwareType:"Optical module" (no chassis, no boards)
OptiXtrans, E6616X, TNG1N206, TNG1N210, TNG2DAP, TMB1, TNV1T210U 0

The board-spec tool (speccenter) was already closed by pbiIdMd5 not unique in §4. Both halves of Info-Finder are now closed by measurement.

Correction worth keeping: support.huawei.com product pages answer 200 only to the Googlebot UA; Chrome/Firefox/empty UA get Akamai 403 (414‑463 B, errors.edgesuite.net). Read with a browser UA the site looks withdrawn; it is not — the document ids still 302 to /view/notFound.

Two new R026 ids added to the wall: EDOC1100622610 (E9600 V100R026C00 Product Description 01) and EDOC1100622612 (Feature Description 01) → both 302 -> /view/notFound, same as EDOC1100621488 / EDOC1100625542; hedex hdx.do?docid= returns the 3,728 B shell.

Gates: syntax-check.js 410 files OK; audit-port-types.js no contradiction; audit-devices.js no hard defects. Doc-only change, no device spec touched.

Still missing for #810: one client-board port table (TNG1N206/TNG1N210/TNG1N401/TNG1T401), or a stated configuration (E9624, 1:3 mode, 20x <board>).

Refs #810 (does not close it). Extends `research/optixtrans-infofinder-api.md` with the tool the earlier pass never asked — Info-Finder **Hardware Center** (`/info-finder/hardware/v4/queryModels`), which answers anonymously at `domain:"0"`: | keyword | total | |--|--| | `""` | 8,137 | | `OSN 9800` | 32, **all `hardwareType:"Optical module"`** (no chassis, no boards) | | `OptiXtrans`, `E6616X`, `TNG1N206`, `TNG1N210`, `TNG2DAP`, `TMB1`, `TNV1T210U` | **0** | The board-spec tool (`speccenter`) was already closed by `pbiIdMd5 not unique` in §4. Both halves of Info-Finder are now closed by measurement. Correction worth keeping: `support.huawei.com` product pages answer 200 **only** to the Googlebot UA; Chrome/Firefox/empty UA get Akamai 403 (414‑463 B, `errors.edgesuite.net`). Read with a browser UA the site looks withdrawn; it is not — the document ids still 302 to `/view/notFound`. Two new R026 ids added to the wall: `EDOC1100622610` (E9600 V100R026C00 Product Description 01) and `EDOC1100622612` (Feature Description 01) → both `302 -> /view/notFound`, same as `EDOC1100621488` / `EDOC1100625542`; hedex `hdx.do?docid=` returns the 3,728 B shell. Gates: `syntax-check.js` 410 files OK; `audit-port-types.js` no contradiction; `audit-devices.js` no hard defects. Doc-only change, no device spec touched. Still missing for #810: one client-board port table (`TNG1N206`/`TNG1N210`/`TNG1N401`/`TNG1T401`), or a stated configuration (`E9624, 1:3 mode, 20x <board>`).
research: Info-Finder Hardware Center carries no OptiXtrans chassis or boards; Googlebot-UA correction for support.huawei.com (refs #810)
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 9s
CI / Server smoke test (pull_request) Successful in 5s
CI / Docker build (pull_request) Successful in 18s
CI / Test (Node 20) (pull_request) Successful in 49s
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 17s
ec4fdf136f
jaylouisw force-pushed catalogue/1118-0826 from ec4fdf136f
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 9s
CI / Server smoke test (pull_request) Successful in 5s
CI / Docker build (pull_request) Successful in 18s
CI / Test (Node 20) (pull_request) Successful in 49s
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 17s
to d2b2bf0f15
Some checks failed
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 18) (pull_request) Failing after 1m5s
CI / Test (Node 20) (pull_request) Successful in 1m0s
CI / Test (Node 22) (pull_request) Successful in 1m3s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-18 08:34:02 +00:00
Compare
jaylouisw force-pushed catalogue/1118-0826 from d2b2bf0f15
Some checks failed
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 18) (pull_request) Failing after 1m5s
CI / Test (Node 20) (pull_request) Successful in 1m0s
CI / Test (Node 22) (pull_request) Successful in 1m3s
CI / Arm auto-merge (pull_request) Successful in 3s
to 2dd0078b4a
All checks were successful
CI / Classify the change (pull_request) Successful in 5s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 5s
CI / Docker build (pull_request) Successful in 19s
CI / Test (Node 18) (pull_request) Successful in 53s
CI / Test (Node 20) (pull_request) Successful in 44s
CI / Test (Node 22) (pull_request) Successful in 46s
CI / Arm auto-merge (pull_request) Successful in 10s
2026-11-18 08:35:02 +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!1959
No description provided.