research(optixtrans): the E6616X is short of an E1 port type, not a census (#803) #2072

Merged
jaylouisw merged 1 commit from catalogue/1119-0222 into main 2026-11-19 02:41:03 +00:00
Owner

Does not close #803. No device spec is added: this is the measurement that says the next pass should stop hunting Huawei's login wall and take a decision instead.

The census is settled, and it is 32 per pair

Three independent pages agree that the 2M pair presents 32 x E1/T1: szhuaxunjia.com/product/2298.html (42,382 B, 32 x 75/120-ohm E1 or 100-ohm T1), szdingwei.net/Product/6542134456.html (34,588 B, titled 32路E1/T1电接口板) and the Tanatel price row 03034FAA TMB2TPS 32xE1/T1 tributary board(1*DMS+2*PD1). The 配套关系 table only the szhuaxunjia reprint prints names the X outright: TMB2DMS | E6616X | TM65UXCL | V100R022C10SPC010, and its TMB2PD1 page prints the same row as 表2. Per docs/MAINTAINING.md a re-hosted page is last resort and not a source for a field, so nothing here is quoted into a spec.

What actually blocks the spec is the engine

engine/media.js has no E1/T1 port type and no E1 cage. The families are ethernet / wireless / console / dsl / pon / coax / powerline / serial; serial resolves to the V.35 cage (serial-v35, 1.544 Mbps, cable v35) and coax to an F-connector. A 32-port G.703 board would therefore render as a WIC-2T or a cable-TV socket, and scripts/audit-port-types.js polices exactly that mismatch. So #803 belongs with #807/#808/#810 at rank 2 of docs/plans/stated-configurations.md ('a port type the engine does not have'), not rank 3 ('the vendor never published it') - and this stream does not carry engine changes.

Two instrument corrections

  • https://e.huawei.com/en/products/optical-transmission/optixtrans-e6616x answers 200 with <title>404</title> (336,300 B, byte-identical to the non-existent -e6608 URL); the real E6600 page is 339,756 B, md5 22eea469.... A 200 on that host is not a product page, and the X has none of its own.
  • Tanatel is reachable again (200, 1,020,978 B) and lists six X chassis SKUs - K31/K32 DC, K33/K34/K36 AC 1500 W, K35 DC - so every AC SKU of the X is 1500 W and the 12/10 AC split is an E6616 property, not the X's.

Gates

node scripts/syntax-check.js - 434 files, all OK. node scripts/audit-port-types.js - "No port contradicts its declared type". test/hardware-invariants.test.js - 26 passed, 0 failed. test/catalogue-hygiene.test.js - pass. docs/DEVICE_REGISTRY.md regenerated from the JSON, not hand-edited.

Does **not** close #803. No device spec is added: this is the measurement that says the next pass should stop hunting Huawei's login wall and take a decision instead. ## The census is settled, and it is 32 per pair Three independent pages agree that the 2M pair presents **32 x E1/T1**: `szhuaxunjia.com/product/2298.html` (42,382 B, 32 x 75/120-ohm E1 or 100-ohm T1), `szdingwei.net/Product/6542134456.html` (34,588 B, titled `32路E1/T1电接口板`) and the Tanatel price row `03034FAA TMB2TPS 32xE1/T1 tributary board(1*DMS+2*PD1)`. The `配套关系` table only the szhuaxunjia reprint prints names the X outright: `TMB2DMS | E6616X | TM65UXCL | V100R022C10SPC010`, and its TMB2PD1 page prints the same row as 表2. Per `docs/MAINTAINING.md` a re-hosted page is last resort and not a source for a field, so nothing here is quoted into a spec. ## What actually blocks the spec is the engine `engine/media.js` has no E1/T1 port type and no E1 cage. The families are ethernet / wireless / console / dsl / pon / coax / powerline / serial; `serial` resolves to the V.35 cage (`serial-v35`, 1.544 Mbps, cable `v35`) and `coax` to an F-connector. A 32-port G.703 board would therefore render as a WIC-2T or a cable-TV socket, and `scripts/audit-port-types.js` polices exactly that mismatch. So #803 belongs with #807/#808/#810 at rank 2 of `docs/plans/stated-configurations.md` ('a port type the engine does not have'), not rank 3 ('the vendor never published it') - and this stream does not carry engine changes. ## Two instrument corrections - `https://e.huawei.com/en/products/optical-transmission/optixtrans-e6616x` answers **200 with `<title>404</title>`** (336,300 B, byte-identical to the non-existent `-e6608` URL); the real E6600 page is 339,756 B, md5 `22eea469...`. A 200 on that host is not a product page, and the X has none of its own. - Tanatel is reachable again (200, 1,020,978 B) and lists **six** X chassis SKUs - K31/K32 DC, K33/K34/K36 AC 1500 W, K35 DC - so every AC SKU of the X is 1500 W and the 12/10 AC split is an E6616 property, not the X's. ## Gates `node scripts/syntax-check.js` - 434 files, all OK. `node scripts/audit-port-types.js` - "No port contradicts its declared type". `test/hardware-invariants.test.js` - 26 passed, 0 failed. `test/catalogue-hygiene.test.js` - pass. `docs/DEVICE_REGISTRY.md` regenerated from the JSON, not hand-edited.
research(optixtrans): the E6616X is short of an E1 port type, not a census (#803)
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Classify the change (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 26s
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 1m3s
CI / Arm auto-merge (pull_request) Successful in 3s
869f443337
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!2072
No description provided.