devices(ubiquiti): the ER-X family modelled no PoE, and none of the three cited a source (refs #130) #2138
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!2138
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-1052"
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 (does not close it — the Dream Wall Pro is still unbuildable; this is the family the request falls back into).
The request's stated lab is NAT, DHCP, VPN, cellular WAN in a routed topology. The three compact EdgeOS routers below are the cheapest rows a requester is handed for it, and all three had no
sourceUrlat all — every port count, rate and power figure in them was unattributed. The two PoE members also modelled no PoE: the ER-X'seth4/PoE Outsourced nothing and itseth0/PoE Inwas not a PD, so a lab that powered the router from a PoE switch was told it was not powered.devices/ubiquiti/ER-X.jsonpoeIn: 5on port1,poeOut: 5(passive) on port5,poe.budgetW: 5, datasheet + QSG citeddevices/ubiquiti/ER-X-SFP.jsonpoeOut: 12(passive),poe.budgetW: 50, datasheet + tech-spec citeddevices/ubiquiti/edgerouter4.jsonpoeIn: falseon the three copper ports, tech-spec + store citedSources.
https://dl.ui.com/datasheets/edgemax/EdgeRouter_X_DS.pdf(200,application/pdf, 3,594,850 B, 7 pp — one PDF, two tables: ER-X p5, ER-X-SFP p6),https://dl.ui.com/guides/edgemax/EdgeRouter_ER-X_QSG.pdf(200,application/pdf, 1,362,583 B, 18 pp — the only place the ER-X passthrough watts are printed),techspecs.ui.com/uisp/wired/{er-x,er-x-sfp,er-4}(200; 575,859 / 582,211 / 575,010 B),store.ui.com/us/en/products/{er-x,er-x-sfp,er-4}(200; 326,228 / 328,876 / 323,081 B).Traps recorded in
research/ubiquiti-edgerouter-poe-census.md:Metworking interface: (3) 10/100/1000 RJ45 ports(Ubiquiti's typo) and hides the other two ports in itsPoE interfacerow — reading that row alone models a three-port router.12 W/combined 50 Wrows on that PDF sit under the ER-X-SFP heading; applying them to the ER-X would invent a 50 W budget.dl.ui.com/datasheets/ER-X.pdf,dl.ui.com/qig/er-x/,dl.ubnt.com/datasheets/edgerouterx/ER-X_DS.pdf,.../EdgeRouter_4_DS.pdfand.../EdgeRouter_X_SFP_DS.pdfall answer 200 with the 609,911-byte tech-specs front page — so a 200 proves nothing on that host in either direction (the ER-X has a datasheet, the ER-4 does not).One thing this pass found and did not fix:
er-4.jsonandedgerouter4.jsonare the same EdgeRouter 4 under two model strings, both citing the same page. The pair is waived intest/known-issues.json(duplicateLabels, a list that can only shrink), so collapsing it decides which model string labs keep — its own increment. This PR corrects theEdgeRouter-4row; the two still agree that the box can neither sink nor source power.Gates.
syntax-check.js449 files OK ·audit-port-types.js"No port contradicts its declared type" ·audit-poe-budget.jssilent PSEs 104 of 405 (2 PSE ports added, 0 added silent; budget-with-no-PSE-port still 0) ·hardware-invariants.test.js26/26 ·poe-inference17/17 ·poe21/21 ·poe-agreement17/17 ·poe-allocation-order26/26 ·run-tests.js370 suites, 12,589 assertions, 0 failed. Registry doc regenerated, no diff.One earlier attempt on this branch declared
poe-pdas a device capability;isPoePd()then gave ports 2–4 a 12.95 W draw each (15 W of phantom PD on a 5 W router), so the token is deliberately absent and the single PD port carries its own figure — the same lesson as #2128.