ubiquiti: give the UDW its published 420 W PoE budget and 10M speed cap (#130 follow-up) #1979
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!1979
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1118-1126"
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 Pro is still unpublished).
While re-checking the fallback this issue names, I found the fallback itself was wrong: #130's thread and
docs/DEVICE_REGISTRY.mdboth describedevices/ubiquiti/udw.jsonas carrying "a 420 W budget", and it did not. The spec had 12 PSE ports and nopoe.budgetW, soshow power inlineon a UDW printsWhat the vendor actually publishes
Read today, crawler UA, Ubiquiti-hosted only:
dl.ui.com/ds/udw_ds.pdf§PoE interfaceThe PDF text layer corroborates the port census verbatim - "(17) LAN: GbE RJ45 ports", "(1) WAN: 2.5 GbE RJ45 port", "(1) LAN: 10G SFP+ port", "(1) WAN: 10G SFP+ port", "(4) PoE ... (4) PoE+ ... (4) PoE++ ...", "Max. power consumption 532W" with the two 550 W PSUs - and the 420 W budget is on the spec page only, which is why the budget was missing.
What this changes
devices/ubiquiti/udw.json:"poe": {"budgetW": 420, "sourceUrl": "https://techspecs.ui.com/unifi/cloud-gateways/udw"}-Devicenow resolvespoeBudget = 420,poeBudgetSource = 'research', with 12 PSE ports;10Mto the 17 GbE ports'speedCaps(1G/100M/10Mis what the page prints; the spec said1G/100M);No port, class or budget is invented: the 12 PoE ports and their 4/4/4 split are the datasheet's, the 420 W is the spec page's, and nothing was inferred from the Pro (which still has no vendor page, datasheet, FCC grant or store listing).
Gates
node scripts/syntax-check.js- 414 files, OKnode scripts/audit-port-types.js- no port contradicts its declared typenode scripts/run-tests.js- 341 suites, 11,852 assertions, 0 failed (includeshardware-invariants,catalogue-hygiene,import-devices-capabilities)node scripts/regen-registry-doc.js- registry current, 2,356 models, no doc change