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
There are no new issues identified in 7.2.11.
Existing known issues
The following issues have been identified in a previous version of FortiManager Cloud and remain in FortiManager Cloud 7.2.11.
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. |
Device Manager
|
Bug ID |
Description |
|---|---|
| 894948 | FortiManager Cloud fails to push the FortiAnalyzer 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. |
Others
|
Bug ID |
Description |
|---|---|
| 703585 | FortiManager may return 'Connection aborted' error with JSON API request. |
| 968647 |
On the Log View (when FortiAnalyzer is added to FortiManager Cloud) changing time filters, first request always fails but second one is successful. Workaround: Use FortiAnalyzer Log View to view logs. |
| 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" and save. It can be deleted after that. Once ADOM upgraded, new g-default is created. |
| 1052341 | Not able to select Address type MAC in SD-WAN rule source address. |
| 1093040 | SD-WAN template import failed when meta variable has the default value set. |
| 1142559 | When attempting to upload the firmware image from FortiGuard, FortiManager returns the following error "Code: -1, Invalid image". This issue has primarily been observed on FortiGate hardware platforms running special build firmware versions, where the image contains an encrypted MBR such as on the FortiGateRugged-70G-5G-Dual, FortiGateRugged-70G, FortiGateRugged-50G-5G, FortiWiFi-70G models. |
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. |
| 971065 | When the number of Custom Internet Services exceeds 256, installation fails due to this limitation. |
| 1029921 | Under the "Web Application Firewall" security profiles, users are unable to disable the signatures via GUI. |
| 1030914 | Copy and paste function in GUI removes name of the policy rule and adds unwanted default security profiles (SSL-SSH no-inspection and default PROTOCOL OPTIONS). |
| 1054707 | FortiManager Cloud tries to install "unset qos-policy" and installation fails. |
| 1131041 | Not able to create ZTNA Server due to the certificate error. |
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 configuration prior to the workaround. Perform the following command to check & repair the FortiManager Cloud configuration database. diagnose cdb check policy-packages <adom> After running this command, FortiManager 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. |