Known Issues
The following issues have been identified in FortiAnalyzer version 6.4.6. For inquires about a particular bug or to report a bug, please contact Fortinet Customer Service & Support.
Device Manager
|
Bug ID |
Description |
|---|---|
| 639479 | FortiGate v6.0 with sub-ca certificate may not be able to establish oftp connection with FortiAnalyzer without sub-ca certificate. |
|
696853 |
When manually adding a device in FortiNAC ADOM, version v8.8 is not listed in the version option. |
|
716486 |
FortiAnalyzer still populating unauthorized device list even after |
FortiSOC
|
Bug ID |
Description |
|---|---|
| 668942 | A playbook running AV scan on endpoint may return error: failed results- can not find parameters for connector. |
FortiView
| Bug ID | Description |
|---|---|
| 539298 | Customer may not see data on cloud application bytes in FortiView. |
| 579828 | There may be bandwidth discrepancy under FortiView > Application & websites > Top websites. |
| 616675 | Bandwidth may not match between FortiAnalyzer and FortiGate. |
| 626530 | Bytes Sent/Received should match between Top Destinations and Policy Hit charts under FortiView when filtered by the same policy ID. |
| 640553 | FortiView monitor WiFi widget is not showing Bridged SSID information. |
| 641596 | FortiAnalyzer may show No Data in User Vulnerabilities Summary widget. |
| 642837 | The GUI should indicate if Sandbox detection only supports FortiGate in Fabric ADOM. |
| 663930 | Ports status may not be incorrect in Secure SD-WAN Monitor and SD-WAN Performance status. |
| 667076 | FortiView Top Cloud Users may show no entry found message but there is a session graph shown. |
| 683525 | The return lines may be incorrect after adding filters to Top Website Categories. |
| 688537 | Information End User located in Summary should match with time range and logs. |
| 707480 | Top Threats(FortiClient) may only display Threat level LOW and Allowed incidents. |
|
721008 |
Threats > Compromised Hosts may not be able to acknowledge compromised hosts when the end user is not a known IP. |
| 691570 | FortiAnalyzer may not be able to cancel IOC re-scan task. |
Log View
|
Bug ID |
Description |
|---|---|
| 608139 | Opening compressed FortiClient traffic file on FortiAnalyzer may cause other compressed FortiClient traffic logs fail to open. |
| 633393 | Some IPS archive files only contain BODY of Attack Context instead of the whole Attack Context. |
| 635598 | FortiAnalyzer may not display Traffic Logs in Log View and return Web Server Error 500. |
| 641013 | After created ADOM for FortiMail, the ADOM is not visible on GUI and mail domain logs are not going to the default FortiMail ADOM. |
| 653765 | Some log files under Log Browse may contain a mix of event and traffic messages. |
| 661094 | In Log View, importing log may fail. |
| 674027 | Filtering FortiClient event logs with wildcard UID filter returns no data. |
| 704206 | When filtering with Action and Source IP under the Traffic menu, the filter output may be incorrect with the combination of smart action with any other field. |
Others
|
Bug ID |
Description |
|---|---|
| 584105 | The
/drive0/private/restapi/sync/fgt_intf_stat location may use too much inodes. |
| 616355 | FortiGate may display SSL error or OFTP error when testing connectivity with FortiAnalyzer. |
| 632971 | FortiAnalyzer should have the ability to query CPU utilization on individual CPU core. |
| 660810 | FortiAnalyzer-200F rebuild may get stuck and sqllogd may crash due to insufficient memory. |
| 687809 | Log insert lag time may go above 5 hours on a properly sized FortiAnalyzer. |
|
701753 |
SIEM database should be trimmed at the same time when quota enforcement occurs. |
|
724625 |
Upgrade from 6.4.6 to 7.0.0 will result in all configuration being lost. |
Reports
| Bug ID | Description |
|---|---|
| 628823 | FortiAnalyzer is not generating all local Event logs for reports. |
| 653207 | FortiAnalyzer may have incorrect dataset queries without considering the direction field. |
| 677090 | Report Filter may not work with devname. |
System Settings
| Bug ID | Description |
|---|---|
| 629663 | Free text filter does not work
when using (~) tilde sign on syslog ADOM for the msg field. |
| 630654 | Imported logs may not sync to slave. |
| 638380 | FortiAnalyzer may accept invalid which may break some widgets. |
| 653371 | CEF log forwarding start time does not match with event time. |
| 669402 | FortiAnalyzer may not time out admin a session after many hours. |
|
717524 |
Users may not be able to add a username which contains a Slash "/" inside Device Log Setting. |