PoE Power Planning Guide: How to Budget Power for APs, Cameras and Phones Without Random Reboots
| Network Infrastructure
PoE is not just "power over the cable". This guide covers the af / at / bt standards, how to calculate a power budget, cabling and distance limits, and the power causes behind access points that keep rebooting, with a fault reference table.
Introduction: Why Does the AP Keep Rebooting on Its Own?
Many offices have seen this pattern: an access point reboots by itself, a camera drops offline from time to time, an IP phone freezes the moment a call starts. The equipment gets replaced, the system gets reset, and the problem persists. In the end, the cause is not the equipment at all, but the power supply: the PoE power budget is not enough.
PoE (Power over Ethernet) lets one network cable carry both data and power, so access points, IP cameras, IP phones and door-access readers do not need separate power cables, and installation positions become far more flexible. But the idea that "plug in the cable and there is power" misses the critical question: power has limits. The total power a switch can deliver, the power each port can deliver, and the loss along the cable are all capped. Exceed those caps and devices become under-powered, showing up as reboots, disconnections and malfunctioning features.
This article explains how PoE works, how the three generations of standards differ, how to calculate a power budget, what the cabling and distance limits are, and how to troubleshoot faults from the power angle.
What Is PoE: Data and Power Over the Same Cable
A standard network cable contains four twisted pairs. PoE superimposes direct current onto the pairs that carry data, or uses spare pairs to deliver power, so that power-sourcing equipment (PSE, such as a PoE switch) can power a powered device (PD, such as an AP or a camera) over the cable. Before powering a device, the PSE performs a low-power detection step to confirm the other end is a PoE device; equipment that does not support PoE receives no power and is not damaged. That negotiation step is a basic protection built into the PoE design.
The benefits of PoE are practical: no separate power cable for every AP and every camera, no need to find a socket near the ceiling, corridor or doorway; equipment positions can follow signal needs rather than socket positions; and with centralised power in the comms room, a UPS can hold up the whole PoE system during a power cut. The precondition is that the power budget is calculated properly during planning.
Three Generations of Standards Compared
| Item | 802.3af (PoE) | 802.3at (PoE+) | 802.3bt (PoE++ Type 3 / Type 4) |
|---|---|---|---|
| Year published | 2003 | 2009 | 2018 |
| Max output per PSE port | 15.4 W | 30 W | 60 W / 90 W |
| Power available at the PD (after cable loss) | About 12.95 W | About 25.5 W | About 51 W / about 71 W |
| Pairs used | Two pairs | Two pairs | Four pairs |
| Typical applications | Basic IP phones, simple APs, basic cameras | Mainstream APs, PTZ cameras, video phones | High-power APs, PTZ cameras with heaters, LED lighting, thin clients |
How to read this table: the easiest mistake is treating "PSE output" as "power available at the device". Power is lost along the cable, so the power a powered device actually receives is always less than the PSE output. When calculating a budget, always use the "power available at the PD" row, not the output row. Another key point: a device's real consumption is not the standard ceiling, but the maximum and typical consumption figures on the device's own datasheet.
How to Calculate a Power Budget: Three Steps
Step 1: List Each Device's Maximum Consumption
Go to each device's datasheet and find its maximum power consumption or PoE power requirement. Do not budget on "typical consumption", because consumption peaks at start-up, when a heater switches on, when a PTZ head pans, or when infrared night vision engages. A PTZ camera might typically draw a modest wattage, but with its heater and pan motor running at the same time, consumption can be far higher. Budgeting on typical values means the first cold spell that switches the heater on will blow the budget.
Step 2: Add Them Up, Then Compare With the Switch's Total Budget
Add up the maximum consumption of all powered devices and compare the total with the PoE switch's total PoE power budget. Note: the port count printed on a switch does not mean all ports can deliver full power simultaneously. A 24-port switch can have every port labelled PoE+ while its total power budget is still not enough for all 24 ports at full load. That is the root of many "each device works on its own, but everything breaks once all are plugged in" cases: single-device testing stays within budget, but all devices together exceed the total budget, the PSE starts limiting output, and some devices reboot or drop features.
Step 3: Leave Headroom — Never Budget to the Limit
After adding everything up, leave headroom. Cable loss varies with temperature and length; a firmware update can change a device's consumption; and adding devices later is common, so reserved expansion room avoids having to replace the whole switch. In practice, running the budget to around seventy percent is a prudent reference level — do not calculate it to ninety-nine percent and stop. Headroom is not waste; it is the cost of stability.
Cabling and Distance: Two Hard Limits
The 100-Metre Channel Limit
The channel length limit for Ethernet cabling is 100 metres, including horizontal cabling plus patch cords at both ends. Beyond that length, both signal and power suffer: data may show errors, speed drops and disconnections; power loss along the cable increases, and the powered device receives less power. For long cable runs, do not just think "it reaches"; think about whether the power still suffices.
Cable Quality Directly Affects Power Delivery
Cable quality matters more for PoE than for data alone. Thinner conductors and higher resistance mean more power lost in transit and more heat generated. PoE++ high-power applications are especially sensitive, because the current is larger and heating is more pronounced. Tightly bundled cables, overfilled cable trays and high ambient temperatures all raise cable temperature and further affect power delivery. When doing PoE cabling, cable specification, installation workmanship and ventilation space are all part of the power design, not merely "pulling cable".
Four-Pair vs Two-Pair Power Delivery
802.3bt delivers power over all four pairs, spreading the current, which reduces both cable loss and heating; 802.3af / at deliver over two pairs, so the current is more concentrated at the same power. That is one reason high-power devices need the bt standard — not only because the total power is larger, but because the delivery method itself suits high-power transmission better. When designing, confirm that the switch, cabling and powered device standards match: if the switch supports bt but the device only supports at, the result is still at-level power; conversely, if the switch only supports af while the device needs at, the result is under-powering.
Power Design Checklist: Think About These During Planning
- Segmented power: do not hang the whole site's PoE devices off one switch. Split by floor or by zone, each with its own power budget, so a fault in one segment does not drag down the whole site, and maintenance does not require shutting down the entire system.
- UPS backup: the benefit of centralised PoE power is that a UPS can hold everything up during a power cut. But UPS capacity must be sized on total PoE load, not just the switch's own consumption. With cameras, APs and phones all PoE-powered, the UPS load is the sum of all powered devices plus the switch itself.
- Switch placement: a fully loaded PoE switch generates substantial heat; the rack needs adequate ventilation and must not sit in a sealed cabinet. Poor cooling makes the switch throttle, or even shut down on thermal protection.
- Documentation: record which port connects to which device, that device's maximum consumption, and where each cable run goes. Without records, troubleshooting becomes guesswork, and replacing a switch means estimating everything from scratch.
- Reserved expansion: for new fit-outs and new offices, reserve roughly twenty percent of PoE ports and power headroom. Adding a camera or an AP is common; with headroom reserved, there is no need to keep replacing the switch.
Fault Reference Table: Symptoms, Power Causes, How to Check
| Symptom | Possible power cause | How to check |
|---|---|---|
| AP reboots occasionally, especially at busy times | Total power budget insufficient; output limited when load is high | Check the switch's PoE usage against its total budget; check whether other devices are at high load at the same time |
| Camera drops offline at night, fine in daytime | Infrared night vision raises consumption beyond the allocation | Check the camera's consumption with infrared on and off; check the port's actual delivered power |
| PTZ camera drops when the head pans | Motor plus heater switching on together, momentary consumption peaks | Check the camera's maximum-consumption specification; test port power while panning |
| IP phone freezes when a call starts | Consumption rises during calls; older switch only supports a lower standard | Compare the phone's requirement with the switch port's standard |
| Adding one new device makes old devices fail | Combined total exceeds the total budget | Recalculate the maximum consumption of all devices and compare with the total budget |
| The device on the long run is unstable; short runs are fine | Long cable means high cable loss and insufficient power at the device | Measure the run length; check cable specification and connector quality; consider shortening the run or moving the power source |
Troubleshooting principle: look at the switch's PoE status page first, confirm each port's actual output power and total usage, then compare with the maximum consumption on each device's datasheet. If total usage is already close to the total budget, insufficient power is the prime suspect — do not replace equipment first.
Common Misunderstandings
- If all ports on a PoE switch are filled, there must be enough power? Wrong. Port count and total power budget are two different things. Always check the total budget, not just the port count.
- Will PoE burn out equipment that does not support PoE? No. Standard PoE probes first and only delivers power after confirming the other end is a PoE device. But note that non-standard "passive PoE" injectors have no such negotiation — do not mix them in casually.
- Does cabling only affect speed, not power? Wrong. Conductor size, length and temperature all affect cable loss and heating, which directly affect how much power the powered device receives.
- Does an AP rebooting mean the AP is broken? Not necessarily. Insufficient power is one common cause; check the PoE status and power budget before replacing the AP.
Conclusion: Power Is Design, Not After-the-Fact Repair
The core of PoE planning is one sentence: calculate properly, leave headroom, document everything. List each device's maximum consumption, compare the total with the budget, leave expansion room, and record what is connected to each port and what load it carries. Doing this work at the planning stage costs the least; tracing it back after devices keep rebooting costs far more. For PoE power and network planning assessed against your actual site, see office networks; for Wi-Fi deployment, see Wi-Fi solutions. Our team surveys the site first, then recommends a solution.