Fortinet black logo

Version:


Table of Contents

6.4.4
Download PDF
Copy Link

Known Issues

The following issues have been identified in 6.4.1.r5. For inquires about a particular bug or to report a bug, please contact Customer Service & Support.

SD-WAN Orchestrator MEA

Bug ID

Description

641221

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

649447

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

654540

Memory usage slowly increases.

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

656872

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

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.

664959

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

671382

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

673991

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

674777

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

674812

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

675112

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

676632

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.

677174

Modifying the servers in a Health Check will cause it to fail.

Workaround: Clear the SLA servers and re-configure the Health Check.

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.

598603/

598895

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

628750

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

628750/

630007

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

640431

 

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

640431/

641740

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

643825

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

Workaround: Reboot FortiGate.

662106

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

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.

677397

SD-WAN Orchestrator should be supported when Workspace/Workflow in per-ADOM mode is disabled.

FortiSwitch and FortiAP

Bug ID

Description

578622/

586763

Installation fails when creating FortiLink interfaces.

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.

645946

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

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

Known Issues

The following issues have been identified in 6.4.1.r5. For inquires about a particular bug or to report a bug, please contact Customer Service & Support.

SD-WAN Orchestrator MEA

Bug ID

Description

641221

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

649447

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

654540

Memory usage slowly increases.

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

656872

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

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.

664959

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

671382

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

673991

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

674777

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

674812

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

675112

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

676632

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.

677174

Modifying the servers in a Health Check will cause it to fail.

Workaround: Clear the SLA servers and re-configure the Health Check.

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.

598603/

598895

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

628750

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

628750/

630007

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

640431

 

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

640431/

641740

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

643825

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

Workaround: Reboot FortiGate.

662106

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

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.

677397

SD-WAN Orchestrator should be supported when Workspace/Workflow in per-ADOM mode is disabled.

FortiSwitch and FortiAP

Bug ID

Description

578622/

586763

Installation fails when creating FortiLink interfaces.

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.

645946

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

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