devices(ubiquiti): three Enterprise Campus PoE rows served 0 W from a 2,150 W chassis #2249
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!2249
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1120-0252"
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?
Does not close #130 — the UDW-PRO blocker is unchanged (see the comment on that issue; no Ubiquiti-hosted artefact names the SKU). This PR repairs the Enterprise Campus PoE family instead, which is what the last pass on #130 recorded as the next job.
The defect
ecs-48-poe.jsonandecs-24s-poe.jsondeclared PoE+++ on 48 and 24 ports and carried nopoe.budgetW. The loader therefore named the budget from the model string, found no wattage, and served 0 W while thedescriptionbeside each claimed 2,150 W and 1,050 W. Same defect class as #2235, #2175 and #2244.Per model
ECS-48-PoE (
devices/ubiquiti/ecs-48-poe.json) — Vendor prints availability as four rows against (2) 1,200 W modules: 200-240 V shared 2,150 W / 100-120 V shared 1,750 W / 200-240 V redundant 950 W / 100-120 V redundant 750 W. 2,150 W modelled, all four conditions inpoe.note. Port layout is three rows (16 x 2.5G, 32 x 10G, 4 x SFP28); no Console and no OOB port on this row, so 52 jacks is the whole box. Both RJ45 banks were missing the 10M rung.ECS-24S-PoE (
devices/ubiquiti/ecs-24s-poe.json) — Six availability rows across two PSU options.budgetWis 1,050 W, the as-shipped (2) 600 W shared figure, matching the convention already inecs-24-poe.json; the page marks the 1,200 W modules "sold separately", so 2,250 W is recorded inpoe.noteas a condition a lab must state, not as the ceiling. Plus: the serial console was absent (31 of 32 jacks - nothing could be cabled to the out-of-band path), the 1G OOB port and both RJ45 banks were missing 10M, and the QSFP28 pair now carries the vendor note "Stacking port only, does not support uplink. Breakout cables are not supported".ECS-24-PoE (
devices/ubiquiti/ecs-24-poe.json) — budget was already correct; 10M rung added to both RJ45 banks, notes added.ECS-48S-PoE (
devices/ubiquiti/ecs-48s-poe.json) — finishing #2244: the 16 x 10G bank was the one bank left without the 10M rung the page prints.All four / phantom PSE. The engine credits every RJ45 jack on a
poe-pseswitch with 15.4 W when the spec is silent, which put a PSE on each row's OOB management port - a port the vendor annotates "OOB Management port only".eth0on both S rows now declarespoeOut: false, which is what makespseabove equal the vendor's own "PoE Ports: 48 / 24" row instead of 49 / 25.Evidence
Every field traces to the vendor's server-rendered spec table, byte counts recorded in each spec's
notes:Port-layout rows are quoted verbatim in the notes; the tooltip annotations ("OOB Management port only", "Stacking port only...", "1,200W power modules sold separately", "802.3bt Type 4, Class 8") are quoted from the page's own spec JSON.
Gates
docs/CONNECTORS.mdregenerated (2,355 models, 29,726 sockets, 973 distinct port shapes);docs/DEVICE_REGISTRY.mdunchanged.f4030557f8bbe25d20f1Rebased onto main (
f86c9a27) and squash-merged as84426ad8. The only conflict was the catalogue totals sentence indocs/CONNECTORS.md, which #2251 had already moved: rather than pick a side,node scripts/regen-registry-doc.jsrewrote it from the merged tree -> 2,355 models, 29,729 sockets, 972 distinct port shapes. Re-ran audit-port-types, check-control-bytes, doc-catalog-counts (43), faceplate-catalogue (14), hardware-invariants (26), poe (21), validation (22) - all green before the force-push; headbbe25d20went 7/7.