devices(ubiquiti): one UDM-Pro row with two 10G cages, not a 10G copper port (#130) #2093
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!2093
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-0452"
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 - this does not close it.
The catalogue bug, one device.
devices/ubiquiti/described the UDM-Pro twice and both copies were wrong about the 10G side.UDM-Pro.json(the file holding the model string) modelled the second cage as a bareethernet 10Gport with no connector: one cage, plus a 10G port nothing can seat in - a guessed port of exactly the kind the evidence rule forbids.unifi-dream-machine-pro.jsonhad the right count but under model"UniFi Dream Machine Pro"(a product name), categoryhost, and the engine'shostcapability, which means an end device that terminates packets (engine/device.js) rather than a console that hosts apps, on a gateway.Vendor census (read today, text layer + rendered table).
https://dl.ui.com/ds/udm-pro.pdf- HTTP 200, 353,553 B,application/pdf, 2 pages:Networking interface (8) LAN: GbE RJ45 ports/(1) WAN: GbE RJ45 port;SFP+ interface (1) LAN: 10G SFP+/(1) WAN: 10G SFP+; IDS/IPS 3.5 Gbps; max power consumption 33 W; internal 50 W PSU.https://techspecs.ui.com/unifi/cloud-gateways/udm-pro- HTTP 200, 676,527 B: same count as a table,1 GbE RJ45 = 9 (1G/100M/10M)and10G SFP+ = 2 (10G/1G); its Datasheet button points at the same PDF.Result: 9x 1G RJ45 (1 WAN + 8 LAN, speedCaps 10/100/1000), 2x 10G SFP+ cages (connector
sfp+, speedCaps 1000/10000), no PoE.devices/ubiquiti/UDM-Pro.jsonnow models that once, withaliasesfor both spellings so search does not lose the deleted name, andscripts/merge-research.js's inline entry is corrected so regeneration cannot reintroduce the connector-less port.Naming trap recorded for the next pass:
dl.ui.com/ds/udm-pro.pdfis the real datasheet, whiledl.ui.com/ds/udm-pro_ds.pdf- the suffix many other Ubiquiti datasheets use - answers 302 to the techspecs front page. A 302 on a_dspath therefore never proved a datasheet was missing. The same control was applied to the UDW-PRO slugs inresearch/ubiquiti-udw-pro-doc-slug-controls.md(added here, re-measured today:qig/udw/200/6,310 B andqig/udm-pro/200/6,185 B againstqig/udw-pro/302/313 B;udw-pro.pdf302/285 B under five spellings).Gates.
syntax-check.js440 files OK;audit-port-types.js2,356 models / 29,715 ports / 0 offending ports;test/hardware-invariants.test.js26/26;test/device-aliases.test.js13/13;test/faceplate-catalogue.test.js14/14;test/apply-research.test.js10/10;npm test361 suites, 12,381 assertions, 0 failed. Registry regenerated (2,357 -> 2,356 models; Ubiquiti 369 -> 368).Issue 130 stays open and blocked. Nothing in this pull request names a UDW-PRO port, PoE wattage or part number; the Pro remains absent from Ubiquiti's techspecs index, both
dl.ui.comdocument trees, the storefront commerce API and its own firmware platform list. Modelling it from the non-Pro UDW's numbers is the family-sibling error this catalogue has corrected three times.