A controller-based AP in a municipal annex powers up but never joins the downtown wireless controller. Firewall logs show the AP's CAPWAP/control traffic to the controller is blocked. What technician awareness applies?
Select an answer to reveal the explanation.
Short Explanation
A lightweight AP without a path to its controller is like a remote worker locked out of HQ VPN—lights may be on, but it never really checks in. Open the control path or that AP stays a brick in join terms.
Full Explanation
Controller-based (lightweight) APs depend on reachability to their controller for join and ongoing control-plane functions such as CAPWAP or the vendor equivalent. If firewalls or ACLs block that path, the AP fails to join even when PoE and local switching look healthy. Technicians troubleshoot join failures by verifying Layer-3/4 reachability to the controller, not by assuming autonomous behavior.