Product

FortiAP

Secure wireless access points integrated with Fortinet’s wired and security stack.

Quick referencesOfficial documents and operational shortcuts

Data SheetFortiAP Series →Verified Sep 2026

QSGQuick Start Guides →InManDis

DocumentationFortiAP Docs →Verified Sep 2026

MatricesFortiAP Matrix →

ToolsFortiAP Finder →Compare FortiAP models →FortiGate/FortiAP Compatibility →

CLICLI Cheat Sheet →InManDis

Naming ConventionsAP Naming Conventions →Official Fortinet PDF

Ordering GuideFortiAP / Wireless Guide →Verified Sep 2026

ReferenceWi-Fi Standards →InManDis

CLI quick reference

Extended CLI Reference

FortiAP CLI Cheat Sheet →

FortiGate-controller commands for FortiAP visibility and troubleshooting. Confirm syntax against the FortiOS/FortiAP release combination.

Managed FortiAP status

get wireless-controller wtp
diagnose wireless-controller wlac -c wtp
diagnose wireless-controller wlac -c sta
diagnose wireless-controller wlac -d sta
diagnose wireless-controller wlac -c vap
diagnose wireless-controller wlac -c radio
diagnose wireless-controller spectral-info

FortiAP managed troubleshooting

# Confirm the AP is reachable from the FortiGate
execute ping <FAP-IP>

# Inspect CAPWAP / AP traffic
diagnose sniffer packet any 'host <FAP-IP>' 4 0 l

# List managed APs and controller state
diagnose wireless-controller wlac -c wtp

# Review connected stations
diagnose wireless-controller wlac -c sta
diagnose wireless-controller wlac -d sta

# Review VAP and radio state
diagnose wireless-controller wlac -c vap
diagnose wireless-controller wlac -c radio

# Controller debug — use only while reproducing the issue
diagnose debug reset
diagnose debug application cw_acd -1
diagnose debug enable
# reproduce the issue
diagnose debug disable
diagnose debug reset

Managed FortiAP workflow: Check AP authorization and CAPWAP reachability first, then WTP state, radio/VAP state, client association, and finally targeted controller debug.

Troubleshooting framework

Step	What to do
1. Symptoms	Write down exactly what is failing, affected scope, start time and last known-good state.
2. Health	Check CPU, memory, interfaces, HA/control-plane status and recent configuration changes.
3. Path	Validate L1/L2/L3, routing, policy, session state and dependencies in that order.
4. Logs	Correlate system/event/traffic logs with packet captures and targeted debugs.
5. Version	Check release notes, known issues, compatibility and lifecycle before assuming configuration error.