Created on 11-30-2023 09:49 PM Edited on 12-13-2024 01:39 AM By Jean-Philippe_P
Description | This article describes the factors that lead to FortiGate entering Conserve Mode during scheduled or manual FortiGuard updates. |
Scope | FortiGate. |
Solution |
Desktop FortiGate hardware models, with memory usage already at 64-72% or higher, might activate memory conserve mode during FortiGuard updates. For example, FortiGate-30E, 40F, 60E, 60F, 70F, 80F, 90G etc. Refer to the Form Factor field in the product datasheet to identify the Hardware type.
A FortiGuard update process may consume an additional 10-20% of memory, potentially surpassing the conserve mode threshold. Instances of conserve mode are especially evident during the download of the Internet Service Database and other database objects, requiring extraction and subsequent processing during updates. This recommendation applies not only to desktop FortiGate hardware models but also to Rackmount FortiGate devices, especially if the unit is already experiencing high memory consumption.
To prevent FortiGate from Triggering Conserve Mode during FortiGuard Updates:
config system autoupdate schedule
config system fortiguard
config system global
Use mini or regular ISDB if 'on-demand' is not available, which is a small-sized Internet Service database with very limited IP addresses:
config system global
For more information, refer to:
|
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 2024 Fortinet, Inc. All Rights Reserved.