FortiOS 5.6.11 is out

[fgtenterprise]

PATCH NOW if you are running 5.6.7 or lower!  2018-13379 is being actively exploited in the wild.

Resolves the SSLVPN LDAP authentication issue that surfaced when Fortinet patched for CVE 2018-13379.  Also addresses other critical CVEs like 2018-13383 and 2018-13382.

Release notes

Patch successful in our HA environment, coming from 5.6.6.  We updated to 5.6.8 then 5.6.11 per the recommended upgrade path.

[Lucascat]

Upgraded two FG60D without problems 

[TecnetRuss]

So far, of the customer 30E's, 60E's, 61E's and a 100EF we've upgraded from 5.6.9 to 5.6.11 last week, all have been smooth and successful with no issues.  All stable and resource usage looks normal.  Be patient with any 30D/30E - it can take about 10-15 minutes and it's "normal" to get an "upgrade is taking longer than normal" warning.

Russ

[Frosty]

Upgraded our FG200E a few days ago.  Everything looks good and stable.

[Lucascat]

System link-monitor is not working as expected. When the gateway ping comes back up, the routes remains down anyway. I have to disable and re-enable link-monitor for that interface.

[Lucascat · Accepted solution]

link-monitor bug confirmed by Fortinet. Upgraded to 6.0.6 without problem

[lubyou]

Hi,

We upgraded about 25 fortigates to 5.6.11 about one and a half weeks ago (60D/60E/100D/100E, mostly), and out of those 25 we have three so far that are essentially unusable due to the CPU being maxed out.

They process little to no packets, remote SSH is not possible, etc.

The only thing that helps is to power cycle the units.

Anybody else with that issue?

Thanks

[paulo_borchardt]

I have the same problem in 5.6.11 on several appliances.

[Kommissar]

lubyou wrote:

We upgraded about 25 fortigates to 5.6.11 about one and a half weeks ago (60D/60E/100D/100E, mostly), and out of those 25 we have three so far that are essentially unusable due to the CPU being maxed out.

paulo.borchardt wrote:

I have the same problem in 5.6.11 on several appliances.

On what models exactly are you having this problem?