[Device]: Peplink SDX Modular Enterprise Grade Router BPL-SDX #458

Closed
opened 2026-11-08 06:15:59 +00:00 by jaylouisw · 1 comment
Owner

Vendor

Peplink

Exact model name

Peplink SDX Modular Enterprise Grade Router BPL-SDX

Category

Router

Ports and interfaces

  • See product page for full port list

Ports inferred from the 4gon product name; confirm against the product page.

PoE budget (watts)

None

Datasheet or product page URL

https://www.4gon.co.uk/peplink-sdx-modular-enterprise-grade-router-bplsdx-p-9178.html

What do you want to model with it?

A router/gateway node in a routed lab (NAT, DHCP, VPN, cellular WAN).

Capabilities

routing, NAT, DHCP, l3-forward

Before submitting

  • I searched the catalog and existing issues, and this model is not there yet.
  • The port list above comes from a datasheet, not from memory or another wiki.
### Vendor Peplink ### Exact model name Peplink SDX Modular Enterprise Grade Router BPL-SDX ### Category Router ### Ports and interfaces - See product page for full port list > Ports inferred from the 4gon product name; confirm against the product page. ### PoE budget (watts) None ### Datasheet or product page URL https://www.4gon.co.uk/peplink-sdx-modular-enterprise-grade-router-bplsdx-p-9178.html ### What do you want to model with it? A router/gateway node in a routed lab (NAT, DHCP, VPN, cellular WAN). ### Capabilities routing, NAT, DHCP, l3-forward ### Before submitting - [x] I searched the catalog and existing issues, and this model is not there yet. - [x] The port list above comes from a datasheet, not from memory or another wiki.
jaylouisw referenced this issue from a commit 2026-11-08 06:43:31 +00:00
Author
Owner

Modelled - devices/peplink/bpl-sdx.json, commit 98890f4 on fix/sfp-plus-connectors.

The blocking problem was that SDX is a modular chassis and the product page leads with its FlexModule. But the datasheet's ordering row names the base chassis exactly, which is what a spec file needs:

BPL-SDX — SDX Base Model, No Expansion module, 2x GE WAN Ports, 2x 10GE SFP+ WAN ports, 8x GE LAN ports, 2x USB WAN

and the chassis drawing adds 1x MGMT and 1x Console. The specs table agrees (WAN: 2x 10G SFP+ Ports, 2x GE Ports, 2x USB 3.0 Ports; LAN: 8x GE Ports with PoE+ Output).

Four carry-overs that matter in a lab:

  • Every LAN port is a PSE and the budget is quoted - PoE Output: 8x 802.3at PoE+, Power Consumption: 80W System, 330W PoE+ Power Budget. So poeOut: 30 on each of the eight and poeBudget: 330, rather than multiplying 8 x 30 W and calling that the budget;
  • the WAN side is faster than the LAN side and mixes media - two 10G SFP+ cages plus two copper GE ports, with WAN Port Convertible into LAN Port kept as a note instead of becoming two extra LAN ports;
  • MGMT is out-of-band and stays out of the lan bridge group;
  • not modelled: the 2x USB 3.0 WAN ports (no USB interface type) and the single FlexModule Plus slot - a module bay is a fact about the host, not a port, per the components clause. With a module fitted the box gains 8 GE or 4 SFP+ ports; this spec is the "No Expansion module" SKU the datasheet names, so #494/#495 (EPX) stay open for the same reason at a larger scale.
Modelled - `devices/peplink/bpl-sdx.json`, commit `98890f4` on `fix/sfp-plus-connectors`. The blocking problem was that SDX is a modular chassis and the product page leads with its FlexModule. But the datasheet's **ordering row names the base chassis exactly**, which is what a spec file needs: > `BPL-SDX — SDX Base Model, No Expansion module, 2x GE WAN Ports, 2x 10GE SFP+ WAN ports, 8x GE LAN ports, 2x USB WAN` and the chassis drawing adds `1x MGMT` and `1x Console`. The specs table agrees (`WAN: 2x 10G SFP+ Ports, 2x GE Ports, 2x USB 3.0 Ports`; `LAN: 8x GE Ports with PoE+ Output`). Four carry-overs that matter in a lab: * **Every LAN port is a PSE and the budget is quoted** - `PoE Output: 8x 802.3at PoE+`, `Power Consumption: 80W System, 330W PoE+ Power Budget`. So `poeOut: 30` on each of the eight *and* `poeBudget: 330`, rather than multiplying 8 x 30 W and calling that the budget; * **the WAN side is faster than the LAN side and mixes media** - two 10G SFP+ cages plus two copper GE ports, with `WAN Port Convertible into LAN Port` kept as a note instead of becoming two extra LAN ports; * **MGMT is out-of-band** and stays out of the `lan` bridge group; * **not modelled:** the 2x USB 3.0 WAN ports (no USB interface type) and the single FlexModule Plus slot - a module bay is a fact about the host, not a port, per the components clause. With a module fitted the box gains 8 GE or 4 SFP+ ports; this spec is the "No Expansion module" SKU the datasheet names, so #494/#495 (EPX) stay open for the same reason at a larger scale.
Sign in to join this conversation.
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#458
No description provided.