catalogue(oceanprotect): X8100/X9100 management-plane census from the vendor white paper (#743) #1902
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1902
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "storage/743"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes #743.
The request was parked on a front-end port count Huawei does not publish. The same array's management plane is published per model, in a document that is not behind the support portal at all: Huawei OceanProtect X Series Backup Appliance Technical White Paper, Issue 01 (2026-09-29), whose material page is
https://e.huawei.com/en/documents/products/storage/eded1b265ecc4dfba2fbf8669b0b8213. Chapter 3 goes model by model, and both models in this request are in it.What is modelled
They are two catalogue entries on purpose: 2 U / 2 controllers against 4 U / 4 controllers, which is what the earlier passes established and what
.../x100-seriesstates.Frame and capacity facts are in
notes, not modelled as ports: 12 hot-swappable interface-module slots and 36 NVMe disk slots for the X8100 (1-2 PiB usable per node, 86.1 x 447 x 920 mm, <= 45 kg), 28 shared interface-module slots for the X9100 (2-3 PiB usable per node, 175 x 447 x 865 mm, <= 89 kg), 4 / 8 controllers maximum per system, C13 or C19 feed. Serial and USB ports are innotesperdocs/DEVICE_SCHEMA.md("Serial consoles, USB, FXS"), and the connector is omitted rather than guessed as RJ45 - the vendor does not publish it.What is still absent, and why that is not a gap in the entry
Every front-end port on these arrays comes from an interface module, and no reachable vendor book states a ports-per-module count. The white paper's section 2.3.2 gives a slot preference order (
IOM 0 > IOM 1 > IOM 3 > IOM 4 > IOM 5 > IOM 2) where the 1.3.0 X6000/X8000 guide gave a restriction ("can be installed only in slots IOM 0, IOM 1, and IOM 4"), and 3.1.5-3.1.6 list the module kinds (8/16/32/64 Gbit/s FC, 10GE, 25GE, 40GE, 100GE, 100 Gbit/s RDMA scale-out, 12 Gbit/s SAS) with no counts.EDOC1100368229,EDOC1100368230,EDOC1100305240andEDOC1100305243all still answer HTTP 302 withX-ALB-HIT: req-hd-bl(measured 2026-11-17). So the entries model the build the vendor describes - node, no interface modules - rather than invent an IOM population.research/oceanprotect-x-series-port-census.mdgains sections 14-15 recording this pass, and section 15 carries the other request's negative result (see the comment on #742).Gates
node scripts/syntax-check.js- 395 files, all OKnode scripts/audit-port-types.js- exit 0, no port contradicts its declared typetest/hardware-invariants.test.js- 26 passed, 0 failed (2,350 models)test/catalogue-hygiene.test.js- 25 passed, 0 failedtest/doc-catalog-counts.test.js- 43 passed, 0 failed (regen:registry-docrun: 2,350 models, 29,245 sockets, 967 shapes)test/spec-vs-description.test.js- 3 passed, 0 failedSurgery pass: rebased onto main and fixed the red run; no content changed.
CI / Testwas failing on one deterministic assertion, not on anything this PR argues:The long alias reproduces the model field (
modelis the slugoceanprotect-x9100, the alias normalises to it), which the invariant rejects twice over. I dropped"OceanProtect X8100"/"OceanProtect X9100"and kept the short"X8100"/"X9100"forms, so nothing becomes less findable. That is the only change: no interface, note, port or research text was touched, andnpm run regen:registry-docproduces no diff.Verified in a scratch worktree, serial:
device-aliases13/0,hardware-invariants26/0,catalogue-hygiene25/0,missing-devices66/0. Pushed asddcd1e0d(rebase ofb2d99ea7onto4881bce4,--force-with-lease).If the census genuinely wants the long form searchable, the fix is the other way round — make
modelthe display name asoceanprotect-x8000.jsondoes — but that changes what the registry renders, so it is the author's call, not mine.b2d99ea7afddcd1e0daf