Fortinet black logo

Known Issues

Known Issues

The following issues have been identified in 6.4.11. To inquire about a particular bug or to report a bug, please contact Customer Service & Support.

Device Manager

Bug ID

Description

692669 Browser may display a message, 'A webpage is slowing down your browser', while checking revision difference.
804142 Creating the "EMACVLAN" type Interface on FortiManager displays an error "VLAN ID is required".
817346 Editing interface with normalized interface mapping displays some unnecessary messages for mapping change.
836206 Devices aren't showing up on the Device Manager GUI.

Others

Bug ID

Description

806522 Application websocket crashes and makes FortiManager's GUI unresponsive.
832351 FortiManager does not allow users to enter to the "root" ADOM; it displays the "ADOM license was expired..." message.
871608 Unable to retrieve routing information from Fortigate via FortiManager when there is a large routing table.
919088 GUI may not work properly in Google Chrome and Microsoft Edge version 114.

Policy & Objects

Bug ID

Description

726105 CLI Only Objects may not be able to select FSSO interface.
774058 Rule list order may not be saved under File Filter Profile.
803460 "User Definitions" entries under the "User & Authentication" cannot be removed from FortiManager.
827416 FortiManager does not display any copy failure errors when utilized objects do not have any default values or per-device mapping.

845022

SDN Connector failed to import objects from VMWare VSphere.

855073 The "where used" feature does not function properly.
870800 Even though each interface is mapped to be used in specific vdoms, the already mapped interface still can be selected for other VDOMs.

889563

FortiManager, for ADOM version 6.4, does not support Creating, Importing, or Inserting Above and Below actions for a deny policy with a "Log Violation Traffic" disabled.

Workarounds:

  • To Insert, use copy & paste instead of the using Insert Above/Below.

  • To Create, either run script to create log disabled deny policy or enable log traffic first, and then edit the policy in order to disable and save it.

Revision History

Bug ID

Description

738376

Config revision diff check may highlight the differences in config even though the both revisions are exactly same.

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 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 this 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.

Known Issues

The following issues have been identified in 6.4.11. To inquire about a particular bug or to report a bug, please contact Customer Service & Support.

Device Manager

Bug ID

Description

692669 Browser may display a message, 'A webpage is slowing down your browser', while checking revision difference.
804142 Creating the "EMACVLAN" type Interface on FortiManager displays an error "VLAN ID is required".
817346 Editing interface with normalized interface mapping displays some unnecessary messages for mapping change.
836206 Devices aren't showing up on the Device Manager GUI.

Others

Bug ID

Description

806522 Application websocket crashes and makes FortiManager's GUI unresponsive.
832351 FortiManager does not allow users to enter to the "root" ADOM; it displays the "ADOM license was expired..." message.
871608 Unable to retrieve routing information from Fortigate via FortiManager when there is a large routing table.
919088 GUI may not work properly in Google Chrome and Microsoft Edge version 114.

Policy & Objects

Bug ID

Description

726105 CLI Only Objects may not be able to select FSSO interface.
774058 Rule list order may not be saved under File Filter Profile.
803460 "User Definitions" entries under the "User & Authentication" cannot be removed from FortiManager.
827416 FortiManager does not display any copy failure errors when utilized objects do not have any default values or per-device mapping.

845022

SDN Connector failed to import objects from VMWare VSphere.

855073 The "where used" feature does not function properly.
870800 Even though each interface is mapped to be used in specific vdoms, the already mapped interface still can be selected for other VDOMs.

889563

FortiManager, for ADOM version 6.4, does not support Creating, Importing, or Inserting Above and Below actions for a deny policy with a "Log Violation Traffic" disabled.

Workarounds:

  • To Insert, use copy & paste instead of the using Insert Above/Below.

  • To Create, either run script to create log disabled deny policy or enable log traffic first, and then edit the policy in order to disable and save it.

Revision History

Bug ID

Description

738376

Config revision diff check may highlight the differences in config even though the both revisions are exactly same.

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 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 this 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.