research(optixtrans): no vendor-stated build exists for E9605/E9612/E9624/E6616X (#807) #1903

Merged
jaylouisw merged 1 commit from otn/optixtrans-stated-config-absent into main 2026-11-17 21:44:32 +00:00
Owner

Refs #807, #808, #810, #803 — research note only; this PR closes nothing.

docs/plans/stated-configurations.md closed the NetEngine 8000 family by copying a build the vendor states (a power-measurement row listing part numbers with counts). This pass asked whether that line exists for the OptiXtrans frames, and measured it rather than searching again.

The vendor's "typical configuration" is an MTBF footnote, not a card complement. In the OptiXtrans E9600 Family brochure (277,705 B) the phrase sits in footnote c on the MTBF/availability rows; in OptiXtrans E6616X V100R026C00 产品彩页 (1,629,242 B) it sits in footnote b on MTTR/MTBF 111.9 years. Neither document carries a service-board part number (TNG 0 in the family brochure; TMB1 0 / TMK1 0 in the E6616X 彩页, whose only part code is TM65UXCL, the cross-connect). The frame chapters decline a default outright: "Service boards need to be configured based on the service plan."

Every open document on the four product pages, counted (crawler UA, /enterprise/en/doc/<EDOC…> one id at a time): E6616X page 260 ids → 47 open (23 video/multimedia); E9612 + E9624 pages 164 ids → 45 open (30 video/multimedia). Body scan for TMB1*/TMK*/TM65*/TNK*/TNG1*/TNV* over all 92 open documents: empty set.

Correction for the next pass: the e.huawei.com sitemaps do not index this document set at all. All 32 sitemap files (111,538 <loc>, 4,151 unique document pages) were downloaded and all 836 enterprise-optical-network / documents/others pages fetched; none of the five known OptiXtrans material hashes appears. Absence from a sitemap is not evidence of non-publication, so the "the public index is complete" reading in research/optixtrans-client-board-chapters.md §5 does not hold.

Gates: syntax-check 395 files OK · audit-port-types no contradiction · importer tripwire losses 0 (the 5 duplicate-spelling collisions are pre-existing in research/incoming) · hardware-invariants 26/26 · catalogue-hygiene 25/25 · doc-catalog-counts 43/43. No device file is touched, so no registry count moves.

Refs #807, #808, #810, #803 — **research note only; this PR closes nothing.** `docs/plans/stated-configurations.md` closed the NetEngine 8000 family by copying a build the vendor states (a power-measurement row listing part numbers with counts). This pass asked whether that line exists for the OptiXtrans frames, and measured it rather than searching again. **The vendor's "typical configuration" is an MTBF footnote, not a card complement.** In the *OptiXtrans E9600 Family* brochure (277,705 B) the phrase sits in footnote `c` on the MTBF/availability rows; in *OptiXtrans E6616X V100R026C00 产品彩页* (1,629,242 B) it sits in footnote `b` on MTTR/MTBF 111.9 years. Neither document carries a service-board part number (`TNG` 0 in the family brochure; `TMB1` 0 / `TMK1` 0 in the E6616X 彩页, whose only part code is `TM65UXCL`, the cross-connect). The frame chapters decline a default outright: *"Service boards need to be configured based on the service plan."* **Every open document on the four product pages, counted** (crawler UA, `/enterprise/en/doc/<EDOC…>` one id at a time): E6616X page 260 ids → 47 open (23 video/multimedia); E9612 + E9624 pages 164 ids → 45 open (30 video/multimedia). Body scan for `TMB1*/TMK*/TM65*/TNK*/TNG1*/TNV*` over all 92 open documents: **empty set**. **Correction for the next pass:** the e.huawei.com sitemaps do not index this document set at all. All 32 sitemap files (111,538 `<loc>`, 4,151 unique document pages) were downloaded and all 836 `enterprise-optical-network` / `documents/others` pages fetched; none of the five known OptiXtrans material hashes appears. Absence from a sitemap is not evidence of non-publication, so the "the public index is complete" reading in `research/optixtrans-client-board-chapters.md` §5 does not hold. Gates: `syntax-check` 395 files OK · `audit-port-types` no contradiction · importer tripwire `losses 0` (the 5 duplicate-spelling collisions are pre-existing in `research/incoming`) · `hardware-invariants` 26/26 · `catalogue-hygiene` 25/25 · `doc-catalog-counts` 43/43. No device file is touched, so no registry count moves.
research(optixtrans): no vendor-stated build exists for the E9605/E9612/E9624/E6616X (#807)
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Successful in 48s
CI / Test (Node 18) (pull_request) Successful in 55s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Arm auto-merge (pull_request) Successful in 18s
eefb8cd1c0
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1903
No description provided.