[Device]: Huawei OceanProtect X8000/X9000 Backup Storage #741
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#741
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Vendor
Huawei
Exact model name
Huawei OceanProtect X8000/X9000 Backup Storage
Category
NAS
Ports and interfaces
PoE budget (watts)
None
Datasheet or product page URL
https://e.huawei.com/en/products/storage/oceanprotect/x-series.html
What do you want to model with it?
Backup storage target or integrated backup appliance (D2D/F2F target).
Capabilities
backup storage (NFS/SMB/iSCSI/S3/FC target)
Before submitting
Blocked on a port count, not on research effort.
Huawei's public page for the OceanProtect X8000/X9000 gives the port types - front-end 10/25/40/100GE and 16/32/64 Gbit/s Fibre Channel, with 2 or 4 controllers per node and up to 8 in a system - but not how many front-end ports a node has. That number depends on the interface-card configuration, and the configuration-specific tables live on
support.huawei.com, which is behind a login wall I cannot pass (plain fetch returns HTTP 422; a real browser returns an empty page).A storage array with no stated port count would have to be invented, so this stays open. If someone can paste the front-end port count for the requested configuration, I will land it the same day.
Closing status: blocked on a stated configuration.
Huawei publishes OceanProtect front-end port types - "16/32/64 Gbit/s FC; 10/25/40/100GE" - and a controller count, but not a port count, because how many front-end ports a backup array has is a function of the controllers and interface cards ordered. E8000's page publishes no interface table at all.
The X-series comparison table is otherwise complete (capacity, bandwidth, controllers, cache), which is why this is a narrow blocker rather than an unreadable page.
What would close it: a controller/interface-card configuration, or an authoritative Huawei ordering guide that pins ports per base model.
docs/DEVICE_REGISTRY.md§"What is left open, and why" records the same reason for all three (#741, #742, #743).Split result this pass: the X8000 half is now settled and modelled; the X9000 half is blocked on a dead URL. PR #1797 adds
devices/huawei/oceanprotect-x8000.jsonand deliberately does not close this issue.The claim three passes repeated was wrong for this family
"Huawei publishes port types and a controller count, never a port count" is true of the datasheets and the marketing spec tables, and false of the Product Description's interface-module chapters - which are ordinary indexed sections:
Sources:
https://support.huawei.com/enterprise/en/doc/EDOC1100319420/7a0c3635/10ge-electrical-interface-module,.../378e8255/25-gbit-s-roce-interface-module,.../c4d726f4/25-gbit-s-rdma-interface-module,.../7c64209f/smartio-interface-module.Slot geometry:
https://support.huawei.com/enterprise/en/doc/EDOC1100318730/ce945100/cabinet-layout-and-connection-planning- "Each of controllers A and B provides six interface module slots"; "Interface modules for the front-end network connection can be installed only in slots IOM 0, IOM 1, and IOM 4"; IOM 0 takes a 10GE electrical module, IOM 1 takes the container front-end module ("Ports P0 and P1 ... Ports P2 ... Port P3"), IOM 3 holds the 25 Gbit/s RoCE module with no cable.What was modelled for X8000: one 2 U two-controller node, a 4-port 10GE electrical module in IOM 0 and another in IOM 1 on each controller - 16 x 10GbE SFP+, no PoE. IOM 0 and IOM 1 are front-end slots under both versions of "Rules for Installing Interface Modules" that the guide serves (they disagree about IOM 4, which is why IOM 4 is not fitted rather than guessed). The internal RDMA/RoCE links, the SAS disk-expansion modules and the figure-only management port are recorded in
notes, not invented.X9000: still open, and the blocker is exact
/enterprise/en/doc/EDOC1100337685/8ed1346b/overview(X9000 1.5.0 PD)/view/notFound(Googlebot UA); 403 (browser UA).../67ea5a63/interface-module,.../ad9f2760/component-descriptioninfo.support.huawei.com/enterprise/en/doc/EDOC1100337685/8ed1346b/overview/supportindex/(91,294 B), not the document.../es/and.../de/locale variants of the same section/enterprise/en/doc/EDOC1100368229(X9000, X9100 1.6.0-1.7.0 & V200R001 PD)/enterprise/en/doc/EDOC1100305237(X9000, X9100 1.x Quick Installation Guide)/enterprise/en/doc/EDOC1100368334(X9000, X9100 1.x Hardware Installation Guide)Exact missing fields: for a stated controller count (2 or 4), which of the 28 slots accept front-end modules, the module mix per quadrant, and the per-module port count for the modules Huawei sells for this node. The X6000/X8000 numbers do not transfer silently - same module names, different controller enclosure and slot numbering, and the X9000's price catalogue lists modules the 2 U node does not have (2-port 40 GbE, 2-port 100 GbE, 4-port 1 GbE).
The trap, so nobody falls into it: the live page
https://info.support.huawei.com/enterprise/en/doc/EDOC1100484689/bb36e2c/connection-planning-between-the-storage-system-and-application-serverprints almost exactly the cached X9000 slot rules (IOM H5..H8 back-end, quadrant front-end rules) and is titled OceanStor Dorado 8000 and Dorado 18000 V700R001 Site Planning Guide.What would unblock X9000: any live section of
EDOC1100368229orEDOC1100368334- one slug opens the whole set, asce945100did for X6000/X8000 - or one stated configuration in the shape "X9000 node, 4 controllers, 4-port 25GE module in IOM H0/L0 ...".Full record incl. every HTTP status:
research/oceanprotect-x-series-port-census.md(this PR).