[Device]: OptiXtrans E9612 #808

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

Vendor

Huawei

Exact model name

OptiXtrans E9612

Category

Other / not sure

Ports and interfaces

  • 13 service slots
  • Subrack 347.2mm (H) x 442mm (W) x 295mm (D)
  • Line rate per channel up to 1.2 Tbit/s

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 optical transport (OTN/WDM) node.

Capabilities

OTN/WDM optical transport; SDH/SONET/Ethernet/SAN/OTN/Video 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 E9612 ### Category Other / not sure ### Ports and interfaces - 13 service slots - Subrack 347.2mm (H) x 442mm (W) x 295mm (D) - Line rate per channel up to 1.2 Tbit/s ### 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 optical transport (OTN/WDM) node. ### Capabilities OTN/WDM optical transport; SDH/SONET/Ethernet/SAN/OTN/Video 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

The frame half of this census is now vendor-sourced, and the "13 service slots" in the request is a maximum, not the base. Still blocked on one field - the client board's port table. PR #1827 carries this note; it does not close the issue.

Document read (Huawei-hosted, HTTP 200, application/pdf, anonymous)
https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/1df5f09736174bdcaed9ea4e9276bf8b/M3T1A669N1188254859888107676/OptiXtrans%20E9612%20-.pdf - OptiXtrans E9600 Product Documentation, OptiXtrans E9612 subrack chapter, 333,351 B, 6 pp. Reached through the material page https://e.huawei.com/en/documents/others/1df5f09736174bdcaed9ea4e9276bf8b (200, 337,523 B), which is server-rendered and carries the asset path inline - the route scripts/huawei-material-fetch.js already encodes. This chapter type (one per frame) had not been fetched before.

What it says about service slots

configuration service board slots slots
DC-powered master 12 IU1-IU12
AC/HVDC-powered master 10 IU3-IU12
DC-powered slave 13 IU1-IU13
AC/HVDC-powered slave 11 IU3-IU13

E3CTU variant: 13 (master or slave, IU1-IU13) / 11 (AC/HVDC, IU3-IU13). One APIU occupies physical slots IU1 and IU2 with logical slot IU1 - which is where the two missing slots go. Other areas: PIU IU100-IU101, fan IU90, TMF1EFI at IU13/logical IU72, TME1EFI IU71-IU72, TME3CTU (master) or AUX (slave) at IU73-IU74. Mechanical 347.2 x 442 x 295 mm, 12.2 kg - matching the brochure, so this is the same subrack.

So the marketplace table's Number of Service Slots 13 and the brochure's 13 are conditional. A model of this frame has to carry the configuration in the label, exactly as the E9624 carries its 1:1 / 1:3 split.

Exact missing field: a client-port board chapter - a TNG1N* / TNG1T* / TNG1M* / TNV* board's Front Panel and Port Specifications. Search by part number (TNG1N206, TNG1N210, TNG1N401, TNG1T401, TNG1M210D, TNV1T210U) still reaches only the family brochure, the ActForNet mirror, an HCIP training deck and resellers. The three published board chapters are all optical-layer (TNG2DAP, TNG2SRAPXF, TNG3SRAPXF).

One caveat on the last pass's reasoning, so nobody leans on it: the sibling carousel on a material page is a recommendation engine, not a document index - an E9605 page recommends OceanStor 5310, CloudEngine 6881H and CloudEngine 16800. Absence from that list is not evidence of absence.

What closes it in one step: any e-file.huawei.com chapter for a client board of this frame, or one stated configuration from a Huawei document ("E9612, DC master, 13 x TNG1N210"). No spec, no guess.

**The frame half of this census is now vendor-sourced, and the "13 service slots" in the request is a maximum, not the base.** Still blocked on one field - the client board's port table. PR #1827 carries this note; it does not close the issue. **Document read (Huawei-hosted, HTTP 200, `application/pdf`, anonymous)** `https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/1df5f09736174bdcaed9ea4e9276bf8b/M3T1A669N1188254859888107676/OptiXtrans%20E9612%20-.pdf` - *OptiXtrans E9600 Product Documentation*, **OptiXtrans E9612** subrack chapter, 333,351 B, 6 pp. Reached through the material page `https://e.huawei.com/en/documents/others/1df5f09736174bdcaed9ea4e9276bf8b` (200, 337,523 B), which is server-rendered and carries the asset path inline - the route `scripts/huawei-material-fetch.js` already encodes. This chapter type (one per *frame*) had not been fetched before. **What it says about service slots** | configuration | service board slots | slots | |--|--|--| | DC-powered master | **12** | IU1-IU12 | | AC/HVDC-powered master | **10** | IU3-IU12 | | DC-powered slave | **13** | IU1-IU13 | | AC/HVDC-powered slave | **11** | IU3-IU13 | E3CTU variant: 13 (master or slave, IU1-IU13) / 11 (AC/HVDC, IU3-IU13). One APIU occupies physical slots IU1 *and* IU2 with logical slot IU1 - which is where the two missing slots go. Other areas: PIU IU100-IU101, fan IU90, TMF1EFI at IU13/logical IU72, TME1EFI IU71-IU72, TME3CTU (master) or AUX (slave) at IU73-IU74. Mechanical 347.2 x 442 x 295 mm, 12.2 kg - matching the brochure, so this is the same subrack. So the marketplace table's `Number of Service Slots 13` and the brochure's 13 are conditional. A model of this frame has to carry the configuration in the label, exactly as the E9624 carries its 1:1 / 1:3 split. **Exact missing field:** a **client-port board chapter** - a `TNG1N*` / `TNG1T*` / `TNG1M*` / `TNV*` board's Front Panel and Port Specifications. Search by part number (`TNG1N206`, `TNG1N210`, `TNG1N401`, `TNG1T401`, `TNG1M210D`, `TNV1T210U`) still reaches only the family brochure, the ActForNet mirror, an HCIP training deck and resellers. The three published board chapters are all optical-layer (`TNG2DAP`, `TNG2SRAPXF`, `TNG3SRAPXF`). **One caveat on the last pass's reasoning, so nobody leans on it:** the sibling carousel on a material page is a recommendation engine, not a document index - an *E9605* page recommends OceanStor 5310, CloudEngine 6881H and CloudEngine 16800. Absence from that list is not evidence of absence. **What closes it in one step:** any `e-file.huawei.com` chapter for a client board of this frame, or one stated configuration from a Huawei document ("E9612, DC master, 13 x TNG1N210"). No spec, no guess.
Author
Owner

This thread's slot figure was wrong, and the enumeration route is now closed by counting rather than by searching. Still blocked on the same field. PR #1855 records it; the issue stays open.

1. "13 service slots, mode-independent, unlike its E9624 sibling" is not what Huawei publishes. The OptiXtrans E9612 - subrack chapter (vendor PDF, 4 pp, read 2026-11-17) gives the slot map per layout and per power option:

subrack layout DC power AC / HVDC power
AUX+SCC IU1-IU12 = 12 service slots IU3-IU12 = 10 (master), 11 (slave)
E3CTU IU1-IU13 = 13 service slots IU3-IU13 = 11

In the case of AC or high-voltage DC power supplies, one APIU board occupies physical service board slots IU1 and IU2, and the occupied logical slot is IU1.

So IU1-IU13 from TNG2DAP section 1.9 is the E3CTU DC figure only. An E9612 with AC power and an APIU has 11 (E3CTU) or 10 (AUX+SCC master) — the same off-by-two the E6616 AC chassis was already found to have. A future E9612 (13x <board>) spec has to name the power option and the layout, exactly as the E9624 has to name its protection mode.

Source: https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/1df5f09736174bdcaed9ea4e9276bf8b/M3T1A669N1188254859888107676/OptiXtrans%20E9612%20-.pdf

2. The board chapter is not "not indexed" — it is absent from an index that has now been counted. https://e.huawei.com/robots.txt lists sitemap-ebg-x-default.xml (11,956 <loc>), of which 881 are document pages (713 unique). Every one is server-rendered with its title in an <h1>; all 713 were fetched. The complete board-chapter set in the public index is two: TNG2DAP (EDFA) and TNG3SRAPXF (Raman + EDFA). TNG1N206, TNG1N210, TNG1N401, TNG1M*, TNG1T*, TNV*, TNK* and TMB1* occur zero times.

3. Also closed today, so the next pass does not re-walk them: the asset bucket refuses to list (/Material/<hash>/, ?list-type=2, ?prefix= -> 403 AccessDenied); info.support.huawei.com/hedex/api/pages/<EDOC>/... answers 200 with the 91,294-byte support index rather than the topic; the per-page "related documents" carousel is a topical mix (it lists an OceanStor 5310 data sheet and a DAG1000 ATA beside TNG2DAP) and not a chapter set; and the vendor file host serves PDFs to an empty User-Agent while returning 403 to a browser UA — a client fingerprint, not a WAF block, which is why three passes recorded that host as unreachable.

Exact missing field, unchanged: the client board's port census — one TNG1N* / TNG1M* chapter with a Port Specifications table.

What would unblock it: that one chapter PDF, or a stated configuration plus the board's port table (e.g. "E9612, AC power, E3CTU layout, 11x TNG1N210"). The remaining routes are EDOC1100621488 and EDOC1100163901 behind the Huawei account wall — access, not effort.

**This thread's slot figure was wrong, and the enumeration route is now closed by counting rather than by searching. Still blocked on the same field. PR #1855 records it; the issue stays open.** **1. "13 service slots, mode-independent, unlike its E9624 sibling" is not what Huawei publishes.** The `OptiXtrans E9612 -` subrack chapter (vendor PDF, 4 pp, read 2026-11-17) gives the slot map per layout and per power option: | subrack layout | DC power | AC / HVDC power | |---|---|---| | AUX+SCC | IU1-IU12 = **12** service slots | IU3-IU12 = **10** (master), 11 (slave) | | E3CTU | IU1-IU13 = **13** service slots | IU3-IU13 = **11** | > In the case of AC or high-voltage DC power supplies, one APIU board occupies physical service board slots IU1 and IU2, and the occupied logical slot is IU1. So `IU1-IU13` from `TNG2DAP` section 1.9 is the **E3CTU DC** figure only. An E9612 with AC power and an APIU has 11 (E3CTU) or 10 (AUX+SCC master) — the same off-by-two the E6616 AC chassis was already found to have. A future `E9612 (13x <board>)` spec has to name the power option and the layout, exactly as the E9624 has to name its protection mode. Source: `https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/1df5f09736174bdcaed9ea4e9276bf8b/M3T1A669N1188254859888107676/OptiXtrans%20E9612%20-.pdf` **2. The board chapter is not "not indexed" — it is absent from an index that has now been counted.** `https://e.huawei.com/robots.txt` lists `sitemap-ebg-x-default.xml` (11,956 `<loc>`), of which 881 are document pages (**713** unique). Every one is server-rendered with its title in an `<h1>`; all 713 were fetched. The complete board-chapter set in the public index is **two**: `TNG2DAP` (EDFA) and `TNG3SRAPXF` (Raman + EDFA). `TNG1N206`, `TNG1N210`, `TNG1N401`, `TNG1M*`, `TNG1T*`, `TNV*`, `TNK*` and `TMB1*` occur **zero** times. **3. Also closed today, so the next pass does not re-walk them:** the asset bucket refuses to list (`/Material/<hash>/`, `?list-type=2`, `?prefix=` -> 403 `AccessDenied`); `info.support.huawei.com/hedex/api/pages/<EDOC>/...` answers 200 with the 91,294-byte support index rather than the topic; the per-page "related documents" carousel is a topical mix (it lists an OceanStor 5310 data sheet and a DAG1000 ATA beside TNG2DAP) and not a chapter set; and the vendor file host serves PDFs to an **empty** User-Agent while returning 403 to a browser UA — a client fingerprint, not a WAF block, which is why three passes recorded that host as unreachable. **Exact missing field, unchanged:** the client board's port census — one `TNG1N*` / `TNG1M*` chapter with a Port Specifications table. **What would unblock it:** that one chapter PDF, or a stated configuration plus the board's port table (e.g. "E9612, AC power, E3CTU layout, 11x TNG1N210"). The remaining routes are `EDOC1100621488` and `EDOC1100163901` behind the Huawei account wall — access, not effort.
Author
Owner

Re-assessed from scratch 2026-11-17 (this issue had not been re-checked since 2026-11-10). The NetEngine-style stated-build route does not exist for the E9600 frames — measured, not assumed — and the blocker is still one client-board chapter. Issue stays open. Note: PR #1903 / research/optixtrans-stated-config-absent.md; it closes nothing.

The frame half, restated because the request's "13 service slots" is a maximum. OptiXtrans E9612 - subrack chapter (https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/1df5f09736174bdcaed9ea4e9276bf8b/M3T1A669N1188254859888107676/OptiXtrans%20E9612%20-.pdf, 200, 333,351 B, 6 pp): DC master 12 (IU1–IU12), AC/HVDC master 10 (IU3–IU12), DC slave 13 (IU1–IU13), AC/HVDC slave 11 (IU3–IU13); E3CTU layout 13 DC / 11 AC. One APIU occupies physical IU1 and IU2 with logical slot IU1. So any future label has to name power option and layout, not just the frame.

Why no build can be copied. devices/huawei/netengine-8000-m14.json exists because the M14 datasheet prints a card complement with counts inside a power row. Nothing in the E9600 set does:

  • OptiXtrans E9600 Family brochure (200, 277,705 B): TNG 0, TMB 0; "typical product configuration" is footnote c on the MTBF rows.
  • The E9612 chapter's own service-board row: "Service boards need to be configured based on the service plan and all of them are installed in the service board area."

Fresh enumeration of this frame's own support page. https://support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9612-pid-250733000 and …-e9624-pid-250733004: 164 unique EDOC ids between them; requested one at a time at /enterprise/en/doc/<ID> → 45 open (30 video / 【Optical Basics】), 119 → /view/notFound. Body scan for TNG1*, TNG2*, TMB1*, TMK*, TNK*, TNV* across all open bodies: empty. The largest open one is EDOC1100605036 Huawei OptiX OSN 9800 and OptiXtrans E9600 User Guide — scope text, no board census. Today EDOC1100163901 (Board Datasheet), EDOC1100621488 (V100R026C00 Product Documentation) and EDOC1100126589 still answer 302 → /view/notFound.

Correction for the next pass: the e.huawei.com sitemaps do not index the chapter set at all (all 32 sitemap files, 111,538 <loc>, 4,151 document pages downloaded; none of the five known OptiXtrans material hashes appears), so "absent from the index" is not evidence of non-publication.

Exact missing field: one client-port board chapter — TNG1N206, TNG1N210, TNG1N401, TNG1A212, TNG1T212, TNG1M210D — with its Front Panel and Port Specifications table. With it the spec is OptiXtrans E9612 (13x <board>, DC slave, E3CTU) = slots x the board's own published port count, and nothing is guessed.

What would unblock it: that one e-file.huawei.com chapter PDF, or EDOC1100163901 / EDOC1100621488 pasted by a reader with a support login.

**Re-assessed from scratch 2026-11-17 (this issue had not been re-checked since 2026-11-10). The NetEngine-style stated-build route does not exist for the E9600 frames — measured, not assumed — and the blocker is still one client-board chapter. Issue stays open.** Note: PR #1903 / `research/optixtrans-stated-config-absent.md`; it closes nothing. **The frame half, restated because the request's "13 service slots" is a maximum.** `OptiXtrans E9612 -` subrack chapter (`https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/1df5f09736174bdcaed9ea4e9276bf8b/M3T1A669N1188254859888107676/OptiXtrans%20E9612%20-.pdf`, 200, 333,351 B, 6 pp): DC master **12** (IU1–IU12), AC/HVDC master **10** (IU3–IU12), DC slave **13** (IU1–IU13), AC/HVDC slave **11** (IU3–IU13); E3CTU layout **13** DC / **11** AC. One APIU occupies physical IU1 *and* IU2 with logical slot IU1. So any future label has to name power option and layout, not just the frame. **Why no build can be copied.** `devices/huawei/netengine-8000-m14.json` exists because the M14 datasheet prints a card complement *with counts* inside a power row. Nothing in the E9600 set does: - *OptiXtrans E9600 Family* brochure (200, 277,705 B): `TNG` 0, `TMB` 0; "typical product configuration" is footnote `c` on the MTBF rows. - The E9612 chapter's own service-board row: *"Service boards need to be configured based on the service plan and all of them are installed in the service board area."* **Fresh enumeration of this frame's own support page.** `https://support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9612-pid-250733000` and `…-e9624-pid-250733004`: 164 unique `EDOC` ids between them; requested one at a time at `/enterprise/en/doc/<ID>` → **45 open** (30 video / *【Optical Basics】*), **119 → `/view/notFound`**. Body scan for `TNG1*`, `TNG2*`, `TMB1*`, `TMK*`, `TNK*`, `TNV*` across all open bodies: **empty**. The largest open one is `EDOC1100605036` *Huawei OptiX OSN 9800 and OptiXtrans E9600 User Guide* — scope text, no board census. Today `EDOC1100163901` (Board Datasheet), `EDOC1100621488` (V100R026C00 Product Documentation) and `EDOC1100126589` still answer `302 → /view/notFound`. **Correction for the next pass:** the e.huawei.com sitemaps do not index the chapter set at all (all 32 sitemap files, 111,538 `<loc>`, 4,151 document pages downloaded; none of the five known OptiXtrans material hashes appears), so "absent from the index" is not evidence of non-publication. **Exact missing field:** one client-port board chapter — `TNG1N206`, `TNG1N210`, `TNG1N401`, `TNG1A212`, `TNG1T212`, `TNG1M210D` — with its Front Panel and Port Specifications table. With it the spec is `OptiXtrans E9612 (13x <board>, DC slave, E3CTU)` = slots x the board's own published port count, and nothing is guessed. **What would unblock it:** that one `e-file.huawei.com` chapter PDF, or `EDOC1100163901` / `EDOC1100621488` pasted by a reader with a support login.
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#808
No description provided.