[Device]: OptiXtrans E9612 #808
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#808
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Vendor
Huawei
Exact model name
OptiXtrans E9612
Category
Other / not sure
Ports and interfaces
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
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.
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 pagehttps://e.huawei.com/en/documents/others/1df5f09736174bdcaed9ea4e9276bf8b(200, 337,523 B), which is server-rendered and carries the asset path inline - the routescripts/huawei-material-fetch.jsalready encodes. This chapter type (one per frame) had not been fetched before.What it says about service slots
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 13and 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.comchapter 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.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:So
IU1-IU13fromTNG2DAPsection 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 futureE9612 (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-.pdf2. The board chapter is not "not indexed" — it is absent from an index that has now been counted.
https://e.huawei.com/robots.txtlistssitemap-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) andTNG3SRAPXF(Raman + EDFA).TNG1N206,TNG1N210,TNG1N401,TNG1M*,TNG1T*,TNV*,TNK*andTMB1*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=-> 403AccessDenied);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
EDOC1100621488andEDOC1100163901behind the Huawei account wall — access, not effort.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.jsonexists because the M14 datasheet prints a card complement with counts inside a power row. Nothing in the E9600 set does:TNG0,TMB0; "typical product configuration" is footnotecon the MTBF rows.Fresh enumeration of this frame's own support page.
https://support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9612-pid-250733000and…-e9624-pid-250733004: 164 uniqueEDOCids between them; requested one at a time at/enterprise/en/doc/<ID>→ 45 open (30 video / 【Optical Basics】), 119 →/view/notFound. Body scan forTNG1*,TNG2*,TMB1*,TMK*,TNK*,TNV*across all open bodies: empty. The largest open one isEDOC1100605036Huawei OptiX OSN 9800 and OptiXtrans E9600 User Guide — scope text, no board census. TodayEDOC1100163901(Board Datasheet),EDOC1100621488(V100R026C00 Product Documentation) andEDOC1100126589still answer302 → /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 isOptiXtrans 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.comchapter PDF, orEDOC1100163901/EDOC1100621488pasted by a reader with a support login.clear counters#1945