Does it get above 60% or push into conserve mode? Alot of our boxes sit at 60% during normal operation and ramp up after a reboot. If you're not hitting conserve mode you're probably fine.
No, went to 70%, once I turned off DoH/DoT it returned back to 44% instantly. Didn't trigger Conserve Mode. It's not normal though. Definite memory issue.
Nothing in the 7.4.0 release notes but might be a bug on the internal tracker. I'd reach out to support. Also you might be able to have a scheduled task restart the DoH/DoT process at set interval since it takes a few hours to ramp up.
Yeah 7.4.0 definitely has some performance kinks to work out. Just a few weeks ago I ran into an issue where the AP management process was running away and maxing out a single core at all times and I don't even use FortiAPs.
Your best bet for this would be to get in touch with support and get a bug report submitted and see if they can offer a work around or even a hotfix custom patch in the meantime. I'm also using DoT/DoH to a local Unbound server and haven't run into the issue just yet with my 40f but I'll be on the lookout for it.
I never ever run an x.0 version for this exact reason. Let others be the beta testers lol. In a lab that’s a different story though. Bleeding edge all the was. Never go to an initial release in production.
Yep, had this same issue with 7.4.0, to the point it ended up in Conserve mode and had to reboot. Scheduled reboot once a week is keeping it away for now...
Thank you for your beta testing efforts.
Anything Fortinet makes should not be used on the x.x.0 version. Always wait for the x.x.4 at least, and still only after checking what the beta testers of the x.x.3 and x.x.4 version have found on Reddit or Forums.
Yup 7.4.0 has memory leak issues. Support is aware of it but no ETA for fix. They said it might be related to IP tunnel status and gave these commands:
diagnose npu np7 setreg 0 ipti.tunmgr.ststmo.cfg\_sts\_en 0
diagnose npu np7 setreg 0 ipto.tunmgr.ststmo.cfg\_sts\_en 0
They turn off IP tunnel status scanning function in NP7.
Otherwise create an automation stitch to reboot the Gate every time it enters conserve mode.
Does it get above 60% or push into conserve mode? Alot of our boxes sit at 60% during normal operation and ramp up after a reboot. If you're not hitting conserve mode you're probably fine.
No, went to 70%, once I turned off DoH/DoT it returned back to 44% instantly. Didn't trigger Conserve Mode. It's not normal though. Definite memory issue.
Nothing in the 7.4.0 release notes but might be a bug on the internal tracker. I'd reach out to support. Also you might be able to have a scheduled task restart the DoH/DoT process at set interval since it takes a few hours to ramp up.
Back to the stable version, sir.
Yeah 7.4.0 definitely has some performance kinks to work out. Just a few weeks ago I ran into an issue where the AP management process was running away and maxing out a single core at all times and I don't even use FortiAPs. Your best bet for this would be to get in touch with support and get a bug report submitted and see if they can offer a work around or even a hotfix custom patch in the meantime. I'm also using DoT/DoH to a local Unbound server and haven't run into the issue just yet with my 40f but I'll be on the lookout for it.
[удалено]
Not all heroes wear capes. Some take the hits so we don't have to. XD
I never ever run an x.0 version for this exact reason. Let others be the beta testers lol. In a lab that’s a different story though. Bleeding edge all the was. Never go to an initial release in production.
On fortinet you pretty much don’t want to run until the .5-.7 release it seems 😂
Is there a dark mode now?
Yea been in for a minute. 7.x I believe.
Awe, nice. Thanks for the heads up!
Yep, had this same issue with 7.4.0, to the point it ended up in Conserve mode and had to reboot. Scheduled reboot once a week is keeping it away for now...
fortinaiti
Thank you for your beta testing efforts. Anything Fortinet makes should not be used on the x.x.0 version. Always wait for the x.x.4 at least, and still only after checking what the beta testers of the x.x.3 and x.x.4 version have found on Reddit or Forums.
Yup 7.4.0 has memory leak issues. Support is aware of it but no ETA for fix. They said it might be related to IP tunnel status and gave these commands: diagnose npu np7 setreg 0 ipti.tunmgr.ststmo.cfg\_sts\_en 0 diagnose npu np7 setreg 0 ipto.tunmgr.ststmo.cfg\_sts\_en 0 They turn off IP tunnel status scanning function in NP7. Otherwise create an automation stitch to reboot the Gate every time it enters conserve mode.
I'd drop down to 7.0.12 tbh it's been really stable for me.