Fortinet black logo

Known Issues

Known Issues

The following issues have been identified in 7.0.10. To inquire about a particular bug or to report a bug, please contact Customer Service & Support.

Device Manager

Bug ID Description
752443 Vertical scroll bar is missing in SD-WAN configuration.

Others

Bug ID Description
777831 When FortiAnalyzer is added as a managed device to FortiManager, the "Incident & Event" tile will be displayed instead of the "FortiSoC" tile.
924164 The firmware template status changes to "unknown" after retrieve.
935430 When FortiAnalyzer is managed by FortiManager and FortiManager's local logs are being sent to FortiAnalyzer, installing PP to FortiGates may display the following message: "Confirm Deletion FortiManager is going to sync the following device deletion to FortiAnalyzer,...".

Policy & Objects

Bug ID Description
538057 The "OR" button in column filter may not work.
751443

FortiManager displays policy installation copy failures error when ipsec template gets unassigned.

Workaround: Instead of unassigning IPSec template, modify IPSec template, replace the reference to IPSec tunnel interface with another interface. Please ensure a fresh FortiManager backup is created prior to any changes.

845022 SDN Connector failed to import objects from VMware VSphere.
851331 Cloning Firewall Addresses under the Firewall Objects does not clone the "Add To Groups" entries.
855317 New users added to the user group for IPSec dial-up XAuth authentication do not get installed.

917471

The EMS connector is automatically being disabled.

938019 Policy Package Status not changed on modification of nested group used in policy block.

963008

Impossible to merge duplicate objects.

966495

In FortiManager v7.0.10, whether it's a fresh setup or an upgrade, a "copy failed error" occurs due to the absence of the default "sd-wan" interface. This may happen on an existing 6.4 ADOM or when attempting to create a new ADOM v6.4.

Workaround: Create a new sd-wan template or create a new "sd-wan" interface.

Revision History

Bug ID

Description

513317 FortiManager may fail to install policy after FortiGate failover on Azure.
801614 FortiManager might display an error message "Failed to create a new revision." for some FortiGates when retrieving their configurations.

System Settings

Bug ID Description
825319 FortiManager fails to promote a FortiGate HA member (running on firmware 7.2.0 to 7.2.4) to the Primary.
853429 Creating FortiManager's configuration backup via scp cannot be done.

VPN Manager

Bug ID Description

784385

If policy changes are made directly on the FortiGates, the subsequent PP import creates faulty dynamic mappings for VPN Manager.

Workaround:

It is strongly recommended to create a fresh backup of the FortiManager's configuration prior to the workaround. Perform the following command to check & repair the FortiManager's configuration database.

diagnose cdb check policy-packages <adom>

After running this command, FortiManager will remove the invalid mappings of vpnmgr interfaces.

Known Issues

The following issues have been identified in 7.0.10. To inquire about a particular bug or to report a bug, please contact Customer Service & Support.

Device Manager

Bug ID Description
752443 Vertical scroll bar is missing in SD-WAN configuration.

Others

Bug ID Description
777831 When FortiAnalyzer is added as a managed device to FortiManager, the "Incident & Event" tile will be displayed instead of the "FortiSoC" tile.
924164 The firmware template status changes to "unknown" after retrieve.
935430 When FortiAnalyzer is managed by FortiManager and FortiManager's local logs are being sent to FortiAnalyzer, installing PP to FortiGates may display the following message: "Confirm Deletion FortiManager is going to sync the following device deletion to FortiAnalyzer,...".

Policy & Objects

Bug ID Description
538057 The "OR" button in column filter may not work.
751443

FortiManager displays policy installation copy failures error when ipsec template gets unassigned.

Workaround: Instead of unassigning IPSec template, modify IPSec template, replace the reference to IPSec tunnel interface with another interface. Please ensure a fresh FortiManager backup is created prior to any changes.

845022 SDN Connector failed to import objects from VMware VSphere.
851331 Cloning Firewall Addresses under the Firewall Objects does not clone the "Add To Groups" entries.
855317 New users added to the user group for IPSec dial-up XAuth authentication do not get installed.

917471

The EMS connector is automatically being disabled.

938019 Policy Package Status not changed on modification of nested group used in policy block.

963008

Impossible to merge duplicate objects.

966495

In FortiManager v7.0.10, whether it's a fresh setup or an upgrade, a "copy failed error" occurs due to the absence of the default "sd-wan" interface. This may happen on an existing 6.4 ADOM or when attempting to create a new ADOM v6.4.

Workaround: Create a new sd-wan template or create a new "sd-wan" interface.

Revision History

Bug ID

Description

513317 FortiManager may fail to install policy after FortiGate failover on Azure.
801614 FortiManager might display an error message "Failed to create a new revision." for some FortiGates when retrieving their configurations.

System Settings

Bug ID Description
825319 FortiManager fails to promote a FortiGate HA member (running on firmware 7.2.0 to 7.2.4) to the Primary.
853429 Creating FortiManager's configuration backup via scp cannot be done.

VPN Manager

Bug ID Description

784385

If policy changes are made directly on the FortiGates, the subsequent PP import creates faulty dynamic mappings for VPN Manager.

Workaround:

It is strongly recommended to create a fresh backup of the FortiManager's configuration prior to the workaround. Perform the following command to check & repair the FortiManager's configuration database.

diagnose cdb check policy-packages <adom>

After running this command, FortiManager will remove the invalid mappings of vpnmgr interfaces.