research: OptiXtrans slot counts are mode-dependent, and three of the five frames have no cross-connect (#807) #1752

Merged
jaylouisw merged 1 commit from catalogue/1116-2355 into main 2026-11-17 00:02:39 +00:00
Owner

Refs #807 — records the census; it does not close the issue.

Adds research/optixtrans-slot-census.md: both OptiXtrans specification tables re-read 2026-11-16, with
three findings the earlier blocker notes did not carry.

  1. Three of the five requested frames have no cross-connect at all. The E6600 page prints
    Cross-connect Capacity ... NA for the E6608T (#804) and the E9600 page prints
    Cross-connect Type ... NA for the E9612 (#808) and E9605 (#807), while E6616/E6616X/
    E9624 print OTN/PKT/SDH and ODUk/PKT/VC. They are photonic shelves, so there is no chassis-only
    port to model even in principle — not one management Ethernet port in the published table.
  2. E9624 is not a 24-slot frame. Huawei's FTTO brochure (25H1) prints
    1:1 mode: 12 large slots or 24 small slots and 1:3 mode: 10 large slots or 20 small slots for
    the same subrack; the marketing page's 12/24 compresses that away. Protection mode belongs in the
    label.
  3. Slot counts, per model, from the vendor: E6616 DC 14 / AC 12 · E6608 DC 6 / AC 4 · E6608T DC 7 /
    AC 5 · E6616X DC 14 / AC 12 · E9605 5 · E9612 13 · E9624 12/24 (1:1) or 10/20 (1:3).

The file ends with the field each issue is still missing (board part number per slot; plus protection
mode for #810), the docs/RESOLUTIONS.md label shape that converts it to a spec in one step, and what
was tried and is not public (EDOC1100624531, the E9600 Board Datasheet, answers HTTP 404 to a crawler
UA today).

Gates: node scripts/syntax-check.js 367 files OK · node scripts/audit-port-types.js no contradiction ·
node test/hardware-invariants.test.js 26 passed · registry regen: 2,339 models, no diff.

Refs #807 — records the census; it does **not** close the issue. Adds `research/optixtrans-slot-census.md`: both OptiXtrans specification tables re-read 2026-11-16, with three findings the earlier blocker notes did not carry. 1. **Three of the five requested frames have no cross-connect at all.** The E6600 page prints `Cross-connect Capacity ... NA` for the **E6608T** (#804) and the E9600 page prints `Cross-connect Type ... NA` for the **E9612** (#808) and **E9605** (#807), while E6616/E6616X/ E9624 print OTN/PKT/SDH and ODUk/PKT/VC. They are photonic shelves, so there is no chassis-only port to model even in principle — not one management Ethernet port in the published table. 2. **E9624 is not a 24-slot frame.** Huawei's FTTO brochure (25H1) prints `1:1 mode: 12 large slots or 24 small slots` and `1:3 mode: 10 large slots or 20 small slots` for the same subrack; the marketing page's `12/24` compresses that away. Protection mode belongs in the label. 3. **Slot counts, per model, from the vendor:** E6616 DC 14 / AC 12 · E6608 DC 6 / AC 4 · E6608T DC 7 / AC 5 · E6616X DC 14 / AC 12 · E9605 5 · E9612 13 · E9624 12/24 (1:1) or 10/20 (1:3). The file ends with the field each issue is still missing (board part number per slot; plus protection mode for #810), the `docs/RESOLUTIONS.md` label shape that converts it to a spec in one step, and what was tried and is not public (`EDOC1100624531`, the E9600 Board Datasheet, answers HTTP 404 to a crawler UA today). Gates: `node scripts/syntax-check.js` 367 files OK · `node scripts/audit-port-types.js` no contradiction · `node test/hardware-invariants.test.js` 26 passed · registry regen: 2,339 models, no diff.
research: OptiXtrans slot counts are mode- and power-dependent, and three of the five frames have no cross-connect (#807)
All checks were successful
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 23s
CI / Test (Node 20) (pull_request) Successful in 1m0s
CI / Docker build (pull_request) Successful in 32s
CI / Test (Node 18) (pull_request) Successful in 1m4s
CI / Test (Node 22) (pull_request) Successful in 1m3s
CI / Arm auto-merge (pull_request) Successful in 15s
2626c20cea
The five open OptiXtrans requests were parked on one sentence - the subrack has no ports until
service boards are fitted. Reading both specification tables again records what that sentence
hides: E6608T, E9605 and E9612 publish NA for the cross-connect row, so they are photonic shelves
with no chassis-only port at all, and E9624's 12/24 is 10/20 in 1:3 mode per Huawei's own FTTO
brochure. docs/RESOLUTIONS.md already fixes the label shape for a stated configuration, so each
issue is one line away rather than one research project away.
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!1752
No description provided.