Description
This article describes when logs need to be collected for the FortiAP random reboot issues.
Solution
Following are the commands need to be collected to analyze the FortiAP random reboot issues.
1) Use the below commands on the FortiAP CLI to make the admin timeout to '0' where the FortiAP CLI will not time out.
cfg -a ADMIN_TIMEOUT=0
cfg -c
2) Open 2 x putty sessions to the specific AP from the FortiGate using the following command. Capture the putty sessions to a separate text file.
# execute ssh admin@<IP address of the FAP>
3) Execute the below command in one of the Putty session. Let it run until the FortiAP reboots.
cw_diag repeat 1000000 2 "cw_diag sys-performance;date;brctl show;arp -an;ifconfig eth0;ifconfig br0;ping -c 1 -s 1000 <default gateway ip>; top -n 2"
'top' command to understand the services and also which service takes more CPU at the time when the issue is seen.
4) Execute the below command on another putty session from the FortiAP CLI. Let it also run until the FortiAP reboots.
#cw_debug app cwWtpd 0x7fff
#cw_debug on
Above command is for the WTP daemon logs to see if something happens with the WTP daemon itself.
5) Along with the above, FortiAP uplink port captures from the switch side is also required. This will help us to analyze whether any broadcast or any specific packets are seen at the time when the FortiAP goes for the reboot.
