catalogue: the E6616 states its power configuration, not just 14 slots (#803) #1942

Merged
jaylouisw merged 1 commit from catalogue/1118-0456 into main 2026-11-18 06:38:49 +00:00
Owner

Refs #803. This does not close it - the E6616X board list is still the blocker on that issue.

What was wrong. devices/huawei/optixtrans-e6616.json said "14 service slots" with no power qualifier, while its two siblings already carry one (OptiXtrans E6608 ... DC chassis, 6x B1LDCD, OptiXtrans E6608T ... DC chassis, 7x TMB1LDCD).

What the vendor chapter prints - chapter 1 (E6616 Chassis), Tables 1-2, in the document the entry already cites as its sourceUrl (OptiXtrans E6600 V100R025C10 Product Documentation, 20 pp, fetched 2026-11-18, 1,535,511 B, application/pdf):

power configuration service board slots slot IDs
DC (TMK5K31AFB) 14 1-14
AC 1500 W, dual power modules (TMK5K33AFB) 12 2, 4, 5-14
AC 2400 W, four power modules (TMK5K35AFB) 10 2, 4, 5-14

APIU boards occupy AC power slots 1 and 3 (1500 W) or 1-4 (2400 W), which is where the two/four service slots go; the chapter prints the count as 12/10 with that note.

Consequence. The same "14x B1LDCD" build read as fitting an AC shelf, overstating it by 2 boards (8 client ports) or 4 boards (16 client ports). label, description and notes now name the DC chassis and print the AC figures; research/optixtrans-e6600-chassis-chapters.md section 4 records that the rule it wrote on 2026-11-17 has been applied to the one entry it was written for.

Port list unchanged: 84 interfaces, 56x 100GE QSFP28 client + 28x 200G CFP2 line - the DC figure the entry always meant.

Evidence URL: https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/621bfc22e8564cf69ae86581569a7594/M3T1A669N1304588489052958777/_2_-OptiXtrans%20E6616-Datasheet.pdf

Gates: syntax-check 405 files OK; audit-port-types no port contradicts its declared type; hardware-invariants 26/26; catalogue-hygiene, spec-vs-description, device-aliases, cable-matrix, import-devices-capabilities, importer-roundtrip all pass; regen-registry-doc reports the catalogue current (2,353 models / 258 vendors / 29,301 sockets), so docs/DEVICE_REGISTRY.md is unchanged.

Refs #803. This does not close it - the E6616X board list is still the blocker on that issue. **What was wrong.** `devices/huawei/optixtrans-e6616.json` said "14 service slots" with no power qualifier, while its two siblings already carry one (`OptiXtrans E6608 ... DC chassis, 6x B1LDCD`, `OptiXtrans E6608T ... DC chassis, 7x TMB1LDCD`). **What the vendor chapter prints** - chapter 1 (E6616 Chassis), Tables 1-2, in the document the entry already cites as its `sourceUrl` (`OptiXtrans E6600 V100R025C10 Product Documentation`, 20 pp, fetched 2026-11-18, 1,535,511 B, `application/pdf`): | power configuration | service board slots | slot IDs | |--|--|--| | DC (TMK5K31AFB) | **14** | 1-14 | | AC 1500 W, dual power modules (TMK5K33AFB) | **12** | 2, 4, 5-14 | | AC 2400 W, four power modules (TMK5K35AFB) | **10** | 2, 4, 5-14 | APIU boards occupy AC power slots 1 and 3 (1500 W) or 1-4 (2400 W), which is where the two/four service slots go; the chapter prints the count as `12/10` with that note. **Consequence.** The same "14x B1LDCD" build read as fitting an AC shelf, overstating it by 2 boards (8 client ports) or 4 boards (16 client ports). `label`, `description` and `notes` now name the DC chassis and print the AC figures; `research/optixtrans-e6600-chassis-chapters.md` section 4 records that the rule it wrote on 2026-11-17 has been applied to the one entry it was written for. **Port list unchanged:** 84 interfaces, 56x 100GE QSFP28 client + 28x 200G CFP2 line - the DC figure the entry always meant. Evidence URL: `https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/621bfc22e8564cf69ae86581569a7594/M3T1A669N1304588489052958777/_2_-OptiXtrans%20E6616-Datasheet.pdf` **Gates:** `syntax-check` 405 files OK; `audit-port-types` no port contradicts its declared type; `hardware-invariants` 26/26; `catalogue-hygiene`, `spec-vs-description`, `device-aliases`, `cable-matrix`, `import-devices-capabilities`, `importer-roundtrip` all pass; `regen-registry-doc` reports the catalogue current (2,353 models / 258 vendors / 29,301 sockets), so `docs/DEVICE_REGISTRY.md` is unchanged.
catalogue: the E6616 states its power configuration, not just 14 slots (#803)
Some checks failed
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Successful in 53s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Arm auto-merge (pull_request) Failing after 35m3s
34d013e855
The cited E6616 chassis chapter (chapter 1, Tables 1-2) prints service slots per power option: DC 1-14 = 14; AC 2, 4, 5-14 = 12/10, where a 1500 W AC chassis (TMK5K33AFB, APIU in slots 1 and 3) has 12 and a 2400 W AC chassis (TMK5K35AFB, APIU in slots 1-4) has 10. The entry said '14 service slots' with no power qualifier, so an AC shelf read as fitting four more muxponder boards than it does; the E6608 and E6608T siblings already said 'DC chassis'. Label, description and notes now name the DC chassis (TMK5K31AFB). Port list untouched: 56 client + 28 line is the DC figure the entry always meant.
jaylouisw force-pushed catalogue/1118-0456 from 34d013e855
Some checks failed
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Successful in 53s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Arm auto-merge (pull_request) Failing after 35m3s
to 71b9237c95
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
CI / Test (Node 18) (pull_request) Has started running
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Test (Node 20) (pull_request) Has started running
CI / Test (Node 22) (pull_request) Has started running
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 21s
CI / Arm auto-merge (pull_request) Has been cancelled
2026-11-18 05:01:52 +00:00
Compare
jaylouisw force-pushed catalogue/1118-0456 from 71b9237c95
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
CI / Test (Node 18) (pull_request) Has started running
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Test (Node 20) (pull_request) Has started running
CI / Test (Node 22) (pull_request) Has started running
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 21s
CI / Arm auto-merge (pull_request) Has been cancelled
to 79636fa075
All checks were successful
CI / Classify the change (pull_request) Successful in 6s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Arm auto-merge (pull_request) Successful in 16s
2026-11-18 06:34:42 +00:00
Compare
jaylouisw force-pushed catalogue/1118-0456 from 79636fa075
All checks were successful
CI / Classify the change (pull_request) Successful in 6s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Arm auto-merge (pull_request) Successful in 16s
to 3648f868dc
All checks were successful
CI / Classify the change (pull_request) Successful in 6s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 18) (pull_request) Successful in 55s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 22) (pull_request) Successful in 51s
CI / Arm auto-merge (pull_request) Successful in 14s
2026-11-18 06:35:10 +00:00
Compare
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!1942
No description provided.