Resolved Issues
The following issues have been fixed in FortiAnalyzer version 7.2.1. To inquire about a particular bug, please contact Customer Service & Support.
Device Manager
Bug ID | Description |
---|---|
798197 | In Device Manager, FortiAnalyzer does not show the color of the logging devices properly (red or green). |
811627 |
FortiWeb FlexVM is not supported by FortiAnalyzer. |
816072 |
In Device Manager, model device configured with pre-shared key is not auto authorized. |
819664 | In Device Manager, Average Log Rate is displayed zero for FortiGates HA Cluster. |
FortiSOC
Bug ID | Description |
---|---|
701751 |
FortiGate Connectors were disappearing from FortiSOC Connectors List. |
769793 |
Incidents cannot be modified. |
773382 |
Running AV scan playbook takes a long time to load for all the endpoints, and users cannot see any progress bar. |
777901 |
EMS cloud playbooks failed due to the error connecting to EMS FortiClient Cloud. |
783212 |
Error Message 403 Client Error is seen when configuring FML connector under the Connectors. |
814419 |
When creating or configuring a playbook from scratch for an incident, the task status failed because of a missing category. |
821135 |
EMS connector status is inconsistent. |
FortiView
Bug ID | Description |
---|---|
754733 |
The No entry found. error is displayed when checking the Top Cloud Applications logs under FortiView. |
754781 | Fortiview Widgets log out even if the auto-refresh feature is being used. |
760228 |
FortiView displays higher bandwidth value than Report. |
794491 |
SD-WAN widgets do not display data properly. |
798471 |
Top SD-WAN Device Throughput widget is displaying wrong numbers. |
818065 | FortiView Top Applications view does not show any data. |
818077 |
Top application axis labels are not displayed correctly in Monitor section. |
822462 |
Secure SD-WAN Monitor devices are not sorted alphabetically like other widgets. |
822471 |
SD-WAN Performance Status widget under the Secure Monitor displays gray intervals, even when data is available. |
Log View
Bug ID | Description |
---|---|
682584 |
FCT logging for Chromebook stops intermittently and can only be resumed by restarting FortiAnalyzer. |
742643 |
Traffic logs for more than one day cannot be downloaded. |
769430 |
The log browse device list does not display all devices. |
779893 |
The |
787988 |
Downloading high volume of logs takes a long time and fails at the end. |
817761 | Downloading the traffic logs with custom time in text format displays error 500. |
Others
Bug ID | Description |
---|---|
719298 |
FortiAnalyzer failed to provide data in API response to FortiPortal request. |
750709 |
Policy Analyzer application exists on the MEA of FortiAnalyzer. |
773745 |
FortiAnalyzer should try to connect to FortiClient or forticlient-emsproxy.forticloud.com when enabling EMS Cloud. |
798630 |
Typo in widget name Top SD-WAN Device Throughout. |
804868 |
FortiAnalyzer log and logs-only backup do not work if using server-name instead of server IP address. |
804934 |
Type mismatch error is displayed for the column dstuuid. |
805509 |
FortiGates cannot display logs from FortiAnalyzer. |
812730 | There is an issue on HA member Synchronization on Azure Platform. |
817639 | FortiAnalyzer archive logs caused unexpected increase in the disk quota usage. |
823294 |
SSH connection between FortiGate and FortiAnalyzer/FortiManager v7.0.4/7.2.1 or later fails due to server_host_key_algorithms mismatch. |
Reports
Bug ID | Description |
---|---|
754265 |
Scheduled reports are not generated as configured. |
766123 |
The Selected data binding is invalid error is shown for Data Binding in the chart details for Traffic statistic. |
769473 |
FortiAnalyzer displays the error message At least one column is required. when creating a join statement from temporary tables and mapping it to a chart. |
770191 |
The SD-WAN internal and external throughput values are displayed incorrectly. |
783172 |
Reports may only show 64 device report details after upgrade. |
806284 |
FortiAnalyzer wrongly mixes and displays multiple device or customer info in the same report. |
816975 |
Unable to upload the report to server by output profile. |
817871 |
Session data is displayed improperly on predefined chart Top 30 users by bandwidth and sessions. |
821794 |
Predefined dataset (fml-History-Top-Sender) result is not right with nested count. |
824260 |
Failed to create reports using API request in FortiAnalyzer. |
System Settings
Bug ID | Description |
---|---|
669478 | Several dev-type mismatches have been observed between CLI and GUI under log-forwarding configuration. |
695968 | In the local event logs, Device Name doesn't match the FortiAnalyzer's hostname. |
734407 |
HA status does not display the DB inserting issue on the secondary member. |
741288 | SSO users cannot connect to the map server. |
745468 | Enabling the SNMP event raid-changed in CLI
does not enable it on the GUI. |
784290 | Primary FortiAnalyzer shows the secondary FortiAnalyzer hostname incorrectly. |
784345 |
FortiAnalyzer connects to map server and GeoIP server directly even when the web-proxy is enabled. |
793006 |
When Forward server is disabled, user has no visibility on the log forwarding servers setting. |
801936 |
FGFM access cannot be set for IPv6 interface when FortiAnalyzer has FIPS mode enabled. |
804897 | The Log forward configuration with IPv6 address destination cannot be set from the GUI. |
813243 |
FortiAnalyzer log-forwarding unable to forward FortiManager events with Log-ID filter to syslog. |
815644 | In FortiAnalyzer, cannot configure log forwarding exclusions for FortiClient. |