Fortinet white logo
Fortinet white logo

Resolved Issues

Resolved Issues

The following issues have been fixed in FortiAnalyzer version 6.4.7. To inquire about a particular bug, please contact Customer Service & Support.

Device Manager

Bug ID Description
716486 FortiAnalyzer still populates the unauthorized device list even after detect-unregistered-log-device is set to disable.
731063 FortiAnalyzer supports FortiAuthenticator-300F.

FortiView

Bug ID Description
719441 FortiView may return sql-report dataset query error when Export to Report Chart in FortiClient Software inventory.
721008 Threats > Compromised Hosts may not be able to acknowledge compromised hosts when the end user is not a known IP.
723194 Secure SD-WAN Monitor Packet Loss widget may show no data.

724435

SD-WAN performance status widget may be empty if one of the SD-WAN members is down.

727056 SD-WAN Monitor may show incorrect bandwidth.
734359 FortiAnalyzer may return an error when applying source IP filter and exporting data to PDF with Top Browsing Users.

Log View

Bug ID Description
662830 FortiAnalyzer daylight adjustment does not take affect for real-time logging until rebooting the system.
688619 Logs received from FortiClient show logs with +1 hour in the time than the actual time on the end device or FortiAnalyzer.
715960 FortiClient Device ID takes FortiClient EMS SN value when displaying the log information from the historical view.
724223 Device list in Log View does not show correct devices after switching ADOMs.
726340 oftpd may not work properly if many log requests are received at the same time.

Others

Bug ID

Description

621473 FortiSOC is missing in cloud-based VMs.

682539

Local Connector Update Endpoint may fail due to endpoint's record contains unicode characters.

723352 oftpd may have memory leaks when the system has 2800+ FortiGate devices within CSF ADOMs.
723638 The dvmcmd process may crash when running TAC report.
724837 Redis server may consume high CPU usage when there are many ADOMs with many devices.
726782 The Percent of used memory is much higher in 7.0 than 6.4.
731070 FortiAnalyzer should add support for FortiNAC v9.1 in supported-platforms.
731319 There may be high memory usage on logfwd with FortiAnalyzer collector.
735760 FortiAnalyzer-200F may be slow with high CPU usage.

Reports

Bug ID Description
715680 Default chart VPN User Logins may return different values in two reports for the same device or data range.
717557 FortiAnalyzer reports may be empty when enabling LDAP Query.
718172 Report may be showing user or source as malicious code.
726688 All predefined report/template/chart/macro/dataset may be missing from newly created ADOM after a reboot.
734152 Report group filter may not work in FortiProxy ADOM.
734167 Report log field filter drop-down may be missing pick-list in non FortiGate ADOM.

System Settings

Bug ID Description
667488 Read-only user should not be able to change RAID level from GUI.
712043 HA cluster failover may not work with the secondary unit stuck in the init-syncing state.
717524 Users may not be able to add a username which contains a Slash "/" inside Device Log Setting.

Resolved Issues

Resolved Issues

The following issues have been fixed in FortiAnalyzer version 6.4.7. To inquire about a particular bug, please contact Customer Service & Support.

Device Manager

Bug ID Description
716486 FortiAnalyzer still populates the unauthorized device list even after detect-unregistered-log-device is set to disable.
731063 FortiAnalyzer supports FortiAuthenticator-300F.

FortiView

Bug ID Description
719441 FortiView may return sql-report dataset query error when Export to Report Chart in FortiClient Software inventory.
721008 Threats > Compromised Hosts may not be able to acknowledge compromised hosts when the end user is not a known IP.
723194 Secure SD-WAN Monitor Packet Loss widget may show no data.

724435

SD-WAN performance status widget may be empty if one of the SD-WAN members is down.

727056 SD-WAN Monitor may show incorrect bandwidth.
734359 FortiAnalyzer may return an error when applying source IP filter and exporting data to PDF with Top Browsing Users.

Log View

Bug ID Description
662830 FortiAnalyzer daylight adjustment does not take affect for real-time logging until rebooting the system.
688619 Logs received from FortiClient show logs with +1 hour in the time than the actual time on the end device or FortiAnalyzer.
715960 FortiClient Device ID takes FortiClient EMS SN value when displaying the log information from the historical view.
724223 Device list in Log View does not show correct devices after switching ADOMs.
726340 oftpd may not work properly if many log requests are received at the same time.

Others

Bug ID

Description

621473 FortiSOC is missing in cloud-based VMs.

682539

Local Connector Update Endpoint may fail due to endpoint's record contains unicode characters.

723352 oftpd may have memory leaks when the system has 2800+ FortiGate devices within CSF ADOMs.
723638 The dvmcmd process may crash when running TAC report.
724837 Redis server may consume high CPU usage when there are many ADOMs with many devices.
726782 The Percent of used memory is much higher in 7.0 than 6.4.
731070 FortiAnalyzer should add support for FortiNAC v9.1 in supported-platforms.
731319 There may be high memory usage on logfwd with FortiAnalyzer collector.
735760 FortiAnalyzer-200F may be slow with high CPU usage.

Reports

Bug ID Description
715680 Default chart VPN User Logins may return different values in two reports for the same device or data range.
717557 FortiAnalyzer reports may be empty when enabling LDAP Query.
718172 Report may be showing user or source as malicious code.
726688 All predefined report/template/chart/macro/dataset may be missing from newly created ADOM after a reboot.
734152 Report group filter may not work in FortiProxy ADOM.
734167 Report log field filter drop-down may be missing pick-list in non FortiGate ADOM.

System Settings

Bug ID Description
667488 Read-only user should not be able to change RAID level from GUI.
712043 HA cluster failover may not work with the secondary unit stuck in the init-syncing state.
717524 Users may not be able to add a username which contains a Slash "/" inside Device Log Setting.