devices(ubiquiti): UCG-Ultra and UDM-Pro accept no PoE, so their copper ports are not PDs #2124
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!2124
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-0852"
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.
isPoePd()matchesunifiinmodel + ' ' + label, so every RJ45 socket on a UniFi gatewaythat does not declare its own
poeInwas filled in as a 12.95 W 802.3af powered device. Twogateway rows in
devices/ubiquiti/were still in that state; the UXG family was cleared lastpass (#2121).
devices/ubiquiti/UCG-Ultra.jsondevices/ubiquiti/UDM-Pro.jsonMeasured through the engine, not by hand:
new Device('x', spec)and summinginterfaces.hardware.poeInonorigin/mainversus this branch.What the vendor says
UCG-Ultra —
https://techspecs.ui.com/unifi/cloud-gateways/ucg-ultra(HTTP 200, 657,109 B):Port Layout
(4) 1 GbE & (1) 2.5 GbE, Max. WAN Port Count 4, Max. Power Consumption 6.2 W,Power Method USB type C (5V DC/3A), Power Supply
USB type C (5V DC/3A) (Adapter included).Zero occurrences of
PoEor802.3in the document.https://store.ui.com/us/en/products/ucg-ultra(200, 550,854 B):PoE Supportflag Empty,PoE Budgetflag Empty,Max. PoE Wattage per Port by PSEflag Empty.UDM-Pro —
https://techspecs.ui.com/unifi/cloud-gateways/udm-pro(200, 676,527 B):Port Layout
(9) 1 GbE & (2) 10G SFP+, Max. Power Consumption 33 W, Power Method(1) Universal AC input, 100-240V AC, 50/60 Hz+(1) USP-RPS DC input, Power SupplyAC/DC, internal, 50W. Zero occurrences ofPoEor802.3.https://store.ui.com/us/en/products/udm-pro(200, 600,589 B):PoE Support,PoE BudgetandMax. PoE Wattage per Port by PSEall flag Empty.So the watts were not merely unverified, they were impossible: a 6.2 W USB-C console and a 50 W
AC/DC console, neither with a PSE, each "receiving" more power over copper than it can consume.
Traps recorded
ucg-ultra's payload containsPower Method = PoE / IEEE 802.3afand copy for a "PoE Integrated AC Adapter" and a"PoE-powered 5G RedCap antenna". Those are cross-sell
SpecificationEntityblocks for otherSKUs; the entries that belong to this product are the ones carrying the
Emptyflags above.Reading the first
PoEstring on the page would have made this console a PD for real.https://dl.ui.com/ds/ucg-ultra.pdfand.../ucg-ultra_ds.pdfboth answer 302 ->https://techspecs.ui.com- the same silentfallback already recorded for
uxg-fiber, not a redirect to a PDF.devices/ubiquiti/UDM-Pro.jsoncarried twosourceUrlkeys; JSON kept the last(
https://dl.ui.com/ds/udm-pro.pdf), so the row was not uncited, but the duplicate is gone.Gates
Port counts and speeds are untouched: 5x (1x 2.5G + 4x 1G) and 9x 1G + 2x 10G SFP+ stand as
before, each matching the vendor Port Layout row quoted above.
Driving request: the UDW-PRO asked for in issue 130 still has no Ubiquiti source at all, so no
dream-wall Pro row is added here and issue 130 stays open.
isPoePd() matches 'unifi' in the model+label, so every silent copper port on a UniFi gateway became a 12.95 W 802.3af draw. That put 64.75 W of phantom load on a 6.2 W UCG-Ultra and 116.55 W on a UDM-Pro whose own supply is 50 W AC/DC. Both rows now say poeIn: false on every RJ45 socket, cited to the vendor's own pages: techspecs.ui.com/unifi/cloud-gateways/{ucg-ultra,udm-pro} (Power Method USB-C 5V/3A and Universal AC + USP-RPS DC respectively, zero PoE rows in the whole document) and the matching store rows (PoE Support / PoE Budget / Max. PoE Wattage per Port by PSE all flagged Empty). UDM-Pro also carried a duplicate sourceUrl key; collapsed. Refs #130.Red classification: real failing suite, not superseded, not stale. (#2124, head
6534489b, base59a45b53)CONFLICT (add/add), no files main already carries. It is not a superseded branch.Failure (reproduced locally on
6534489balone, node 26):npm test→ 367 suites, 12,347 passed, 10 failed in five suites:Root cause.
UCG-Ultrais the canonical powered-device fixture in this repo, and this PR makes every one of its portspoeIn: false(correctly —isPoePd()had been inventing 12.95 W per silent port on a 6.2 W USB-C box). The fixture now has no PoE draw, so the budget/denial/flow scenarios have nothing to power:test/poe.test.js:21const PD = 'UCG-Ultra';test/poe-allocation-order.test.js:29sametest/flow.test.js:259const PD = 'UCG-Ultra';test/show-power-inline.test.js:46non-plain case isUCG-Ultratest/ui-render.test.js:182,212PoE render fixtures areUCG-UltraNeeds a decision, not a rebase. The branch is right about the hardware and the tests are right about the engine behaviour; the fixture has to move to a device the catalogue still records as PoE-fed (there are
"poeIn": trueentries underdevices/mikrotik/, plus anycapabilities: ["poe-pd"]device). Rewriting fivetest/files is outside my remit (I never edittest/as my own contribution), and picking a replacement PD changes what those suites assert, so it is a source decision.Ask: either the catalogue loop rebases this branch and repoints the five fixtures at a genuine PD (keeping the vendor facts), or Jay says the PoE-PD inference should be keyed on something other than
UCG-Ultra. Until then #2124 stays unmerged: it has a red head SHA.Surgery re-check after four merges (2026-11-19 09:4xZ) — still red, and the decision is now one-sided.
Head unchanged at
6534489b, now 7 behind main. Merged it onto current main locally (clean, no conflicts) and re-ran the full suite: 368 suites, 12,424 assertions, 10 failed — byte-for-byte the same ten failures inpoe,poe-allocation-order,flow,show-power-inline,ui-renderas at 09:16Z. The three PRs that landed meanwhile (#2128, #2126, #2127) do not touch them.docs/plans/poe-pd-inference.mdlanded as9ac4fccb(#2129) since my last comment, and it answers the question I escalated: it measuresUCG-Ultraat 0 PSE / 5 PD → 64.75 W fromengine/media.js:1104-1107promoting a device-levelisPoePd()claim to every copper port, with no device-shape gate and nopoeInDeclaredcounterpart topoeOutDeclared. So this PR's JSON is right and the fixtures are right; the engine inference is what must change, and the plan already names the files (media.js:1086-1116,device.js:1433/:1651-1658,simulator.js:2555-2612,web/faceplate.js:630,web/app.js:2202,docs/DEVICE_SCHEMA.md:204,test/poe.test.js:21).Not merging it, per the red-PR rule — not superseded (merges cleanly, no add/add), not staleness. Two options and both are source changes, so neither is mine:
test/poe.test.js:21and four siblings) to a genuine PD and let the inferred ports stand.Needs Jay's decision: (1) or (2). Option 1 is the plan's own conclusion and fixes 448 devices' worth of inferred ports; option 2 unblocks this PR in one commit and leaves the guess in place.
The catalogue change was right; five suites had been using
UCG-Ultraas the powered far end (poe,poe-allocation-order,flow,show-power-inline,ui-render), so removing the phantom 12.95 W left them with no PD at all. Swapped that fixture for a genuine 802.3af PD (MikroTik SXTsq 5 ac, 12.95 W, single coppereth1, L3) - same arithmetic, same assertions.poe.test.jsnow also asserts the point of the PR: both gateways declarepoeIn: false, neither port enters the allocation table, and the PSE spends 0 W on them.Full suite: 367 suites, 12,470 assertions, 0 failed.
node scripts/syntax-check.js: 446 files OK.e57785d92e29668edbec