peplink: EPX-M8-LW1C3F3, the 24-PoE+ build the datasheet only looked self-contradictory about #1771

Merged
jaylouisw merged 1 commit from catalogue/1117-0225 into main 2026-11-17 02:34:43 +00:00
Owner

Fixes #495

Adds devices/peplink/epx-m8-lw1c3f3.json - the third and last orderable EPX build, and the one this issue was parked on: EPX-M8-LW1C3F3 (Wired SD-WAN Powerhouse), 3x EXM-4F + 3x EXM-8C + 1x EXM-3LTEA in all 7 FlexModule Plus slots = 12x 10G SFP+, 24x 1G RJ45 (all PoE+), 3x LTE-A. 39 interfaces, 330 W PoE+ budget.

Why the earlier pass called it contradictory, and what settles it

Three statements used to disagree, and they are all from Peplink's own files:

Source Says
EPX datasheet rev 2404-v15, EPX-M8 spec table PoE Output 8x 802.3at PoE+ Output, 330W PoE+ Power Budget
same table, LAN row LAN Interface 8-56x GE Ports with PoE+ Output
FlexModule datasheet ref 2507-v26 EXM-8C: 15 W (Max. 240W, 30W / PoE+ port, total 8 PoE+ ports)
EPX datasheet rev EPX-201910-v7 (2019) footnote: The EPX-8M can support a maximum of 2 modules delivering PoE

The flat 8x row cannot be a chassis ceiling and the 8-56 row cannot be a typo: 56 is only reachable at 8 GE ports per module across 7 slots, so 8x is the one-module base figure and PoE+ scales with the modules fitted. The module datasheet says the same thing positively - total 8 PoE+ ports per EXM-8C. The 2019 "maximum of 2 PoE modules" footnote is absent from both current documents; 2507-v26 replaces it with ^This FlexModule with HW2 is not compatible with SDX (HW1 - HW3) and FlexModule Slot 2 of EPX, which leaves six PoE-capable slots and does not touch a three-module build.

So the census is 3 x 8 = 24 PoE+ GE ports, and the budget recorded is the chassis figure (330 W): the module's 240 W is per-module headroom the chassis cannot fund three times over.

One residual contradiction is written into the spec's notes rather than smoothed: 7 slots x 8 = 56 PoE+ ports in the range row, while the slot-2 restriction permits six. It does not reach a 3-module build, and inventing an answer for the extreme case is exactly what this issue was left open for.

Sources recorded in the spec:

The two sibling specs' notes no longer claim this SKU is uncataloguable; they now point at the two current documents that resolve it. docs/DEVICE_REGISTRY.md, README, docs/CONNECTORS.md and the wiki headline were regenerated (2,344 models / 29,091 sockets / 962 shapes), not hand-edited.

Gates

  • node scripts/syntax-check.js -> Syntax-checked 371 files: all OK
  • node scripts/audit-port-types.js -> No port contradicts its declared type.
  • node scripts/check-control-bytes.js -> No control bytes in source.
  • node test/hardware-invariants.test.js -> 26 passed, 0 failed (catalogue 2,344 models)
  • node test/poe.test.js -> 18 passed, 0 failed
  • node scripts/regen-registry-doc.js --check -> catalogue pages current
  • registry load check: EPX-M8-LW1C3F3 present, 39 interfaces, 24 with poeOut
Fixes #495 Adds `devices/peplink/epx-m8-lw1c3f3.json` - the third and last orderable EPX build, and the one this issue was parked on: `EPX-M8-LW1C3F3` (Wired SD-WAN Powerhouse), 3x EXM-4F + 3x EXM-8C + 1x EXM-3LTEA in all 7 FlexModule Plus slots = **12x 10G SFP+, 24x 1G RJ45 (all PoE+), 3x LTE-A**. 39 interfaces, 330 W PoE+ budget. ### Why the earlier pass called it contradictory, and what settles it Three statements used to disagree, and they are all from Peplink's own files: | Source | Says | |---|---| | EPX datasheet rev 2404-v15, EPX-M8 spec table | `PoE Output 8x 802.3at PoE+ Output`, `330W PoE+ Power Budget` | | same table, LAN row | `LAN Interface 8-56x GE Ports with PoE+ Output` | | FlexModule datasheet ref 2507-v26 | EXM-8C: `15 W (Max. 240W, 30W / PoE+ port, total 8 PoE+ ports)` | | EPX datasheet rev EPX-201910-v7 (2019) | footnote: `The EPX-8M can support a maximum of 2 modules delivering PoE` | The flat `8x` row cannot be a chassis ceiling and the `8-56` row cannot be a typo: 56 is only reachable at 8 GE ports per module across 7 slots, so `8x` is the **one-module base figure** and PoE+ scales with the modules fitted. The module datasheet says the same thing positively - `total 8 PoE+ ports` per EXM-8C. The 2019 "maximum of 2 PoE modules" footnote is absent from both current documents; 2507-v26 replaces it with `^This FlexModule with HW2 is not compatible with SDX (HW1 - HW3) and FlexModule Slot 2 of EPX`, which leaves six PoE-capable slots and does not touch a three-module build. So the census is 3 x 8 = 24 PoE+ GE ports, and the budget recorded is the chassis figure (330 W): the module's 240 W is per-module headroom the chassis cannot fund three times over. One residual contradiction is written into the spec's notes rather than smoothed: 7 slots x 8 = 56 PoE+ ports in the range row, while the slot-2 restriction permits six. It does not reach a 3-module build, and inventing an answer for the extreme case is exactly what this issue was left open for. Sources recorded in the spec: - https://web.archive.org/web/20200421214219/https://download.peplink.com/resources/peplink_epx_datasheet.pdf (ordering row `EPX-M8-LW1C3F3 Wired SD-WAN Powerhouse: EPX with LCD Module, 12x 10G SFP+, 24x GE, and 3x LTE-A (Worldwide).`) - https://download.peplink.com/resources/peplink_epx_datasheet.pdf (2404-v15: 8-56x ranges, PoE row, 330 W) - https://download.peplink.com/resources/peplink_flexmodule_datasheet.pdf (2507-v26: EXM-8C 8 PoE+ ports / 240 W / 30 W per port, EXM-4F 4x SFP+, slot-2 footnote) - https://www.peplink.com/compare/tech-specs/epx.pdf (7 FlexModule Plus slots, 30 Gbps) - https://download.peplink.com/manual/peplink-balance-and-mediafast-firmware-manual-8.1.3.pdf (`EXM-8C ... LAN Interface 8x GE; 802.3at PoE Output`) The two sibling specs' notes no longer claim this SKU is uncataloguable; they now point at the two current documents that resolve it. `docs/DEVICE_REGISTRY.md`, README, `docs/CONNECTORS.md` and the wiki headline were regenerated (2,344 models / 29,091 sockets / 962 shapes), not hand-edited. ### Gates - `node scripts/syntax-check.js` -> Syntax-checked 371 files: all OK - `node scripts/audit-port-types.js` -> No port contradicts its declared type. - `node scripts/check-control-bytes.js` -> No control bytes in source. - `node test/hardware-invariants.test.js` -> 26 passed, 0 failed (catalogue 2,344 models) - `node test/poe.test.js` -> 18 passed, 0 failed - `node scripts/regen-registry-doc.js --check` -> catalogue pages current - registry load check: EPX-M8-LW1C3F3 present, 39 interfaces, 24 with `poeOut`
peplink: EPX-M8-LW1C3F3, the 24-PoE+ build the datasheet only looked self-contradictory about (#495)
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 20s
CI / Server smoke test (pull_request) Successful in 11s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 20) (pull_request) Successful in 1m1s
CI / Test (Node 18) (pull_request) Successful in 1m6s
CI / Test (Node 22) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 7s
14cd0ce4d8
jaylouisw force-pushed catalogue/1117-0225 from 14cd0ce4d8
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 20s
CI / Server smoke test (pull_request) Successful in 11s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 20) (pull_request) Successful in 1m1s
CI / Test (Node 18) (pull_request) Successful in 1m6s
CI / Test (Node 22) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 7s
to 258e4bb12b
All checks were successful
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 11s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Docker build (pull_request) Successful in 17s
CI / Arm auto-merge (pull_request) Successful in 17s
2026-11-17 02:30:06 +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!1771
No description provided.