FortiADC enhances the scalability, performance, and security of your applications whether they are hosted on premises or in the cloud.
Article Id 245037

This article describes which information should be collected and shared with the TAC-Support in order to analyze the root cause of a crash event.




From CLI, collect the output of the commands below, the latest ones are related to the crash event that was recorded in FortiADC:


# exe date

# get sys status

# get sys performance

# diagnose hardware get sysinfo cpu

# diagnose hardware get sysinfo interrupts

# diagnose hardware get sysinfo partition

# diagnose hardware get sysinfo df

# diagnose hardware get sysinfo memory

# get sys ha-status

# get sys vdom-status

# diagnose system top    <-----Press 'Shift + P' 5 times. (sort by CPU usage).

# diagnose system top    <-----Press 'Shift + M' 5 times. (sort by MEM usage).

# diagnose tech-report

# fnsysctl ls var/log


# diagnose crash list

# diagnose crashlog upload <ftp | tftp> <file_name | all> <TFTP-Server>




(P) FortiADC-10 (root) # diagnose crash list

6.6M Oct 5 16:32 named-4032-1665005553.gz

6.5M Oct 5 16:17 named-4861-1665004653.gz

6.6M Oct 5 15:58 named-4674-1665003523.gz

6.5M Oct 5 15:47 named-4791-1665002833.gz

6.5M Oct 5 11:30 named-4486-1664987401.gz


(P) FortiADC-10 (root) # diagnose crashlog upload tftp

<file_name>    file name

all    all log file


(P) FortiADC-10 (root) # diagnose crashlog upload tftp all

crash.tar            100% |****************************************************************************************************************************************************************************************| 33529k  0:00:00 ETA


Share this information collected and a backup-configuration with the TAC-Support.