[Device]: OptiXaccess S0316 #785
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#785
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 S0316
Category
Other / not sure
Ports and interfaces
PoE budget (watts)
None (no PoE output)
Datasheet or product page URL
https://e.huawei.com/en/products/optical-access/optixaccess-s0316
What do you want to model with it?
PoF scenarios: power + optical signal delivery to ONUs over PoF cables.
Capabilities
Power-over-fiber distribution; optical power split
Before submitting
Modelled -
devices/huawei/optixaccess-s0316.json, commit6ff7be0onfix/sfp-plus-connectors(the.htmlURL again - the extensionless page renders only navigation).The spec table is unusually complete for a box this size:
NNI: 2 x SC/UPC- two upstream optical ports;UNI: 16 x Hybrid SC(PoF)- sixteen downstream ports carrying both the optical signal and power;PoF output power: max 30W per port (PoE/PoE+), total 400W.Three things this one gets right that are usually guessed:
poeBudget: 400withpoeOut: 30on each UNI port is a published claim - unlike #527, where "400 W" was a supply rating and only volts and amps were published, so no budget was declared;sc-upcinstead of inheriting thesc-apcconvention every OLT in this catalogue uses. The sixteen hybrid SC UNI ports match the hybrid SC cords already incatalogue/optics/hybrid-patch-cords.json, whosesc-upcend is what makes a PoF run legal;splitRatiois absent.One assumption, flagged in
notes: the datasheet publishes no optical rate. The ports carry GPON to ONUs, so they carry the GPON ladder[1244, 2488]used by every OLT and ONU here - a family convention, not a figure from this page.Correction to this spec - two errors, both caught this iteration. Commit
ea303fcremoves both.poeOut: 30on the sixteen UNI ports andpoeBudget: 400on the device.test/poe-inference.test.jscaught it with its catalogue-wide rule: no port on a non-copper cage may source power. That rule is right - this engine's PoE model is a copper model, computing PSE class, per-port output, a shared budget and the PD draw across Ethernet pairs, andsc-upcis an optical cage. Power over Fibre is real and this box really does 30 W a port / 400 W total, but a machine-readable claim would have the engine evaluate a power budget over a medium it does not simulate. The figures now live innotes, anddocs/DEVICE_REGISTRY.md§"What the catalogue cannot represent" says why: making PoF first-class needs a PoF media id, PoF cords and power on the optical rail - a feature, not a spec file.catalogue/optics/hybrid-patch-cords.json". They do not: hybrid in those cords means ferrule polish (SC/UPC one end, SC/APC the other, one factory assembly - the issue #18 case), not power. There is no PoF cord in this catalogue at all, which is the same gap seen from the other side.What stands unchanged and verified: 2x SC/UPC NNI, 16 hybrid SC UNI,
sc-upcbecause the vendor states UPC on this box, nosplitRatio(2 NNI to 16 UNI is genuinely ambiguous), and the GPON ladder flagged as a family convention rather than a figure from the page.