Known issues
Known issues are organized into the following categories:
To inquire about a particular bug or to report a bug, please contact Fortinet Customer Service & Support.
New known issues
No new issues have been identified in version 7.4.5.
Existing known issues
The following issues have been identified in a previous version of FortiManager Cloud and remain in FortiManager Cloud 7.4.5.
AP Manager
|
Bug ID |
Description |
|---|---|
| 1032762 | Since FortiOS 7.4.4 now supports the selection of multiple 802.11 protocols and has trimmed the band options, importing FortiOS 7.4.3 AP profiles may result in some bands and channels being un-matched or unset. |
| 1041445 | The AP attributes do not automatically update in the AP Manager. |
| 1062154 | Due to a syntax mismatch between FortiGates and FortiManager Clouds for FortiAPs, installation may fail. Currently, FortiManager Cloud v7.4.3 with ADOM 7.4 only supports the FortiAP syntax of the latest FortiGates version 7.4.4. |
| 1076200 |
Policy install fails due to FortiManager Cloud installs unexpected changes related to "<wifi_intf> address". Workaround: Create a CLI template with all subnet addresses and assign to device. |
| 1081136 |
FortiManager Cloud is trying to delete and create ssid interface subnet address after upgrade. |
Device Manager
|
Bug ID |
Description |
|---|---|
|
952422 |
IPsec templates created by SDWAN Overlay does not create tunnels for all the underlay interfaces. |
| 973365 |
FortiManager Cloud does not display the IP addresses of FortiGate interfaces configured with DHCP addressing mode. Workaround: Disable Addressing Mode from DHCP to Manual in FortiManager Cloud Device DB, then retrieve from FortiGate and IP will be updated successfully. |
| 974925 |
The NTP Server setting may not display the correct configuration. This issue might occur on managed devices running FortiOS version 7.4.2 or higher. Workaround: Edit NTP server setting under CLI configuration. |
| 1004220 | The SD-WAN Overlay template creates route-map names that exceed the 35-character limit. |
| 1053194 | If the "system interface speed" attribute is changed from the
FortiManager Cloud, it may potentially cause an installation failure. Modifying the
"system interface speed" is not currently supported on the FortiManager Cloud and
must be done on the FortiGate side. |
| 1070943 |
Unable to upgrade the devices through the 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. |
|
1074717 |
An error might be observed when the SD-WAN template health check name contains a space, displaying the following message: "Bad health check name...". |
|
1075747 |
SD-WAN Monitor does not display the members under the SD-WAN Rules (Map View or Table View). |
| 1080414 |
CSV import fails to set metadata variables due to old header format ("name"). |
Others
|
Bug ID |
Description |
|---|---|
| 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 thedisk 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 |
| 1019784 | ADOM Upgrade from 7.0 to 7.2 fails with the "Fail(errno=0):invalid value" error message. |
| 1029677 |
Unable to upgrade ADOM from v6.4 to v7.0 due to global scope error in webfilter profile. Workaround:
Rename the " |
Policy & Objects
|
Bug ID |
Description |
|---|---|
| 845022 | SDN Connector failed to import objects from VMware VSphere. |
| 991720 |
FortiManager Cloud still has an option to enable the "match-vip" through the policy package for "allow" policies. However, this is not supported anymore on the FortiGates. Workaround: Disable the option under advance option in Firewall Rule. |
| 998850 |
Modification to Policy with install target does not update the policy package status. Workaround: Remove the Installation Target and re-add to the policy which will trigger Policy Package Modification and the install preview will also show the changes made. |
|
1029921 |
Under the "Web Application Firewall" security profiles, users are unable to disable the signatures through the GUI. |
|
1074686 |
FortiManager Cloud fails to import NAC policies. Workaround: Manually create the NAC policy in the policy package and then install. |
| 1076659 |
When policy package configured with policy block, installation to multiple devices may have copy fail errors if combined length of the Policy Block name and Policy name is greater than 35 characters and if the total number of such policies exceeds 1000. |
| 1079678 |
FortiManager Cloud does not provide any warning when there is a "deny all" policy in the middle of a Policy Package. This can be still seen on the "task monitor". |
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. |