-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fortigate | conservemode | It seems like this check gives false positive with FortiOS 7.0.6 #83
Comments
Ok thanks, since the upgrade to 7.0.6 (coming from 6.4.x) we have the alarm all the time, but we cannot see this on the Fortigate itself ... |
We still have this now on FortiOS 7.0.9 |
Other modes, like CPU or MEM always return 0% on 7.0.9 - is this known, or worth opening an additional issue? |
Any update, this seems broken on any Fortigate now :( |
I checked the Script and got the Value for the total low mem Capacity on the device as a "0" Value instead of a real value so the check fails. I contacted FortiNet and they say patch to 7.4.x and 7.2.latest, i didn´t checked these versions yet. |
Interesting, we got a different response from FortiNet, saying, this mode was for 32 bit firewalls and on 64 bit conserve mode does not work like that anymore always returning 0... But i will look into thise FW versions. |
Anyone has a final verdict here? We have the issue on v7.0.12 atm |
OK we did a test on FortiOS 7.2.6 , but the same issue. Something must have changed / be wrong with the check in general |
Anyone experienced this? Any way to verifiy?
Originally posted by @HOSTED-POWER in #63 (comment)
The text was updated successfully, but these errors were encountered: