research(optixtrans): the OSN 1800 V hardware description is gated in every edition too #2039

Merged
jaylouisw merged 1 commit from catalogue/1118-2122 into main 2026-11-18 21:40:14 +00:00
Owner

Refs #803.

One more route measured shut, not a spec. TMB2DMS is sold as an OptiX OSN 1800 V Pro board, and the only public index of the generation's board chapters links them under an 1800v/ hedex package path (.../resources/1800v/hd/pkg/tmk1ex10/tmk1ex10.html), not an E6600 one. So a public OSN 1800 V hardware description would carry the same TMB2DMS chapter - with the 配套设备 table that is the whole blocker.

It does not. Seven editions listed on https://support.huawei.com/enterprise/en/optical-transmission/optix-osn-1800-v-pro-pid-250732494 (200, 476,757 B, 391 document links), one GET /hedex/api/navi/<id>/first-level-tree each, Googlebot UA:

document id answer
OSN 1800 Hardware Description 01 EDOC1100558550 401 NOT LOGIN
OSN 1800 V V100R025C00 HD 01 EDOC1100525975 401
OSN 1800 V V100R024C10 HD 03 EDOC1100456158 401
OSN 1800 V V100R022C10 HD 01 EDOC1100303420 401
OSN 1800 V V100R021C10 HD 05 EDOC1100249290 401
OSN 1800 V V100R019C10 HD 06 EDOC1100192279 401
OSN 1800 V V100R025C10 Product Description 01 EDOC1100558552 401

Controls in the same minute, same endpoint and UA: EDOC1100447312 200, EDOC9999999999 404. Also 401: the English OptiXtrans E6616X Quick Installation Guide 02, EDOC1100299472, printed under Quick Start on the E6616X support page - which pairs it with the Chinese EDOC1100299473 already on record, so the two ids are one document.

Evidence in research/optixtrans-osn1800v-hd-also-gated.md; research/open-device-requests.json and the generated docs/DEVICE_REGISTRY.md carry the narrowed entry.

devices/ is untouched. The frame fields are vendor-sourced and waiting (14/12 service slots, 780G OTN / 620G OSU / 160G VC-4 SDH / 820G packet, 100 Gbit/s grey per channel); no cableable port count is published behind them. Unblock is unchanged: one free Huawei enterprise account reading EDOC1100558549 (§ TMB2DMS), or a stated configuration E6616X DC chassis, slots 1-14: n x TMB2DMS + n x TMB2PD1.

Gates: syntax-check 425 files OK; audit-port-types no contradiction; test/hardware-invariants 26 passed; test/request-queue 32 passed; check-control-bytes clean; registry regenerated.

Refs #803. **One more route measured shut, not a spec.** `TMB2DMS` is sold as an OptiX OSN 1800 V Pro board, and the only public index of the generation's board chapters links them under an `1800v/` hedex package path (`.../resources/1800v/hd/pkg/tmk1ex10/tmk1ex10.html`), not an E6600 one. So a public OSN 1800 V hardware description would carry the same `TMB2DMS` chapter - with the `配套设备` table that is the whole blocker. It does not. Seven editions listed on `https://support.huawei.com/enterprise/en/optical-transmission/optix-osn-1800-v-pro-pid-250732494` (200, 476,757 B, 391 document links), one `GET /hedex/api/navi/<id>/first-level-tree` each, Googlebot UA: | document | id | answer | |--|--|--| | OSN 1800 Hardware Description 01 | EDOC1100558550 | 401 NOT LOGIN | | OSN 1800 V V100R025C00 HD 01 | EDOC1100525975 | 401 | | OSN 1800 V V100R024C10 HD 03 | EDOC1100456158 | 401 | | OSN 1800 V V100R022C10 HD 01 | EDOC1100303420 | 401 | | OSN 1800 V V100R021C10 HD 05 | EDOC1100249290 | 401 | | OSN 1800 V V100R019C10 HD 06 | EDOC1100192279 | 401 | | OSN 1800 V V100R025C10 Product Description 01 | EDOC1100558552 | 401 | Controls in the same minute, same endpoint and UA: `EDOC1100447312` **200**, `EDOC9999999999` **404**. Also 401: the English `OptiXtrans E6616X Quick Installation Guide 02`, `EDOC1100299472`, printed under *Quick Start* on the E6616X support page - which pairs it with the Chinese `EDOC1100299473` already on record, so the two ids are one document. Evidence in `research/optixtrans-osn1800v-hd-also-gated.md`; `research/open-device-requests.json` and the generated `docs/DEVICE_REGISTRY.md` carry the narrowed entry. `devices/` is untouched. The frame fields are vendor-sourced and waiting (14/12 service slots, 780G OTN / 620G OSU / 160G VC-4 SDH / 820G packet, 100 Gbit/s grey per channel); no cableable port count is published behind them. Unblock is unchanged: one free Huawei enterprise account reading `EDOC1100558549` (§ TMB2DMS), or a stated configuration `E6616X DC chassis, slots 1-14: n x TMB2DMS + n x TMB2PD1`. Gates: `syntax-check` 425 files OK; `audit-port-types` no contradiction; `test/hardware-invariants` 26 passed; `test/request-queue` 32 passed; `check-control-bytes` clean; registry regenerated.
research(optixtrans): the OSN 1800 V hardware description is gated in every edition too
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 7s
CI / Server smoke test (pull_request) Successful in 12s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Successful in 53s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Test (Node 18) (pull_request) Successful in 59s
CI / Arm auto-merge (pull_request) Successful in 3s
88c14f424e
Refs #803.

TMB2DMS is sold as an OSN 1800 V Pro board and the board chapters sit under an
1800v/ hedex package path, so a public OSN 1800 V hardware description would
carry the same chapter the E6600 gate hides. Seven editions measured on
optix-osn-1800-v-pro-pid-250732494: every one answers 401 NOT LOGIN to
/hedex/api/navi/<id>/first-level-tree, against controls answering 200
(EDOC1100447312) and 404 (EDOC9999999999) in the same minute. The English
E6616X Quick Installation Guide EDOC1100299472 is 401 as well, pairing it with
the Chinese EDOC1100299473 already on record.

Catalogue unchanged: no port count is published behind the E6616X frame.

This branch conflicts with main, so it was not rebased:

docs/DEVICE_REGISTRY.md research/open-device-requests.json research/optixtrans-osn1800v-hd-also-gated.md 

A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.

This branch conflicts with `main`, so it was not rebased: ``` docs/DEVICE_REGISTRY.md research/open-device-requests.json research/optixtrans-osn1800v-hd-also-gated.md ``` A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.
jaylouisw force-pushed catalogue/1118-2122 from 88c14f424e
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 7s
CI / Server smoke test (pull_request) Successful in 12s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Successful in 53s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Test (Node 18) (pull_request) Successful in 59s
CI / Arm auto-merge (pull_request) Successful in 3s
to 8cf7efa9fc
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 6s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Test (Node 18) (pull_request) Successful in 59s
CI / Arm auto-merge (pull_request) Successful in 2s
2026-11-18 21:38:16 +00:00
Compare
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
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!2039
No description provided.