Known Issues
The following are known issues in FortiAIOps version 2.0.2. For inquiries about a particular issue, contact Customer Support.
|
Issue ID |
Description |
Workaround |
|---|---|---|
|
984470 |
FortiAIOps docker fails to start on Google Cloud Platform (GCP) upon reboot. |
|
|
992173 |
In the AI Insights dashboard, the statistics for connected switch clients take longer (2.5 minutes approximately) to display, only for a duration of 1 week. |
|
|
992778 |
Sometimes, SAM measured baseline tests fail due to time zone errors. |
|
| 995350 | [AI Insights dashboard] The Overall Network Health and the Impacted Clients charts are not supported in the Firefox browser. |
Use a supported browser, such as, Chrome, Edge, and Safari. |
|
1000705 |
In Wireless > Clients, the trend data displayed for more than 12 hours is inaccurate. |
|
|
1011884 |
Interfering SSID data reported by radio 3 is not displayed in the Channel Summary. |
|
|
1013904 |
In Wireless > applications, the data in the User, Access Points, and SSID columns for bridge SSID profiles is incorrect in all widgets. |
|
|
1014527 |
Currently, there is a delay in the switch SLA data in the Impacted SLA and Impacted Devices pages. |
|
|
1020336 |
FortiAIOps does not detect FaceTime application due to signature issues in FortiGuard. |
|
|
1034404 |
FortiGates managed by FortiAIOps lose connectivity on upgrade. |
FortiAIOps rigorously scrutinizes the certificate chain. On upgrading (when using the Fortinet_GUI_Server certificate), if FortiGate ignores the CA certificate in FortiAIOps, then it loses connectivity. To restore the FortiGate’s online status, perform any of the following.
|