Technical Tip: Logs to be collected for AP reboot issues on the FortiWLC

1. Make a note of the AP-IDs of the recent APs that rebooted using the below commands:

show ap
show ap-reboot-event
show ap-reboot-count

show ap-reboot-top10

2. 'Conn' to these affected APs and check if it prints any log using the below commands:

conn ap <AP_ID>
ap-id>sys gl
ap-id>flashcmds show all

3. If yes, AP would display the log prints. Then, erase the AP flash, to collect fresh logs if these APs reboot again.

ap-id>file areaerase logk0
ap-id>file areaerase logk1

4. If the same set of APs reboots again, then execute the below commands that will contain fresh logs and attach them to the Fortinet Support Ticket:

conn ap <AP_ID>

ap-id>sys p

ap-id>sys exec cmd dmesg

ap-id>dmesg

ap-id>flashcmds show all

ap-id>config show ethernet

ap-id>sys gl

ap-id>sys exec cmd cat /proc/slabinfo
ap-id>sys exec cmd cat /proc/meminfo
ap-id>sys load

5. Also, attach the FortiWLC System Diagnostics file to the Fortinet Support Ticket for analysis: 

Navigate to FortiWLC GUI -> Maintenance -> Diagnostics -> Under Collect Diagnostics, Select 'System Diagnostics' -> Hit 'System Diagnostics'.

    6. The newer FortiWLC v8.6.7 firmware has multiple AP stability fixes: Fixed Issues v8.6.7.