Fortinet black logo

Release Notes

Resolved Issues

Resolved Issues

The following issues have been fixed in 6.0.10. For inquires about a particular bug, please contact Customer Service & Support.

Device Manager

Bug ID Description
603291 Group membership may be incorrect after adding a VDOM.

FortiSwitch Manager

Bug ID

Description

642959 Re-installing or installing any policy package, FortiManager attempts to install security-8021x-dynamic-vlan-id even if there is no 8021x authentication configured on FortiManager.

Others

Bug ID Description
667421 FortiManager may report repeated miglogd crashes which causes logs to be lost.

Policy and Objects

Bug ID

Description

565301 Exporting policy package to Excel may not work.
569226 Section title should always be displayed for filtered policy and section title should not be deleted after policy was deleted.
608268 Users may not be able to edit firewall policy due to session-ttl:out of range in v5.6 or v6.0 ADOM.
628389 When Workspace is enabled, Policy Package Status may change to Modified when there is nothing to be installed.
630055 Some custom application signatures have id 0 in the application list.
632545 Installing policy package may result in an error: Could not read zone validation results.
636010 FortiManager cannot push custom application signatures from different policy packages to the same FortiGate.
639753 After a FortiToken is activated on the FortiGate, the next policy install from FortiManager will unset reg-id and os-ver on the token.
645367 Discarded policy deletion in Policy Package may delete all policies while they are still visible on the GUI.

654710

FortiManager may not be able to filter out IPS signatures by Protocol.

663219 FortiManager may not be able to add more than 10240 service objects.

Revision History

Bug ID Description

546939

Installing to Google Cloud Platform may fail due to unset key-passwd.

610687 FortiManager should not unset forward-error-correct during install.
632129 The syslogd setting source-ip is still visible after setting Status to Disable, which causes verification to fail.
633515 FortiManager should improve error message when FortiManager receives blank or invalid configurations from FortiGate.
660525 When installing from FortiManager, it may unset comment, organization, and subnet-name during install.

System Settings

Bug ID Description
574548 ADOM upgrade from version 5.6 to 6.0 may fail due to conflict with WTP.
596212 SSH filter profile is unset in firewall profile group upon ADOM upgrade.
618213 When trying to upgrade FortiManager cluster from FortiManager Master GUI, FortiManager Master reboots before sending the firmware to FortiManager Slave.
618607 Upgrading 5.4 ADOM does not convert delay-tcp-npu-sessoin to delay-tcp-npu-session and deletes the option.
642205 While FortiAnalyzer model is disabled, FortiManager may fail to create an ADOM due to over size with disk quota.

Resolved Issues

The following issues have been fixed in 6.0.10. For inquires about a particular bug, please contact Customer Service & Support.

Device Manager

Bug ID Description
603291 Group membership may be incorrect after adding a VDOM.

FortiSwitch Manager

Bug ID

Description

642959 Re-installing or installing any policy package, FortiManager attempts to install security-8021x-dynamic-vlan-id even if there is no 8021x authentication configured on FortiManager.

Others

Bug ID Description
667421 FortiManager may report repeated miglogd crashes which causes logs to be lost.

Policy and Objects

Bug ID

Description

565301 Exporting policy package to Excel may not work.
569226 Section title should always be displayed for filtered policy and section title should not be deleted after policy was deleted.
608268 Users may not be able to edit firewall policy due to session-ttl:out of range in v5.6 or v6.0 ADOM.
628389 When Workspace is enabled, Policy Package Status may change to Modified when there is nothing to be installed.
630055 Some custom application signatures have id 0 in the application list.
632545 Installing policy package may result in an error: Could not read zone validation results.
636010 FortiManager cannot push custom application signatures from different policy packages to the same FortiGate.
639753 After a FortiToken is activated on the FortiGate, the next policy install from FortiManager will unset reg-id and os-ver on the token.
645367 Discarded policy deletion in Policy Package may delete all policies while they are still visible on the GUI.

654710

FortiManager may not be able to filter out IPS signatures by Protocol.

663219 FortiManager may not be able to add more than 10240 service objects.

Revision History

Bug ID Description

546939

Installing to Google Cloud Platform may fail due to unset key-passwd.

610687 FortiManager should not unset forward-error-correct during install.
632129 The syslogd setting source-ip is still visible after setting Status to Disable, which causes verification to fail.
633515 FortiManager should improve error message when FortiManager receives blank or invalid configurations from FortiGate.
660525 When installing from FortiManager, it may unset comment, organization, and subnet-name during install.

System Settings

Bug ID Description
574548 ADOM upgrade from version 5.6 to 6.0 may fail due to conflict with WTP.
596212 SSH filter profile is unset in firewall profile group upon ADOM upgrade.
618213 When trying to upgrade FortiManager cluster from FortiManager Master GUI, FortiManager Master reboots before sending the firmware to FortiManager Slave.
618607 Upgrading 5.4 ADOM does not convert delay-tcp-npu-sessoin to delay-tcp-npu-session and deletes the option.
642205 While FortiAnalyzer model is disabled, FortiManager may fail to create an ADOM due to over size with disk quota.