edgecore: the ECS4120 access-switch family, five members from the R16 datasheet #1700

Merged
jaylouisw merged 1 commit from catalogue/1116-1755 into main 2026-11-16 18:06:05 +00:00
Owner

Adds Edgecore's own ECS4120 L2+/L3 Lite access switches, which the catalogue did not have at all (only the bare-metal AS-series was modelled).

Port census, from the ECS4120 Series datasheet R16 (EC-DS-0324-R16, 2024-03-12)

https://www.edge-core.com/download/ecs4120-series-ds-r16/?wpdmdl=1696

model ports uplinks capacity forwarding power
ECS4120-28T 24x 10/100/1000BASE-T 4x 10G SFP+ 128 Gbps 95 Mpps 20 W, fanless
ECS4120-52T 48x 10/100/1000BASE-T 4x 10G SFP+ 176 Gbps 130 Mpps 60 W
ECS4120-28Fv2 20x 100/1000BASE-X SFP + 4 combo 4x 10G SFP+ 128 Gbps 95 Mpps 60 W, AC+DC
ECS4120-28Fv2-I same, -10 to 65 C 4x 10G SFP+ 128 Gbps 95 Mpps 60 W, dying gasp
ECS4120-28P 24x 1G PoE+ (30 W a port) 4x 10G SFP+ 128 Gbps 95 Mpps 370 W budget

Both fibre members also carry a 1x GE RJ-45 out-of-band management port and an RJ-45 console; the two copper members have a console and no OOB port (the R16 table prints No for that row).

Where the numbers come from, and what is not from R16

  • ECS4120-28P is not in R16. It is the family's PoE member and it completed EOL on 1 January 2019. Its 30 W a port and 370 W budget are stated on the product page (https://www.edge-core.com/product/ecs4120-28p/, "The ECS4120-28P can provide up to 30 Watts of power ... The PoE Power Budget is 370W") and repeated verbatim in the Web Management Guide R03 (https://www.edge-core.com/_upload/images/ECS4120-EC_WG-R03_2019-02-20.pdf); its 128 Gbps / 95 Mpps come from datasheet R10 (https://www.edge-core.com/_upload/images/ECS4120_series_DS_R10_20200108.pdf). 24 ports at 30 W is 720 W, so the 370 W budget is the binding limit - the spec says that in poe.note rather than pretending each port can run Class 4 at once.
  • No product page exists for the 52T (/product/ecs4120-52t/ answers 404), so the series datasheet is its only vendor source; the spec notes that.
  • Fibre port numbering. The CLI reference (https://www.edge-core.com/wp-content/uploads/2025/12/ECS4120-Series_CLI-R06_20251014.pdf) fixes both ends: "Ports 1-24 (1000BASE SFP) support 1000sfp or 100fx" and "Ports 25-28 (10G SFP+) support 1000sfp". The four combo positions are written as 21-24 from the datasheet's port order (20 SFP, then 4 combo). Edgecore prints no full 28F port map, so that placement is the one part of the census read from order, and notes says so instead of implying a printed list.
  • Firmware/metadata. V1.2.2.30 is the current image on the product download list, with u-boot v2.0.0.2 as a separate upgrade; flash 256 MB, DRAM 512 MB, MAC table 16 K, jumbo 9 KB, DHCP server 8 pools / 512 addresses, static routes plus RIP v1/v2 - which is what l3-forward and dhcp-server rest on. No member has NAT, and none declares it.

Validation

  • node scripts/syntax-check.js - 356 files, OK
  • node scripts/audit-port-types.js - exit 0, "No port contradicts its declared type"
  • test/hardware-invariants.test.js 26/26, spec-vs-description 3/3, catalogue-hygiene 25/25, faceplate-catalogue 14/14
  • importer dry run over the five specs (--all): 5 scanned, 5 duplicates (already written), 0 rejected
  • doc-catalog-counts 43/43, doc-citations 11/11, canonical-urls 52/52
  • node scripts/regen-registry-doc.js: 2,252 -> 2,257 models, 898 port shapes

Unverifiable / left alone

  • Whether Edgecore sells a current PoE member of this family: R16 lists none, and the only PoE datasheet is the 2019-EOL 28P. No spec asserts a current PoE ECS4120.
  • The 28P's 802.3af-only load figure: not published, so only the 30 W (802.3at) class is modelled.
Adds Edgecore's own ECS4120 L2+/L3 Lite access switches, which the catalogue did not have at all (only the bare-metal AS-series was modelled). ## Port census, from the ECS4120 Series datasheet R16 (EC-DS-0324-R16, 2024-03-12) https://www.edge-core.com/download/ecs4120-series-ds-r16/?wpdmdl=1696 | model | ports | uplinks | capacity | forwarding | power | |---|---|---|---|---|---| | ECS4120-28T | 24x 10/100/1000BASE-T | 4x 10G SFP+ | 128 Gbps | 95 Mpps | 20 W, fanless | | ECS4120-52T | 48x 10/100/1000BASE-T | 4x 10G SFP+ | 176 Gbps | 130 Mpps | 60 W | | ECS4120-28Fv2 | 20x 100/1000BASE-X SFP + 4 combo | 4x 10G SFP+ | 128 Gbps | 95 Mpps | 60 W, AC+DC | | ECS4120-28Fv2-I | same, -10 to 65 C | 4x 10G SFP+ | 128 Gbps | 95 Mpps | 60 W, dying gasp | | ECS4120-28P | 24x 1G PoE+ (30 W a port) | 4x 10G SFP+ | 128 Gbps | 95 Mpps | 370 W budget | Both fibre members also carry a 1x GE RJ-45 out-of-band management port and an RJ-45 console; the two copper members have a console and no OOB port (the R16 table prints No for that row). ## Where the numbers come from, and what is not from R16 - **ECS4120-28P is not in R16.** It is the family's PoE member and it completed EOL on 1 January 2019. Its 30 W a port and 370 W budget are stated on the product page (https://www.edge-core.com/product/ecs4120-28p/, "The ECS4120-28P can provide up to 30 Watts of power ... The PoE Power Budget is 370W") and repeated verbatim in the Web Management Guide R03 (https://www.edge-core.com/_upload/images/ECS4120-EC_WG-R03_2019-02-20.pdf); its 128 Gbps / 95 Mpps come from datasheet R10 (https://www.edge-core.com/_upload/images/ECS4120_series_DS_R10_20200108.pdf). 24 ports at 30 W is 720 W, so the 370 W budget is the binding limit - the spec says that in `poe.note` rather than pretending each port can run Class 4 at once. - **No product page exists for the 52T** (/product/ecs4120-52t/ answers 404), so the series datasheet is its only vendor source; the spec notes that. - **Fibre port numbering.** The CLI reference (https://www.edge-core.com/wp-content/uploads/2025/12/ECS4120-Series_CLI-R06_20251014.pdf) fixes both ends: "Ports 1-24 (1000BASE SFP) support 1000sfp or 100fx" and "Ports 25-28 (10G SFP+) support 1000sfp". The four combo positions are written as 21-24 from the datasheet's port order (20 SFP, then 4 combo). Edgecore prints no full 28F port map, so that placement is the one part of the census read from order, and `notes` says so instead of implying a printed list. - **Firmware/metadata.** V1.2.2.30 is the current image on the product download list, with u-boot v2.0.0.2 as a separate upgrade; flash 256 MB, DRAM 512 MB, MAC table 16 K, jumbo 9 KB, DHCP server 8 pools / 512 addresses, static routes plus RIP v1/v2 - which is what `l3-forward` and `dhcp-server` rest on. No member has NAT, and none declares it. ## Validation - `node scripts/syntax-check.js` - 356 files, OK - `node scripts/audit-port-types.js` - exit 0, "No port contradicts its declared type" - `test/hardware-invariants.test.js` 26/26, `spec-vs-description` 3/3, `catalogue-hygiene` 25/25, `faceplate-catalogue` 14/14 - importer dry run over the five specs (`--all`): 5 scanned, 5 duplicates (already written), **0 rejected** - `doc-catalog-counts` 43/43, `doc-citations` 11/11, `canonical-urls` 52/52 - `node scripts/regen-registry-doc.js`: 2,252 -> 2,257 models, 898 port shapes ## Unverifiable / left alone - Whether Edgecore sells a current PoE member of this family: R16 lists none, and the only PoE datasheet is the 2019-EOL 28P. No spec asserts a current PoE ECS4120. - The 28P's 802.3af-only load figure: not published, so only the 30 W (802.3at) class is modelled.
edgecore: the ECS4120 access-switch family, five members from the R16 datasheet
All checks were successful
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 17s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 20) (pull_request) Successful in 59s
CI / Test (Node 18) (pull_request) Successful in 1m4s
CI / Test (Node 22) (pull_request) Successful in 1m4s
3a05e3cfb6
The catalogue had Edgecore's bare-metal data-centre boxes (AS4610, AS7726,
AS9716) and nothing from the ECS line - the vendor's own-software L2+/L3 Lite
access switches that the ECS4120 series belongs to.

Census from the ECS4120 Series datasheet R16 (EC-DS-0324-R16, 2024-03-12),
which prints a per-model port table:

  ECS4120-28T     24x 1G RJ-45, 4x 10G SFP+, 128 Gbps, 95 Mpps, fanless, 20 W
  ECS4120-52T     48x 1G RJ-45, 4x 10G SFP+, 176 Gbps, 130 Mpps, 60 W
  ECS4120-28Fv2   20x 100/1000 SFP, 4 combo, 4x 10G SFP+, 1x GE OOB, DC, 0-50 C
  ECS4120-28Fv2-I same, -10 to 65 C, dying gasp
  ECS4120-28P     24x 1G RJ-45 all PoE+ at 30 W a port on a 370 W budget,
                  4x 10G SFP+ - the PoE member, EOL 1 January 2019

Nothing is guessed. The 28P is not in R16; its 370 W budget and 30 W a port come
from its product page and the Web Management Guide R03, and its 128 Gbps /
95 Mpps from datasheet R10, all cited in the spec notes. Port numbering on the
fibre members is fixed at both ends by the CLI reference ("Ports 1-24 (1000BASE
SFP)", "Ports 25-28 (10G SFP+)"); the four combo positions are placed at 21-24
from the datasheet port order, and the spec says so rather than implying the
vendor printed a 28F port map.

Firmware facts recorded: V1.2.2.30 is the current image with u-boot v2.0.0.2 as
a separate upgrade; flash 256 MB, DRAM 512 MB, MAC 16 K, jumbo 9 KB, DHCP
server 8 pools / 512 addresses, static routes plus RIP v1/v2, which is what the
l3-forward and dhcp-server capabilities rest on. No member has NAT.

Gates: syntax-check 356 files OK; audit-port-types exit 0 ("No port contradicts
its declared type"); hardware-invariants 26/26, spec-vs-description 3/3,
catalogue-hygiene 25/25, faceplate-catalogue 14/14; importer dry run over the
five specs: 5 scanned, 0 rejected; doc-catalog-counts 43/43, doc-citations 11/11,
canonical-urls 52/52.
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-16 18:05:57 +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!1700
No description provided.