devices(ubiquiti): three EdgeSwitch PoE rows sourced 0 W and had no console #2251
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!2251
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1120-0322"
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 only. This PR does not answer the UDW-PRO request and is deliberately worded so a merge cannot be read as one: no Ubiquiti-hosted artefact names that SKU (see the issue's own comment thread), so the request stays open on its blocker.
The defect
devices/ubiquiti/es-24-250w.json,es-48-500w.jsonandes-48-750w.jsonmodelled every copper port as a bare 1G ethernet jack: noconnector, nospeedCaps, nopoeOut, nopoeblock, and nosourceUrlat all. So:show power inlinewith 0 PSE ports - an AP onPort 5got no power from a box whose own page prints "Total PoE available: 250W" / "500W";What the vendor pages say (read 2026-11-20)
Per-port ceiling on all three is
PoE+: 34.2W(802.3at Type 2, 50-57V); max draw excluding PoE is 30W / 64W / 64W.The 750 W model is modelled
budgetUnknown, not 750 W. Its page printsPower supply: AC/DC, internal, 750WandMax. power consumption: Includes PoE output: 750W; Excludes PoE output: 64W, and noTotal PoE availablerow - unlike its 500 W sibling. The arithmetic ceiling for PDs would be 750 - 64 = 686 W, and that subtraction is ours, not Ubiquiti's, so the ports and their 802.3at class are modelled and the budget is left explicitly unknown: the same call already recorded forES-24-500W. If a maintainer prefers the derived 686 W, the two printed rows are in the file'spoe.note.Also here
es-16-150w.json: its page states(16) 10/100/1000 Mbps RJ45 ports, but the ports declared 1G/100M - the 10M rung is added, the same fix #2249 made across the ECS family. Its 150 W budget is not re-sourced by this pass: that page prints a 150 W PSU and a 150 W max consumption and no total-PoE row, so the figure is still the SKU name's, as the file's notes now state.10/100/1000on the 48-750W and the 16-150W,GbE(1G/100M) on the 24-250W and 48-500W,10G/1Gon the SFP+ cages.Gates
Sources:
https://techspecs.ui.com/uisp/wired/es-24-250w(583,341 B),.../es-48-500w(583,292 B),.../es-48-750w(582,768 B),.../es-16-150w(574,980 B) - all HTTP 200, server-rendered#product-attribute-specs-table, and none the 609,911 B techspecs front page that this host serves for a slug it does not have.ES-24-250W, ES-48-500W and ES-48-750W modelled every copper port as a plain 1G ethernet jack: no connector, no poeOut, no budget. A 48-port PoE+ switch therefore refused power to anything cabled to it, and the serial console each page prints was missing from the faceplate. Read from each model's own tech-spec table (uisp/wired/<model>): - (24)/(48) PoE/PoE+ ports, 34.2 W per port by PSE, 24V passive on the same jacks; - "Total PoE available" 250W (24-250W) and 500W (48-500W); - 48-750W prints no total-PoE row at all - only a 750 W PSU and 64 W max draw excluding PoE - so it is modelled budgetUnknown, the same call already made for ES-24-500W; - (1) RJ45 serial console; - ES-16-150W gains the 10M rung its page states as 10/100/1000.