Product

FortiGate

Next-generation firewall platform and the control point for many Fortinet secure networking designs.

Quick referencesOfficial documents and operational shortcuts

Data SheetFortiOS Data Sheet →Verified Sep 2026

DocumentationFortiGate Docs →Verified Sep 2026

MatricesFortiGate Matrix →Official FortiGate Matrix →

ToolsFortiGate Finder →Compare FortiGate models →FortiLink Compatibility Tool →FortiGate/FortiAP Compatibility →FortiGate OS Recommendation →

CLICLI Cheat Sheet →InManDis

Ordering GuideFortinet Ordering Guides →Verified Sep 2026

CLI quick reference

Extended CLI Reference

FortiGate CLI Cheat Sheet →

Common operational and troubleshooting starting points. Confirm syntax against the FortiOS release before production use.

Health & status

get system status
get system performance status
diagnose sys top 1 20
diagnose debug crashlog read
get router info routing-table all
diagnose vpn tunnel list

Troubleshooting CLI

diagnose sys session list
diagnose sys session filter clear
diagnose sys session filter src <SOURCE-IP>
diagnose sys session filter dst <DESTINATION-IP>
diagnose sys session list

diagnose sniffer packet any 'host <IP>' 4 0 l

diagnose debug reset
diagnose debug flow filter clear
diagnose debug flow filter addr <IP>
diagnose debug flow show function-name enable
diagnose debug flow trace start 100
diagnose debug enable
# reproduce the issue
diagnose debug disable
diagnose debug flow trace stop

execute ping <IP>
execute traceroute <IP>
get router info routing-table details <DESTINATION-IP>

Tip: Always stop debug output when finished. Packet captures and flow debug can generate significant output on busy systems.

Troubleshooting framework

Step	What to do
1. Symptoms	Write down exactly what is failing, affected scope, start time and last known-good state.
2. Health	Check CPU, memory, interfaces, HA/control-plane status and recent configuration changes.
3. Path	Validate L1/L2/L3, routing, policy, session state and dependencies in that order.
4. Logs	Correlate system/event/traffic logs with packet captures and targeted debugs.
5. Version	Check release notes, known issues, compatibility and lifecycle before assuming configuration error.