research(optix): E9600 subrack chapters are public; E9612/E9605 service slots are configuration-dependent #1827

Merged
jaylouisw merged 1 commit from catalogue/1117-1031 into main 2026-11-17 10:33:29 +00:00
Owner

Carries the vendor-sourced frame census for #807 and #808 and corrects the service-slot figure those requests quote. Does not close either issue: no client-board chapter, so no port census.

Documents read (anonymous, e-file.huawei.com via the material-page route in scripts/huawei-material-fetch.js)

Findings

  1. E9612 service board slots are 12 (DC master, IU1-IU12) / 10 (AC master, IU3-IU12) / 13 (DC slave, IU1-IU13) / 11 (AC slave, IU3-IU13); the brochure-and-page "13" is the maximum, not the base. Same shape as the E9624 1:1 12/24 vs 1:3 10/20 split.
  2. E9605: 5 service boards in IU1-IU5 and IU73-IU74, PIU/APIU IU100-IU101, EFI IU71-IU72, fan IU90, two CTU 1+1; 177 x 442 x 260 mm (vendor chapter) vs 295 mm on brochure/page � recorded, not resolved. IU73-IU74 residency is an open question, not guessed.
  3. Correction to our own note: the material-page sibling carousel is a recommender, not a document index (an E9605 page recommends OceanStor 5310, CloudEngine 6881H, ...), so it cannot prove the absence of a client-board chapter.

Gates: syntax-check 384 files OK; audit-port-types no contradiction; hardware-invariants 1/1 pass; check-doc-citations exit 0. Research-only: no spec, no engine change, DEVICE_REGISTRY untouched.

Carries the vendor-sourced frame census for #807 and #808 and corrects the service-slot figure those requests quote. Does **not** close either issue: no client-board chapter, so no port census. **Documents read (anonymous, e-file.huawei.com via the material-page route in scripts/huawei-material-fetch.js)** - `OptiXtrans E9612 -` 333,351 B, 6 pp � https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/1df5f09736174bdcaed9ea4e9276bf8b/M3T1A669N1188254859888107676/OptiXtrans%20E9612%20-.pdf - `OptiXtrans E9605 -` 117,447 B, 2 pp � https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/cc7356212e6146b58f38b74dd1102e08/M3T1A669N1188254859704168616/OptiXtrans%20E9605%20-.pdf **Findings** 1. E9612 service board slots are 12 (DC master, IU1-IU12) / 10 (AC master, IU3-IU12) / 13 (DC slave, IU1-IU13) / 11 (AC slave, IU3-IU13); the brochure-and-page "13" is the maximum, not the base. Same shape as the E9624 1:1 12/24 vs 1:3 10/20 split. 2. E9605: 5 service boards in IU1-IU5 and IU73-IU74, PIU/APIU IU100-IU101, EFI IU71-IU72, fan IU90, two CTU 1+1; 177 x 442 x **260** mm (vendor chapter) vs 295 mm on brochure/page � recorded, not resolved. IU73-IU74 residency is an open question, not guessed. 3. Correction to our own note: the material-page sibling carousel is a recommender, not a document index (an E9605 page recommends OceanStor 5310, CloudEngine 6881H, ...), so it cannot prove the absence of a client-board chapter. Gates: syntax-check 384 files OK; audit-port-types no contradiction; hardware-invariants 1/1 pass; check-doc-citations exit 0. Research-only: no spec, no engine change, DEVICE_REGISTRY untouched.
research(optix): the E9600 subrack chapters are public, and the service-slot count is configuration-dependent (#808)
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Classify the change (pull_request) Successful in 8s
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 49s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Test (Node 18) (pull_request) Successful in 59s
CI / Arm auto-merge (pull_request) Successful in 12s
6969df8066
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!1827
No description provided.