Description
This article describes that FortiAP-F and FortiAP-G randomly reboots several times a day and how to resolve it.
Scope
FortiAP-F versions before v7.2.2 build 0318 and up, all versions of FortiAP-G.
Solution
It is possible to notice that units are rebooting if the following logs on the FortiGate Wifi Event Log are observed:
logid="0104043552" type="event" subtype="wireless" level="notice" vd="root" logdesc="Physical AP leave" sn="FPXXXFTXXXXX"
Along with the following log descriptions:
- AC daemon reset timer expired (Fair Health).
- ECHO req is missing (Fair Health).
- Control message max. re-transmission limit reached (Fair Health).
- Physical FortiAP fails.
All other expected causes for the entries above have been discarded as per best practices described in the following KB article:
Technical Tip: How to interpret FortiWiFi or FortiAP various 'Health Status' reasons and the best pr...
Therefore is a reasonable suspicion if along with those verifications, on the FortiAP health menu, connection uptime is fair very recently from suspicious affected FortiAP.
It could be an indicator the FortiAP is affected by one or more known kernel panic issues resolved on our latest releases:
Resolved issues
Always try to upgrade the FortiAP series device to our latest GA release available in our support site, at the moment those messages can be observed. Then monitor for a couple of days and if messages still appears on Fortigate wifi event logs, proceed as requested in this article.
Try latest GA on family v7.4.X and v7.6.X
If messages likethose mentioned in this KB article still can be observed or other issues start to happen after the upgrade, contact TAC and provide the following information on a support ticket to start an in-depth investigation.
Download and provide config files, Event Log files for System Events, and Wi-Fi events filtered from Serial Number, an affected FortiAP, and a FortiGate.
Use putty to gather all diagnose info and share it with us in clear text format: Technical Tip: How to create a log file of a session using PuTTY
Provide the output of the following commands on the FortiGate:
get sys status
get hardware status
diag debug crashlog read
show wireless-controller setting
show wireless-controller global
show wireless-controller timmer
show wireless-controller wtp
show wireless-controller wtp-profile
show wireless-controller vap
diagnose wireless-controller wlac -c wtp
Provide the output of the following commands in the FortiAP where the problem occurs:
cfg -s
fap-get-status
date
fap-tech
Refer to Technical Tip: How to check why FortiAP got Offline from FortiGate for information on the FortiAP CLI in cases where it is difficult to gather info from the affected FortiAP. The last section explains how to enable SSH access to FortiAP.
All other diagnose commands from FortiAP mentioned in the above article were replaced by the 'fap-tech' command on newer versions, as recommended in this article.
