PoE Budget Planning for Multi-Site WiFi Deployments

Welcome to the Purple Technical Briefing. I'm your host, and today we are tackling a critical infrastructure challenge that often catches IT directors and network architects off guard: PoE budget planning for multi-site WiFi deployments. If you are upgrading a hotel, a retail chain, or a stadium to WiFi 6E or WiFi 7, the radio frequency design is only half the battle. The other half is power. Power over Ethernet, or PoE, has evolved dramatically from the days of simply powering legacy VoIP phones. Modern access points are power-hungry, and if you miscalculate your switch sizing across fifty or a hundred sites, you are looking at brownouts, degraded performance, or a massive, unexpected capital expenditure for switch replacements. Let's dive into the technical reality. We have moved from 802.3af, which delivered 15.4 watts, to 802.3at, known as PoE+, delivering 30 watts. But for WiFi 6E and especially WiFi 7, we are firmly in the territory of 802.3bt, or PoE++. Type 3 delivers up to 60 watts, and Type 4 pushes up to 100 watts. Why the massive increase? Modern APs have more radios, wider channels, and dedicated scanning radios for security and analytics. They require serious power. If you plug a WiFi 6E AP into an older PoE+ switch, it will likely negotiate down, disabling radios or reducing transmit power, which completely defeats the purpose of the upgrade. So, how do you calculate the total PoE budget per site? You cannot simply look at the maximum output of a switch and divide by the number of ports. You need to calculate the worst-case draw of every connected device—access points, IP cameras, IoT sensors—and then add a safety margin, typically 20 to 25 percent. This accounts for power loss over long cable runs and provides headroom for future additions. If you have a 48-port switch with a 740-watt power supply, and you connect forty-eight WiFi 6 APs drawing 25.5 watts each, you need 1,224 watts. That switch will fail to power them all. You either need a switch with a larger power supply, often 1440 watts, or you need to distribute the load across multiple switches. Let's look at implementation recommendations and common pitfalls. The biggest pitfall is ignoring the cable infrastructure. PoE++ pushes up to 100 watts over all four pairs of a twisted-pair cable. This generates heat. If you have tightly bundled Cat5e cables in a ceiling tray, the heat cannot dissipate, which increases resistance and voltage drop. You need Cat6A for new deployments to handle the thermal load of PoE++. Furthermore, future-proofing your switch investments means looking at the total cost of ownership. It is often cheaper to deploy multi-gigabit PoE++ switches now than to rip and replace PoE+ switches in three years when the business demands WiFi 7. Now for a rapid-fire Q&A based on common client concerns. Question one: Can I mix PoE+ and PoE++ switches in the same IDF? Yes, absolutely. Place your high-density APs on the PoE++ switch and lower-power devices like standard APs or IP phones on the PoE+ switch to optimise cost. Question two: What happens if I exceed the PoE budget? The switch will begin shedding load based on port priority. If priorities aren't configured, it's a lottery. Critical APs in high-traffic areas might drop offline during peak usage. Always configure port priorities. To summarise, multi-site PoE planning requires rigorous auditing of existing switch power budgets, understanding the exact power draw of your chosen APs, and upgrading cabling where necessary. Don't let power be the bottleneck in your next-generation wireless deployment. For more detailed calculations and architecture diagrams, refer to the full technical guide provided by Purple. Thank you for listening, and keep your networks resilient.