research(oceanprotect): the X8100 and X9100 books by ID — and why the pair is two enclosures #1811

Merged
jaylouisw merged 1 commit from catalogue/1117-0755 into main 2026-11-17 08:04:39 +00:00
Owner

Refs #743 — records the evidence; it does not close the issue.

What changed

research/oceanprotect-x-series-port-census.md gains a section identifying the four documents that carry the OceanProtect X8100/X9100 interface-module census, plus three findings that stop the next pass re-walking this ground.

1. The vendor page names the books. https://support.huawei.com/enterprise/en/data-protection/oceanprotect-x8100-pid-268353477 (200, 420,838 B) splits the request in two: Product Description EDOC1100368229 / Hardware Installation Guide EDOC1100305240 cover X6000, X8000, X8100; Product Description EDOC1100368230 / HIG EDOC1100305243 cover X9000, X9100.

2. The data sheet is a PPTX and still has no port count. Huawei OceanProtect X8100 X9100 Backup Storage Data Sheet V200R001C30.pptx (200, 5,265,602 B, 5 slides) carries one Front-End Port Types row (16/32/64 Gbit/s FC; 10/25/40/100GE) and zero occurrences of slot, IOM, interface module or port count across all five slides. Same shape as the E8000 data sheet: Huawei storage data sheets are PowerPoint files, so a PDF hunt never finds them — and finding them does not yield a socket count.

3. They are two enclosures, not one model. X8100: 2 U, 86.1 x 447 x 920 mm, <=45 kg, 2 controllers per node (max 4). X9100: 4 U, 175 x 447 x 865 mm, <=89 kg, 4 controllers per node (max 8). A single oceanprotect-x8100 spec cannot stand for the pair.

Access state recorded: doc roots 302 to /view/notFound on both support.huawei.com and support.huawei.cn; hedex/hdx.do?docid= returns a 3,728-byte viewer shell; hedex/api/navi/<EDOC>/first-level-tree answers 401 {"status":401,"message":"NOT LOGIN!"}; a section hash borrowed from the 1.3.0 book does not transfer (302), while the 1.3.0 book itself still parses (200, 501,601 B) — which is why devices/huawei/oceanprotect-x8000.json exists and these two do not.

Gates

  • node scripts/syntax-check.js — Syntax-checked 379 files: all OK
  • node scripts/audit-port-types.js — No port contradicts its declared type
  • node test/hardware-invariants.test.js — 26 passed, 0 failed
  • node scripts/check-doc-citations.js — exit 0
  • node scripts/regen-registry-doc.js --check — current: 2,348 models across 258 vendors, 29,235 sockets, 966 distinct port shapes

No device JSON touched, so the importer tripwire and the registry generator have nothing to say; docs/DEVICE_REGISTRY.md is unchanged and still current.

Blocker, unchanged in kind

Missing per model: the interface-module slot count on the controller enclosure, which slots accept front-end modules, and the per-module port counts for the 10/25/40/100GE and 16/32/64 Gb FC modules Huawei sells for each. Unblocks on any one live section of those four EDOCs (one slug opens a whole book, as ce945100 did for X6000/X8000), a stated configuration, or a Huawei ordering guide pinning ports per base model.

Refs #743 — records the evidence; it does not close the issue. ## What changed `research/oceanprotect-x-series-port-census.md` gains a section identifying the four documents that carry the OceanProtect X8100/X9100 interface-module census, plus three findings that stop the next pass re-walking this ground. **1. The vendor page names the books.** `https://support.huawei.com/enterprise/en/data-protection/oceanprotect-x8100-pid-268353477` (200, 420,838 B) splits the request in two: Product Description **EDOC1100368229** / Hardware Installation Guide **EDOC1100305240** cover *X6000, X8000, X8100*; Product Description **EDOC1100368230** / HIG **EDOC1100305243** cover *X9000, X9100*. **2. The data sheet is a PPTX and still has no port count.** `Huawei OceanProtect X8100 X9100 Backup Storage Data Sheet V200R001C30.pptx` (200, 5,265,602 B, 5 slides) carries one `Front-End Port Types` row (16/32/64 Gbit/s FC; 10/25/40/100GE) and **zero** occurrences of `slot`, `IOM`, `interface module` or `port count` across all five slides. Same shape as the E8000 data sheet: Huawei storage data sheets are PowerPoint files, so a PDF hunt never finds them — and finding them does not yield a socket count. **3. They are two enclosures, not one model.** X8100: 2 U, 86.1 x 447 x 920 mm, <=45 kg, 2 controllers per node (max 4). X9100: 4 U, 175 x 447 x 865 mm, <=89 kg, 4 controllers per node (max 8). A single `oceanprotect-x8100` spec cannot stand for the pair. **Access state recorded:** doc roots 302 to `/view/notFound` on both `support.huawei.com` and `support.huawei.cn`; `hedex/hdx.do?docid=` returns a 3,728-byte viewer shell; `hedex/api/navi/<EDOC>/first-level-tree` answers `401 {"status":401,"message":"NOT LOGIN!"}`; a section hash borrowed from the 1.3.0 book does not transfer (302), while the 1.3.0 book itself still parses (200, 501,601 B) — which is why `devices/huawei/oceanprotect-x8000.json` exists and these two do not. ## Gates - `node scripts/syntax-check.js` — Syntax-checked 379 files: all OK - `node scripts/audit-port-types.js` — No port contradicts its declared type - `node test/hardware-invariants.test.js` — 26 passed, 0 failed - `node scripts/check-doc-citations.js` — exit 0 - `node scripts/regen-registry-doc.js --check` — current: 2,348 models across 258 vendors, 29,235 sockets, 966 distinct port shapes No device JSON touched, so the importer tripwire and the registry generator have nothing to say; `docs/DEVICE_REGISTRY.md` is unchanged and still current. ## Blocker, unchanged in kind Missing per model: the interface-module slot count on the controller enclosure, which slots accept front-end modules, and the per-module port counts for the 10/25/40/100GE and 16/32/64 Gb FC modules Huawei sells for each. Unblocks on any one live section of those four EDOCs (one slug opens a whole book, as `ce945100` did for X6000/X8000), a stated configuration, or a Huawei ordering guide pinning ports per base model.
research(oceanprotect): the X8100 and X9100 books by ID, and why the pair is two enclosures
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Classify the change (pull_request) Successful in 9s
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 48s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Arm auto-merge (pull_request) Successful in 15s
447c160c11
#743 asks for "X8100/X9100" as one device. The X8100 support page names the four
documents that would settle it (Product Description EDOC1100368229 / EDOC1100305240
for X6000, X8000 and X8100; EDOC1100368230 / EDOC1100305243 for X9000 and X9100), and
the X8100/X9100 data sheet V200R001C30 - a 5.2 MB PowerPoint - publishes no slot,
IOM or interface-module row at all: zero occurrences of "slot", "IOM" and
"interface module" across its five slides, and one "Front-End Port Types" row.

The two models cannot share a spec anyway: X8100 is a 2 U node 86.1 x 447 x 920 mm at
45 kg, X9100 a 4 U node 175 x 447 x 865 mm at 89 kg.

Records the access state of all four books too: doc roots 302 to /view/notFound on both
support hosts, the hedex navi API answers 401 NOT LOGIN, and a section hash borrowed
from the 1.3.0 book does not transfer - while the 1.3.0 book itself still parses
(501,601 bytes), which is why the X8000 spec exists and these two do not.

Refs #743.
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!1811
No description provided.