research(optixtrans): the "(N)-" e-file documents are an uploader bundle, and it holds no client board #1871

Merged
jaylouisw merged 1 commit from catalogue/1117-1625 into main 2026-11-17 16:40:08 +00:00
Owner

Refs #803 (does not close it: the client-board port census is still unpublished).

What this pass did. Walked the one route the threads had described but never exhausted: the six-link "Related Materials" list on every e.huawei.com/en/documents/others/<32-hex> page. Breadth-first from the five optical pages already cited on #803/#807/#808/#810, it drains at 40 pages, 27 of them numbered (2)-(28) with only (1) missing — one uploader's bundle, not a manual's chapter sequence, so (N)- cannot be extended by arithmetic.

Two of them are board chapters, both fetched and read end to end (vendor, anonymous):

chapter bytes content
(6)-UXCME 590,457 TMK5UXCME system control/switching/timing — front panel, indicators, micro switches. Zero occurrences of E6616X, E6608T, E6616, E9605, TMB1, TMK1; no Valid Slots section.
(21)-TMB3AUX 482,177 AUX board — dry contact, orderwire, clock cascading CLK1/TOD1-CLK3/TOD3 / HP1.... Its port table is clock/time and cascading only, no tributary cage. E6616X 0, E6608 0, Valid Slot 0.

So the bundle proves the pipeline — the E6600 documentation is published one chapter per PDF on e-file, anonymously, with four V100R022C10 chapters verified 200 application/pdf today — and it does not hold a client board. It also exposes a template difference that matters for #803: E6600 board chapters carry no Valid Slots table at all, unlike the E9600 TNG2DAP chapter, so even the missing client-board chapter may not state which subrack accepts it.

Route state recorded (2026-11-17, 16:20-16:35 UTC): hedex is closed for every user-agent (hdx.do?docid=EDOC1100163901 403, /hedex/api/doc/ 302, and the Dorado path that answered 200 this morning now 302); Wayback CDX returns [] for the E6600 boards-overview prefixes (info.support.huawei.com variants got IA 503, unverified); dc67ba7b... (the search hit for the E6616 V100R025C10 brochure) now serves a 404 page with no asset path.

Files: research/optixtrans-e-file-numbered-bundle.md (new), research/open-device-requests.json (#803 entry corrected: the blocking wall is the unindexed client board chapter, not hedex), regenerated docs/DEVICE_REGISTRY.md.

Gates: syntax-check 390 files OK; audit-port-types "No port contradicts its declared type"; hardware-invariants 26 passed / 0 failed; check-control-bytes clean; check-doc-citations exit 0. No device spec changed, so no port, speed or PoE figure was touched.

Refs #803 (does not close it: the client-board port census is still unpublished). **What this pass did.** Walked the one route the threads had described but never exhausted: the six-link "Related Materials" list on every `e.huawei.com/en/documents/others/<32-hex>` page. Breadth-first from the five optical pages already cited on #803/#807/#808/#810, it **drains at 40 pages**, 27 of them numbered `(2)`-`(28)` with only `(1)` missing — one uploader's bundle, not a manual's chapter sequence, so `(N)-` cannot be extended by arithmetic. **Two of them are board chapters, both fetched and read end to end (vendor, anonymous):** | chapter | bytes | content | |--|--|--| | `(6)-UXCME` | 590,457 | `TMK5UXCME` system control/switching/timing — front panel, indicators, micro switches. Zero occurrences of `E6616X`, `E6608T`, `E6616`, `E9605`, `TMB1`, `TMK1`; no `Valid Slots` section. | | `(21)-TMB3AUX` | 482,177 | AUX board — dry contact, orderwire, clock cascading `CLK1/TOD1`-`CLK3/TOD3` / `HP1...`. Its port table is clock/time and cascading only, no tributary cage. `E6616X` 0, `E6608` 0, `Valid Slot` 0. | So the bundle proves the pipeline — the E6600 documentation *is* published one chapter per PDF on e-file, anonymously, with four V100R022C10 chapters verified 200 `application/pdf` today — and it does **not** hold a client board. It also exposes a template difference that matters for #803: E6600 board chapters carry no `Valid Slots` table at all, unlike the E9600 `TNG2DAP` chapter, so even the missing client-board chapter may not state which subrack accepts it. **Route state recorded (2026-11-17, 16:20-16:35 UTC):** hedex is closed for every user-agent (`hdx.do?docid=EDOC1100163901` 403, `/hedex/api/doc/` 302, and the Dorado path that answered 200 this morning now 302); Wayback CDX returns `[]` for the E6600 boards-overview prefixes (`info.support.huawei.com` variants got IA 503, unverified); `dc67ba7b...` (the search hit for the E6616 V100R025C10 brochure) now serves a 404 page with no asset path. **Files:** `research/optixtrans-e-file-numbered-bundle.md` (new), `research/open-device-requests.json` (#803 entry corrected: the blocking wall is the unindexed client board chapter, not hedex), regenerated `docs/DEVICE_REGISTRY.md`. **Gates:** `syntax-check` 390 files OK; `audit-port-types` "No port contradicts its declared type"; `hardware-invariants` 26 passed / 0 failed; `check-control-bytes` clean; `check-doc-citations` exit 0. No device spec changed, so no port, speed or PoE figure was touched.
research(optixtrans): the "(N)-" e-file documents are an uploader's bundle, and it holds no client board
All checks were successful
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 23s
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 7s
63e2aba7d4
Enumerates the related-materials graph behind #803/#807/#808/#810 completely:
40 pages, 27 numbered parts (2..28, (1) unpublished). Two of them are board
chapters - (6)-UXCME (TMK5UXCME system control, 590,457 B) and (21)-TMB3AUX
(auxiliary, 482,177 B) - and neither is a client board; neither carries a
Valid Slots table, unlike the E9600 board chapters.

Also records today's route state: hedex 302/403 for every user-agent (the
Dorado path that answered 200 this morning included), no Wayback capture of
the E6600 boards overview, and dc67ba7b... (E6616 V100R025C10 brochure) now
serving a 404 page with no asset path.

Corrects the #803 queue record: E6600 board documentation is published per
chapter on e-file anonymously, so the blocker is the unindexed client board
chapter, not the hedex wall.
jaylouisw force-pushed catalogue/1117-1625 from 63e2aba7d4
All checks were successful
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 23s
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 7s
to 9707df2eca
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 8s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 23s
CI / Test (Node 20) (pull_request) Successful in 46s
CI / Test (Node 22) (pull_request) Successful in 51s
CI / Test (Node 18) (pull_request) Successful in 55s
CI / Arm auto-merge (pull_request) Successful in 17s
2026-11-17 16:38:09 +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!1871
No description provided.