Fortinet white logo
Fortinet white logo

Known Issues

Known Issues

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

New known issues

There are no new issues identified in 7.2.7.

Existing known issues

The following issues have been identified in a previous version of FortiManager Cloud and remain in FortiManager Cloud 7.2.7.

AP Manager

Bug ID

Description

1010632 Floor Map shows wrong AP status and does not show the rest of APs when adding a new AP.

1040365

FortiManager Cloud is generating false vulnerability reports for certain FortiAPs:

  • U431F

  • U231F

Device Manager

Bug ID

Description

894948 FortiManager Cloud fails to push the FortiManager Cloud override settings to the FortiGate.
980362 The Firmware Version column in Device Manager incorrectly shows "Upgrading FortiGate from V1 to V2" even after a successful upgrade has been completed.
1004220 The SD-WAN Overlay template creates route-map names that exceed the 35-character limit.
1041440

Some FortiGate platforms (FGT-40F and FGT-60F) do not support the "ip-managed-by-fortiipam" and FortiGate refuses to take the configuration from FortiManager Cloud; hence users will be experiencing the install error.

Workaround:

Use a script on device database on FortiManager Cloud to unset "ip-managed-by-fortiipam" under wan interface (every time before installation), and then install the configuration.

1062545 When using the backslash "\" in the preshared key of IPSEC settings, the install may fail.
1063835 FortiManager Cloud ZTP installation to FortiGate versions 7.2.8 and lower may fail due to differing default "ssh-kex-algo" settings between FortiManager Cloud and FortiGate.

1070943

Unable to upgrade the devices via Device Group Upgrade Firmware feature.

Workaround:

Upgrade devices individually by using the "Device Firmware Upgrade" feature or Create New Firmware Template for single devices or device groups and use the "Assign to Devices/Groups" feature.

Others

Bug ID

Description

703585 FortiManager Cloud may return "Connection aborted" error with JSON API request.
777831 When FortiAnalyzer is added as a managed device to FortiManager Cloud, Incident & Event tile will be displayed instead of the FortiSoC.
1003711

During the FortiGate HA upgrade, both the primary and secondary FortiGates may reboot simultaneously, which can disrupt the network. This issue is more likely to occur in FortiGates that require disk checks, leading to longer boot times.

Workaround:

Disabling the disk check on fmupdate before the upgarde.

1019261

Unable to upgrade ADOM from 7.0 to 7.2, due to the error "Do not support urlfilter-table for global scope webfilter profile".

Workaround:

Run the following script against the ADOM DB:

config webfilter profile

edit "g-default"

config web

unset urlfilter-table

end

next

end

1029677

Unable to upgrade ADOM from v6.4 to v7.0 due to global scope error in webfilter profile.

Workaround:

Rename the "g-default" to "g-test" > save. It can be deleted after that. Once ADOM upgraded, new g-default is created.

Policy & Objects

Bug ID

Description

845022 SDN Connector failed to import objects from VMware VSphere.
967271 Installation failed when trying to remove firewall internet-service-name objects.
1004929

FortiManager Cloud removes the Web Filter Profile from the Profile Group for Policy-Based FortiGates.

Workaround:

Use individual profiles in the policy instead of the profile group.

1005161 The policy package status changes for all devices even when an address object is opened and saved without any modifications. This issue is particularly observed in objects utilizing the per-device mapping feature.

Script

Bug ID

Description

931088 Unable to delete VDOMs using the FortiManager Cloud script. Interfaces remain in the device database, causing the installation to fail.

System Settings

Bug ID

Description

825319 FortiManager Cloud 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 policy package import creates faulty dynamic mappings for VPN Manager.

Workaround:

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

diagnose cdb check policy-packages <adom>

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

1042701 The traffic view page for the full mesh does not display the FortiGate and the external gateway.

Known Issues

Known Issues

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

New known issues

There are no new issues identified in 7.2.7.

Existing known issues

The following issues have been identified in a previous version of FortiManager Cloud and remain in FortiManager Cloud 7.2.7.

AP Manager

Bug ID

Description

1010632 Floor Map shows wrong AP status and does not show the rest of APs when adding a new AP.

1040365

FortiManager Cloud is generating false vulnerability reports for certain FortiAPs:

  • U431F

  • U231F

Device Manager

Bug ID

Description

894948 FortiManager Cloud fails to push the FortiManager Cloud override settings to the FortiGate.
980362 The Firmware Version column in Device Manager incorrectly shows "Upgrading FortiGate from V1 to V2" even after a successful upgrade has been completed.
1004220 The SD-WAN Overlay template creates route-map names that exceed the 35-character limit.
1041440

Some FortiGate platforms (FGT-40F and FGT-60F) do not support the "ip-managed-by-fortiipam" and FortiGate refuses to take the configuration from FortiManager Cloud; hence users will be experiencing the install error.

Workaround:

Use a script on device database on FortiManager Cloud to unset "ip-managed-by-fortiipam" under wan interface (every time before installation), and then install the configuration.

1062545 When using the backslash "\" in the preshared key of IPSEC settings, the install may fail.
1063835 FortiManager Cloud ZTP installation to FortiGate versions 7.2.8 and lower may fail due to differing default "ssh-kex-algo" settings between FortiManager Cloud and FortiGate.

1070943

Unable to upgrade the devices via Device Group Upgrade Firmware feature.

Workaround:

Upgrade devices individually by using the "Device Firmware Upgrade" feature or Create New Firmware Template for single devices or device groups and use the "Assign to Devices/Groups" feature.

Others

Bug ID

Description

703585 FortiManager Cloud may return "Connection aborted" error with JSON API request.
777831 When FortiAnalyzer is added as a managed device to FortiManager Cloud, Incident & Event tile will be displayed instead of the FortiSoC.
1003711

During the FortiGate HA upgrade, both the primary and secondary FortiGates may reboot simultaneously, which can disrupt the network. This issue is more likely to occur in FortiGates that require disk checks, leading to longer boot times.

Workaround:

Disabling the disk check on fmupdate before the upgarde.

1019261

Unable to upgrade ADOM from 7.0 to 7.2, due to the error "Do not support urlfilter-table for global scope webfilter profile".

Workaround:

Run the following script against the ADOM DB:

config webfilter profile

edit "g-default"

config web

unset urlfilter-table

end

next

end

1029677

Unable to upgrade ADOM from v6.4 to v7.0 due to global scope error in webfilter profile.

Workaround:

Rename the "g-default" to "g-test" > save. It can be deleted after that. Once ADOM upgraded, new g-default is created.

Policy & Objects

Bug ID

Description

845022 SDN Connector failed to import objects from VMware VSphere.
967271 Installation failed when trying to remove firewall internet-service-name objects.
1004929

FortiManager Cloud removes the Web Filter Profile from the Profile Group for Policy-Based FortiGates.

Workaround:

Use individual profiles in the policy instead of the profile group.

1005161 The policy package status changes for all devices even when an address object is opened and saved without any modifications. This issue is particularly observed in objects utilizing the per-device mapping feature.

Script

Bug ID

Description

931088 Unable to delete VDOMs using the FortiManager Cloud script. Interfaces remain in the device database, causing the installation to fail.

System Settings

Bug ID

Description

825319 FortiManager Cloud 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 policy package import creates faulty dynamic mappings for VPN Manager.

Workaround:

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

diagnose cdb check policy-packages <adom>

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

1042701 The traffic view page for the full mesh does not display the FortiGate and the external gateway.