research(huawei): the E6616X has its own grey-only spec sheet, and the chapter fetch 403s to node (#803) #2054

Merged
jaylouisw merged 1 commit from catalogue/1118-2352 into main 2026-11-19 00:38:19 +00:00
Owner

Refs #803 - evidence only, no spec written, the issue stays open.

What this pass measured (2026-11-18 23:5x UTC)

  • The E6616X has its own vendor spec sheet: OptiXtrans E6616X Product Brochure, 216,145 B, 4 pp, md5 6f217c3b057a42e86d927a3d18aca7e5 - 680 Gbit/s OTN, 680 Gbit/s OSU, 800 Gbit/s packet, 160/20 Gbit/s SDH, 100 Gbit/s grey per channel, line rates 2.5/10/100 Gbit/s, 14 service slots DC / 12 AC. Zero TMB, zero TMK, no port count.
  • The sibling substitute is now ruled out by the vendor's own numbers. devices/huawei/optixtrans-e6616.json is 14x B1LDCD (4x 100GE client into 2x 100G/200G CFP2 DWDM line). The E6616X sheet caps per channel at 100 Gbit/s grey and gives it no wavelength plan (N/A on the product page too, where the Maximum Rate per Channel row is a colspan="3" 400 Gbit/s cell plus a single 100Gbit/s(grey) cell - a flat text dump of that table reads the column wrongly). The frame transfers, the population does not; E6616X occurs 0 times in the 22,964-character E6616 datasheet text.
  • The leaflet class is measured shut: E6616X brochure (TMB 0), OptiXtrans E6616 V100R025C10 产品彩页 .docx, 516,108 B (TMB 0; the ten TMK mentions are K5SXCH/K5XCH/K6XCH/K5UXCME/K5XCS/K1XCL/K1FXCL, all cross-connect/control), and Railway Optical Communication Network 26H1 (8 pp; board types EMR8/UXCMS/UNQ2 only).

Instrument repair. scripts/huawei-material-fetch.js answered page 403 on every material page today: the host fingerprints the TLS client, not the headers (node 403 / 428-byte body vs curl 200 / 337,802 B on the same URL, same UA, same minute; browser UA changes nothing). It now fetches through curl when curl is on PATH, node client kept as fallback. Re-verified: (2)-OptiXtrans E6616-Datasheet 1,535,511 B, (21)-TMB3AUX 482,177 B - the byte count already on record.

Still missing, exactly: a service-board part number valid in an E6616X plus its front-panel census. Unblock unchanged: one authenticated read of EDOC1100625826 (配套设备), EDOC1100299472, or a stated configuration E6616X DC (12x <board>).

Gates: node scripts/syntax-check.js 430 files all OK; node scripts/audit-port-types.js no port contradicts its declared type; node --test test/hardware-invariants.test.js 1/1 pass; test/catalogue-hygiene.test.js + test/doc-catalog-counts.test.js 2/2 pass; docs/DEVICE_REGISTRY.md regenerated by npm run regen:registry-doc, not hand-edited. devices/ untouched.

Refs #803 - evidence only, no spec written, the issue stays open. **What this pass measured (2026-11-18 23:5x UTC)** - The **E6616X has its own vendor spec sheet**: `OptiXtrans E6616X Product Brochure`, 216,145 B, 4 pp, md5 `6f217c3b057a42e86d927a3d18aca7e5` - 680 Gbit/s OTN, 680 Gbit/s OSU, 800 Gbit/s packet, 160/20 Gbit/s SDH, **100 Gbit/s grey per channel**, line rates 2.5/10/100 Gbit/s, 14 service slots DC / 12 AC. Zero `TMB`, zero `TMK`, no port count. - **The sibling substitute is now ruled out by the vendor's own numbers.** `devices/huawei/optixtrans-e6616.json` is 14x B1LDCD (4x 100GE client into 2x 100G/200G CFP2 **DWDM** line). The E6616X sheet caps per channel at 100 Gbit/s grey and gives it **no wavelength plan** (`N/A` on the product page too, where the `Maximum Rate per Channel` row is a `colspan="3"` `400 Gbit/s` cell plus a single `100Gbit/s(grey)` cell - a flat text dump of that table reads the column wrongly). The frame transfers, the population does not; `E6616X` occurs 0 times in the 22,964-character E6616 datasheet text. - **The leaflet class is measured shut**: E6616X brochure (`TMB` 0), `OptiXtrans E6616 V100R025C10 产品彩页` .docx, 516,108 B (`TMB` 0; the ten `TMK` mentions are K5SXCH/K5XCH/K6XCH/K5UXCME/K5XCS/K1XCL/K1FXCL, all cross-connect/control), and Railway Optical Communication Network 26H1 (8 pp; board *types* EMR8/UXCMS/UNQ2 only). **Instrument repair.** `scripts/huawei-material-fetch.js` answered `page 403` on every material page today: the host fingerprints the TLS client, not the headers (node 403 / 428-byte body vs curl 200 / 337,802 B on the same URL, same UA, same minute; browser UA changes nothing). It now fetches through curl when curl is on PATH, node client kept as fallback. Re-verified: `(2)-OptiXtrans E6616-Datasheet` 1,535,511 B, `(21)-TMB3AUX` 482,177 B - the byte count already on record. **Still missing, exactly:** a service-board part number valid in an E6616X plus its front-panel census. Unblock unchanged: one authenticated read of `EDOC1100625826` (`配套设备`), `EDOC1100299472`, or a stated configuration `E6616X DC (12x <board>)`. **Gates**: `node scripts/syntax-check.js` 430 files all OK; `node scripts/audit-port-types.js` no port contradicts its declared type; `node --test test/hardware-invariants.test.js` 1/1 pass; `test/catalogue-hygiene.test.js` + `test/doc-catalog-counts.test.js` 2/2 pass; `docs/DEVICE_REGISTRY.md` regenerated by `npm run regen:registry-doc`, not hand-edited. `devices/` untouched.
research(huawei): the E6616X has its own grey-only spec sheet, and the chapter fetch 403s to node (#803)
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Classify the change (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 29s
CI / Test (Node 20) (pull_request) Successful in 54s
CI / Test (Node 22) (pull_request) Successful in 57s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Arm auto-merge (pull_request) Successful in 3s
d8d9171e5b
The E6616X Product Brochure (216,145 B, 4 pp) rates the box at 680 Gbit/s OTN/OSU, 800 Gbit/s packet and 100 Gbit/s grey per channel with 14/12 service slots - so the frame is fully vendor-sourced and the E6616 row's 14x B1LDCD (200G CFP2 DWDM line) cannot stand in. No board part number appears in any leaflet-class document. scripts/huawei-material-fetch.js now fetches through curl: the host answers 403 to node's TLS client on a page curl reads as 200.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 00:10:26 +00:00
jaylouisw deleted branch catalogue/1118-2352 2026-11-19 00:38:20 +00:00
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!2054
No description provided.