research(optixtrans): no vendor-stated build exists for E9605/E9612/E9624/E6616X (#807) #1903
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1903
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "otn/optixtrans-stated-config-absent"
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?
Refs #807, #808, #810, #803 — research note only; this PR closes nothing.
docs/plans/stated-configurations.mdclosed 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
con the MTBF/availability rows; in OptiXtrans E6616X V100R026C00 产品彩页 (1,629,242 B) it sits in footnotebon MTTR/MTBF 111.9 years. Neither document carries a service-board part number (TNG0 in the family brochure;TMB10 /TMK10 in the E6616X 彩页, whose only part code isTM65UXCL, 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 forTMB1*/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 836enterprise-optical-network/documents/otherspages 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 inresearch/optixtrans-client-board-chapters.md§5 does not hold.Gates:
syntax-check395 files OK ·audit-port-typesno contradiction · importer tripwirelosses 0(the 5 duplicate-spelling collisions are pre-existing inresearch/incoming) ·hardware-invariants26/26 ·catalogue-hygiene25/25 ·doc-catalog-counts43/43. No device file is touched, so no registry count moves.