Platform, Tools, and Environment
Architectures you must distinguish
AWCC expects you to know where control logic lives. In a controller-based design, APs build a control tunnel to the controller and may switch traffic locally or tunnel it. Cloud-managed designs move configuration and monitoring to a hosted plane while data stays at the edge. Distributed designs push forwarding and some control to the AP itself. Each choice changes what breaks when a WAN link fails.
Discovery and prerequisites
An AP must find its manager before it can serve clients: DHCP option 43, DNS resolution of a configured name, Layer 2 broadcast, or a static entry. Underneath that, the environment must supply DHCP scopes, working trunks, NTP, and DNS. Certificate-based joins fail silently when the clock is wrong, so time sync is a provisioning dependency, not an afterthought.
Power and cabling
802.3af delivers about 15.4 W at the PSE (12.95 W at the device), 802.3at about 30 W, and 802.3bt up to 60 W or 90 W. Budget the switch's total PoE allocation, not just per-port class, and account for cable loss over long runs. Cat5e supports 1 GbE to 100 m; 2.5G/5G/10GBASE-T need Cat6 or better and shorter runs.
Worked example
A 24-port switch advertises a 370 W PoE budget. Twelve APs reserve 30 W each: 360 W, leaving 10 W - technically within budget but with no headroom. Adding a thirteenth AP needs 30 W more and exceeds the budget, so the correct fix is a second switch or a lower power class, not disabling PoE priority.
Tools and traps
Spectrum analyzers find non-802.11 interference; protocol captures find handshake and DHCP failures; iperf3 measures throughput without wireless counters. Common traps: mistaking device draw for PSE reservation, assuming discovery crosses NAT, and ignoring licensing state during troubleshooting.