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

Address Object and Group names in FortiManager don't match names in SD-WAN Orchestrator.

Memory usage slowly increases.

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

When Load Policy is MANUAL and Manual Path is an MPLS link, business rules fail to be deployed to FortiGates.

Port statuses are incorrect in SD-WAN Underlay Performance Status chart.

Exchange the IP address used to connect to peer hub, and a conflict occurs.

Workaround: Configure a different IP address, and then switch back.

While enabling or disabling short guard-interval setting, it won't sync to FortiManager's AP profile settings.

The CPU usage of JAVA process is very high from time to time when managing 200 FortiGate devices.

When the old configuration contains HA referencing the aggregate interface, the new configuration cannot be overwritten.

Shortcut monitor is empty if FortiGates are in a NAT traversal scenario.

Installation causes conflict after switching from QA to Dev, and then switching back to QA branch.

Shortcut cannot be generated when two edge devices are behind the same NAT gateway.

Changing ISP link from public to private and private to public results in a conflict.

Workaround: Reset the FortiGate to default, join SD-WAN Orchestrator, and install the configuration again.

Once the name of address object has changed, the address referred in business rule and firewall policy does not change.

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

When Service Access is enabled on FortiManager interface, ONOS failed to start up.

When Service Access is enabled on FortiManager interface, SDWAN Orchestrator fails to start up.

Conflict reported as system sdwan commit check error after changing ISP link of all device's port1 from Internet to MPLS.

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

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

Workaround: Reboot FortiGate.

Conflict occurs when installing business rules that include internet service group.

If FortiManager task fails the retrieve action, it causes the HA mode to become standalone mode.

The Device column is empty on hubs when the traffic is from the subnet behind its edge.

Controller task cannot stop in 57h. This issue is found in 500-FGT test bed.

Installation fails when creating FortiLink interfaces.

Changing subnet of hard switch interface will cause FortiManager and FortiGate conflict.

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