Recommendations and Limitations

Fortinet recommends the following versions and configurations to use with FortiAIOps.

Product	Recommendation
FortiManager	This release of FortiAIOps requires FortiManager version 7.2.1. The ADOM version supports FortiOS version 7.0.x and 7.2.x. Configure and enable syslog.
FortiAP/FortiAP-U	FortiAP (FAP) version 7.2.0 and FortiAP-U (FAP-U) version 6.2.4 are recommended.
FortiSwitch	FortiSwitch OS version 7.2.1 is recommended.
FortiOS	FortiOS version 7.2.1 is recommended to generate all events in FortiAIOps.
FortiGate	[FortiGate/FortiAnalyzer] Configure the FortiManager IP address in the FortiGate syslog or FortiAnalyzer to send events to FortiAIOps. Ensure that you enable the detection of interfering SSIDs in FortiGate to allow reporting of Throughput SLA - interference issues in FortiAIOps. To detect interfering SSIDs in FortiGate, configure the FortiAP profile to use Radio Resource Provisioning or a WIDS profile with AP scan enabled. To receive SD-WAN logs, ensure that the SD-WAN monitoring license is applied in FortiGate. This is to generate congestion logs. Configure the sla-fail and sla-pass log failure period, the recommended duration is 30 to 60 seconds.

The following limitations apply to FortiAIOps.

The Time to Connect DNS is not supported.
For wired SLA, only Linux/Windows/MacBook devices are considered as end clients.
Backup and restore operations are not supported.
All Throughput SLAs are not supported in FortiAIOps, if the FortiOS/FortiAP/FortiAP-U deployed are below the recommended versions.
Currently FortiAIOps evaluates only some de-authentication reasons.
Configuring the set sla-fail-log-period to less than 30 seconds generates many SD-WAN logs. Also, this may overload FortiAIOps.
Currently FortiAIOps receives the channel utilization data excluding WiFi and non-WiFi interference utilization data.
Retry information is not available for these FortiAP models, FAP-43xF, FAP-U43xF, FAP-23xF.

Recommendations

Fortinet recommends the following versions and configurations to use with FortiAIOps.

Product

Recommendation

FortiManager

FortiAP/FortiAP-U

FortiAP (FAP) version 7.2.0 and FortiAP-U (FAP-U) version 6.2.4 are recommended.

FortiSwitch

FortiOS

FortiGate

[FortiGate/FortiAnalyzer] Configure the FortiManager IP address in the FortiGate syslog or FortiAnalyzer to send events to FortiAIOps.
Ensure that you enable the detection of interfering SSIDs in FortiGate to allow reporting of Throughput SLA - interference issues in FortiAIOps. To detect interfering SSIDs in FortiGate, configure the FortiAP profile to use Radio Resource Provisioning or a WIDS profile with AP scan enabled.
To receive SD-WAN logs, ensure that the SD-WAN monitoring license is applied in FortiGate. This is to generate congestion logs.
Configure the sla-fail and sla-pass log failure period, the recommended duration is 30 to 60 seconds.

Limitations

The following limitations apply to FortiAIOps.

The Time to Connect DNS is not supported.

For wired SLA, only Linux/Windows/MacBook devices are considered as end clients.

Backup and restore operations are not supported.

All Throughput SLAs are not supported in FortiAIOps, if the FortiOS/FortiAP/FortiAP-U deployed are below the recommended versions.

Currently FortiAIOps evaluates only some de-authentication reasons.

Configuring the set sla-fail-log-period to less than 30 seconds generates many SD-WAN logs. Also, this may overload FortiAIOps.

Currently FortiAIOps receives the channel utilization data excluding WiFi and non-WiFi interference utilization data.

Retry information is not available for these FortiAP models, FAP-43xF, FAP-U43xF, FAP-23xF.