6.2.1 on a 60E. New location for a client. Having above issue. diag test
authserver ldap ****** username password works on a cli. Test
Credentials gets the ldap_-5
Mike@ftnt wrote:Hi Aron1, This is one known issue in FortiOS 6.2.1, and
it will be fixed by 6.2.2.The workaround is to add FAP's IP or subnet
into admin trusthost list. Cheers,Mike Hi Mike... Thanks for confirming
that... We figured that out as well....
Side note... While upgrading to 6.2.1, we are seeing a bug... If your
admin account is locked down to certain IP address ranges, and your WIFI
SSID isn't in the ip range, you might not be able to bring up the AP's
after upgrading to 6.2.1. We thought...
Vinicius wrote:Hello,Anyone having this issue on 6.2.1?Every week i must
restart those cause they run into conserve mode.Already
set-memory-threshold-green to 89 and red to 90. I'm running 6.2.1 on a
30E and on 60E. I have a client with 12 forti FW's...
Try this... get sys perf top ID app that is running the most memory. For
me, I have seen both ipsmonitor and wad causing the mem issue.
Restarting the problematic thread gets you out of conserve mode, but
isn't a fix.This will restart the app:diagnos...
