research(optixtrans): the e-file board chapter is one board per file, and only optical-layer chapters are public (#810) #1819

Merged
jaylouisw merged 1 commit from catalogue/1117-0855 into main 2026-11-17 09:05:10 +00:00
Owner

Refs #810 — this PR does not close it. It records the evidence that moves #810 from "blocked on an unknown document" to "blocked on one named chapter", and it removes a trap that would otherwise be walked into.

What this pass measured (2026-11-17)

  • support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9605-pid-250732995 (200, 436,367 B, crawler UA) enumerates the whole E9600 family document set with IDs. The eleven package / HD / datasheet IDs are now in the note, so EDOC1100621488 (V100R026C00 Product Documentation) and EDOC1100163901 (Board Datasheet) can be named instead of described. All four doc roots retested today: 302 -> /view/notFound; hedex is a 3,728 B SPA shell; hedex/api/navi still 401 NOT LOGIN.
  • TNG2DAP -.pdf downloaded and read end to end (871,676 B, 51 pp, 123,451 chars of text layer). It carries the sentence "This document describes all boards supported by the device" and zero occurrences of TNG1N, TNG1M, TNG1T, TNV or TMB1. The sentence is boilerplate: the file is one board, so the census still needs the client board chapter.
  • 1.9 Valid Slots gives the E9624 row #810 asked for, from a vendor-hosted file rather than a partner mirror: IU1 to IU24, and "In the 1:3 mode of an E9624 subrack, service boards cannot be installed in slots IU6, IU7, IU18, and IU19." Frame arithmetic is now sourced; ports are not.
  • The chapter that is public must not be used to unblock the request: TNG2DAP is a dual-channel pluggable amplifier, and its own port table lists IN / OUT / VI / VO / MON, all LC, none of them a client tributary. E9605 (5x TNG2DAP) would be a five-slot amplifier shelf — a true statement about a configuration nobody asked for, and a false answer to an OTN node request. Same for TNG2SRAPXF and TNG3SRAPXF.
  • Enumeration is closed: the asset path is <32-hex material>/M3T1A669N<19 digits>/<file> with no relation to the board name, and the listing endpoints (contenthub, pep/api/search, /en/search, e-file /api/search) all answer 403 from the WAF; Bing and DDG scraping returns nothing.

Gates: node scripts/syntax-check.js 382 files all OK; node scripts/audit-port-types.js "No port contradicts its declared type"; node scripts/check-doc-citations.js shows only the four pre-existing drift suspects.

No spec is written: the port census for E9605/E9612/E9624 needs one TNG1N* or TNG1M* chapter, and inventing it is exactly the bug this queue exists to prevent.

Files: research/optixtrans-client-board-chapters.md.

Refs #810 — **this PR does not close it.** It records the evidence that moves #810 from "blocked on an unknown document" to "blocked on one named chapter", and it removes a trap that would otherwise be walked into. **What this pass measured (2026-11-17)** - `support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9605-pid-250732995` (200, 436,367 B, crawler UA) enumerates the whole E9600 family document set with IDs. The eleven package / HD / datasheet IDs are now in the note, so `EDOC1100621488` (V100R026C00 Product Documentation) and `EDOC1100163901` (Board Datasheet) can be named instead of described. All four doc roots retested today: `302 -> /view/notFound`; `hedex` is a 3,728 B SPA shell; `hedex/api/navi` still `401 NOT LOGIN`. - `TNG2DAP -.pdf` downloaded and read end to end (871,676 B, 51 pp, 123,451 chars of text layer). It carries the sentence *"This document describes all boards supported by the device"* and **zero** occurrences of `TNG1N`, `TNG1M`, `TNG1T`, `TNV` or `TMB1`. The sentence is boilerplate: the file is one board, so the census still needs the client board chapter. - `1.9 Valid Slots` gives the E9624 row #810 asked for, from a vendor-hosted file rather than a partner mirror: `IU1 to IU24`, and *"In the 1:3 mode of an E9624 subrack, service boards cannot be installed in slots IU6, IU7, IU18, and IU19."* Frame arithmetic is now sourced; ports are not. - The chapter that *is* public must not be used to unblock the request: TNG2DAP is a dual-channel pluggable amplifier, and its own port table lists `IN / OUT / VI / VO / MON`, all `LC`, none of them a client tributary. `E9605 (5x TNG2DAP)` would be a five-slot amplifier shelf — a true statement about a configuration nobody asked for, and a false answer to an OTN node request. Same for `TNG2SRAPXF` and `TNG3SRAPXF`. - Enumeration is closed: the asset path is `<32-hex material>/M3T1A669N<19 digits>/<file>` with no relation to the board name, and the listing endpoints (`contenthub`, `pep/api/search`, `/en/search`, `e-file /api/search`) all answer 403 from the WAF; Bing and DDG scraping returns nothing. **Gates:** `node scripts/syntax-check.js` 382 files all OK; `node scripts/audit-port-types.js` "No port contradicts its declared type"; `node scripts/check-doc-citations.js` shows only the four pre-existing drift suspects. No spec is written: the port census for E9605/E9612/E9624 needs one `TNG1N*` or `TNG1M*` chapter, and inventing it is exactly the bug this queue exists to prevent. Files: `research/optixtrans-client-board-chapters.md`.
research(optixtrans): the e-file board chapter is one board per file, and only optical-layer chapters are public (#810)
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Classify the change (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 25s
CI / Test (Node 20) (pull_request) Successful in 46s
CI / Test (Node 18) (pull_request) Successful in 54s
CI / Test (Node 22) (pull_request) Successful in 50s
CI / Arm auto-merge (pull_request) Successful in 17s
bf52717905
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!1819
No description provided.