Known Issues
The following issues have been identified in 6.4.1.r6. For inquires about a particular bug or to report a bug, please contact Customer Service & Support.
SD-WAN Orchestrator MEA
|
Bug ID |
Description |
|---|---|
|
649447 |
Address object and group names in FortiManager don't match names in SD-WAN Orchestrator MEA. |
|
663933 |
Port statuses are incorrect in SD-WAN Underlay Performance Status chart. |
|
664675 |
Exchange the IP address used to connect to peer hub, and a conflict occurs. Workaround: Configure a different IP address, and then switch back. |
|
669656 |
The number of internet service in Monitor is mismatched due to SD-WAN Orchestrator MEA display limitation. |
|
670820 |
Sometimes conflict occurs when config between FortiGate and FortiManager is different due to sync failures. At the same time, the FortiGate admin happens to click Dont' show again in the login page. Workaround: Execute retrieve config on FortiManager, and install config again on SD-WAN Orchestrator MEA. |
|
675112 |
Shortcut cannot be generated when two edge devices are behind the same NAT gateway. |
|
691408 |
Repeat auto-inject enable and disable in BGP neighbor and Global routing table doesn't take effect. Note: IBGP is not supported in SD-WAN networks. AS configured on adjacent routers should be different with that auto-generated by SD-WAN Orchestrator MEA and deployed to FortiGates. |
|
696898 |
FortiWiFi-40F-3G4G platform after sync all reports conflict with switch-interface member. Workaround: Install the configuration again. |
|
700703 |
The global theme change in FortiManager GUI is not supported in SD-WAN Orchestrator MEA. |
|
702503 |
Create FortiManager addressgroup object with address/addrgrp objects created by adding IP Pool in SD-WAN Orchestrator MEA, and then delete IP Pool. A conflict occurs. Workaround: Do not use address /addrgrp objects that are automatically generated by SD-WAN Orchestrator MEA in FortiManager. |
|
704283 |
Cloning any hardware type of profile to a VM profile should remove Extender options. Workaround: Create a new profile for FortiGate VM. Do not clone a hardware profile to create a VM profile. |
FortiManager and FortiOS
|
Bug ID |
Description |
|---|---|
|
572485/ 632946 |
Once the name of address object has changed, the address referred in business rule and firewall policy does not change. |
|
628750/ 630007 |
When Service Access is enabled on FortiManager interface, SD-WAN Orchestrator MEA fails to start up. |
|
643825 |
SLA in IPsec tunnels sometimes fails due to not sending out SLA probe packets. Workaround: Reboot FortiGate. |
|
669976 |
The Device column is empty on hubs when the traffic is from the subnet behind its edge. |
|
673361 |
Controller task cannot stop in 57h. This issue is found in 500-FGT test bed. Workaround: Reboot FortiManager. |
|
677174 |
Exchange the server of health-check will cause failure. Workaround: Clear the SLA servers and configure again. |
|
677397 |
SD-WAN Orchestrator MEA should be supported when Workspace/Workflow in per-ADOM mode is disabled. |
|
701492 |
First time online sync conflict in stress test bed. Workaround: Try reinstalling the configuration again. |
FortiSwitch and FortiAP
|
Bug ID |
Description |
|---|---|
|
618165/ 587742 |
Changing subnet of hard switch interface will cause FortiManager and FortiGate conflict. |
|
645309 |
Change the FortiSwitch profile to operate smoothly. For a workaround, see FortiSwitch profiles. |