huawei: the E6616 fabric is a named switch board, and 2.8 Tbit/s is not the only one (#803) #1983

Merged
jaylouisw merged 1 commit from catalogue/1118-1256 into main 2026-11-18 13:01:07 +00:00
Owner

Refs #803 (does not close - the E6616X service-board census is still unpublished).

Correction. devices/huawei/optixtrans-e6616.json fabric.note attributed "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:

Cross-connect board per slot ODUk per slot SDH subrack ODUk subrack SDH VC-4 subrack SDH VC-3/VC-12
TMK5SXCH 200 Gbit/s 10 Gbit/s 2.8 Tbit/s 140 Gbit/s 20 Gbit/s
TMK5XCH 200 Gbit/s N/A 2.4 Tbit/s N/A N/A
TMK6XCH 200 Gbit/s N/A 2.8 Tbit/s N/A N/A

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.md s.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.

Refs #803 (does not close - the E6616X service-board census is still unpublished). **Correction.** `devices/huawei/optixtrans-e6616.json` `fabric.note` attributed "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: | Cross-connect board | per slot ODUk | per slot SDH | subrack ODUk | subrack SDH VC-4 | subrack SDH VC-3/VC-12 | |--|--|--|--|--|--| | TMK5SXCH | 200 Gbit/s | 10 Gbit/s | **2.8 Tbit/s** | 140 Gbit/s | 20 Gbit/s | | TMK5XCH | 200 Gbit/s | N/A | **2.4 Tbit/s** | N/A | N/A | | TMK6XCH | 200 Gbit/s | N/A | **2.8 Tbit/s** | N/A | N/A | 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.md` s.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.
huawei: the E6616 fabric is a named switch board, and 2.8 Tbit/s is not the only one (#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 9s
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 29s
CI / Test (Node 20) (pull_request) Successful in 1m0s
CI / Test (Node 22) (pull_request) Successful in 1m4s
CI / Test (Node 18) (pull_request) Successful in 1m9s
CI / Arm auto-merge (pull_request) Successful in 16s
fae79208c0
The fabric note said "2.8 Tbit/s OTN cross-connect for the 14-slot shelf". Chapter 1
(E6616 Chassis), Table 1 "Current subrack capacity", in the document the spec already
cites, breaks that figure out per cross-connect board: TMK5SXCH 200 Gbit/s ODUk per
slot into 2.8 Tbit/s (and the only board with SDH: 10 Gbit/s per slot, 140 Gbit/s
VC-4 / 20 Gbit/s VC-3/VC-12 per subrack), TMK6XCH the same 2.8 Tbit/s OTN with no SDH,
TMK5XCH 2.4 Tbit/s. Quoting the frame figure without the board would let a TMK5XCH
build claim capacity it does not have.

Also drops "400G per slot capable" from the description: the cited chapter caps a
service slot at 200 Gbit/s ODUk for all three switch boards and does not contain the
string 400G at all, so that phrase traced to nothing.

Table transcribed verbatim into research/optixtrans-e6600-chassis-chapters.md s.9.
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!1983
No description provided.