huawei: the E6616X's two brochures disagree, and one of them does name a board (#803) #1986

Merged
jaylouisw merged 1 commit from catalogue/1118-1326 into main 2026-11-18 13:34:27 +00:00
Owner

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.md section 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):

PDF M1T1A669N837008945971838990 DOCX M3T1A590N1227914753962237967 (V100R025C10)
bytes 216,145, 4 pp 1,628,703
OTN cross-connect 680 Gbit/s 780 Gbit/s, licence-gated
OSU cross-connect 680 Gbit/s 620 Gbit/s (420 Gbit/s pass-through)
packet switching 800 Gbit/s 820 Gbit/s
TM* board numbers none TM65UXCL

The 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

TM65UXCL is 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 are K5UXCME/K5SXCH/K6XCH and its service boards B1LDCD/TMB1LDCD. So "a TMB1*/TMK1* chapter whose Valid Slots names E6616X" is aimed at the sibling's order-code namespace; the X's is TM65. TM65UXCL is a cross-connect/system board with no client ports, so it still cannot supply a front-panel census and #803 stays blocked on a TM65* service board or a stated build ("E6616X DC, 14x ").

Also recorded as dead

info.support.huawei.com looks 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 with Location: https://support.huawei.com/. And the localised product pages are client-side rendered: e.huawei.com/en/products/.../optixtrans-e6600 is 45,722 B and .../hu/... 53,363 B, with zero TM[56] order codes in either body.

Gates

node scripts/syntax-check.js        Syntax-checked 414 files: all OK
node scripts/check-control-bytes.js No control bytes in source.
node scripts/audit-port-types.js    No port contradicts its declared type.
node scripts/check-doc-citations.js exit 0
node scripts/regen-registry-doc.js --check  current: 2,356 models across 258 vendors, 29,721 sockets, 972 shapes
node test/hardware-invariants.test.js  26 passed, 0 failed

No spec file touched, so the importer capability tripwire has nothing to compare.

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.md` section 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): | | PDF `M1T1A669N837008945971838990` | DOCX `M3T1A590N1227914753962237967` (V100R025C10) | |--|--|--| | bytes | 216,145, 4 pp | 1,628,703 | | OTN cross-connect | 680 Gbit/s | **780 Gbit/s**, licence-gated | | OSU cross-connect | 680 Gbit/s | **620 Gbit/s** (420 Gbit/s pass-through) | | packet switching | 800 Gbit/s | **820 Gbit/s** | | `TM*` board numbers | none | **`TM65UXCL`** | The 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 `TM65UXCL` is 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 are `K5UXCME`/`K5SXCH`/`K6XCH` and its service boards `B1LDCD`/`TMB1LDCD`. So "a TMB1*/TMK1* chapter whose Valid Slots names E6616X" is aimed at the sibling's order-code namespace; the X's is `TM65`. `TM65UXCL` is a cross-connect/system board with no client ports, so it still cannot supply a front-panel census and #803 stays blocked on a `TM65*` **service** board or a stated build ("E6616X DC, 14x <board>"). ## Also recorded as dead `info.support.huawei.com` looks 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 with `Location: https://support.huawei.com/`. And the localised product pages are client-side rendered: `e.huawei.com/en/products/.../optixtrans-e6600` is 45,722 B and `.../hu/...` 53,363 B, with zero `TM[56]` order codes in either body. ## Gates ``` node scripts/syntax-check.js Syntax-checked 414 files: all OK node scripts/check-control-bytes.js No control bytes in source. node scripts/audit-port-types.js No port contradicts its declared type. node scripts/check-doc-citations.js exit 0 node scripts/regen-registry-doc.js --check current: 2,356 models across 258 vendors, 29,721 sockets, 972 shapes node test/hardware-invariants.test.js 26 passed, 0 failed ``` No spec file touched, so the importer capability tripwire has nothing to compare.
huawei: the E6616X's two brochures disagree, and one of them does name a board (#803)
All checks were successful
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Test (Node 20) (pull_request) Successful in 54s
CI / Test (Node 22) (pull_request) Successful in 54s
CI / Arm auto-merge (pull_request) Successful in 15s
37da7a7827
The census said both brochure assets print the same specification table and neither names a board. Re-extracting the same two URLs shows three of four switching figures differ between the editions (OTN 780 vs 680 Gbit/s, OSU 620 vs 680, packet 820 vs 800) and that the V100R025C10 docx names TM65UXCL in a licence footnote - the first board part number any Huawei-hosted E6616X document has yielded, and in a different order-code family from the E6616's TMB1/TMK5 boards. Also records info.support.huawei.com as an alias (302 to the support root) and the localised product pages as client-side rendered. No spec, no close.
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!1986
No description provided.