FortiGate-500E does not show up in Available Devices list.

In FortiGate 800-device test bed, not all devices are completely synchronized each time.

Workaround: Install configuration again.

Conflict reported as java.lang.NullPointerException when disabling a WAN port and installing config when it's referenced in MANUAL.

Workaround: Remove and re-configure the business rule.

Memory usage slowly increasing.

Workaround: Use the FortiManager CLI to set sdwancontroller disable and then enable.

When Load Policy is MANUAL and Manual Path is a MPLS link, business rule will fail to be deployed to FortiGate.

[Projecct_6.4.1] Change a wan port to be lan and add it to aggregate interface by changing profile, conflict will occur.

Workaround: Increase the FortiGate VM's memory to at least 4GB.

[Project_6.4.0]The share source SLA Server, while the name is duplicate with existed one, it also can be saved.

[Project_6.4.0]The share source SLA Quality and SLA Server, while the name include special character, it is unable to delete.

SLA in IPsec tunnels sometimes fails due to not sending out SLA probe packets.

Workaround: Reboot the FortiGate.

When changing ISP link of WAN port from MPLS to Internet or reversely, conflict may occur.

When Service Access is enabled on FortiManager interface, SD-WAN Orchestrator MEA fails to start up.

Adding FortiGate 300E and FortiGate 600E by Add Model Device will get a conflict and deployment process gets stuck.

Sometimes FortiGate 30E warns conflict as execute script:Response has no task attribute!.

Installation fails when creating FortiLink interface.

Workaround: Deploy FortiLink-related configuration before connecting FortiSwitch to FortiGate.

Conflict reported as delete 'fortivoice.fortilink when FortiSwitch first comes online.

Workaround: Use SD-WAN Orchestrator MEA to install configuration to FortiGate again. If it still fails, authorize FortiSwitch on FortiManager or FortiGate, and try to install configuration again.

Changing subnet of hard switch interface will cause FMG and FGT conflict.

It will cause conflict if manual create VLAN on FGT but controller did not has this VLAN.

Change the FortiSwich profile to operate smoothly. For a workaround, see FortiSwitch profiles.