FortiOS 5.2.10 is out

[simonpt]

http://docs.fortinet.com/...2.10-release-notes.pdf

[romanr]

Selective wrote:

 Only Fortimanager integration with FMG 5.2.9 gives us some minor troubles.

We also use FMG 5.2.9, can you explain what troubles you are experiencing ?

FMG tries to purge objects in replace-msg groups and has troubles on some newer AP hardware... Nothing that makes real trouble. But Fortigates might not show up in sync!!

[ddskier]

Update:   Installed on two production 200D and a single 100D.   No issues.

Will roll it out to another 12 100D today.

[MikePruett]

Popped it on a few 100D's yesterday with no issue.

[keij]

Have upgrade to 5.2.10.

No problem with operation so far.

But there is something I was interested in.

It seems that the NAT option is not working.(NAT option "Fixed Port") As a result of referring to the session information, the source port number has not changed.

I have not checked whether it was functioning in the previous version.

It may be a problem peculiar to this version.

[Carl_Wallmark]

I have upgraded about 40 boxes, various models, 60D, 92D, 100D, 200D.

No issues so far! 

[BarryM]

This release fixed the high CPU utilization in my 300C.

There was no way my unit was maxed out in features and settings. Now the CPU barely spikes.

[laf]

Hi guys,

I am currently using a cluster A-P:

FortiGate-100D v5.2.4,build0688,150722 (GA)

being managed by

get system status 

Platform Type : FMG-VM64 Platform Full Name : FortiManager-VM64 Version : v5.4.1-build1082 160629 (GA)

Now if I update Fortigate cluster to 5.2.10 ; what should I do exactly on FGM?

As you can guess it's my 1st time I have to update a Fortigate and take care also on the FortiManager. This compatibility document shows software wise is supported, but what else is needed on FortiManager. Do I need to rediscover Fortigate? Or anything else?

[Jonas_Reusser]

We updated all our Fortigates. No issues so far. Seems to be a stable version.

60D, 100D, 311B

[BarryM]

Of course now my FortiWifi 30D is a brick. I don't know if the update is responsible or it decided to quit.

I reset to factory, downgraded, reloaded 5.2.10 etc. At every step it would run for 5 minutes and then freeze up.

Even the basic config doesn't resolve the problem.

It's a brick.

update.

Support seems to have resolved the problem. It was necessary to download an HQIP image and run diags. The problem may have been flash corruption. I had to reset to factory but my config is not too complicated. So far so good with the 5.2.10 image.

I will tweek the config later. The logs are being reviewed.

[MikePruett]

BarryM wrote:

Of course now my FortiWifi 30D is a brick. I don't know if the update is responsible or it decided to quit.

I reset to factory, downgraded, reloaded 5.2.10 etc. At every step it would run for 5 minutes and then freeze up.

Even the basic config doesn't resolve the problem.

It's a brick.

update.

Support seems to have resolved the problem. It was necessary to download an HQIP image and run diags. The problem may have been flash corruption. I had to reset to factory but my config is not too complicated. So far so good with the 5.2.10 image.

I will tweek the config later. The logs are being reviewed.

Nothing quite like bricking a device to get the blood flowing :p