Technical Tip: Conserve mode changes in FortiGate 5.6 and above
Description
This article describes the changes to conserve mode self protection mechanisms starting in version 5.6.
Scope
FortiGate version 5.6 and above.
Solution
The main differences are as follows:
- No more distinction between 'kernel' versus 'Proxy' or 'system' types of conserve mode.
- Definitions for 3 thresholds: 'green', 'red', 'extreme', all adjustable through the CLI.
- A new trigger based on 'memory used'.
- New event logs.
- New diagnose command 'diagnose hardware sysinfo conserve'.
- New conserve mode stats in proxy stats via 'diag sys proxy stats all' (see the conserve_mode line).
3 memory thresholds: green, red, and extreme.
'red' and 'extreme': Both 'red' and 'extreme' are thresholds to enter in 'conserve mode' when the system memory used is over their thresholds.
• Red: FortiGate enters conserve mode and No Quarantine or Sandboxing
• Green: FortiGate exits conserve mode
Configurable thresholds.
Though it is recommended to keep the default memory threshold, a new CLI command has been added to allow administrators to adjust the thresholds.
- Red: 88% of total memory is considered "used memory"
- Extreme: 95% of total memory is considered "used memory"
- Green: 82% of total memory is considered 'used memory'.
Configuration (CLI only):
Diag command:

