Technical Tip: How to collect information specifically for FortiGate model FGR-60F low-end models that enter conserve mode in a script

[bkarl]

Description	This article describes a quick way to collect information for FortiGate model FGR-60F low-end models that enter conserve mode in a script. The information to be collected is specifically for this range of FortiGate models and intended for use in a ticket submitted to the Support TAC team.
Scope	FGR-60F/FGR-60F-3G4G.
Solution	First, attempt the optimization highlighted in Troubleshooting Tip: How to optimize memory usage specifically for FGR-60F low-end models. Try to collect system information. Refer to Technical Tip: FortiGate monitoring script for continuous information collection. It is necessary to capture the status before and after the issue and then submit a ticket with TAC. Include the following collection commands:  fnsysctl date get system status get hardware status get sys perf status get sys perf firewall statistics diagnose autoupdate versions diagnose sys session stat diagnose hardware sysinfo memory diagnose hardware sysinfo slab diagnose hardware sysinfo shm diagnose sys vd list | grep fib diagnose sys mpstat 1 5 diagnose sys top-all 2 50 diagnose sys top-mem 20 diagnose sys top-fd 20 diagnose snmp ip frags diagnose ips session status diagnose ips memory status diagnose ips raw status diagnose ips session performance diagnose ips session list by-mem diagnose wad memory report diagnose debug report fnsysctl df -k 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 required to run the 'fnsysctl' command.