catalogue: Peplink EPX — EPX-M8-LW5C1F1 and EPX-M8-LW2C1F1 from the vendor ordering table #1736

Merged
jaylouisw merged 1 commit from catalogue/1116-2125 into main 2026-11-16 21:37:44 +00:00
Owner

Fixes #494

What this adds

Two specs in devices/peplink/, both built from Peplink's own EPX ordering table rather than from the model-level ranges:

model ports modelled slots used
EPX-M8-LW5C1F1 4x 10G SFP+ · 8x 1G RJ45 PoE+ · 15 LTE-A (Cat-6) 7 of 7
EPX-M8-LW2C1F1 4x 10G SFP+ · 8x 1G RJ45 PoE+ · 6 LTE-A (Cat-6) 4 of 7

The census comes straight out of the ordering table and the FlexModule table, and the two agree:

  • EPX-M8-LW5C1F1 Wireless SD-WAN Powerhouse: EPX with LCD Module, 4x 10G SFP+, 8x GE and 15x LTE-A (Worldwide).
  • EPX-M8-LW2C1F1 EPX with LCD Module, 4x 10G SFP+, 8x GE and 6x LTE-A (Worldwide).
  • modules: EXM-4F = 4x SFP+ ports · EXM-8C = 8x 10/100/1000M Ethernet, capable of PoE+ · EXM-3LTEA = 3x LTE-A modems, 300/50 Mbps Cat-6
  • Module Expansion: Yes (7 slots for FlexModule Plus)

1x EXM-4F + 1x EXM-8C + 5x EXM-3LTEA = 7 slots, which is the slot count the tech-spec sheet prints — the decode is self-checking. The LW2 build is the same chassis with two LTE-A modules instead of five.

Discrepancy stated, not smoothed over

The datasheet contradicts itself on PoE, and the port count is the only clean part:

  • rev 2404-v15, EPX-M8 table: PoE Output 8x 802.3at PoE+ Output / 330W PoE+ Power Budget
  • rev EPX-201910-v7, EXM-8C module table: 15W (255W max. with PoE Output) plus footnote ^ The EPX-8M can support a maximum of 2 modules delivering PoE
  • 2020 revision, same module: 15W (105W max. with PoE+ Output)

So the module ceiling (105 W / 255 W) and the chassis ceiling (330 W) are different numbers for the same box. poe.budgetW is recorded as 330 W, the figure the current datasheet prints for the chassis, and all three quoted numbers are in the spec's notes rather than averaged into a fourth.

Deliberately not catalogued yet

EPX-M8-LW1C3F3 (12x 10G SFP+, 24x GE, 3x LTE-A) is named in the same table and is left out on purpose: its three EXM-8C modules give 24 PoE-capable ports, while the chassis row says 8 PoE ports and the v7 footnote says at most 2 PoE modules (16). None of the three statements can be checked against the others, and a guessed PoE split is the kind of array that only surfaces when a lab cables 24 powered devices. Same for the bare EPX-M8 chassis: its ordering row is EPX Base Model, 1x LCD Module and the archived datasheet's "Base Chassis" page lists throughput, power and dimensions but no interfaces at all, so there is nothing to cable to — issue #495's comment records that.

Sources

Gates

  • node scripts/syntax-check.js — 362 files, all OK
  • node scripts/audit-port-types.js — No port contradicts its declared type.
  • node test/hardware-invariants.test.js — 26 passed, 0 failed
  • node test/spec-vs-description.test.js — 3 passed, 0 failed
  • node test/device-aliases.test.js — 13 passed, 0 failed
  • node scripts/import-devices.js (dry run) — neither new spec rejected (the run's two rejects are pre-existing incoming files, unrelated)
  • node scripts/regen-registry-doc.js — 2,329 → 2,331 models, registry doc regenerated, not hand-edited

Punctuation/duplicate gate: EPX-M8-LW5C1F1 and EPX-M8-LW2C1F1 are distinct orderable part numbers with different port censuses, so they are two devices rather than one spelling of the other. The AP-band twins (EPX-M8-LP5C1F1, EPX-M8-LP2C1F1) are not separate specs: identical ports, modem band region only, the same treatment the SDX Pro storage SKUs got.

Fixes #494 ## What this adds Two specs in `devices/peplink/`, both built from Peplink's own EPX ordering table rather than from the model-level ranges: | model | ports modelled | slots used | |---|---|---| | `EPX-M8-LW5C1F1` | 4x 10G SFP+ · 8x 1G RJ45 PoE+ · 15 LTE-A (Cat-6) | 7 of 7 | | `EPX-M8-LW2C1F1` | 4x 10G SFP+ · 8x 1G RJ45 PoE+ · 6 LTE-A (Cat-6) | 4 of 7 | The census comes straight out of the ordering table and the FlexModule table, and the two agree: - `EPX-M8-LW5C1F1 Wireless SD-WAN Powerhouse: EPX with LCD Module, 4x 10G SFP+, 8x GE and 15x LTE-A (Worldwide).` - `EPX-M8-LW2C1F1 EPX with LCD Module, 4x 10G SFP+, 8x GE and 6x LTE-A (Worldwide).` - modules: `EXM-4F` = 4x SFP+ ports · `EXM-8C` = 8x 10/100/1000M Ethernet, capable of PoE+ · `EXM-3LTEA` = 3x LTE-A modems, 300/50 Mbps Cat-6 - `Module Expansion: Yes (7 slots for FlexModule Plus)` 1x EXM-4F + 1x EXM-8C + 5x EXM-3LTEA = 7 slots, which is the slot count the tech-spec sheet prints — the decode is self-checking. The LW2 build is the same chassis with two LTE-A modules instead of five. ## Discrepancy stated, not smoothed over The datasheet contradicts itself on PoE, and the port count is the only clean part: - rev 2404-v15, EPX-M8 table: `PoE Output 8x 802.3at PoE+ Output` / `330W PoE+ Power Budget` - rev EPX-201910-v7, EXM-8C module table: `15W (255W max. with PoE Output)` plus footnote `^ The EPX-8M can support a maximum of 2 modules delivering PoE` - 2020 revision, same module: `15W (105W max. with PoE+ Output)` So the module ceiling (105 W / 255 W) and the chassis ceiling (330 W) are different numbers for the same box. `poe.budgetW` is recorded as **330 W**, the figure the current datasheet prints for the chassis, and all three quoted numbers are in the spec's `notes` rather than averaged into a fourth. ## Deliberately not catalogued yet `EPX-M8-LW1C3F3` (12x 10G SFP+, 24x GE, 3x LTE-A) is named in the same table and is left out on purpose: its three EXM-8C modules give 24 PoE-capable ports, while the chassis row says 8 PoE ports and the v7 footnote says at most 2 PoE modules (16). None of the three statements can be checked against the others, and a guessed PoE split is the kind of array that only surfaces when a lab cables 24 powered devices. Same for the bare `EPX-M8` chassis: its ordering row is `EPX Base Model, 1x LCD Module` and the archived datasheet's "Base Chassis" page lists throughput, power and dimensions but no interfaces at all, so there is nothing to cable to — issue #495's comment records that. ## Sources - https://web.archive.org/web/20200421214219/https://download.peplink.com/resources/peplink_epx_datasheet.pdf — Peplink EPX datasheet: ordering table, FlexModule table, base-chassis page - https://www.peplink.com/compare/tech-specs/epx.pdf — 7 FlexModule Plus slots, 30 Gbps, `Serial Interface: No`, `USB WAN: No`, `Wi-Fi AP: No` - https://download.peplink.com/resources/peplink_epx_datasheet.pdf — rev 2404-v15: 4-28x 10G SFP+, 8-56x GE, 330 W PoE+ budget - https://www.advantesco.com/assets/files/peplink_epx_datasheet.pdf — rev EPX-201910-v7: EXM-8C 255 W figure, 2-PoE-module footnote ## Gates - `node scripts/syntax-check.js` — 362 files, all OK - `node scripts/audit-port-types.js` — `No port contradicts its declared type.` - `node test/hardware-invariants.test.js` — 26 passed, 0 failed - `node test/spec-vs-description.test.js` — 3 passed, 0 failed - `node test/device-aliases.test.js` — 13 passed, 0 failed - `node scripts/import-devices.js` (dry run) — neither new spec rejected (the run's two rejects are pre-existing incoming files, unrelated) - `node scripts/regen-registry-doc.js` — 2,329 → 2,331 models, registry doc regenerated, not hand-edited Punctuation/duplicate gate: `EPX-M8-LW5C1F1` and `EPX-M8-LW2C1F1` are distinct orderable part numbers with different port censuses, so they are two devices rather than one spelling of the other. The AP-band twins (`EPX-M8-LP5C1F1`, `EPX-M8-LP2C1F1`) are not separate specs: identical ports, modem band region only, the same treatment the SDX Pro storage SKUs got.
catalogue: Peplink EPX (EPX-M8-LW5C1F1, EPX-M8-LW2C1F1) from the vendor's ordering table (#494)
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 17s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Arm auto-merge (pull_request) Successful in 6s
1573657a84
jaylouisw force-pushed catalogue/1116-2125 from 1573657a84
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 17s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Arm auto-merge (pull_request) Successful in 6s
to 74b06f52e1
All checks were successful
CI / Classify the change (pull_request) Successful in 20s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Server smoke test (pull_request) Successful in 19s
CI / Test (Node 20) (pull_request) Successful in 49s
CI / Test (Node 18) (pull_request) Successful in 54s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Docker build (pull_request) Successful in 27s
CI / Arm auto-merge (pull_request) Successful in 14s
2026-11-16 21:33:29 +00:00
Compare
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!1736
No description provided.