Edgecore AS4610: four 1G access switches, 1650 W of PoE that is not 48 x 30 W, and a capacity figure its own datasheet doubles #1555
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!1555
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1115-2226"
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?
Adds the Edgecore AS4610 family (bare-metal 1G access switches, ONIE, no NOS) to
devices/edgecore/: AS4610-30T, AS4610-30P, AS4610-54T, AS4610-54P - 4 specs.What the datasheets say
All four: BCM56340 Helix4, dual-core ARM Cortex-A9 1 GHz, 2 GB DDR3 ECC, 8 MB SPI flash, 4 MB shared buffer, 96 K MACs, 4 K VLANs, 1x 1G RJ-45 management port, serial console, 2x 20G QSFP+ stacking cages, 1RU, two hot-swap AC PSUs.
Discrepancies stated, not smoothed over
fabricnote on each spec carries the conflict. The 30T/30P 104 Gbps figure agrees across both documents; the model datasheets print 95 Mpps where the series table prints 156 Mpps, so only the capacity is recorded.poenote says so; every copper port is modelled at 30 W because the datasheet never enumerates which eight ports are the 60 W UPoE ones.SPEEDShas no 20G), and calling them 40G QSFP+ or 10G would state a rate no datasheet gives. They are described innotes, the declared port list is 24/48 + 4 SFP+ + mgmt + console.Sources (per spec:
sourceUrl= product page; PDFs named innotes,poe.sourceUrl,fabric.note)Validation
node scripts/import-devices.js --apply(isolatedPF_INCOMING): 4 specs, 0 rejected, 0 duplicates, 0 capability losses. Two warnings per PoE model (802.3af/802.3atare descriptive tokens the engine does not implement - kept as declared, same as every other PoE switch in the catalogue).node scripts/audit-port-types.js- exit 0, "No port contradicts its declared type."node scripts/audit-devices.js- "No hard defects."node scripts/syntax-check.js- 325 files, all OK.node --test test/importer-roundtrip.test.js test/catalogue-hygiene.test.js test/import-devices-capabilities.test.js test/faceplate-catalogue.test.js test/doc-catalog-counts.test.js test/poe-agreement.test.js- all pass.node scripts/regen-registry-doc.js- switch count 298 -> 302.Unverifiable / left out: which eight numbered ports carry UPoE (datasheet shows a block, not numbers); forwarding rate where the two documents disagree (95 vs 156 Mpps, 190 vs 191 Mpps); console flavour varies by airflow variant (RJ-45 or micro-USB), so both are described rather than one declared.
6ad40daf798023164d9dRebased onto main (
d013e7c2) — the only conflict was docs/DEVICE_REGISTRY.md, which is generated. I took main's copy and regenerated withnode scripts/regen-registry-doc.jsrather than hand-merging: 2,074 -> 2,078 models, switch 306 -> 310 (the four AS4610s). Nothing hand-edited. Verified: doc-catalog-counts 24, catalogue-hygiene 25, faceplate-catalogue 14, device-aliases 13, missing-devices 66, apply-research 10, import-devices-capabilities 29 — all passing, 0 failed. Head is now8023164d, mergeable. No CI run has been dispatched for it yet.This branch conflicts with
main, so it was not rebased:A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.
8023164d9ddd4afed659