Purpose
This document provides a structured procedure to identify, analyse, and resolve Power over Ethernet (PoE)–related power issues affecting Access Points (APs).
Proper PoE troubleshooting helps ensure:
Stable AP operation
Continuous Wi-Fi availability
Reduced client disconnections
Reliable cloud connectivity
Scope
Applies to sites where Access Points are powered using:
PoE Switches (IEEE 802.3af / 802.3at / 802.3bt)
PoE Injectors
External Power Adapters
Relevant for deployments in:
Retail stores
Offices
Branch networks
Hospitality environments
Symptoms of PoE Power Issues
These indicators help technicians quickly determine that the issue may be related to power delivery rather than configuration or RF problems.
Common symptoms (if APs are powered on POE) include:
AP completely offline
AP not visible in cloud controller
AP LED OFF
AP continuously rebooting
“Insufficient Power” or similar warning in controller
Clients disconnecting intermittently
AP uptime resetting frequently
Troubleshooting Procedure
Follow this structured process to isolate PoE-related faults.
Step 1 — Physical Inspection
Verify:
Ethernet cable firmly connected at both ends
AP LED status (power / fault indication)
No visible cable damage or loose connectors
If PoE injector is used → confirm power adapter is ON and properly connected
Also check:
Cable length not exceeding recommended limits (~100 meters)
Step 2 — Check Switch Port & PoE Status
On the switch management interface verify:
Port link status is UP
POE is enabled on Switch port AP is connected
PoE status shows Delivering Power via CLI
Power allocated (in Watts) is visible
Look for error indicators such as:
Power denied
Overcurrent condition
Short circuit detection
PoE fault or shutdown
Switch Port not coming up (Physical Port issue)
Step 3 — Verify PoE Budget
Confirm:
Total PoE budget available on switch
Total allocated power vs maximum capacity
If the switch PoE budget is exhausted:
Newly connected AP may not power on
Existing APs may reboot intermittently
Step 4 — Validate PoE Standard Compatibility
Check AP power requirements from datasheet.
Example scenarios:
AP requires 802.3at (≈30W)
Switch provides only 802.3af (≈15.4W)
This may result in:
AP boot failure
Reduced radio performance
Random reboots
High-performance or dual-radio APs typically require higher power.
Step 5 — Test Alternate Port or Cable
To isolate fault:
Move AP to a known working PoE port
Replace Ethernet patch cable
Test using PoE injector (if available)
This helps determine whether issue is caused by:
Faulty switch port
Cable issue
AP hardware failure
Resolution Actions
Depending on root cause:
Increase PoE budget (add power module if switch supports it)
Replace faulty switch port or switch hardware
Replace damaged Ethernet cable
Use correct PoE injector (e.g., 802.3at instead of 802.3af)
Replace AP if hardware failure confirmed
️Verification After Fix
Confirm:
AP LED shows normal operational state
AP appears online in cloud controller
AP uptime remains stable (no reboot cycles)
Clients connect successfully
Switch PoE status shows Delivering Power
Monitor stability for 10–15 minutes after remediation.
Preventive Best Practices
To avoid future PoE issues:
Plan PoE budget during network deployment
Document power requirements of each AP model
Avoid fully exhausting switch PoE capacity
Enable SNMP or monitoring alerts for PoE threshold
Perform periodic switch power utilization audits
Maintain spare PoE injector for field troubleshooting
Escalation Guidelines
Escalate to Network Engineering or Vendor Support if:
Multiple APs fail simultaneously
Switch power supply failure suspected
Repeated overcurrent or PoE fault alarms observed
Firmware-related power instability suspected
PoE controller chipset (ASIC) fault suspected
Provide the following details:
Site name
Switch model and firmware version
AP model
Affected switch port numbers
Observed PoE fault messages