After a library branch adds a second radio-heavy AP to a PoE switch…

Question

After a library branch adds a second radio-heavy AP to a PoE switch that was already near its power budget, the new AP boots then repeatedly reboots when clients associate and radios ramp up. What is the most likely PoE-related cause?

Accepted Answer

The PSE power budget or per-port wattage is undersized for the AP’s draw under load, causing brownout and reboot cycles. — AP comes up, then keels over when the radios get busy? Classic underfed PoE. Check the switch budget and class—starving an AP under load makes it reboot like a laptop with a dying battery.

Answer

The SSID name is too long, which forces the AP to reboot as a standards requirement.

Answer

Client isolation being disabled always triggers a forced PoE renegotiation loop.

Answer

HTTPS management being enabled consumes more PoE watts than the radios, so HTTPS must be turned off.

After a library branch adds a second radio-heavy AP to a PoE switch that was already near its power budget, the new AP boots then repeatedly reboots when clients associate and radios ramp up. What is the most likely PoE-related cause?

Short Explanation

Full Explanation