research(e6616x): the E6600 board tables live in the presales decks, and they disagree on slot cost (#803) #2000

Merged
jaylouisw merged 1 commit from catalogue/1118-1557 into main 2026-11-18 16:04:46 +00:00
Owner

Refs #803 - does not close it. One increment: the E6600 board tables exist in Huawei's channel training decks, and the two decks contradict each other on slot cost.

Read (both Huawei-authored, both third-party re-hosted, both slide images so text comes from the hosts' index):

  • https://www.scribd.com/document/931093259/HCSA-Presales-Transmission-V1-0-Training-Material - prints TMB2TPS / TMB1PL1D / TMB1SP3DE / TMB1TPSE against 2 Slot / 1 Slot / 1 Slot / 2 Slot and 2 x 16E1/T1 / 2 x 16E1/T1 / 2 x 21E1 / 2 x 16E1, and lists B2TPS/B2OTPS/B1TPSE under OptiXtrans E6616X.
  • https://www.slideshare.net/ssuserc99286/optixtrans-e6600-main-slidepdf - TMB1TPS(DMS+PD1) 32xE1/T1, DMS 32 x E1/T1 electrical signals ... Two PD1 boards and one DMS board work together to provide TPS protection.

What it settles: the ports are on the DMS board and B2TPS is the E6616X's tributary family (TM65UXCL + B2*), corroborating the Ningbo deployment list independently of it.

Why it cannot close #803: that same three-board assembly is priced at "2 Slot", which cannot hold 1*DMS+2*PD1; and 2 x 16E1/T1 is printed against a 1-slot board as well, so no per-board port count can be quoted. A spec would have to guess between 2 slots/32 E1 and 3 slots/32 E1.

No spec field or sources entry rests on a re-hosted deck, per the evidence rule. devices/huawei/optixtrans-e6616x.json is unchanged.

Gates: node scripts/syntax-check.js 418 files OK; node scripts/audit-port-types.js no contradictions; node --test test/hardware-invariants.test.js 1 pass 0 fail; regen-registry-doc.js no diff (no spec touched).

Refs #803 - does not close it. One increment: the E6600 board tables exist in Huawei's channel training decks, and the two decks contradict each other on slot cost. **Read (both Huawei-authored, both third-party re-hosted, both slide images so text comes from the hosts' index):** - `https://www.scribd.com/document/931093259/HCSA-Presales-Transmission-V1-0-Training-Material` - prints `TMB2TPS / TMB1PL1D / TMB1SP3DE / TMB1TPSE` against `2 Slot / 1 Slot / 1 Slot / 2 Slot` and `2 x 16E1/T1 / 2 x 16E1/T1 / 2 x 21E1 / 2 x 16E1`, and lists `B2TPS/B2OTPS/B1TPSE` under *OptiXtrans E6616X*. - `https://www.slideshare.net/ssuserc99286/optixtrans-e6600-main-slidepdf` - `TMB1TPS(DMS+PD1) 32xE1/T1`, `DMS 32 x E1/T1 electrical signals ... Two PD1 boards and one DMS board work together to provide TPS protection`. **What it settles:** the ports are on the DMS board and `B2TPS` is the E6616X's tributary family (`TM65UXCL` + `B2*`), corroborating the Ningbo deployment list independently of it. **Why it cannot close #803:** that same three-board assembly is priced at "2 Slot", which cannot hold `1*DMS+2*PD1`; and `2 x 16E1/T1` is printed against a 1-slot board as well, so no per-board port count can be quoted. A spec would have to guess between 2 slots/32 E1 and 3 slots/32 E1. No spec field or `sources` entry rests on a re-hosted deck, per the evidence rule. `devices/huawei/optixtrans-e6616x.json` is unchanged. Gates: `node scripts/syntax-check.js` 418 files OK; `node scripts/audit-port-types.js` no contradictions; `node --test test/hardware-invariants.test.js` 1 pass 0 fail; `regen-registry-doc.js` no diff (no spec touched).
research(e6616x): the E6600 board tables live in the presales decks, and they disagree on slot cost (#803)
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
CI / Classify the change (pull_request) Successful in 5s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Arm auto-merge (pull_request) Successful in 31s
46e056d8ce
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-18 16:02:02 +00:00
forgejo-actions force-pushed catalogue/1118-1557 from 46e056d8ce
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
CI / Classify the change (pull_request) Successful in 5s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Arm auto-merge (pull_request) Successful in 31s
to 31413fc761 2026-11-18 16:04:34 +00:00
Compare
jaylouisw deleted branch catalogue/1118-1557 2026-11-18 16:04:48 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
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!2000
No description provided.