We reverted FortiOS 6.0.9 back to 6.0.8 after nine days, because memory
usage went up from 41% to 46% and kept growing.At cli, "diag sys
top-summary '-n 5 --sort=mem' " showed 6.0.9:PID RSS CPU% ^MEM% FDS
TIME+ NAME * 208 1G 0.0 17.6 637 34:16.79 ips...
We upgraded our FAZVM to 6.0.1 from 5.6.4 and needed to roll back. Two
problems after the upgrade:[ol]FAZ ran fine at the beginning but
suddenly FortiGates stopped sending logs to FAZ until we re-entered the
credentials for each firewall on the Devic...
We have a 100E updated to 5.6.7 five days ago. It did not have the
bcm.user high cpu problem. CPU usage has been changing between 2 to
4%.Another 100E running 5.6.6 with 49 days uptime. bcm.user CPU usage is
also between 2 to 4%.
The Security Fabric marketing hype does not make firewall admins' jobs a
lot easier. I agree with Ken (emnoc) that "... we don't have enough
builds that are proven good." We don't need many choices. We need better
QA firmware.
We ran into the same network problem as gdoornenbal.We used to have
port1 mapping to "Network Adapter1" on 5.4.4. We lost the network
connection after upgrade to 5.6.1.We had to go to VMware to disable
"Network Adapter1" and enable ""Network Adapter4...
The fortianalyzer compatibility doc was updated on Dec 14, 2017 and now
FAZ 5.4.4 is compatible with FortiOS
5.4.7.https://docs.fortinet.com/d/fortianalyzer-compatibility
