devices(ubiquiti): the EdgeRouter 10X passed power through no port, and drew it on nine (refs #130) #2179
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!2179
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-1622"
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
The UDW-PRO itself is still blocked (no Ubiquiti-hosted page, datasheet, QSG, grant, storefront entry or firmware platform names it; the nine surfaces in the issue thread are exhausted and were not re-walked). This PR spends the increment on the routed-lab fallback path the issue's stated lab needs - a router that can be the gateway, NAT/DHCP/VPN - and on the one EdgeRouter row in it that could not pass power.
What was wrong
devices/ubiquiti/er-10x.json(EdgeRouter 10X) declaredpoe-pseand modelled no sourcing port, so a lab cabling an AP to it got:Ubiquiti's tech-spec table prints both sockets: PoE In: (1) 24V passive PoE port, 2-pair (4, 5+; 7, 8-) and PoE Out: (1) 24V passive PoE port, 2-pair (4, 5+; 7, 8-), with Passive PoE output = DC/PoE passthrough and Passive PoE Max. wattage per port = 15W (24V, 0.63A). The store page for the same SKU summarises it: "Gigabit router with a built-in Layer 2 switch, (10) Gigabit RJ45 ports, a PoE input, and PoE passthrough port."
The same silence ran the other way: the row keeps the device-level
poe-pdtoken, soisPoePd()gave all ten copper ports a 12.95 W 802.3af draw - 124.55 W of phantom load on hardware whose supply is a 24 W adapter and whose max consumption is 8 W.After
show power inline(AP on eth9)% No PoE ... no port on this device can supply powerAvailable:15.0(w) Used:13.0(w) Remaining:2.0(w)/eth9 auto on 12.95 W APfalseon eth1-eth9poe.budgetWspeedCaps["1G","100M"][1000,100,10]- the vendor says "10/100/1000"Which socket is which is a convention, not a vendor figure (neither host numbers the PoE pair): inlet on eth0, outlet on eth9 (last port), the same placement as
devices/ubiquiti/ER-X.jsonanddevices/ubiquiti/ucg-fiber.json. The count (1 + 1), the class (24V passive), the 15 W ceiling and the 8 W draw are the vendor's.test/poe-inference.test.jshad ER-10X on itsPD_ONLYlist - which is part of why "sources nothing" survived. It leaves that list and gets a stricter assertion in its place: exactly one outlet (eth9, 15 W) and exactly one inlet (eth0, 8 W), so the ten-port-PSE defect the list was written for is still refused.Sources (read 2026-11-19)
Trap recorded in
notes: this SKU has no datasheet or quick-start -https://dl.ui.com/datasheets/edgemax/EdgeRouter_10X_DS.pdfandhttps://dl.ui.com/guides/edgemax/EdgeRouter_10X_QSG.pdfboth answer 200 with the 609,911-byte techspecs front page, the silent fallback already trapped for ucg-fiber/uxg-pro/er-6p/er-12p. The console port (Management interface = (1) RJ45 serial port) is recorded innotes, notinterfaces, perdocs/DEVICE_SCHEMA.md.Gates
node scripts/syntax-check.js- 459 files, all OKnode scripts/audit-port-types.js- no port contradicts its declared typenode scripts/audit-poe-budget.js- 407 PSEs (was 406), 0 budgets with no PSE portnode test/hardware-invariants.test.js- 26 passed, 0 failednode scripts/regen-registry-doc.js- catalogue pages current (2,356 models, 29,719 sockets)node scripts/import-devices.js --dry-run- refusal list unchanged from main (two pre-existing duplicate spellings in research/incoming), 0 capability lossesnode scripts/run-tests.js- 380 suites, 12,863 assertions, 0 failed