devices(ubiquiti): the EdgeSwitch 18X sourced power on fifteen sockets it has not got #2403
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!2403
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rev/1121-0942"
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?
Ubiquiti's ES-18X datasheet names both ends of the passthrough in one sentence - "PoE input on port 1 and PoE passthrough on port 16" - while the tech-spec row the entry was built from says only "(1) 24V passive PoE port". The entry put that one port on
eth0(an assumption its own note admitted), and because aswitchwithpoe-psehas its copper ports inferred,derivePortHardware()filledeth1-eth15with 15.4 W of 802.3af on a 24 V passive box.show power inlinelisted sixteen PSE ports where the hardware has one.eth15(port 16):poeOut: 15,poeOutClass: passive- the outlet at the vendor's per-port ceiling.eth0(port 1):poeIn: 14- the inlet at the box's ownMax. Power Consumption: 14W (Excludes PoE Output), the same shapeer-10x.jsonuses for its 8 W inlet;poe-pdadded.eth1-eth14:poeOut: false, so the switch-wide inference cannot re-promote them.poe.budgetW: 10, marked DERIVED (24 W adapter - 14 W draw, the ES-10XP's arithmetic) because Ubiquiti prints no total PoE row. The audit's silent cohort drops 33 -> 32.test/es-10x-passthrough.test.jspins the outlet, the absence of every other PSE, the inlet, the derived budget and the console's answer.Sources: ES-18X datasheet, tech specs, EdgeSwitch X datasheet (ES-10X: same construction), HostiFi EdgeMAX PoE table. Open questions in
research/es-18x-passthrough-port.md.Gates:
node scripts/syntax-check.js(522 files OK);npm test442 suites, 14,926 assertions, 0 failed.