devices(ubiquiti): the EF-Core's MGMT and console jacks were not modelled (refs #130) #2212

Merged
jaylouisw merged 1 commit from catalogue/1119-2122 into main 2026-11-19 22:09:02 +00:00
Owner

refs #130

The requested UDW-PRO stays blocked (no vendor artefact; nine surfaces already closed on the thread, none re-walked today). This pass took the family the thread has been circling - Ubiquiti's own cloud-gateway index - and ran its Port Layout tables against the specs, one page per card.

devices/ubiquiti/ef-core.json was the only row that contradicted its own page. The vendor prints six Port Layout rows:

  • 1 GbE RJ45 = 2 (1G/100M/10M)
  • 10 GbE RJ45 = 8 (10G/5G/2.5G/1G/100M)
  • 25G SFP28 = 4 (25G/10G/1G)
  • 100G QSFP28 = 4 (100G/40G)
  • MGMT = 1 (1G/100M/10M)
  • Console = 1

The spec modelled the middle four only: 18 jacks for a 20-jack 1U firewall. The MGMT socket is a separate front-panel RJ45, not one of the two 1 GbE data ports - its own row, its own rate set, and the same page's Management section reads "Ethernet" beside the 1.3" LCM touchscreen. Added as mgmt (rj45, 1G/100M/10M) and console; the two 1 GbE data ports also gain the 10M rung the vendor prints for them.

Sources (all 200 at their own URL, so none is the 609,911 B not-found page this host serves for an unknown slug):

Census recorded in research/ubiquiti-cloud-gateway-port-layout-census.md (all sixteen products, verbatim rows, page bytes).

Not claimed fixed here: udm-beast prints Console = 1 and its spec does not carry one - one device per increment, so it is recorded as the next row in that census rather than folded into this diff.

Gates: node scripts/syntax-check.js (468 files, all OK); node scripts/audit-port-types.js (no port contradicts its declared type); node scripts/import-devices.js dry run (no new refusal); hardware-invariants + catalogue-hygiene + faceplate-catalogue (26 passed, 0 failed); node scripts/regen-registry-doc.js (2,355 models, 29,723 sockets, 971 shapes - docs/CONNECTORS.md regenerated).

refs #130 The requested UDW-PRO stays blocked (no vendor artefact; nine surfaces already closed on the thread, none re-walked today). This pass took the family the thread has been circling - Ubiquiti's own cloud-gateway index - and ran its Port Layout tables against the specs, one page per card. `devices/ubiquiti/ef-core.json` was the only row that contradicted its own page. The vendor prints six Port Layout rows: - `1 GbE RJ45 = 2 (1G/100M/10M)` - `10 GbE RJ45 = 8 (10G/5G/2.5G/1G/100M)` - `25G SFP28 = 4 (25G/10G/1G)` - `100G QSFP28 = 4 (100G/40G)` - `MGMT = 1 (1G/100M/10M)` - `Console = 1` The spec modelled the middle four only: 18 jacks for a 20-jack 1U firewall. The MGMT socket is a separate front-panel RJ45, not one of the two 1 GbE data ports - its own row, its own rate set, and the same page's Management section reads "Ethernet" beside the 1.3" LCM touchscreen. Added as `mgmt` (rj45, 1G/100M/10M) and `console`; the two 1 GbE data ports also gain the 10M rung the vendor prints for them. Sources (all 200 at their own URL, so none is the 609,911 B not-found page this host serves for an unknown slug): - https://techspecs.ui.com/unifi/cloud-gateways/ef-core - 674,322 B, read 2026-11-19 - https://techspecs.ui.com/unifi/cloud-gateways - 610,412 B, the sixteen-card index the census walks Census recorded in `research/ubiquiti-cloud-gateway-port-layout-census.md` (all sixteen products, verbatim rows, page bytes). Not claimed fixed here: `udm-beast` prints `Console = 1` and its spec does not carry one - one device per increment, so it is recorded as the next row in that census rather than folded into this diff. Gates: `node scripts/syntax-check.js` (468 files, all OK); `node scripts/audit-port-types.js` (no port contradicts its declared type); `node scripts/import-devices.js` dry run (no new refusal); hardware-invariants + catalogue-hygiene + faceplate-catalogue (26 passed, 0 failed); `node scripts/regen-registry-doc.js` (2,355 models, 29,723 sockets, 971 shapes - docs/CONNECTORS.md regenerated).
devices(ubiquiti): the EF-Core's MGMT and console jacks were not modelled (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 17s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 11s
CI / Server smoke test (pull_request) Successful in 12s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Test (Node 20) (pull_request) Successful in 1m6s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Docker build (pull_request) Successful in 27s
CI / Arm auto-merge (pull_request) Successful in 4s
0cb3665d4e
Port Layout on the vendor page prints six rows for this 1U firewall, including MGMT = 1 (1G/100M/10M) and Console = 1; the spec carried four, so a 20-jack unit was a 18-jack row. Both 1 GbE data ports also gain the 10M rung the same row prints.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 21:44:57 +00:00
jaylouisw deleted branch catalogue/1119-2122 2026-11-19 22:09:03 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!2212
No description provided.