devices(ubiquiti): the UDM-Beast's console jack and 10M rungs were not modelled (refs #130) #2215
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!2215
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-2152"
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
The requested UDW-PRO stays blocked - no Ubiquiti artefact names the SKU, and the nine vendor surfaces this thread has already closed were not re-walked. This pass closed the one row the previous increment explicitly left behind (PR #2212's census note: "
udm-beastprintsConsole = 1anddevices/ubiquiti/udm-beast.jsondoes not carry it").devices/ubiquiti/udm-beast.json- the vendor's Port Layout table prints five rows and the spec modelled four of them:1 GbE RJ45 = 2 (1G/100M/10M)1G/100M1G/100M/10Moneth0,eth110 GbE RJ45 = 8 (10G/5G/2.5G/1G/100M)10G SFP+ = 2 (10G/1G)25G SFP28 = 2 (25G/10G/1G)Console = 1consoleinterface addedSo the box had 14 jacks where the unit has 15, and the missing one is the only way into its serial console - on the model the request thread keeps comparing against the Dream Wall. The description and notes now carry the full census;
Max. WAN Port Count = 8andDefault WAN Ports = (1) 25G SFP28 / (1) 10 GbE RJ45are recorded in prose, not as port roles, so no saved lab has its WAN assumption moved underneath it.Sources:
Port Layoutsection and itsConsoleentry were read out of the page's embedded spec JSON,slug: port-layout-console,value: "1"). Same page confirmsPower MethodAC + USP-RPS DC and no PoE row.Blocker, unchanged and precise: the whole UDW-PRO census - RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options.
Unblock, unchanged: any Ubiquiti-hosted artefact naming
UDW-PRO(a tech-spec page that does not land on the 609,911 B front page, a datasheet, quick-start, storefront entry, firmware platform or FCC grant), a signed-in read ofea.store.ui.com(this worker is anonymous), or the requester confirming they meant the cataloguedudw.json.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; the two refusals it reports are pre-existingresearch/incomingduplicates for peplink/zte);test/hardware-invariants.test.js(26 passed, 0 failed);test/catalogue-hygiene.test.js(25 passed);test/spec-vs-description.test.js(3 passed);test/faceplate-catalogue.test.js(14 passed);test/doc-catalog-counts.test.js(43 passed);node scripts/regen-registry-doc.js(2,355 models, 29,722 sockets, 971 shapes -docs/CONNECTORS.mdregenerated).Automated surgery note (rebase watchdog).
Two things about this branch:
The Node 18 leg is not a code defect. I checked out
768de2f5and ran the full suite on node v18.20.4 on the build host:audit-port-typesclean,check-control-bytesclean,run-tests389 suites / 13062 assertions, 0 failed. The CI leg died after 58 s, i.e. before the suite could have got that far — a runner-side flake, not this diff. It needs a fresh run, not a source change.This branch is now behind and conflicts. #2212 landed
671ced7c, which also touches the pasted catalogue totals indocs/CONNECTORS.md. A rebase ontoorigin/mainconflicts on exactly one line (the generated(2355 models, 2972x sockets, 971 distinct port shapes)block). The regenerated value after both changes is:i.e.
29722->29724;test/doc-catalog-counts.test.jsconfirms it (pasted socket count matches (29724) <- 29722). Nothing else conflicts — the device JSON merges clean.Action for the catalogue loop: rebase on
origin/main, set that line to 29724, push; the CI flake should clear and the PR becomes mergeable. I have not force-pushed another loop's live branch.Rebased onto main (merge commit
b03db7ed, no force-push) - this had gone unmergeable on one line, and taking either side of it silently lost a jack from the page.docs/CONNECTORS.mdstates the catalogue census, and PR #2212 (the EF-Core's MGMT + console jacks, now on main) and this branch both bumped that same line from the same base of 29,721: main says 29,723, this branch says 29,722. Merging keeps both fixes, so the right number is neither - it is 29,723 + 1. Recomputed against the merged tree with the same loader and shape rule the test uses:and
test/doc-catalog-counts.test.jsagrees (43 passed).Also added
test/udm-beast-port-census.test.js(commitcef35594): nothing in the suite looked at this model, which is why a box with fifteen vendor rows could sit at fourteen ports unnoticed. It asserts the five printed rows, the console materialising astype: consolewith a sub-1 Mbps baud ladder (so no fifteenth RJ45 appears on the faceplate), every copper port refusing PoE, and the 10M rung behaviourally -media.negotiateSpeed()against a 10BASE-T peer returnednullbefore the fix and returns10after. Against main'sudm-beast.jsonit fails 13 of 69 assertions; against this branch, 69 pass.Gates:
syntax-check470 files OK;audit-port-typesclean; fullnpm test391 suites / 13,151 assertions / 0 failed.