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
The following issues have been identified in version 7.4.4.
AP Manager
|
Bug ID |
Description |
|---|---|
| 1050466 | The 802.11ax-5g AP profile is missing for all FortiAPs that support WiFi 6. |
Device Manager
|
Bug ID |
Description |
|---|---|
|
1075281 |
Unable to add FortiAnalyzer to FortiManager when " Workaround: Set " |
| 1075747 | SD-WAN Monitor does not display the members under the SD-WAN Rules (Map View or Table View). This issue is most likely to occur when "priority-zone" is configured. |
|
1080414 |
CSV import fails to set metadata variables due to old header format ("name"). To update to the current format, see "Device blueprint header" in Special Notices. |
Policy & Objects
|
Bug ID |
Description |
|---|---|
|
1074686 |
FortiManager fails to import NAC policies. Workaround: Manually create the NAC policy in the policy package and then install. |
|
1079678 |
FortiManager does not provide any warning when there is a "deny all" policy in the middle of a Policy Package. This warning can be still be seen on the "task monitor". |
System Settings
|
Bug ID |
Description |
|---|---|
|
1047252 |
Incorrect warning message displayed in FortiManager GUI during upgrade from Feature build to Mature build. |
Existing known issues
The following issues have been identified in a previous version of FortiManager and remain in FortiManager 7.4.4.
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. |
| 1076200 |
Policy install fails due to FortiManager installs unexpected changes related to "<wifi_intf> address". Workaround: Create a CLI template with all subnet addresses and assign to device. |
| 1076200 |
Policy install fails due to FortiManager installs unexpected changes related to "<wifi_intf> address". Workaround: Create a CLI template with all subnet addresses and assign to device . |
Device Manager
|
Bug ID |
Description |
|---|---|
|
973365 |
FortiManager does not display the IP addresses of FortiGate interfaces configured with DHCP addressing mode. Workaround: Disable Addressing Mode from DHCP to Manual in FortiManager 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, it may potentially cause an installation failure. Modifying the "system interface speed" is not currently supported on the FortiManager and must be done on the FortiGate side. |
Others
|
Bug ID |
Description |
|---|---|
| 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 |
|
1049457 |
When FortiAnalyzer is added as a managed device, users may encounter an issue in the FortiManager GUI when expanding the log details. |
|
1058185 |
FortiProxy policies not imported if the policies have either internet service or IPv6 used in the source or destination. |
|
1254367 |
FortiManager instances deployed on Azure may lose all data—including configuration, logs, and reports—if the VM is deallocated and subsequently reallocated. This may occur during Azure-level operations such as VM stop (deallocate) or SKU/size changes. Please refer to the Special Notices for more information. |
Policy & Objects
|
Bug ID |
Description |
|---|---|
| 845022 | SDN Connector failed to import objects from VMware VSphere. |
| 991720 |
FortiManager 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. |
|
1029921 |
Under the "Web Application Firewall" security profiles, users are unable to disable the signatures via GUI. |
|
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. |
| 1077964 |
After ZTNA server real server address type changes from FQDN to IP, the policy installation may fail; FortiManager pushes ZTNA server config with wrong order. |
| 1079678 |
FortiManager 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". |