Fortinet Document Library

Version:

Version:

Version:

Version:

Version:


Table of Contents

Handbook

diagnose commands

You can use the CLI diagnose commands to gather diagnostic information that can be useful to Fortinet Customer Care when diagnosing any issues with your system. The commands are similar to the Linux commands used for debugging hardware, system, and IP networking issues.

The most important command for customers to know is diagnose debug report. This prepares a report you can give to your Fortinet support contact to assist in debugging an issue.

The following examples show the lists of diagnose commands:

FortiADC-VM # diagnose ?

debug debug

hardware hardware

llb llb

netlink netlink

server-load-balance server-load-balance

sniffer sniffer

system system

 

FortiADC-VM # diagnose debug ?

application set/get debug level for daemons

cli set/get debug level for CLI and CMDB

config-error-log read/clear config error information

crashlog crashlog

disable disable debug output

enable enable debug output

flow flow

info show debug info

kernel set/get debug level for kernel

report Report for tech support.

timestamp timestamp

 

FortiADC-VM # diagnose hardware get ?

deviceinfo list device status and information

ioport read data from an I/O port

pciconfig list information on PCI buses and connected devices

sysinfo list system hardware information

 

FortiADC-VM # diagnose netlink ?

backlog set netlink backlog length

device display network devices statistic information

interface netlink interface

ip ip

ipv6 ipv6

neighbor netlink neighbor

neighbor6 netlink neighbor for ipv6

route netlink routing table

route6 netlink routing table

tcp display tcp statistic information

udp display udp statistic information

 

FortiADC-VM # diagnose system ?

top show top process

vm check vm state

 

For details, see the FortiADC CLI Reference.

diagnose commands

You can use the CLI diagnose commands to gather diagnostic information that can be useful to Fortinet Customer Care when diagnosing any issues with your system. The commands are similar to the Linux commands used for debugging hardware, system, and IP networking issues.

The most important command for customers to know is diagnose debug report. This prepares a report you can give to your Fortinet support contact to assist in debugging an issue.

The following examples show the lists of diagnose commands:

FortiADC-VM # diagnose ?

debug debug

hardware hardware

llb llb

netlink netlink

server-load-balance server-load-balance

sniffer sniffer

system system

 

FortiADC-VM # diagnose debug ?

application set/get debug level for daemons

cli set/get debug level for CLI and CMDB

config-error-log read/clear config error information

crashlog crashlog

disable disable debug output

enable enable debug output

flow flow

info show debug info

kernel set/get debug level for kernel

report Report for tech support.

timestamp timestamp

 

FortiADC-VM # diagnose hardware get ?

deviceinfo list device status and information

ioport read data from an I/O port

pciconfig list information on PCI buses and connected devices

sysinfo list system hardware information

 

FortiADC-VM # diagnose netlink ?

backlog set netlink backlog length

device display network devices statistic information

interface netlink interface

ip ip

ipv6 ipv6

neighbor netlink neighbor

neighbor6 netlink neighbor for ipv6

route netlink routing table

route6 netlink routing table

tcp display tcp statistic information

udp display udp statistic information

 

FortiADC-VM # diagnose system ?

top show top process

vm check vm state

 

For details, see the FortiADC CLI Reference.