research(optix): the E9600 family has a fourth subrack, E9624X (#810) #1876

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

Refs #810 (does not close it - the client board chapter is still missing).

New this pass: the E9600 family has a fourth subrack, and it is easy to confuse with the E9624.

  • https://e.huawei.com/en/products/optical-transmission/optixtrans-e9600 (200, 344,531 B) prints three columns - E9624 / E9612 / E9605 - and the string E9624X occurs zero times in those bytes.
  • https://e.huawei.com/en/products/optical-transmission/optixtrans-e9624x (200, 339,739 B) is the fourth subrack's own page: 825 x 442 x 295 mm, 12/24 service slots, cross-connect SDH/OTN/fgOTN/PKT, 10 Gbit/s OTN+TDM / 400 Gbit/s ponder per channel, -48/-60 V DC only. The E9624 is 747.2 mm tall, ODUk/PKT/VC, 1.2 Tbit/s per channel, DC + AC + HVDC. Only the slot arithmetic is shared.
  • TNG2DAP section 1.9 lists all four devices (E9624X: IU1 to IU24) and section 1.6 gives the functional split: Opticallayer ASON | E9605/E9612/E9624 subrack: Supported / E9624X subrack: Not supported.
  • The X has its own Board Datasheet, EDOC1100214449, linked from https://support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9624x-pid-251792361 (200, 436,521 B). It answers 302 -> /view/notFound, byte-for-byte the same as EDOC1100163901. The wall now covers two named board datasheets.
  • The same page's Product Brochure link (/en/documents/products/enterprise-optical-network/05062a0bc9a84a5f9642a37e14d67b96) returns a 200 shell whose text begins 404 with zero pep/asset/.../Material/... paths; scripts/huawei-material-fetch.js reports no asset path in the page.

Unchanged blocker: one TNG1N206 / TNG1N210 / TNG1N401 board chapter with a Port Specifications table, plus the protection mode (1:1 = 24, 1:3 = 20 usable slots). That yields E9624 (24x TNG1N210) as a stated card complement and needs no guessed field. A readable copy of EDOC1100163901 or EDOC1100214449 would also do it.

Files: research/optixtrans-e9624x-fourth-subrack.md (new), research/open-device-requests.json + regenerated docs/DEVICE_REGISTRY.md.

Gates: syntax-check 392 files OK; audit-port-types no contradiction; hardware-invariants 26 passed; request-queue 23 passed; doc-catalog-counts 43 passed; regen-registry-doc --check current (2,348 models / 258 vendors / 29,235 sockets).

Refs #810 (does not close it - the client board chapter is still missing). **New this pass: the E9600 family has a fourth subrack, and it is easy to confuse with the E9624.** - `https://e.huawei.com/en/products/optical-transmission/optixtrans-e9600` (200, 344,531 B) prints three columns - E9624 / E9612 / E9605 - and the string `E9624X` occurs **zero** times in those bytes. - `https://e.huawei.com/en/products/optical-transmission/optixtrans-e9624x` (200, 339,739 B) is the fourth subrack's own page: **825 x 442 x 295 mm**, 12/24 service slots, cross-connect **SDH/OTN/fgOTN/PKT**, **10 Gbit/s OTN+TDM / 400 Gbit/s ponder** per channel, **-48/-60 V DC only**. The E9624 is 747.2 mm tall, ODUk/PKT/VC, 1.2 Tbit/s per channel, DC + AC + HVDC. Only the slot arithmetic is shared. - `TNG2DAP` section 1.9 lists all four devices (E9624X: IU1 to IU24) and section 1.6 gives the functional split: `Opticallayer ASON | E9605/E9612/E9624 subrack: Supported` / `E9624X subrack: Not supported`. - The X has its own Board Datasheet, `EDOC1100214449`, linked from `https://support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9624x-pid-251792361` (200, 436,521 B). It answers **302 -> /view/notFound**, byte-for-byte the same as `EDOC1100163901`. The wall now covers two named board datasheets. - The same page's Product Brochure link (`/en/documents/products/enterprise-optical-network/05062a0bc9a84a5f9642a37e14d67b96`) returns a 200 shell whose text begins `404` with **zero** `pep/asset/.../Material/...` paths; `scripts/huawei-material-fetch.js` reports `no asset path in the page`. **Unchanged blocker:** one `TNG1N206` / `TNG1N210` / `TNG1N401` board chapter with a Port Specifications table, plus the protection mode (1:1 = 24, 1:3 = 20 usable slots). That yields `E9624 (24x TNG1N210)` as a stated card complement and needs no guessed field. A readable copy of `EDOC1100163901` or `EDOC1100214449` would also do it. Files: `research/optixtrans-e9624x-fourth-subrack.md` (new), `research/open-device-requests.json` + regenerated `docs/DEVICE_REGISTRY.md`. Gates: `syntax-check` 392 files OK; `audit-port-types` no contradiction; `hardware-invariants` 26 passed; `request-queue` 23 passed; `doc-catalog-counts` 43 passed; `regen-registry-doc --check` current (2,348 models / 258 vendors / 29,235 sockets).
research(optix): the E9600 family has a fourth subrack, E9624X (#810)
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Classify the change (pull_request) Successful in 10s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 25s
CI / Test (Node 20) (pull_request) Successful in 49s
CI / Test (Node 18) (pull_request) Successful in 55s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Arm auto-merge (pull_request) Successful in 17s
e899387d8b
The E9600 family page prints three columns (E9624/E9612/E9605) and the string
"E9624X" occurs zero times in its 344,531 bytes, but Huawei ships a fourth
subrack with its own product page and its own spec table: 825 x 442 x 295 mm,
12/24 service slots, cross-connect SDH/OTN/fgOTN/PKT, 10 Gbit/s OTN+TDM and
400 Gbit/s ponder per channel, -48/-60 V DC only. Against the E9624 that is a
different height, a different backplane, a different pluggable rate and no AC
option - so answering #810 from the E9624X page would repeat the
E6608-from-E6608T error.

TNG2DAP 1.9 lists all four subracks (E9624X IU1-IU24) and 1.6 gives the
functional split (optical-layer ASON supported on E9605/E9612/E9624, not on
E9624X). The X has its own Board Datasheet, EDOC1100214449, which 302s to
/view/notFound exactly like EDOC1100163901, and its Product Brochure link
renders a 404 shell with no asset path - both measured this pass.

The blocker is unchanged and now covers two named board datasheets: one
TNG1N206/TNG1N210/TNG1N401 chapter plus the protection mode, which yields
E9624 (24x TNG1N210) as a stated card complement.
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!1876
No description provided.