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.0.14.
Existing known issues
The following issues have been identified in a previous version of FortiManager Cloud and remain in FortiManager Cloud 7.0.14.
Device Manager
|
Bug ID |
Description |
|---|---|
|
752443 |
Vertical scroll bar is missing in SD-WAN configuration. |
| 997344 | FortiManager Cloud is missing the "set members 0" feature when creating SDWAN
Performance SLA. |
| 1102790 | FortiManager Cloud pushes the unset auto-connect command
to config system lte-modem, where the default value is disabled on FortiOS
but still enabled on FortiManager Cloud. |
Others
| Bug ID | Description |
|---|---|
| 988477 | There is not detail output information when executing "diagnose cdb
check policy-packages". |
| 1080463 |
An admin with access to a specific ADOM can view the database and clone objects to another ADOM, even if they do not have direct access to it. |
Policy & Objects
|
Bug ID |
Description |
|---|---|
| 751443 |
FortiManager Cloud 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 Cloud 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. |
| 925609 | Unused firewall shaping-profile is copied to device db and will be installed to devices. |
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. |
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'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. |