Keep the budget at the PSE output boundary
A PoE switch or injector is the power sourcing equipment (PSE); the equipment receiving power is the powered device (PD). A static allocation plan must fit both the available output pool and each physical port. Adding device wattages alone does not test both constraints.
Use the available PoE output budget for one identified pool and configuration. An AC input rating or power-adapter rating does not by itself state that output budget. Record the PSE model, installed supply and configuration, connected devices, and the document or setting that supports each value. If a switch has separate pools or an upstream limit, check the applicable boundaries separately; combining unrelated pools here would hide a constraint.
Every row describes one physical port, with all power values in watts at the PSE output boundary:
| Symbol | Meaning | Input basis |
|---|---|---|
| B | Available output budget for this pool | Applicable PSE documentation and the stated configuration |
| C | Output limit for this port | Applicable hardware and configured port limit |
| A | Power allocated to this port in the plan | The explicit allocation being checked, supported by the configuration or planning basis |
| R | Required PSE-side allowance for this port | A requirement established for the connected equipment and conditions, expressed at the same output boundary |
A PD’s own load-side wattage is not automatically its required PSE-side allowance. Establish R at the PSE boundary, accounting for the applicable link and equipment requirements through a supported source or separate calculation. The tool does not invent cable-loss, efficiency, reserve, or class-to-power values. A live consumption reading likewise does not automatically define the allocation A. If an allocation or requirement is unknown, it must be established before the static plan can be checked; an empty field is not treated as zero.
Read all three port margins and the shared pool
Each row has three signed margins. Their signs show why a port passes or fails the supplied constraints:
- A − R: allocation left after meeting the stated PSE-side requirement. A negative value means the allocation is insufficient.
- C − A: port-limit space left after allocation. A negative value means the allocation exceeds the port limit.
- C − R: port-limit space above the requirement. A negative value means the required allowance itself exceeds that port’s stated limit.
The third margin makes a requirement that exceeds the port limit visible even when the plan also has an allocation shortfall. All three must be nonnegative. The separate pool margin is B − ΣA, using allocations rather than required allowances or measured consumption. An acceptable pool total cannot compensate for one failed port. Conversely, every port can pass individually while their allocations overfill the pool.
The overall result is supplied static constraints passed only when every port satisfies A ≥ R, C ≥ A, and R ≤ C, and the pool satisfies ΣA ≤ B. Comparisons use exact decimal arithmetic before three-decimal display rounding. A tiny negative margin may display as −0.000 W while its status still correctly says failed. Zero margin means exact equality under the stated inputs; it does not create a reserve for startup, uncertainty, or later additions.
Port margins: A − R, C − A, and C − R must each be ≥ 0 W.
Pool margin: B − ΣA must be ≥ 0 W.
Overall: every port and the shared pool must satisfy these supplied static constraints.
Worked allocation plan and two distinct failures
Consider a hypothetical 80 W PSE output pool and these two ports. The values illustrate the arithmetic and are not specifications for actual products.
| Port | C (W) | A (W) | R (W) | A − R (W) | C − A (W) | C − R (W) |
|---|---|---|---|---|---|---|
| Port 1 | 30 | 20 | 18 | 2 | 10 | 12 |
| Port 2 | 30 | 30 | 24 | 6 | 0 | 6 |
Total allocation is 20 + 30 = 50 W; total required allowance is 18 + 24 = 42 W. The pool has 80 − 50 = 30 W unallocated. Every listed margin is nonnegative, so these supplied static constraints pass. The 42 W requirement total is useful for review, but the pool check uses the 50 W allocation total.
If Port 1 instead requires 31 W, its 30 W limit cannot support that stated allowance. Keeping A at 20 W gives A − R = −11 W and C − R = −1 W. The pool would still have 30 W unallocated across the original two ports, but that does not repair Port 1’s failure.
For a different failure, three ports each with C = 30 W, A = 30 W, and R = 24 W pass their individual port checks. Their total allocation is 90 W, leaving 80 − 90 = −10 W in the same 80 W pool. That plan fails the pool constraint.
An explicit 0 W allocation with a 0 W requirement is permitted, including in a 0 W pool, provided C remains positive. That is a statement about the entered plan. It does not establish that connected equipment needs no power or can start.
Static allocation is not a switch admission policy
Actual PoE behavior depends on the PSE model, firmware, configuration, device negotiation, and power state. Cisco Meraki’s PoE support documentation for MS and cloud-managed C9000 switches, under PoE Power Budgeting, distinguishes MS consumption-based behavior from the default requested-power behavior described for MS390 and cloud-managed C9000. Its Flexible PoE section describes oversubscription with specific support conditions. Those are different operating policies; this calculator applies the explicit static condition ΣA ≤ B throughout.
MikroTik’s PoE-Out documentation, under PoE-Out limitations, separates individual port limits from the total PSE limit. Its PoE-Out Logs section distinguishes LLDP denial reasons including budget, hardware limit, and class limit. The arithmetic here checks only the limits and requirements you enter. It does not determine a PoE class, negotiate power, predict which port a switch will shed, or verify startup and device compatibility.
For a separate low-voltage DC load outside the PoE allocation boundary, use the DC load budget calculator. If a downstream converter’s source-side power must be established from output load and supported efficiency data, the DC converter load calculator handles that conversion. Include the resulting requirement once at the appropriate boundary; do not count both a downstream load and the same power again as another physical PoE port.