FortiOS 4.3.5 is out

[ejhardin]

Downloading now... Now has support for Citrix XEN server.

[wraezor]

Is there still a good reason not to go to MR3? I steered well clear of it for the first few releases, but is it stablized now? This is going on a pair of 200Bs.

[cmberry]

I upgraded directly from 4.3.3 to 4.3.5, and everyting seems fine to me, about 24 hours later.

[wraezor]

Went from 4.2.9 to 4.3.5 on Feb 4th. No issues at all.

[mhe]

cmberry and wraezor, what devices are you using?

[Secure_IT_BE_Nick]

Still a lot of issues with memory and FGT80C. running at 75% again, after 2 months still not fixed, IF you hear someone from Fortinet it' s only to say that they know there' s a problem.

[Matthijs]

Nick, Is it the IPS engine that is using the memory? There are some known issues but there are also workarounds. You might want to open a support case for it ;)

[Lucascat]

Is it the IPS engine that is using the memory? There are some known issues but there are also workarounds

Can you tell me where can I find information about workaround? Thanks

[Secure_IT_BE_Nick]

Yes it is IPS, the workaround don' t work. We have tried to finetune it to compensate the memory problem, still nothing. The thing is, i made a ticket from the first moment we saw this problem, that was on the 6th of december. The only updates we get is just saying, yes there is a problem, and no we cannot fix it now.. that' s it... So the result is, device is running in conserve mode and no more changes to the firewall (cmdb error). If there' s a cluster we can reboot with rather small impact, if you are quickly enough we can change settings.

[ddskier]

ORIGINAL: nickpieters Yes it is IPS, the workaround don' t work. We have tried to finetune it to compensate the memory problem, still nothing. The thing is, i made a ticket from the first moment we saw this problem, that was on the 6th of december. The only updates we get is just saying, yes there is a problem, and no we cannot fix it now.. that' s it... So the result is, device is running in conserve mode and no more changes to the firewall (cmdb error). If there' s a cluster we can reboot with rather small impact, if you are quickly enough we can change settings.

Are people only experiencing this issue with the lower end models? How about the 110C or the 200B?

[veechee]

On the 60C I have loaded 4.3.5 on, my observation so far is that the memory management is slightly better than previous 4.3 releases. However, I just had the CPU usage running through the roof, mostly used by the SQL and HTTP processes. This required a reboot to fix.