Fortinet black logo

Known Issues

Known Issues

The following issues have been identified in 7.0.12. 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.

1016987

FGFM's tunnel went down after upgrade because the device's SN doesn't match the expected certificate.

Workaround:

This check can be manually disabled globally on FortiManager side by entering the following command in the CLI:

config system global

set fgfm-peercert-witoutsn enable

end

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".

Policy & Objects

Bug ID Description
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's 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.

1012400

The policy package installation is hanging due to a crash in the "securityconsole" application.

Revision History

Bug ID

Description

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.

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.12. 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.

1016987

FGFM's tunnel went down after upgrade because the device's SN doesn't match the expected certificate.

Workaround:

This check can be manually disabled globally on FortiManager side by entering the following command in the CLI:

config system global

set fgfm-peercert-witoutsn enable

end

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".

Policy & Objects

Bug ID Description
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's 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.

1012400

The policy package installation is hanging due to a crash in the "securityconsole" application.

Revision History

Bug ID

Description

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.

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.