Staff

Troubleshooting Tip: Memory debugs needed when creating a bug ticket

April 24, 2026 at 3:27 PM
0 replies
1739 views

Description

This article lists the CLI commands that should be provided to developers when creating an internal Bug ID related to a suspected FortiGate memory leak.

Scope

FortiGate v7.2.6+, FortiGate v7.4.0+, FortiGate v7.6.0+.

Solution

CLI commands:

get system status
fnsysctl date
get sys perf status

diagnose autoupdate version

diagnose sys session stat
diagnose hardware sysinfo memory
diagnose hardware sysinfo slab
diagnose sys vd list | grep fib
diagnose sys mpstat 1 5
diagnose sys top-all 2 30
diagnose sys top-mem 10
diagnose firewall packet distribution
diagnose snmp ip frags
fnsysctl df -k
fnsysctl ls -l /tmp
fnsysctl du -i /tmp
fnsysctl du -a /tmp
fnsysctl du -a / -d 1
fnsysctl du -i /dev/shm
fnsysctl du -a /dev/shm
fnsysctl du -i /node-scripts
fnsysctl du -a /node-scripts

Note: Super Admin privileges are necessary to run the 'fnsysctl' command. Otherwise, FortiGate will return an error. For more details, see Technical Tip: fnsysctl command returns Unknown action 0.

It is also possible to attach the output of the commands from this related article:

Technical Tip: Memory Debugs