Mist Access Point Onboarding and Configuration
This domain tests the AP lifecycle from power-on to production: PoE, DHCP/DNS/NTP, claim, site assignment, templates, and firmware. Questions often present a disconnected AP and ask for the next check.
Power and reachability
APs are PoE-powered (802.3af/at/bt depending on model and features). After power, the AP needs DHCP, DNS, NTP, and outbound TCP 443 to Mist. There is no inbound port requirement and no on-prem controller.
Claim and assign
The claim code on the AP label ties it to an Organization. Claimed devices sit in Inventory; assign them to a Site so site rules, RF templates, and WLANs apply. Firmware upgrades are staged by Mist and can be scheduled.
Configuration layers
Org-level templates (WLAN, RF, Site) and device profiles define standard config; site-level settings and per-device overrides win where they conflict. RF templates control band, channel width, and channel/power, either auto or fixed. Mist auto-RF adjusts channel and power using neighbor and interference data.
Worked example: a new AP is claimed but shows disconnected and serves no clients. Claim succeeded, so ownership is fine. Check PoE class first (is it powering on?), then switch port VLAN and DHCP scope, DNS, and firewall 443. If the LED never leaves boot, suspect power; if it boots but never connects, suspect DHCP, DNS, or 443.
Traps: claiming to the wrong org; leaving an AP unassigned so it inherits only org defaults; assuming auto-RF fixes bad physical placement; forcing 80 MHz on every AP in a dense office.