fortigate | conservemode | It seems like this check gives false positive with FortiOS 7.0.6

[sgruber94]

    It seems like this check gives false positive with FortiOS 7.0.6

Anyone experienced this? Any way to verifiy?

Originally posted by @HOSTED-POWER in #63 (comment)

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

[jhuebner79]

Other modes, like CPU or MEM always return 0% on 7.0.9 - is this known, or worth opening an additional issue?

[PatrickSchmidtSE]

Any update, this seems broken on any Fortigate now :(

[sgruber94]

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.
my $oid_lowmem_capacity = ".1.3.6.1.4.1.12356.101.4.1.10.0";

I contacted FortiNet and they say patch to 7.4.x and 7.2.latest, i didn´t checked these versions yet.

[PatrickSchmidtSE]

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

[dkolasinski]

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. my $oid_lowmem_capacity = ".1.3.6.1.4.1.12356.101.4.1.10.0";

I contacted FortiNet and they say patch to 7.4.x and 7.2.latest, i didn´t checked these versions yet.

This is the core of the problem. It is probably unfixible till FG fixes above OID. I tried to find another way to fix it but there is just not enough data to do it.