I have AWS FortiGate with T2.small instance size with the latest firmware version 7.2.3 and it keeps entering conserve mode, and I notice the following:
Any ideas on how to solve this!!!!
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
I had this issue. It seems to go back to version 7.0.x
Fortinet Support gave me a work around which kills the WAD process which is usually responsible for this. Scroll down a few messages...
https://community.fortinet.com/t5/Support-Forum/Fortios-7-0-x-memory-leak/m-p/208721/highlight/true#...
Hello,
I can't define exactly which process is responsible for this!
can you share how I can find it?
Beside I feel my case is slightly different specially with the threshold part
You are mostly hitting 798303
798303 |
The threshold for conserve mode is lowered. |
https://docs.fortinet.com/document/fortigate/7.0.8/fortios-release-notes/289806/resolved-issues
This is fixed from 7.0.8 and 7.2.4
my current OS is 7.2.3, what is your suggestion?
The 2 possible options I can think is 1. Move to 7.0.x version or 2. Wait for 7.2.4.
How long the system stays in conserve mode? Is it creating huge traffic disruption?
Actually, it does create huge impact, just this morning I have another appliance started to act the same, making huge business impact. I performed that last upgrade as they promise it will be solve but here we are again and I'm afraid even if they released a new update they problem will continue.
Is it possible/feasible to start a new instance in 7.0.9 and migrate the traffic to that and monitor?
Hello,
I have been engaged with Fortinet support and it's seems that there's a bug in the firmware "AGAIN", and they will release new FortiOS very soon and it's should fix this bug.
Regards,
Hello,
> FortiGate enters conserve mode when memory used"1585 MB" is below the red threshold"1769" and even below the green threshold.
The reported issue matches the internal engineering ticket 0798303.
Due to a miscalculation the conserve mode might be triggered before reaching the red threshold.
The cause got resolved in code in FortiOS 7.0.8 and 7.2.4.
> my current OS is 7.2.3, what is your suggestion?
FortiOS 7.2.4 got released recently, 7.0.8 is available since a longer time.
It's recommended to upgrade to 7.2.4.
> As a temporary solution I have raised red threshold.
Correct, as a workaround the thresholds should be increased:
config system global
set memory-use-threshold-extreme 97
set memory-use-threshold-green 90
set memory-use-threshold-red 95
end
And reverted back to the default after upgrading:
config system global
unset memory-use-threshold-extreme
unset memory-use-threshold-green
unset memory-use-threshold-red
end
Regards
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1517 | |
1013 | |
749 | |
443 | |
209 |
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.