v5.0.7 Resolved/Known Issues - How affect the FAZ?

[AtiT]

Hi, I have a FAZ-VM64 running on v5.0.5. I did not upgrade to 5.0.6 because in release notes there were known issues that I cound not accept. In v5.0.7 it seems to be OK but I have some questions: Known Issues: 0237692 The disk quota value is not saved after promoting a device. 0242641 On a FortiAnalyzer VM, the system may consume high CPU resources and affect response time. How the first issue with the disk quota affect the FAZ? Does anyone have FAZ VM with the new version of OS? Is everything OK? What about the second issue? Do you see some more CPU usage? Regarding the version v5.0.6: 0236228 Some registered device are lost after upgrading to v5.0.6. 0228960 FortiAnalyzer cannot generate a report with a chart that has more than 1500 rows. 0218622 FortiAnalyzer does not generate reports based on global font settings set at the section level and at the layout level. 0233112 Use chart description instead of chart name when in generating a report. 0236004 After upgrade, all custom reports and output profiles are missing. 0243494 FortiAnalyzer needs to support query when entries are longer than 2048 characters The first issue - did you recognized any missing device? Were the custom reports and output profiles missing? The release notes say: Upgrading from FortiAnalyzer v5.0.6 or earlier FortiAnalyzer v5.0.7 has re-sized the flash partition storing system firmware. In order to accommodate the re-sizing, you MUST upgrade to FortiAnalyzer v5.0.6 first. The secondary firmware and System Settings stored in the partition will be lost after upgrade. Please reconfigure System Settings as needed. In VM environments, you will need to change the hard disk provisioned size to 513MB or more before powering on the FortiAnalyzer VM. In VM environment should I upgrade to 5.0.6 first also?

[pcraponi]

I' ve upgrade a VM to 5.0.7 without issue at now.. I' ve re-sized the primary disk to 576MB first... After upgrade all data will be rebuilding automatically. For you, the best are open a TAC case... The will investigate with developers to reply..

[Matthijs]

It seems the quota for logging has moved back from Log array to Log device so if you had provisioned 10GB for a log array it will now use 20GB (10GB per device instead of the log array?)

[AtiT]

Hi, I received answer from Fortinet TAC: Firstly upgrade to 5.0.6. Resize the disk and upgrade to 5.0.7. This is the same for the VM. Thank you guys.