huawei: the E6616X's two brochures disagree, and one of them does name a board (#803) #1986
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!1986
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1118-1326"
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 #803 - does not close it. No spec is added; no port, slot or PoE figure changes.
The correction
research/optixtrans-e6616x-anonymous-doc-census.mdsection 4 closed with: "Both print the same specification table - 14/12 service slots, 680G OTN / 680G OSU / 160G+20G SDH / 800G packet cross-connect - and neither names a board." Both halves are wrong, and this PR carries the evidence plus a pointer at the false sentence.Re-extracting the same two asset URLs (no new route, crawler UA):
M1T1A669N837008945971838990M3T1A590N1227914753962237967(V100R025C10)TM*board numbersTM65UXCLThe PDF also contradicts itself inside four pages: highlights say 620G OTN / 820G packet, its own table says 680G / 800G. That matters because #803's body reads "OTN 620G / PKT 820G / SDH 160G" - 620G is a highlights figure no table states.
Why the board matters
TM65UXCLis the first board part number any Huawei-hosted E6616X document has yielded, and its prefix is not the family the registry's next step names: the E6616's system boards areK5UXCME/K5SXCH/K6XCHand its service boardsB1LDCD/TMB1LDCD. So "a TMB1*/TMK1* chapter whose Valid Slots names E6616X" is aimed at the sibling's order-code namespace; the X's isTM65.TM65UXCLis a cross-connect/system board with no client ports, so it still cannot supply a front-panel census and #803 stays blocked on aTM65*service board or a stated build ("E6616X DC, 14x ").Also recorded as dead
info.support.huawei.comlooks like a second support portal (search engines index the E6616X page there) but every path -/enterprise/en/...,/enterprise/zh/...,/hedex/api/navi/EDOC1100558549/first-level-tree- answers 302 withLocation: https://support.huawei.com/. And the localised product pages are client-side rendered:e.huawei.com/en/products/.../optixtrans-e6600is 45,722 B and.../hu/...53,363 B, with zeroTM[56]order codes in either body.Gates
No spec file touched, so the importer capability tripwire has nothing to compare.