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.13.
Existing known issues
The following issues have been identified in a previous version of FortiManager and remain in FortiManager7.0.13.
Device Manager
| Bug ID | Description |
|---|---|
| 752443 | Vertical scroll bar is missing in SD-WAN configuration. |
| 997344 | FortiManager is missing the "set members
0" feature when creating SDWAN Performance SLA. |
Others
| Bug ID | Description |
|---|---|
| 777831 | When FortiAnalyzer is added as a managed device to FortiManager, "Incident & Event" tile will be displayed instead of the "FortiSoC" tile. |
| 988477 | There is not detail output information when executing "diagnose cdb
check policy-packages". |
Policy & Objects
| Bug ID | Description |
|---|---|
| 751443 |
FortiManager 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 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. |
System Settings
| Bug ID | Description |
|---|---|
| 825319 |
FortiManager 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 PP 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. |