Created on ‎11-23-2023 06:37 AM Edited on ‎08-29-2025 01:10 AM
Description |
This article describes an optimization steps to free up resources, with a primary focus on memory on FortiGate Desktop and FortiWiFi models such as 40F, 60E, 60F, 80E, 90E, and Rugged 60F (only the 2 GB versions). These devices are often configured to run multiple features simultaneously, operating in oversubscription due to misuse or incorrect sizing. Any system operating constantly above 65% of RAM usage is at high risk of performance degradation or service disruption due to the lack of available headroom to handle unexpected or unpredictable loads, which are common in security infrastructure. As part of the optimization process, it is strongly recommended to use the FortiOS version appropriate for the FortiGate model in use.
Another important point is the maximum capacity of FortiGate Desktop (Entry-Level) devices, including awareness of their limitations and correct deployment by assigning appropriate roles. Accurate sizing helps avoid performance issues caused by misplacement or misuse. Refer to Technical Tip: FortiGate Role Alignment and Capacity Planning for further details on the importance of correct sizing.
Below also are available some key points to explain the restrictions affecting entry-level FortiGate devices (with less than 2GB of RAM) starting from FortiOS version 7.4.4.
|
Scope | FortiGate. FortiOS 7.x. |
Solution |
Suggested actions:
Configuration steps:
Global System Configuration:
set memory-use-threshold-extreme 97 end
IPS Configuration:
config ips global set np-accel-mode none set engine-count 2 set exclude-signatures none end
Session TTL Configuration:
set default 300 config port edit 0 set protocol 17 next end end
DNS Configuration:
set dns-cache-limit 600 end
FortiGuard Configuration:
config system fortiguard set webfilter-cache-ttl 600 set frequency daily end
Automation Action Configuration:
edit "RestartWAD" set action-type cli-script next end
Automation Trigger Configuration:
config system automation-trigger edit "Enters Conserve Mode" set event-type low-memory next end
Automation Stitch Configuration:
edit "Restart WAD during Conserve Mode" set trigger "Enters Conserve Mode" config actions edit 1 set action "RestartWAD" next end next end
Auto-Script Configuration:
config system auto-script edit restart_IPSengine set interval 43200 next end
Log optimization:
config log memory setting config log disk filter
Disabled the security rating submission:
Reduce internet-service-database:
exe update-ffdb-on-demand <----- To manually trigger an update of the FortiGuard Web Filtering Database (FFDB) on demand.
In conclusion, these steps can make smaller FortiGate devices handle memory better. It is important to change these settings to fit a given network's specific needs.
Related articles:
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.