[Device]: OptiXaccess MA5800 Series #783
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#783
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
OptiXaccess MA5800 Series
Category
OLT (PON headend)
Ports and interfaces
PoE budget (watts)
None (no PoE output)
Datasheet or product page URL
https://e.huawei.com/en/products/optical-access/ma5800
What do you want to model with it?
ISP/enterprise aggregation OLT for FTTH/FTTB.
Capabilities
olt, pon (GPON/XG-PON/XGS-PON), l2-forward, cli
Before submitting
Not closing this one, but the blocker is now named precisely so it can be finished quickly.
The MA5800
.htmlpage does render a full model table (X17 / X15 / X7 / X2), and it gives:Every one of those is a capacity, not a census. A chassis OLT has no fixed ports: it has slots, and which ports exist depends on which service boards and which control board are fitted. Modelling X17 as a 272-PON device would let a lab cable 272 PONs into a frame that might have sixteen; modelling it as a 16-PON device would be equally invented.
So the request needs the same thing the FS NC8200/NC8400 chassis (#757/#760) need: a stated configuration - "MA5800-X7 with one MPLB control board and three GPHF service boards" - and then the ports fall out of the board tables. That is a decision a requester can make in one line; it is not something a spec file should invent.
(For contrast, #787/#784/#786 - the EA5801E, MA5801 and EA5801S - are box OLTs where Huawei publishes a fixed port count per model, which is why those closed.)
Closing: the whole MA5800 series is now in the catalogue, each model as one stated configuration. The blocker named in the 2026-11-10 comment — "capacity, not a census" — was resolved by modelling a named card set rather than the shelf maximum, and all four subracks now exist:
devices/huawei/ma5800-x17.jsondevices/huawei/ma5800-x15.jsondevices/huawei/ma5800-x7.jsondevices/huawei/ma5800-x2.jsonSource for every row: Huawei's MA5800 specification table,
https://e.huawei.com/en/products/optical-access/ma5800— board configuration per subrack, "GPON ports 272 / XG-PON 272 / XGS-PON 272" (X17) down to 32 (X2), and the board table the configuration names: H901MPLA "4x GE / 10GE upstream" (which is why the uplinks arexge0/1-4), H901GPHF "16 GPON ports", plus H901XGHD / H901TWED / H901OGHK / H901OXHD / H901NXED as the alternatives a requester can name instead.The 272 figure stays in the description and notes as capacity, not as ports: cabling 272 PONs into a frame holding one 16-port card is the failure mode this modelling avoids. A different card set is a one-line change — name it ("X7 with MPLG and three H901OGHK") and the ports follow from the same board table.
X17 landed as
969c999c(PR #1650); X15/X7/X2 have been in the catalogue since the optical-access import. Nothing here is guessed, and no PoE is declared: a PON subrack sources no power on its PON ports.