Known issues
The following issues are known is FortiAIOps version 1.0.1. For inquiries about a particular issue, visit the Fortinet Support website.
FortiAIOps
Issue ID |
Description |
---|---|
718461 |
DNS delays are not displayed in the Time to Connect SLA dashboard. |
720372 |
DHCP failure is not displayed when the client MAC address is blocked in the SSID. |
723096 | MAC addresses inserted in the database are not the stations for impacted switch. |
726276 | Active client count mismatch observed between FortiAIOps and FortiGate GUI. |
726636 |
When FortiSwitch is restarted, its details are not displayed in the AP health topology for some time. |
726889 |
Active clients are displayed from deleted FortiGate controllers. |
740904 |
The wireless impacted client data displayed in the trend graph mismatches with the data in the SSID bubble/ SLA data. |
743441 |
Toggling between the failure events displays incorrect data in the topology donut chart. |
743700 |
On clicking the classifier donut only related sub-classifier donuts should be displayed. |
744593 | FortiSwitch health events are not displayed every 10 minutes under AP health and FortiSwitch health SLA. |
747885 | Association failure (maximum clients reached) events do not display the SSID and client details. |
FortiGate/FortiOS
Issue ID |
Description |
---|---|
726888 |
The physical topology does not match with the device count connected to FortiGate. |
FortiManager
Issue ID |
Description |
---|---|
745312 |
Memory leak observed in the svc sys daemon process. |
746901 |
Delayed response from the FortiGate-FortiManager tunnel for a certain APIs. |