When troubleshooting FortiWLM issues, it is helpful to submit the diagnostics file to Fortinet support for further analysis.

This article describes how to gather the diagnostics from FortiWLM.

The operation of gathering diagnostics on the FortiWLM could take a long time in a large network.
The data collection starts and the browser window displays the collection status and progress.
After the collection is complete, a message for the successful completion of the diagnostics generation is displayed.

From GUI.

- Go to Operate -> Tools -> Diagnostics.
- Select 'Generate Diagnostics'.

From CLI.

Enter the following command to start gathering diagnostics comprising of NM related logs and other files.

# diagnostics

Sample Output.
# diagnostics
ls: cannot access nm.gather*: No such file or directory
Getting process information ...
Getting system log information ...
Getting kernel information ...
Getting network information ...
Getting software information ...
Getting version information ...
Getting disk information ...
Getting NM data ...
cp: cannot stat '/opt/meru/images/upgrade_patch.log*': No such file or directory
Getting SAM data ...
Getting Rollback logs ...
Getting Spectrum data ...
Data gathering phase complete

/data/diagnostics/nm.gather.WLM.2020-12-24.16-39-20.tar.gz created
Use the ftp/tftp/scp option of the IOSCLI command to move this file off the machine.
Usage:copy /data/diagnostics/nm.gather.WLM.2020-12-24.16-39-20.tar.gz <ftp/tftp/scp>://<user_name>@<destinationip>/<destination path>

To view the diagnostics:
# cd diagnostics
# dir
total 1
-rw-r--r-- 1 root root 658201 Dec 24 16:39 nm.gather.WLM.2020-12-24.16-39-20.tar.gz
Once the diagnostics command has completed, use ftp/scp to export the diagnostics file to local PC.
# copy <diagnostics-filename.tar.gz> ftp://username@FTP-IP-Address/
For example:
# copy nm.gather.WLM.2020-12-24.16-39-20.tar.gz ftp://username@<ftp-ip>/