This problem persist to me: "memory traffic log is 95% full", although if i make this commands:
config log memory setting set diskfull overwrite
Any idea? Thanks!
Solved! Go to Solution.
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.
That looks properly configured, actually. There are warning thresholds set when the log memory approaches being full. If you have set the FortiGate to overwrite the oldest file once it reaches a certain age or size, it will simply delete the oldest file and open a new one. The threshold alerts shouldn't be anything to get alarmed about.
Regards, Chris McMullan Fortinet Ottawa
It can not disable , but it can change setting at :
config log memory global-setting set max-size 163840 set full-first-warning-threshold 75 set full-second-warning-threshold 90 set full-final-warning-threshold 95 end
If you increase max-size, it may have less chance to report this event log, thanks.
<When i get these "memory traffic log is 95% full" the Fortigate block my GUI conections.>
That should be a bug, one way you may disable "traffic log " on policy, heavy traffic log to memory is useless. Thanks.
That looks properly configured, actually. There are warning thresholds set when the log memory approaches being full. If you have set the FortiGate to overwrite the oldest file once it reaches a certain age or size, it will simply delete the oldest file and open a new one. The threshold alerts shouldn't be anything to get alarmed about.
Regards, Chris McMullan Fortinet Ottawa
It can not disable , but it can change setting at :
config log memory global-setting set max-size 163840 set full-first-warning-threshold 75 set full-second-warning-threshold 90 set full-final-warning-threshold 95 end
If you increase max-size, it may have less chance to report this event log, thanks.
Jeff_FTNT wrote:It can not disable , but it can change setting at :
config log memory global-setting set max-size 163840 set full-first-warning-threshold 75 set full-second-warning-threshold 90 set full-final-warning-threshold 95 end
If you increase max-size, it may have less chance to report this event log, thanks.
Hi Jeff_FTNT, thanks for reply. When i get these "memory traffic log is 95% full" the Fortigate block my GUI conections. If i increase the max-size, i only delays carrying the problem, it will relock. How can avoid this? The logs increase very quickly.
<When i get these "memory traffic log is 95% full" the Fortigate block my GUI conections.>
That should be a bug, one way you may disable "traffic log " on policy, heavy traffic log to memory is useless. Thanks.
Jeff_FTNT wrote:<When i get these "memory traffic log is 95% full" the Fortigate block my GUI conections.>
That should be a bug, one way you may disable "traffic log " on policy, heavy traffic log to memory is useless. Thanks.
Yes, something is wrong with the firewall, i not use the memory log often, so i'll disabled it, and use only syslog server.
Thanks for reply
Yes, something is wrong with the firewall, i not use the memory log often. I'll disabled it i use only syslog server.
Thanks for reply
Hello,
Other option is change the inspection mode from Proxy mode to Flow-Based.
Proxy : More security more resources
Flow-based: Less resources but you lose features like DLP.
In the new FortiOS 6.2 you can merge the inspection modes by policy :)
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 |
---|---|
1660 | |
1077 | |
752 | |
443 | |
220 |
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.