research(e6616x): the E6600 board tables live in the presales decks, and they disagree on slot cost (#803) #2000
No reviewers
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2000
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1118-1557"
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. 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- printsTMB2TPS / TMB1PL1D / TMB1SP3DE / TMB1TPSEagainst2 Slot / 1 Slot / 1 Slot / 2 Slotand2 x 16E1/T1 / 2 x 16E1/T1 / 2 x 21E1 / 2 x 16E1, and listsB2TPS/B2OTPS/B1TPSEunder 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
B2TPSis 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; and2 x 16E1/T1is 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
sourcesentry rests on a re-hosted deck, per the evidence rule.devices/huawei/optixtrans-e6616x.jsonis unchanged.Gates:
node scripts/syntax-check.js418 files OK;node scripts/audit-port-types.jsno contradictions;node --test test/hardware-invariants.test.js1 pass 0 fail;regen-registry-doc.jsno diff (no spec touched).46e056d8ce31413fc761