devices(ubiquiti): the EdgePoint S16's sixteen PoE ports could light nothing (refs #130) #2202
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!2202
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-1952"
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 #130 (blocked on the Pro; this is the family's next real defect, not a close).
devices/ubiquiti/ep-s16.jsoncarried sixteenpoeOutports and nopoeblock, soengine/simulator.jsopenedcomputePoe()withif (!dev.poeBudget) continue;and skipped the box: the ports were not "unknown", they could power nothing, andshow power inlineprinted "budget not modelled".Two more faults came out of the same census:
poeOutClass: "PoE"(802.3af, 48 V negotiated); the vendor describes them as(4) 54V or 24V /1.4A, 4-Pair ... Passive PoE, Ports 1 to 4. Ports 5-16 are the ones that actually negotiate:(12) 802.3af/at or 24V/0.7A, 2-Pair. So the four 75.6 W ports were filed as the weakest, and a 48 V 802.3af PD on port 1 was told it would work on hardware with no 802.3 detection at all - the UISP Router defect again (test/uisp-r-poe.test.js).(2) 54V / 1.5A, 4-Pairpassive PoE input, sopoeIn: 40(the vendor's ownMax. power consumption 40W) on eth0/eth1; cabling the switch to a PoE source now powers it instead of reporting an unpowered box.Budget, derived and labelled as such. Neither surface prints a PoE-budget row. Both print
(1) DC terminal block, 54V DC, 6A input= 324 W andMax. power consumption 40W (Excludes PoE output), so 324 - 40 = 284 W leave the ports on the stated DC-input configuration;poe.notealso records the PoE-input alternative (2 x 54V/1.5A = 162 W in, so 122 W out). Same arithmetic shape asuisp-r/er-6p.l2-forwardadded: the datasheet calls the EP-S16 "Layer-2 switch with some layer-3 capabilities" and lists Static/PBR routing, sol3-forwardstays.Sources (read 2026-11-19):
application/pdf, 6,571,516 B, 12 pp, "Models: EP-R6, EP-R8, EP-S16"; page 8 is the EP-S16 hardware table, page 4 the bottom-panel port map, page 5 the EP-R6 and page 6 the EP-R8 (three models, three adjacent tables).(12) PoE/PoE+ or 24V/0.7A.Trap recorded in
research/ubiquiti-edgepoint-poe-census.md:EdgePoint_S16_DS.pdf,EP-S16.pdf,EdgePoint_S16.pdfanddatasheets/edgemax/EP-S16_DS.pdfall 302 into the 609,911 B tech-spec front page - a 200 check reads that as a document.Gates: syntax 463 OK; audit-port-types clean; audit-devices no hard defects; hardware invariants 26/0; census/description 3/0; audit-poe-budget silent PSEs 103 -> 102; run-tests 385 suites / 12,944 assertions, 0 failed; control-bytes clean; registry doc current (2,355 models).
Siblings left for their own increment, census written up in the research note:
ep-r6(five passive outputs, none modelled) andep-r8(seven outputs, two modelled, both mislabelled; ports 7-8 are combo cages with nocomboPorts).