research(oceanprotect): the X8100 and X9100 books by ID — and why the pair is two enclosures #1811
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!1811
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1117-0755"
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?
Refs #743 — records the evidence; it does not close the issue.
What changed
research/oceanprotect-x-series-port-census.mdgains 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 oneFront-End Port Typesrow (16/32/64 Gbit/s FC; 10/25/40/100GE) and zero occurrences ofslot,IOM,interface moduleorport countacross 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-x8100spec cannot stand for the pair.Access state recorded: doc roots 302 to
/view/notFoundon bothsupport.huawei.comandsupport.huawei.cn;hedex/hdx.do?docid=returns a 3,728-byte viewer shell;hedex/api/navi/<EDOC>/first-level-treeanswers401 {"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 whydevices/huawei/oceanprotect-x8000.jsonexists and these two do not.Gates
node scripts/syntax-check.js— Syntax-checked 379 files: all OKnode scripts/audit-port-types.js— No port contradicts its declared typenode test/hardware-invariants.test.js— 26 passed, 0 failednode scripts/check-doc-citations.js— exit 0node scripts/regen-registry-doc.js --check— current: 2,348 models across 258 vendors, 29,235 sockets, 966 distinct port shapesNo device JSON touched, so the importer tripwire and the registry generator have nothing to say;
docs/DEVICE_REGISTRY.mdis 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
ce945100did for X6000/X8000), a stated configuration, or a Huawei ordering guide pinning ports per base model.