huawei: the E6616 fabric is a named switch board, and 2.8 Tbit/s is not the only one (#803) #1983
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1983
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1118-1256"
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 - the E6616X service-board census is still unpublished).
Correction.
devices/huawei/optixtrans-e6616.jsonfabric.noteattributed "2.8 Tbit/s OTN cross-connect" to "the 14-slot shelf". The chapter the spec already cites, OptiXtrans E6600 V100R025C10 Product Documentation chapter 1 (E6616 Chassis), Table 1 Current subrack capacity, attributes it to the switch board:Source (re-fetched and re-read today, HTTP 200, 1,535,511 B, 20 pp):
https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/621bfc22e8564cf69ae86581569a7594/M3T1A669N1304588489052958777/2-OptiXtrans%20E6616-Datasheet.pdf
(material page: https://e.huawei.com/en/documents/others/621bfc22e8564cf69ae86581569a7594)
Second fix. The description said "400G per slot capable". The cited chapter contains no occurrence of "400G" and caps a service slot at 200 Gbit/s ODUk for all three switch boards, so the phrase traced to nothing and is gone; the slot figure now matches Table 1.
Table transcribed verbatim into
research/optixtrans-e6600-chassis-chapters.mds.9, including the TMK5UXCME caveat (920 Gbit/s ODUk + 920 Gbit/s OSU, footnote caps OSU add/drop at 4 x 9.6 Gbit/s) so it is not read as a fourth fabric.Gates: syntax-check 414 files OK; audit-port-types "No port contradicts its declared type."; hardware-invariants 26 passed / 0 failed; regen-registry-doc produced no diff. No port list changed.