[Device]: OptiXtrans E9624 #810
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#810
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 E9624
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/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
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.
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:1occupied 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— all302 -> /view/notFoundagain today;hedexis a 3,728 B SPA shell;hedex/api/navi/<ID>still401 {"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,TNVorTMB1. And TNG2DAP is an amplifier — its port table isIN / OUT / VI / VO / MON, allLC, 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 forTNG1N206/210/401,TNG1M210D/402/404DM/520SMreturn 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) orEDOC1100163901(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.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 stringE9624Xoccurs 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.
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 givesOpticallayer ASON | E9605/E9612/E9624 subrack: SupportedagainstOpticallayer 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) linksOptiXtrans E9624X Board DatasheettoEDOC1100214449, which answers302 -> /view/notFoundexactly likeEDOC1100163901. Its Product Brochure link (/en/documents/products/enterprise-optical-network/05062a0bc9a84a5f9642a37e14d67b96) returns a 200 shell whose text begins404, with zero asset paths.What would close it, unchanged: one
TNG1N206(6 x 10G line),TNG1N210(10 x 10G line) orTNG1N401(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 isE9624 (24x TNG1N210)as a stated card complement, with no guessed field. A readable copy ofEDOC1100163901orEDOC1100214449would also do it.Recorded in
research/optixtrans-e9624x-fourth-subrack.mdand the #810 row ofdocs/DEVICE_REGISTRY.md§"What is left open, and why".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's12 large / 24 smallvs10 / 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:
TNG0,TMB0; the phrase "typical product configuration" is footnotecon the MTBF rows, not a complement.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 uniqueEDOCids, requested one at a time at/enterprise/en/doc/<ID>→ 45 open (30 of them video / 【Optical Basics】), 119 →/view/notFound; a body scan forTNG1*,TNG2*,TMB1*,TMK*,TNK*,TNV*across all open documents returns nothing.EDOC1100163901,EDOC1100621488andEDOC1100126589all answer302 → /view/notFoundtoday.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 ofresearch/optixtrans-client-board-chapters.mdshould not be cited for it.Exact missing field: one client-port board chapter (
TNG1N2066x10G,TNG1N21010x10G,TNG1N4011x100G,TNG1A21212x10G,TNG1T212,TNG1M210D) with its Front Panel + Port Specifications, plus the protection mode for the label. Then it isOptiXtrans 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/EDOC1100621488pasted by a reader with a support session, or a Huawei document stating a configuration line for this frame.E9624Xmaterial does not substitute — different height, DC-only power, SDH-first cross-connect.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.cnhad never been tested. Its E6616X product page is a 25,028 B Nuxt shell with zero document links;/enterprise/en/doc/EDOC1100486186and/enterprise/en/doc/EDOC1100163901both answer 200 with 3,800 bytes - the identicalsupportview/lstbundle loader - andsupportgateway/view/v1/enterprise/doc/catalogue?nid=EDOC1100163901returns the same 401support-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.comis 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 deadhedexpath already returns. So a 200 frominfo.is the not-found, exactly thedl.ui.comtrap in reverse.3. There is no asset index to enumerate.
e-file.huawei.com/robots.txtand/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) andEDOC1100365420(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) orTNG1N401(1x100G) - carrying its Front Panel and Port Specifications, plus the protection mode for the label. With it this isOptiXtrans 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,
EDOC1100163901pasted 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.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 intodocs/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) orTNG1N401(1 x 100 Gbit/s line), whichTNG2DAPsection 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:N2060,N2100,N4010,10 Gbit/s0. The codes it does carry are amplifier/OSC/control only (TNG2OACU*,TNG3OACU*/TNG3OBCU*/TNG3OACE*,TNG1/3/4CXP,TNG2HSOCXP,TNG3CXCS*); noTNZ*.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 hedexEDOC1100126589BEJ09047— 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 supportedoccurs 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=03viewer 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:
TNG1N2066×10G,TNG1N21010×10G,TNG1N4011×100G are named with their counts. Validity is. Rows for #807, #808 and #810 corrected; detail inresearch/optixtrans-dap-slots-are-dap-only.md.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)
https://support.huawei.com/enterprise/en/optical-transmission/optixtrans-e9612-pid-250733000/softwareOptiXtrans E9600 V100R026C00 Product Documentation(2026-11-02), i.e. the current release — are not files. Each links tohttps://support.huawei.com/hedex/hdx.do?docid=EDOC1100621487&lang=en.<title>,TNG1N0 — the identical SPA shell already recorded forEDOC1100163901, so the package route ends at the same gate as the chapter route.https://support.huawei.com/enterprise/en/doc/EDOC1100621487/view/notFound.https://support.huawei.com/enterprise/en/optical-transmission/optix-osn-9800-m24-pid-22048459EDOC1000074739; that URL, with and withoutidPath, 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-9856748Datasheet. 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/Aon 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.
clear counters#1945Re-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
TNG1N210chapter reads: 80 x ODU0 / 40 x ODU1 / 80 x ODUflex / 10 x ODU2 <-> 10 x OTU2 and 10 x ODU2e <-> 10 x OTU2e, WDM-sideOTU2/OTU2e, pluggable list allSFP+ -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/M24atIU1-5 / IU1-13 / IU1-24versusTNG2DAP§1.9'sOptiXtrans E9605/E9612/E9624at 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 pairsE9605withM05. That join stays an inference (identical counts plus Huawei's ownOptiXtrans 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 thedocuments/productsattachment route (20,242,639 B docx), containsTNG1N0,TNG1M0,TNV0,TMB0 — 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(or1:3, 20x), which settles validity, complement and mode together.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 rowOptiX 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 M24leaves 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.
TNG1N0,TNG1M0,TNG20,TMK10 in the ST's 87 pages, and no port count for TNG4CXP/TME3CTU. One vendor copy of an N-series chapter (orEDOC1100163901) 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 -.pdfinside theTNG2DAPasset folder all return S3AccessDenied(controlTNG2DAP -.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.comanswers a Chrome UA with an Akamai403 text/htmland a crawler UA with200 application/pdf- a 403 there is not evidence of absence, but a403 application/xmlcarrying<Code>AccessDenied</Code>is.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/queryModelswith{"domain":"0","language":"en","keyword":"<kw>","toolType":"hardwarecenter"}answers anonymously:""OSN 9800hardwareType:"Optical module"(OSN080N10CFP 1310 nm 103.125G,OSN040N08QSFP-DD 400G,OSN010B00/B01BiDi QSFP28…) — no chassis, no boardsOptiXtrans,E6616X,TNG1N206,TNG1N210,TNG2DAP,TMB1,TNV1T210UThe 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) returnsdata:nullfor every keyword — a separate deployment, not a second dataset.2. Correction other passes should carry.
support.huawei.comproduct pages answer 200 only to the Googlebot UA. Chrome, Firefox and empty UA all get Akamai403(414–463 B,errors.edgesuite.net). With a browser UA this host looks withdrawn; it is not — the document ids still302 -> /view/notFound, which is a publication decision.3. Two new R026 ids added to the wall:
EDOC1100622610(OptiXtrans E9600 V100R026C00 Product Description 01) andEDOC1100622612(Feature Description 01) — both302 -> /view/notFound, same asEDOC1100621488/EDOC1100625542. Their hedex equivalents return the same 3,728 B Vue shell.Exact missing field, unchanged: one client-port board chapter —
TNG1N206,TNG1N210,TNG1N401orTNG1T401— 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 beOptiXtrans 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) /EDOC1100622610from a reader with a support login.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 joinsOSN 9800 M24(the name the board chapters print) toE9624.research/open-device-requests.jsonloses its #810 row;research/optixtrans-e9624-stated-build.mdrecords 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.