[Device]: OptiXtrans E9624 #810

Closed
opened 2026-11-08 06:21:28 +00:00 by jaylouisw · 11 comments
Owner

Vendor

Huawei

Exact model name

OptiXtrans E9624

Category

Other / not sure

Ports and interfaces

  • 12/24 service slots (1:1 cross-connect mode: 12 large or 24 small slots)
  • Subrack 747.2mm (H) x 442mm (W) x 295mm (D)
  • Line rate per channel up to 1.2 Tbit/s; C/L band, 120 wavelengths @ 50GHz

PoE budget (watts)

None (no PoE output)

Datasheet or product page URL

https://e.huawei.com/en/products/optical-transmission/optixtrans-e9600

What do you want to model with it?

Metro/core optical transport (OTN/WDM) node with ODUk/PKT/VC cross-connect.

Capabilities

OTN/WDM optical transport; SDH/SONET/PDH/Ethernet/SAN/OTN/Video/OSU services

Before submitting

  • I searched the catalog and existing issues, and this model is not there yet.
  • The port list above comes from a datasheet, not from memory or another wiki.
### Vendor Huawei ### Exact model name OptiXtrans E9624 ### Category Other / not sure ### Ports and interfaces - 12/24 service slots (1:1 cross-connect mode: 12 large or 24 small slots) - Subrack 747.2mm (H) x 442mm (W) x 295mm (D) - Line rate per channel up to 1.2 Tbit/s; C/L band, 120 wavelengths @ 50GHz ### PoE budget (watts) None (no PoE output) ### Datasheet or product page URL https://e.huawei.com/en/products/optical-transmission/optixtrans-e9600 ### What do you want to model with it? Metro/core optical transport (OTN/WDM) node with ODUk/PKT/VC cross-connect. ### Capabilities OTN/WDM optical transport; SDH/SONET/PDH/Ethernet/SAN/OTN/Video/OSU services ### Before submitting - [x] I searched the catalog and existing issues, and this model is not there yet. - [x] The port list above comes from a datasheet, not from memory or another wiki.
Author
Owner

Closing status: blocked on a stated configuration.

The OptiXtrans E6600/E9600 specification tables publish what a frame can do - service board slots (E6600: "Number of Service Board Slots: DC chassis 14 / AC chassis 12"), cross-connect capacity, maximum wavelengths and per-channel rate - and nothing about ports, because an OTN subrack has none until service boards are fitted. A 400G/λ, 96-wavelength figure is a capacity, not a socket count.

So the issue stays open; docs/DEVICE_REGISTRY.md §"What is left open, and why" records the reason for the family (#803, #804, #807, #808, #810).

What would close it: the board set you intend to model (e.g. "E6616 with two TN13LSC boards"), or a decision to model the frame's slots as a repeatable module - which would be an engine feature, not a spec file.

Closing status: **blocked on a stated configuration.** The OptiXtrans E6600/E9600 specification tables publish what a *frame* can do - service board slots (E6600: "Number of Service Board Slots: DC chassis 14 / AC chassis 12"), cross-connect capacity, maximum wavelengths and per-channel rate - and nothing about ports, because an OTN subrack has none until service boards are fitted. A 400G/λ, 96-wavelength figure is a capacity, not a socket count. So the issue stays open; `docs/DEVICE_REGISTRY.md` §"What is left open, and why" records the reason for the family (#803, #804, #807, #808, #810). **What would close it:** the board set you intend to model (e.g. "E6616 with two TN13LSC boards"), or a decision to model the frame's slots as a repeatable module - which would be an engine feature, not a spec file.
Author
Owner

Re-checked. Still blocked, on one named file — and the frame arithmetic this request quotes is now vendor-sourced.

Sources read 2026-11-17 (this pass)

  • https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/e75c775ac71144e6b522d7cef1601604/M3T1A669N1188254864652623965/TNG2DAP%20-.pdf — HTTP 200, application/pdf, 871,676 B, 51 pp. §1.9 Valid Slots, Table 1, E9624 row: 1 occupied slot, physical and logical IU1 to IU24, with the footnote "In the 1:3 mode of an E9624 subrack, service boards cannot be installed in slots IU6, IU7, IU18, and IU19." That is 20 in 1:3 mode, which matches the brochure's "10 large slots or 20 small slots" — the 24/20 split is confirmed from the board side, not just the frame table.
  • https://support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9605-pid-250732995 — 200, 436,367 B. Enumerates the document set with IDs (below).
  • EDOC1100163901, EDOC1100156387, EDOC1100625542, EDOC1100456418 — all 302 -> /view/notFound again today; hedex is a 3,728 B SPA shell; hedex/api/navi/<ID> still 401 {"status":401,"message":"NOT LOGIN!"}.

One trap closed. The published board chapters carry the sentence "This document describes all boards supported by the device." That is boilerplate, not an index: the TNG2DAP chapter contains zero occurrences of TNG1N, TNG1M, TNG1T, TNV or TMB1. And TNG2DAP is an amplifier — its port table is IN / OUT / VI / VO / MON, all LC, none a client tributary. So "E9605/E9624 (Nx TNG2DAP)" would be an amplifier shelf, not this request's OTN node. The only chapters public on e-file are optical-layer (TNG2DAP, TNG2SRAPXF, TNG3SRAPXF) plus transceivers; queries for TNG1N206/210/401, TNG1M210D/402/404DM/520SM return nothing. Asset paths are <32-hex material>/M3T1A669N<19 digits>/<file>, so a client chapter cannot be derived from a sibling, and every listing endpoint (contenthub, pep/api/search, /en/search) is 403 from the WAF.

Exact missing field for the E9624: the port census of a board that fits it — a TNG1N*/TNG1M* chapter, or one line of stated configuration (E9624 (N x TNG1N210)).

What closes it in one download: EDOC1100621488 (OptiXtrans E9600 V100R026C00 Product Documentation) or EDOC1100163901 (Board Datasheet, 2026-04-03). Either answers #808 and #810 in the same paste.

Recorded in research/optixtrans-client-board-chapters.md; PR #1819 carries it and does not close this issue. Issue stays open — no spec, no guess.

**Re-checked. Still blocked, on one named file — and the frame arithmetic this request quotes is now vendor-sourced.** **Sources read 2026-11-17 (this pass)** - `https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/e75c775ac71144e6b522d7cef1601604/M3T1A669N1188254864652623965/TNG2DAP%20-.pdf` — HTTP 200, `application/pdf`, 871,676 B, 51 pp. §1.9 *Valid Slots*, Table 1, E9624 row: `1` occupied slot, physical and logical **IU1 to IU24**, with the footnote *"In the 1:3 mode of an E9624 subrack, service boards cannot be installed in slots IU6, IU7, IU18, and IU19."* That is 20 in 1:3 mode, which matches the brochure's "10 large slots or 20 small slots" — the 24/20 split is confirmed from the board side, not just the frame table. - `https://support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9605-pid-250732995` — 200, 436,367 B. Enumerates the document set with IDs (below). - `EDOC1100163901`, `EDOC1100156387`, `EDOC1100625542`, `EDOC1100456418` — all `302 -> /view/notFound` again today; `hedex` is a 3,728 B SPA shell; `hedex/api/navi/<ID>` still `401 {"status":401,"message":"NOT LOGIN!"}`. **One trap closed.** The published board chapters carry the sentence *"This document describes all boards supported by the device."* That is boilerplate, not an index: the TNG2DAP chapter contains **zero** occurrences of `TNG1N`, `TNG1M`, `TNG1T`, `TNV` or `TMB1`. And TNG2DAP is an amplifier — its port table is `IN / OUT / VI / VO / MON`, all `LC`, none a client tributary. So "E9605/E9624 (Nx TNG2DAP)" would be an amplifier shelf, not this request's OTN node. The only chapters public on e-file are optical-layer (`TNG2DAP`, `TNG2SRAPXF`, `TNG3SRAPXF`) plus transceivers; queries for `TNG1N206/210/401`, `TNG1M210D/402/404DM/520SM` return nothing. Asset paths are `<32-hex material>/M3T1A669N<19 digits>/<file>`, so a client chapter cannot be derived from a sibling, and every listing endpoint (`contenthub`, `pep/api/search`, `/en/search`) is 403 from the WAF. **Exact missing field for the E9624:** the port census of a board that fits it — a `TNG1N*`/`TNG1M*` chapter, or one line of stated configuration (`E9624 (N x TNG1N210)`). **What closes it in one download:** `EDOC1100621488` (OptiXtrans E9600 V100R026C00 Product Documentation) or `EDOC1100163901` (Board Datasheet, 2026-04-03). Either answers #808 and #810 in the same paste. Recorded in `research/optixtrans-client-board-chapters.md`; PR #1819 carries it and does **not** close this issue. Issue stays open — no spec, no guess.
Author
Owner

Still blocked on the client board chapter - and this pass found a family trap worth naming before anyone tries to close it from a search hit. PR #1876 records it; it does not close this issue.

1. The E9600 family is four subracks, not three. https://e.huawei.com/en/products/optical-transmission/optixtrans-e9600 (HTTP 200, 344,531 B) has three specification columns - E9624 / E9612 / E9605 - and the string E9624X occurs zero times in those bytes. The fourth subrack has its own page, https://e.huawei.com/en/products/optical-transmission/optixtrans-e9624x (200, 339,739 B).

2. It shares only the slot arithmetic with the E9624.

Parameter OptiXtrans E9624 OptiXtrans E9624X
Height 747.2 mm 825 mm
Service slots 12/24 12/24
Cross-connect type ODUk/PKT/VC SDH/OTN/fgOTN/PKT
Max. rate per channel 1.2 Tbit/s 10 Gbit/s OTN+TDM, 400 Gbit/s ponder
Power supply -48/-60 V DC, 220/110 V AC, 240/336 V HVDC -48/-60 V DC only

A 4.3 U taller SDH-first shelf with no AC option is not this request's box, and modelling it from the X's numbers would repeat the E6608-from-E6608T error the catalogue already corrected once.

3. Huawei's own board documentation splits them functionally. TNG2DAP §1.9 Valid Slots lists four devices - OptiXtrans E9624X | 1 | IU1 to IU24 | IU1 to IU24 - and §1.6 gives Opticallayer ASON | E9605/E9612/E9624 subrack: Supported against Opticallayer ASON | E9624X subrack: Not supported.

4. The wall now covers two named board datasheets. The E9624X support page (.../optixtrans-e9624x-pid-251792361, 200, 436,521 B) links OptiXtrans E9624X Board Datasheet to EDOC1100214449, which answers 302 -> /view/notFound exactly like EDOC1100163901. Its Product Brochure link (/en/documents/products/enterprise-optical-network/05062a0bc9a84a5f9642a37e14d67b96) returns a 200 shell whose text begins 404, with zero asset paths.

What would close it, unchanged: one TNG1N206 (6 x 10G line), TNG1N210 (10 x 10G line) or TNG1N401 (1 x 100G line) chapter with a Port Specifications table - TNG2DAP §1.9 shows each is valid in all four subracks - plus the protection mode. That is E9624 (24x TNG1N210) as a stated card complement, with no guessed field. A readable copy of EDOC1100163901 or EDOC1100214449 would also do it.

Recorded in research/optixtrans-e9624x-fourth-subrack.md and the #810 row of docs/DEVICE_REGISTRY.md §"What is left open, and why".

**Still blocked on the client board chapter - and this pass found a family trap worth naming before anyone tries to close it from a search hit. PR #1876 records it; it does not close this issue.** **1. The E9600 family is four subracks, not three.** `https://e.huawei.com/en/products/optical-transmission/optixtrans-e9600` (HTTP 200, 344,531 B) has three specification columns - E9624 / E9612 / E9605 - and the string `E9624X` occurs **zero** times in those bytes. The fourth subrack has its own page, `https://e.huawei.com/en/products/optical-transmission/optixtrans-e9624x` (200, 339,739 B). **2. It shares only the slot arithmetic with the E9624.** | Parameter | OptiXtrans E9624 | OptiXtrans E9624X | |--|--|--| | Height | 747.2 mm | **825 mm** | | Service slots | 12/24 | 12/24 | | Cross-connect type | ODUk/PKT/VC | **SDH/OTN/fgOTN/PKT** | | Max. rate per channel | 1.2 Tbit/s | **10 Gbit/s OTN+TDM, 400 Gbit/s ponder** | | Power supply | -48/-60 V DC, 220/110 V AC, 240/336 V HVDC | **-48/-60 V DC only** | A 4.3 U taller SDH-first shelf with no AC option is not this request's box, and modelling it from the X's numbers would repeat the E6608-from-E6608T error the catalogue already corrected once. **3. Huawei's own board documentation splits them functionally.** `TNG2DAP` §1.9 *Valid Slots* lists four devices - `OptiXtrans E9624X | 1 | IU1 to IU24 | IU1 to IU24` - and §1.6 gives `Opticallayer ASON | E9605/E9612/E9624 subrack: Supported` against `Opticallayer ASON | E9624X subrack: Not supported`. **4. The wall now covers two named board datasheets.** The E9624X support page (`.../optixtrans-e9624x-pid-251792361`, 200, 436,521 B) links `OptiXtrans E9624X Board Datasheet` to `EDOC1100214449`, which answers `302 -> /view/notFound` exactly like `EDOC1100163901`. Its Product Brochure link (`/en/documents/products/enterprise-optical-network/05062a0bc9a84a5f9642a37e14d67b96`) returns a 200 shell whose text begins `404`, with zero asset paths. **What would close it, unchanged:** one `TNG1N206` (6 x 10G line), `TNG1N210` (10 x 10G line) or `TNG1N401` (1 x 100G line) chapter with a Port Specifications table - `TNG2DAP` §1.9 shows each is valid in all four subracks - plus the protection mode. That is `E9624 (24x TNG1N210)` as a stated card complement, with no guessed field. A readable copy of `EDOC1100163901` or `EDOC1100214449` would also do it. Recorded in `research/optixtrans-e9624x-fourth-subrack.md` and the #810 row of `docs/DEVICE_REGISTRY.md` §"What is left open, and why".
Author
Owner

Re-assessed from scratch 2026-11-17 (last assessment 2026-11-10). Still blocked on one client-board chapter; the stated-build route the NetEngine family used does not exist here, and this pass measured that instead of searching again. Note: PR #1903 / research/optixtrans-stated-config-absent.md; closes nothing.

Frame half (unchanged, vendor-sourced): TNG2DAP §1.9 Valid Slots gives E9624 = IU1–IU24, with the footnote "In the 1:3 mode of an E9624 subrack, service boards cannot be installed in slots IU6, IU7, IU18, and IU19" — 24 small slots in 1:1, 20 in 1:3, which is the brochure's 12 large / 24 small vs 10 / 20. The protection mode must be named in any label.

Why no build can be copied. The M14 spec that closed #799 exists because its datasheet prints part numbers with counts in a power row. The E9600 documents do not:

  • OptiXtrans E9600 Family brochure (200, 277,705 B): TNG 0, TMB 0; the phrase "typical product configuration" is footnote c on the MTBF rows, not a complement.
  • Huawei's OSN 9800 M 26H2 彩页 — the hardware twin (same 12/24, 13, 5, same 747.2 / 347.2 / 177 mm) — prints the same slot arithmetic and likewise no board list, so the twins do not unblock each other either.

Fresh enumeration of this frame's support page (…/optixtrans-e9624-pid-250733004, shared with the E9612 page): 164 unique EDOC ids, requested one at a time at /enterprise/en/doc/<ID> → 45 open (30 of them video / 【Optical Basics】), 119 → /view/notFound; a body scan for TNG1*, TNG2*, TMB1*, TMK*, TNK*, TNV* across all open documents returns nothing. EDOC1100163901, EDOC1100621488 and EDOC1100126589 all answer 302 → /view/notFound today.

Correction so nobody re-walks it: the e.huawei.com sitemaps do not index the chapter set (all 32 sitemap files downloaded — 111,538 <loc>, 4,151 document pages — none of the five known OptiXtrans material hashes appears). "Not in the index" is not evidence of non-publication, and §5 of research/optixtrans-client-board-chapters.md should not be cited for it.

Exact missing field: one client-port board chapter (TNG1N206 6x10G, TNG1N210 10x10G, TNG1N401 1x100G, TNG1A212 12x10G, TNG1T212, TNG1M210D) with its Front Panel + Port Specifications, plus the protection mode for the label. Then it is OptiXtrans E9624 (24x <board>, 1:1 mode) = slots x the board's published count, with no guessed field.

What would unblock it: that chapter PDF, EDOC1100163901 / EDOC1100621488 pasted by a reader with a support session, or a Huawei document stating a configuration line for this frame. E9624X material does not substitute — different height, DC-only power, SDH-first cross-connect.

**Re-assessed from scratch 2026-11-17 (last assessment 2026-11-10). Still blocked on one client-board chapter; the stated-build route the NetEngine family used does not exist here, and this pass measured that instead of searching again.** Note: PR #1903 / `research/optixtrans-stated-config-absent.md`; closes nothing. **Frame half (unchanged, vendor-sourced):** `TNG2DAP` §1.9 Valid Slots gives E9624 = IU1–IU24, with the footnote *"In the 1:3 mode of an E9624 subrack, service boards cannot be installed in slots IU6, IU7, IU18, and IU19"* — 24 small slots in 1:1, 20 in 1:3, which is the brochure's `12 large / 24 small` vs `10 / 20`. The protection mode must be named in any label. **Why no build can be copied.** The M14 spec that closed #799 exists because its datasheet prints part numbers **with counts** in a power row. The E9600 documents do not: - *OptiXtrans E9600 Family* brochure (200, 277,705 B): `TNG` 0, `TMB` 0; the phrase "typical product configuration" is footnote `c` on the MTBF rows, not a complement. - Huawei's OSN 9800 M 26H2 彩页 — the hardware twin (same `12/24`, `13`, `5`, same 747.2 / 347.2 / 177 mm) — prints the same slot arithmetic and likewise no board list, so the twins do not unblock each other either. **Fresh enumeration of this frame's support page** (`…/optixtrans-e9624-pid-250733004`, shared with the E9612 page): 164 unique `EDOC` ids, requested one at a time at `/enterprise/en/doc/<ID>` → **45 open** (30 of them video / *【Optical Basics】*), **119 → `/view/notFound`**; a body scan for `TNG1*`, `TNG2*`, `TMB1*`, `TMK*`, `TNK*`, `TNV*` across all open documents returns nothing. `EDOC1100163901`, `EDOC1100621488` and `EDOC1100126589` all answer `302 → /view/notFound` today. **Correction so nobody re-walks it:** the e.huawei.com sitemaps do not index the chapter set (all 32 sitemap files downloaded — 111,538 `<loc>`, 4,151 document pages — none of the five known OptiXtrans material hashes appears). "Not in the index" is not evidence of non-publication, and §5 of `research/optixtrans-client-board-chapters.md` should not be cited for it. **Exact missing field:** one client-port board chapter (`TNG1N206` 6x10G, `TNG1N210` 10x10G, `TNG1N401` 1x100G, `TNG1A212` 12x10G, `TNG1T212`, `TNG1M210D`) with its Front Panel + Port Specifications, **plus** the protection mode for the label. Then it is `OptiXtrans E9624 (24x <board>, 1:1 mode)` = slots x the board's published count, with no guessed field. **What would unblock it:** that chapter PDF, `EDOC1100163901` / `EDOC1100621488` pasted by a reader with a support session, or a Huawei document stating a configuration line for this frame. `E9624X` material does not substitute — different height, DC-only power, SDH-first cross-connect.
Author
Owner

Re-checked 2026-11-17 23:55 UTC. Still blocked on one client-board chapter - but three surfaces that earlier passes had not measured are now closed, so nobody re-walks them. PR #1920 records it (research/optixtrans-support-portal-census.md §9-10); it closes nothing.

1. A different Huawei TLD is the same deployment. support.huawei.cn had never been tested. Its E6616X product page is a 25,028 B Nuxt shell with zero document links; /enterprise/en/doc/EDOC1100486186 and /enterprise/en/doc/EDOC1100163901 both answer 200 with 3,800 bytes - the identical supportview/lst bundle loader - and supportgateway/view/v1/enterprise/doc/catalogue?nid=EDOC1100163901 returns the same 401 support-view-020003 "need login." as .com. A locale TLD is a CDN edge in front of one gated service, not a second library.

2. info.support.huawei.com is the same wall. …/enterprise/br/optical-transmission/optixtrans-e9624-pid-250733004 → 403 (370 B) for a Chrome UA and 200 / 91,294 B for Googlebot or bare curl - which is the generic support index every dead hedex path already returns. So a 200 from info. is the not-found, exactly the dl.ui.com trap in reverse.

3. There is no asset index to enumerate. e-file.huawei.com/robots.txt and /sitemap.xml → Akamai 403 (387 B / 388 B, errors.edgesuite.net). Material hashes cannot be listed, only guessed, and the 32-hex path is unguessable.

4. ?idPath= is navigation context, not a resolver - tested in the form the site emits. The E9605 support page emits …/enterprise/en/doc/<EDOC>?idPath=24030884|9856748|9858640|250707904|250732995, not bare links. Requested that way, with pipes percent-encoded and a crawler UA: EDOC1100163901 (Board Datasheet, 2026-04-03), EDOC1100456418 (R024C10 Hardware Description, issue 04) and EDOC1100365420 (R023C10 Hardware Description, issue 08) all 404 → /view/notFound, 452,479 B. The last two ids are new to this thread.

Exact missing field, unchanged: one client-port board chapter - TNG1A212 (12x10G), TNG1T212, TNG1M210D, TNG1N206 (6x10G), TNG1N210 (10x10G) or TNG1N401 (1x100G) - carrying its Front Panel and Port Specifications, plus the protection mode for the label. With it this is OptiXtrans E9624 (24x <board>, 1:1 mode) from the 24 service slots in the family spec table, with no guessed field.

What would unblock it: that chapter PDF, EDOC1100163901 pasted by a reader with a support session, or a Huawei document stating a configuration line for this frame. No spec is written from a sibling's numbers.

**Re-checked 2026-11-17 23:55 UTC. Still blocked on one client-board chapter - but three surfaces that earlier passes had not measured are now closed, so nobody re-walks them.** PR #1920 records it (`research/optixtrans-support-portal-census.md` §9-10); it closes nothing. **1. A different Huawei TLD is the same deployment.** `support.huawei.cn` had never been tested. Its E6616X product page is a 25,028 B Nuxt shell with zero document links; `/enterprise/en/doc/EDOC1100486186` and `/enterprise/en/doc/EDOC1100163901` both answer 200 with **3,800 bytes** - the identical `supportview/lst` bundle loader - and `supportgateway/view/v1/enterprise/doc/catalogue?nid=EDOC1100163901` returns the same **401 `support-view-020003` "need login."** as `.com`. A locale TLD is a CDN edge in front of one gated service, not a second library. **2. `info.support.huawei.com` is the same wall.** `…/enterprise/br/optical-transmission/optixtrans-e9624-pid-250733004` → **403** (370 B) for a Chrome UA and **200 / 91,294 B** for Googlebot or bare curl - which is the generic support index every dead `hedex` path already returns. So a 200 from `info.` is the not-found, exactly the `dl.ui.com` trap in reverse. **3. There is no asset index to enumerate.** `e-file.huawei.com/robots.txt` and `/sitemap.xml` → Akamai **403** (387 B / 388 B, `errors.edgesuite.net`). Material hashes cannot be listed, only guessed, and the 32-hex path is unguessable. **4. `?idPath=` is navigation context, not a resolver - tested in the form the site emits.** The E9605 support page emits `…/enterprise/en/doc/<EDOC>?idPath=24030884|9856748|9858640|250707904|250732995`, not bare links. Requested that way, with pipes percent-encoded and a crawler UA: `EDOC1100163901` (Board Datasheet, 2026-04-03), `EDOC1100456418` (R024C10 Hardware Description, issue 04) and `EDOC1100365420` (R023C10 Hardware Description, issue 08) all **404 → `/view/notFound`**, 452,479 B. The last two ids are new to this thread. **Exact missing field, unchanged:** one client-port board chapter - `TNG1A212` (12x10G), `TNG1T212`, `TNG1M210D`, `TNG1N206` (6x10G), `TNG1N210` (10x10G) or `TNG1N401` (1x100G) - carrying its Front Panel and Port Specifications, **plus** the protection mode for the label. With it this is `OptiXtrans E9624 (24x <board>, 1:1 mode)` from the 24 service slots in the family spec table, with no guessed field. **What would unblock it:** that chapter PDF, `EDOC1100163901` pasted by a reader with a support session, or a Huawei document stating a configuration line for this frame. No spec is written from a sibling's numbers.
Author
Owner

Correction to this family's blocker, made from the repo's own record: nothing this project has read says which subrack accepts an N-series board — and the document the open-request row cited for that is the DAP's own slot table. PR #1927 records it; the issue stays open.

1. What was wrong. research/open-device-requests.json (rendered into docs/DEVICE_REGISTRY.md) said the missing field was "one client board chapter plus the protection mode — TNG1N206 (6 x 10 Gbit/s line), TNG1N210 (10 x 10 Gbit/s line) or TNG1N401 (1 x 100 Gbit/s line), which TNG2DAP section 1.9 shows is valid in all four subracks". Read today, section 1.9 of the 51-page TNG2DAP chapter (871,676 B, V100R024C00) is Table 1 Valid slots for the DAP amplifier board: E9605 = IU1–IU5, E9612 = IU1–IU13, E9624 = IU1–IU24, E9624X = IU1–IU24, one occupied slot each, plus the 1:3-mode footnote about IU6/IU7/IU18/IU19. Text-layer counts over all 51 pages: N206 0, N210 0, N401 0, 10 Gbit/s 0. The codes it does carry are amplifier/OSC/control only (TNG2OACU*, TNG3OACU*/TNG3OBCU*/TNG3OACE*, TNG1/3/4CXP, TNG2HSOCXP, TNG3CXCS*); no TNZ*.

2. Where the board names actually come from, and it is second-hand. research/optixtrans-board-census.md §1: a partner mirror, https://www.actfornet.com/solutions/solution/OptiXtrans_E9600_Boards_Overview (200, 226,637 B today), a scrape of hedex EDOC1100126589BEJ09047 — the OptiXtrans E9600 (E9624/E9612/E9605) Boards Overview. Its surviving copy gives the topic titles and counts (TNG1N210: 10 x 10 Gbit/s Line Service Processing Board) and the system-control/cross-connect mapping table for the three subracks, but no per-subrack Y/NA matrix: Not supported occurs 0 times in its 226,637 B. So even the mirror supports the names and counts, not the validity.

3. The vendor copy is gated, re-measured today at two user-agents. …/hedex/pages/EDOC1100126589BEJ09047/03/…/triu64/t212/t212.html → desktop Chrome/120: 403 Access Denied (540 B); Googlebot/2.1: 302, 0 B → hdx.do?docid=EDOC1100126589&tocLibId=BEJ09047&tocLibVer=03 viewer shell.

What would close it (unchanged in kind, one step narrower in name): a vendor copy of the Boards Overview / Board Datasheet (EDOC1100163901) that states board→subrack validity, together with the protection mode (1:1 = 12 large/24 small, 1:3 = 10/20) — or, cheaper and just as good, the requester stating the build, e.g. E9624, 1:1, 24x TNG1N210.

Board part numbers were never the blocker: TNG1N206 6×10G, TNG1N210 10×10G, TNG1N401 1×100G are named with their counts. Validity is. Rows for #807, #808 and #810 corrected; detail in research/optixtrans-dap-slots-are-dap-only.md.

**Correction to this family's blocker, made from the repo's own record: nothing this project has read says which subrack accepts an N-series board — and the document the open-request row cited for that is the DAP's own slot table.** PR #1927 records it; the issue stays open. **1. What was wrong.** `research/open-device-requests.json` (rendered into `docs/DEVICE_REGISTRY.md`) said the missing field was "one client board chapter plus the protection mode — `TNG1N206` (6 x 10 Gbit/s line), `TNG1N210` (10 x 10 Gbit/s line) or `TNG1N401` (1 x 100 Gbit/s line), **which `TNG2DAP` section 1.9 shows is valid in all four subracks**". Read today, section 1.9 of the 51-page TNG2DAP chapter (871,676 B, V100R024C00) is Table 1 *Valid slots* **for the DAP amplifier board**: E9605 = IU1–IU5, E9612 = IU1–IU13, E9624 = IU1–IU24, E9624X = IU1–IU24, one occupied slot each, plus the 1:3-mode footnote about IU6/IU7/IU18/IU19. Text-layer counts over all 51 pages: `N206` **0**, `N210` **0**, `N401` **0**, `10 Gbit/s` **0**. The codes it does carry are amplifier/OSC/control only (`TNG2OACU*`, `TNG3OACU*`/`TNG3OBCU*`/`TNG3OACE*`, `TNG1/3/4CXP`, `TNG2HSOCXP`, `TNG3CXCS*`); no `TNZ*`. **2. Where the board names actually come from, and it is second-hand.** `research/optixtrans-board-census.md` §1: a partner mirror, <https://www.actfornet.com/solutions/solution/OptiXtrans_E9600_Boards_Overview> (200, 226,637 B today), a scrape of hedex `EDOC1100126589BEJ09047` — the *OptiXtrans E9600 (E9624/E9612/E9605) Boards Overview*. Its surviving copy gives the topic titles and counts (`TNG1N210: 10 x 10 Gbit/s Line Service Processing Board`) and the system-control/cross-connect mapping table for the three subracks, but **no** per-subrack Y/NA matrix: `Not supported` occurs **0** times in its 226,637 B. So even the mirror supports the names and counts, not the validity. **3. The vendor copy is gated, re-measured today at two user-agents.** `…/hedex/pages/EDOC1100126589BEJ09047/03/…/triu64/t212/t212.html` → desktop Chrome/120: **403** Access Denied (540 B); `Googlebot/2.1`: **302**, 0 B → `hdx.do?docid=EDOC1100126589&tocLibId=BEJ09047&tocLibVer=03` viewer shell. **What would close it (unchanged in kind, one step narrower in name):** a vendor copy of the *Boards Overview* / Board Datasheet (`EDOC1100163901`) that states board→subrack validity, together with the protection mode (1:1 = 12 large/24 small, 1:3 = 10/20) — or, cheaper and just as good, the requester stating the build, e.g. `E9624, 1:1, 24x TNG1N210`. Board part numbers were never the blocker: `TNG1N206` 6×10G, `TNG1N210` 10×10G, `TNG1N401` 1×100G are named with their counts. Validity is. Rows for #807, #808 and #810 corrected; detail in `research/optixtrans-dap-slots-are-dap-only.md`.
Author
Owner

Re-checked 2026-11-18 04:0x UTC. Two documentation routes this family had never tried are now measured closed, so the family is parked: no further re-check until one of the triggers at the bottom fires.

New this pass (crawler UA, Huawei hosts only)

URL result
https://support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9612-pid-250733000/software 200, 436,216 B. The Downloadable Product Documentation Package entries — including OptiXtrans E9600 V100R026C00 Product Documentation (2026-11-02), i.e. the current release — are not files. Each links to https://support.huawei.com/hedex/hdx.do?docid=EDOC1100621487&lang=en.
that hedex URL 200, 3,728 B, empty <title>, TNG1N 0 — the identical SPA shell already recorded for EDOC1100163901, so the package route ends at the same gate as the chapter route.
https://support.huawei.com/enterprise/en/doc/EDOC1100621487 302 -> /view/notFound.
https://support.huawei.com/enterprise/en/optical-transmission/optix-osn-9800-m24-pid-22048459 200, 442,970 B. Its only Datasheet entry is OptiX OSN 9800 Board Datasheet -> EDOC1000074739; that URL, with and without idPath, answers 302 -> /view/notFound. This matters because the scope sentence that ties the E9600 subracks to the OSN 9800 family is printed in documents filed on exactly that page — the sibling half of the family is gated at the same document.
https://support.huawei.com/enterprise/en/optical-business/optical-transmission-network-pid-9856748 200, 410,648 B, 0 occurrences of the string Datasheet. The index that search engines show with nine datasheet titles is rendered client-side; the server-rendered body carries none, so it cannot be used to enumerate an open board document.

Exact missing fields (unchanged): one service-board part number valid in each of E9605 / E9612 / E9624, plus that board's front-panel census — port count, per-port rate, cage. Grey light at 100 Gbit/s and Maximum Number of Wavelengths: N/A on the E9605/E9612 columns mean every port in these subracks comes from a service board; there is no frame-side fallback.

What would unblock it, concretely. The document exists and Huawei links it from every frame's page; anonymous access is the only barrier. OptiXtrans E9600 Board Datasheet EDOC1100163901 (and, for the X, EDOC1100214449) attached from a logged-in Huawei support account would close #807, #808 and #810 in one PR, because the board-to-subrack matrix is the "stated configuration" this project models from.

Parked, with triggers. Seven passes have now walked this family's public surface to exhaustion. It will be re-checked when (1) a V100R027 or later E9600 document set appears, (2) a board datasheet above becomes readable anonymously, or (3) someone attaches one. Absent those, the next fire should spend its increment on a different request rather than re-reading these URLs.

**Re-checked 2026-11-18 04:0x UTC. Two documentation routes this family had never tried are now measured closed, so the family is parked: no further re-check until one of the triggers at the bottom fires.** **New this pass (crawler UA, Huawei hosts only)** | URL | result | |--|--| | `https://support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9612-pid-250733000/software` | 200, 436,216 B. The *Downloadable Product Documentation Package* entries — including `OptiXtrans E9600 V100R026C00 Product Documentation` (2026-11-02), i.e. the current release — are **not files**. Each links to `https://support.huawei.com/hedex/hdx.do?docid=EDOC1100621487&lang=en`. | | that hedex URL | 200, **3,728 B**, empty `<title>`, `TNG1N` 0 — the identical SPA shell already recorded for `EDOC1100163901`, so the *package* route ends at the same gate as the chapter route. | | `https://support.huawei.com/enterprise/en/doc/EDOC1100621487` | 302 -> `/view/notFound`. | | `https://support.huawei.com/enterprise/en/optical-transmission/optix-osn-9800-m24-pid-22048459` | 200, 442,970 B. Its only Datasheet entry is *OptiX OSN 9800 Board Datasheet* -> `EDOC1000074739`; that URL, with and without `idPath`, answers 302 -> `/view/notFound`. This matters because the scope sentence that ties the E9600 subracks to the OSN 9800 family is printed in documents filed on exactly that page — the sibling half of the family is gated at the same document. | | `https://support.huawei.com/enterprise/en/optical-business/optical-transmission-network-pid-9856748` | 200, 410,648 B, **0** occurrences of the string `Datasheet`. The index that search engines show with nine datasheet titles is rendered client-side; the server-rendered body carries none, so it cannot be used to enumerate an open board document. | **Exact missing fields (unchanged):** one service-board part number valid in each of E9605 / E9612 / E9624, plus that board's front-panel census — port count, per-port rate, cage. Grey light at 100 Gbit/s and `Maximum Number of Wavelengths: N/A` on the E9605/E9612 columns mean every port in these subracks comes from a service board; there is no frame-side fallback. **What would unblock it, concretely.** The document exists and Huawei links it from every frame's page; anonymous access is the only barrier. *OptiXtrans E9600 Board Datasheet* `EDOC1100163901` (and, for the X, `EDOC1100214449`) attached from a logged-in Huawei support account would close #807, #808 and #810 in one PR, because the board-to-subrack matrix is the "stated configuration" this project models from. **Parked, with triggers.** Seven passes have now walked this family's public surface to exhaustion. It will be re-checked when (1) a V100R027 or later E9600 document set appears, (2) a board datasheet above becomes readable anonymously, or (3) someone attaches one. Absent those, the next fire should spend its increment on a different request rather than re-reading these URLs.
Author
Owner

Re-checked 2026-11-18. Still open, but the missing artifact is now named down to the table, and this pass found the trap that sits behind it. PR #1949 (Refs, no spec added); research/optixtrans-board-chapters-name-m-series.md.

1. The census exists, and a reprint shows exactly what it contains. The TNG1N210 chapter reads: 80 x ODU0 / 40 x ODU1 / 80 x ODUflex / 10 x ODU2 <-> 10 x OTU2 and 10 x ODU2e <-> 10 x OTU2e, WDM-side OTU2/OTU2e, pluggable list all SFP+ -10G, single-slot board, 237.1 x 30.5 x 220 mm, 64 W typical / 67 W max — with Valid Slots: OSN 9800 M24 IU1-IU24 (1:1), IU1-IU5, IU8-IU17, IU20-IU24 (1:3); OSN 9800 M12 IU1-IU13; 9800 M05 IU1-IU5 (https://www.thunder-link.com/tng1n210.html, 200, 659,498 B). That is a reseller reprint, so it is a lead and not a citeable source — but it tells the next reader exactly which table to ask for.

2. The trap: that table names the carrier subracks, not the enterprise ones. M05/M12/M24 at IU1-5 / IU1-13 / IU1-24 versus TNG2DAP §1.9's OptiXtrans E9605/E9612/E9624 at the same ranges. They agree slot for slot — the M24 1:3 set is 5+10+5 = 20, exactly the E9624 footnote minus IU6/IU7/IU18/IU19 — so the chapter yields the port census and the placement rule, but not the sentence that pairs E9605 with M05. That join stays an inference (identical counts plus Huawei's own OptiXtrans E9600 (OptiX OSN 9800) document titles on the E9605 support page), which is why this thread is not closed from a reprint.

3. New vendor corroboration, no help on the census. https://e.huawei.com/en/products/optical-transmission/osn-9800 (200, 348,972 B) prints the twin's slot count for the first time: M12 = 13, M24 = 12/24, 347.2 / 747.2 mm. And the OSN 9800 M Series 26H2 brochure, fetched through the documents/products attachment route (20,242,639 B docx), contains TNG1N 0, TNG1M 0, TNV 0, TMB 0 — a brochure is not a census.

Still missing: one vendor copy of that chapter, or the stated build. Cheapest unblock is still one line from the requester: E9624, 1:1, 24x TNG1N210 (or 1:3, 20x), which settles validity, complement and mode together.

**Re-checked 2026-11-18. Still open, but the missing artifact is now named down to the table, and this pass found the trap that sits *behind* it.** PR #1949 (`Refs`, no spec added); `research/optixtrans-board-chapters-name-m-series.md`. **1. The census exists, and a reprint shows exactly what it contains.** The `TNG1N210` chapter reads: *80 x ODU0 / 40 x ODU1 / 80 x ODUflex / 10 x ODU2 <-> 10 x OTU2* and *10 x ODU2e <-> 10 x OTU2e*, WDM-side `OTU2/OTU2e`, pluggable list all `SFP+ -10G`, single-slot board, 237.1 x 30.5 x 220 mm, 64 W typical / 67 W max — with **Valid Slots: OSN 9800 M24 IU1-IU24 (1:1), IU1-IU5, IU8-IU17, IU20-IU24 (1:3); OSN 9800 M12 IU1-IU13; 9800 M05 IU1-IU5** (`https://www.thunder-link.com/tng1n210.html`, 200, 659,498 B). That is a reseller reprint, so it is a lead and not a citeable source — but it tells the next reader exactly which table to ask for. **2. The trap: that table names the carrier subracks, not the enterprise ones.** `M05/M12/M24` at `IU1-5 / IU1-13 / IU1-24` versus `TNG2DAP` §1.9's `OptiXtrans E9605/E9612/E9624` at the same ranges. They agree slot for slot — the M24 1:3 set is 5+10+5 = 20, exactly the E9624 footnote minus IU6/IU7/IU18/IU19 — so the chapter yields the port census and the placement rule, but **not** the sentence that pairs `E9605` with `M05`. That join stays an inference (identical counts plus Huawei's own `OptiXtrans E9600 (OptiX OSN 9800)` document titles on the E9605 support page), which is why this thread is not closed from a reprint. **3. New vendor corroboration, no help on the census.** `https://e.huawei.com/en/products/optical-transmission/osn-9800` (200, 348,972 B) prints the twin's slot count for the first time: M12 = **13**, M24 = **12/24**, 347.2 / 747.2 mm. And the OSN 9800 M Series 26H2 brochure, fetched through the `documents/products` attachment route (20,242,639 B docx), contains `TNG1N` 0, `TNG1M` 0, `TNV` 0, `TMB` 0 — a brochure is not a census. **Still missing:** one vendor copy of that chapter, or the stated build. **Cheapest unblock is still one line from the requester:** `E9624, 1:1, 24x TNG1N210` (or `1:3, 20x`), which settles validity, complement and mode together.
Author
Owner

Re-checked 2026-11-18. Still open - but the last inference in this family is now a Huawei statement, and it came from a document nobody here had read: Huawei's own Common Criteria Security Target.

PR #1952 records it (research/optixtrans-euuc-security-target-brand-join.md); no spec added, nothing closed.

1. The join. EUCC-3089-2026-004 Security Target, Huawei OptiX OSN 9800 & OptiXtrans E9600 management component software, V100R024C10SPC100 - ST, Issue 0.19, 2026-10-14, 87 pp, 3,009,787 B, published by ENISA (https://certification.enisa.europa.eu/document/download/ab9c6a55-bf65-4095-99bb-4e947a28156c_en?filename=EUCC-3089-2026-004%20Security%20Target.pdf, 200). Page 3: "OptiX OSN 9800 is used by both carriers and enterprise networks, and OptiXtrans E9600 is a new commercial brand for enterprise networks." Table 1-1 (p.6) puts both names on one row: OptiX OSN 9800 M24 / OptiXtrans E9624 - CXP: IU71, IU72 - TNG4CXP, and the next row OptiX OSN 9800 M12/M05 / OptiXtrans E9612/E9605 - CTU: IU73, IU74 - TME3CTU. Figures 1-4/1-5/1-6 repeat the pairing per chassis.

So the objection logged at 07:04 today - that an N210 chapter naming only OSN 9800 M24 leaves the E9624 join an inference - no longer holds: a chapter that prints the carrier subrack is admissible for this issue.

2. Free extra: the shelf map is bigger than the service slots. The SCC boards sit outside the IU1-IU24 service range, in IU71/IU72 (E9624) and IU73/IU74 (E9612/E9605), and "all OSN Series devices contain 2 SCC boards". A stated build therefore occupies 24+2 / 13+2 / 5+2 positions.

3. Still missing: the census. TNG1N 0, TNG1M 0, TNG2 0, TMK1 0 in the ST's 87 pages, and no port count for TNG4CXP/TME3CTU. One vendor copy of an N-series chapter (or EDOC1100163901) still settles it; so does the requester's one line, E9624, 1:1, 24x TNG1N210 = 240 x 10G line ports.

4. Closed routes, so they are not re-walked: TNG1N210/206/401/402 -.pdf inside the TNG2DAP asset folder all return S3 AccessDenied (control TNG2DAP -.pdf = 200, 871,676 B), so a chapter is one object with its own token, not a filename in a folder; the e.huawei.com E9600 product page (344,532 B) links no documents, only images; every Google-indexed E9600 chapter on e-file is an optical-layer or transceiver chapter.

Fetch note that cost time: e-file.huawei.com answers a Chrome UA with an Akamai 403 text/html and a crawler UA with 200 application/pdf - a 403 there is not evidence of absence, but a 403 application/xml carrying <Code>AccessDenied</Code> is.

**Re-checked 2026-11-18. Still open - but the last inference in this family is now a Huawei statement, and it came from a document nobody here had read: Huawei's own Common Criteria Security Target.** PR #1952 records it (`research/optixtrans-euuc-security-target-brand-join.md`); no spec added, nothing closed. **1. The join.** `EUCC-3089-2026-004 Security Target`, *Huawei OptiX OSN 9800 & OptiXtrans E9600 management component software, V100R024C10SPC100 - ST*, Issue 0.19, 2026-10-14, 87 pp, 3,009,787 B, published by ENISA (`https://certification.enisa.europa.eu/document/download/ab9c6a55-bf65-4095-99bb-4e947a28156c_en?filename=EUCC-3089-2026-004%20Security%20Target.pdf`, 200). Page 3: *"OptiX OSN 9800 is used by both carriers and enterprise networks, and OptiXtrans E9600 is a new commercial brand for enterprise networks."* Table 1-1 (p.6) puts both names on one row: `OptiX OSN 9800 M24 / OptiXtrans E9624 - CXP: IU71, IU72 - TNG4CXP`, and the next row `OptiX OSN 9800 M12/M05 / OptiXtrans E9612/E9605 - CTU: IU73, IU74 - TME3CTU`. Figures 1-4/1-5/1-6 repeat the pairing per chassis. So the objection logged at 07:04 today - that an N210 chapter naming only `OSN 9800 M24` leaves the E9624 join an inference - no longer holds: a chapter that prints the carrier subrack is admissible for this issue. **2. Free extra: the shelf map is bigger than the service slots.** The SCC boards sit *outside* the IU1-IU24 service range, in IU71/IU72 (E9624) and IU73/IU74 (E9612/E9605), and *"all OSN Series devices contain 2 SCC boards"*. A stated build therefore occupies 24+2 / 13+2 / 5+2 positions. **3. Still missing: the census.** `TNG1N` 0, `TNG1M` 0, `TNG2` 0, `TMK1` 0 in the ST's 87 pages, and no port count for TNG4CXP/TME3CTU. One vendor copy of an N-series chapter (or `EDOC1100163901`) still settles it; so does the requester's one line, `E9624, 1:1, 24x TNG1N210` = 240 x 10G line ports. **4. Closed routes, so they are not re-walked:** `TNG1N210/206/401/402 -.pdf` inside the `TNG2DAP` asset folder all return S3 `AccessDenied` (control `TNG2DAP -.pdf` = 200, 871,676 B), so a chapter is one object with its own token, not a filename in a folder; the e.huawei.com E9600 product page (344,532 B) links no documents, only images; every Google-indexed E9600 chapter on e-file is an optical-layer or transceiver chapter. Fetch note that cost time: `e-file.huawei.com` answers a Chrome UA with an Akamai `403 text/html` and a crawler UA with `200 application/pdf` - a 403 there is not evidence of absence, but a `403 application/xml` carrying `<Code>AccessDenied</Code>` is.
Author
Owner

Re-checked 2026-11-18. Still blocked on one client-board port table; this pass closed the last Info-Finder tool and fixed the user-agent reading that made the support site look withdrawn. PR #1959 / research/optixtrans-infofinder-api.md §7 — Refs, closes nothing.

1. Hardware Center is the third Info-Finder tool and it has no OptiXtrans hardware. POST https://info.support.huawei.com/info-finder/hardware/v4/queryModels with {"domain":"0","language":"en","keyword":"<kw>","toolType":"hardwarecenter"} answers anonymously:

keyword total
"" 8,137 (the whole enterprise part set)
OSN 9800 32 — every row hardwareType:"Optical module" (OSN080N10 CFP 1310 nm 103.125G, OSN040N08 QSFP-DD 400G, OSN010B00/B01 BiDi QSFP28…) — no chassis, no boards
OptiXtrans, E6616X, TNG1N206, TNG1N210, TNG2DAP, TMB1, TNV1T210U 0 each

The board-spec tool (speccenter/v2/getSpecBoards) is already faulted (pbiIdMd5 not unique). So both halves of Info-Finder are now closed by measurement, not by guess. domain:"1" (carrier) returns data:null for every keyword — a separate deployment, not a second dataset.

2. Correction other passes should carry. support.huawei.com product pages answer 200 only to the Googlebot UA. Chrome, Firefox and empty UA all get Akamai 403 (414–463 B, errors.edgesuite.net). With a browser UA this host looks withdrawn; it is not — the document ids still 302 -> /view/notFound, which is a publication decision.

3. Two new R026 ids added to the wall: EDOC1100622610 (OptiXtrans E9600 V100R026C00 Product Description 01) and EDOC1100622612 (Feature Description 01) — both 302 -> /view/notFound, same as EDOC1100621488 / EDOC1100625542. Their hedex equivalents return the same 3,728 B Vue shell.

Exact missing field, unchanged: one client-port board chapter — TNG1N206, TNG1N210, TNG1N401 or TNG1T401 — with a Port Specifications table, plus the cross-connect mode. TNG2DAP §1.9 already proves these are valid in all four E9600 subracks, so the label would be OptiXtrans E9624 (1:3, 20x <board>) with nothing guessed.

What would unblock it: that one e-file chapter, or a readable copy of EDOC1100163901 (Board Datasheet) / EDOC1100622610 from a reader with a support login.

**Re-checked 2026-11-18. Still blocked on one client-board port table; this pass closed the last Info-Finder tool and fixed the user-agent reading that made the support site look withdrawn.** PR #1959 / `research/optixtrans-infofinder-api.md` §7 — `Refs`, closes nothing. **1. Hardware Center is the third Info-Finder tool and it has no OptiXtrans hardware.** `POST https://info.support.huawei.com/info-finder/hardware/v4/queryModels` with `{"domain":"0","language":"en","keyword":"<kw>","toolType":"hardwarecenter"}` answers anonymously: | keyword | total | |--|--| | `""` | 8,137 (the whole enterprise part set) | | `OSN 9800` | 32 — **every row `hardwareType:"Optical module"`** (`OSN080N10` CFP 1310 nm 103.125G, `OSN040N08` QSFP-DD 400G, `OSN010B00/B01` BiDi QSFP28…) — no chassis, no boards | | `OptiXtrans`, `E6616X`, `TNG1N206`, `TNG1N210`, `TNG2DAP`, `TMB1`, `TNV1T210U` | **0** each | The board-spec tool (`speccenter/v2/getSpecBoards`) is already faulted (`pbiIdMd5 not unique`). So both halves of Info-Finder are now closed by measurement, not by guess. `domain:"1"` (carrier) returns `data:null` for every keyword — a separate deployment, not a second dataset. **2. Correction other passes should carry.** `support.huawei.com` product pages answer **200 only to the Googlebot UA**. Chrome, Firefox and empty UA all get Akamai `403` (414–463 B, `errors.edgesuite.net`). With a browser UA this host looks withdrawn; it is not — the document ids still `302 -> /view/notFound`, which is a publication decision. **3. Two new R026 ids added to the wall:** `EDOC1100622610` (*OptiXtrans E9600 V100R026C00 Product Description 01*) and `EDOC1100622612` (*Feature Description 01*) — both `302 -> /view/notFound`, same as `EDOC1100621488` / `EDOC1100625542`. Their hedex equivalents return the same 3,728 B Vue shell. **Exact missing field, unchanged:** one client-port board chapter — `TNG1N206`, `TNG1N210`, `TNG1N401` or `TNG1T401` — with a Port Specifications table, plus the cross-connect mode. `TNG2DAP` §1.9 already proves these are valid in all four E9600 subracks, so the label would be `OptiXtrans E9624 (1:3, 20x <board>)` with nothing guessed. **What would unblock it:** that one e-file chapter, or a readable copy of `EDOC1100163901` (Board Datasheet) / `EDOC1100622610` from a reader with a support login.
Author
Owner

Spec added: PR #1969 — devices/huawei/optixtrans-e9624.json, Fixes #810.

The mode this thread kept waiting for was in the request. Issue body, port line: "12/24 service slots (1:1 cross-connect mode: 12 large or 24 small slots)" — 1:1 stated. That settles it: 1:1 / small slots = IU1-IU24 (TNG2DAP section 1.9) = 24 single-slot TNG1N210 (Boards Overview Table 1: 10 x 10 Gbit/s line) = 240 x 10G line ports. The 1:3 build (20 slots) is named in the spec's notes as a different box rather than averaged in.

So the entry is OptiXtrans E9624 OTN subrack, 1:1 mode, 24x TNG1N210 (240x 10G line). Frame: E9600 Family brochure PDF, E9624 column (24 small / 12 large in 1:1; NOTE on the 11 U -> two 5.5 U split). Cross-connect TNG4CXP in IU71/IU72, outside the service range, per the EUCC Security Target Table 1-1 — that same row is what joins OSN 9800 M24 (the name the board chapters print) to E9624. research/open-device-requests.json loses its #810 row; research/optixtrans-e9624-stated-build.md records the pass.

Note for the same-thread record: open PR #1934 also carried an E9624 spec (identical 240-port reading) alongside E9605/E9612 specs that have since landed as #1955/#1962 — its E9624 third is superseded by #1969, and I have said so there.

Spec added: **PR #1969** — `devices/huawei/optixtrans-e9624.json`, `Fixes #810`. **The mode this thread kept waiting for was in the request.** Issue body, port line: "12/24 service slots (1:1 cross-connect mode: 12 large or 24 small slots)" — 1:1 stated. That settles it: 1:1 / small slots = IU1-IU24 (TNG2DAP section 1.9) = 24 single-slot TNG1N210 (Boards Overview Table 1: 10 x 10 Gbit/s line) = **240 x 10G line ports**. The 1:3 build (20 slots) is named in the spec's notes as a different box rather than averaged in. So the entry is `OptiXtrans E9624 OTN subrack, 1:1 mode, 24x TNG1N210 (240x 10G line)`. Frame: E9600 Family brochure PDF, E9624 column (24 small / 12 large in 1:1; NOTE on the 11 U -> two 5.5 U split). Cross-connect TNG4CXP in IU71/IU72, outside the service range, per the EUCC Security Target Table 1-1 — that same row is what joins `OSN 9800 M24` (the name the board chapters print) to `E9624`. `research/open-device-requests.json` loses its #810 row; `research/optixtrans-e9624-stated-build.md` records the pass. Note for the same-thread record: open PR #1934 also carried an E9624 spec (identical 240-port reading) alongside E9605/E9612 specs that have since landed as #1955/#1962 — its E9624 third is superseded by #1969, and I have said so there.
Sign in to join this conversation.
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#810
No description provided.