Known Issues
The following issues have been identified in 6.0.5. For inquires about a particular bug or to report a bug, please contact Customer Service & Support.
|
Bug ID |
Description |
|---|---|
| 540347 | FortiManager has no option available to configure VLAN IDs under VLAN Pooling. |
|
547361 |
AP Profile in AP Manager may offer redundant options for specific AP models which can lead to failed installation. |
|
548329 |
WiFi Profiles SSID DHCP Server Toolbar is hidden if System Settings is set to None in an Admin Profile. |
|
549001 |
Installation error after changing inspection mode from Proxy to Flow. |
|
549113 |
In case FortiGate is in NGFW policy-based mode, URL or Application control profiles should not be visible on FortiManager. |
|
549615 |
Users should be able to set the |
|
549638 |
MAC address Access control list entries under DHCP server are duplicated when editing one of the entries. |
|
549674 |
FortiManager is unable to create SD-WAN Template in Central Management Mode if System Settings is set to None in an Admin Profile. |
|
550513 |
User cannot change IPSec Phase1 on an existing IPSec Phase2 interface. |
|
551072 |
Assignment of |
|
551077 |
FortiManager may not be able to import policies from FortiGate SLBC. |
|
551237 |
User without Super User Profile is unable to manage Tags from Tag Management. |
|
551701 |
FortiManager is unable to Set OSPF Interface Network Type as P2MP. |
|
552110 |
FortiManager cannot show where used for FortiSwitch Security Policy. |
|
552144 |
Install copy fails when setting captive portal user group for FortiSwitch's VLAN. |
|
553270 |
Imported SSIDs cannot be selected within AP Profile until the SSIDs have been edited. |
|
553276 |
When SSID is in bridge mode, external link to captive portal and CMCC Radius Secret are missing on AP Manager's SSID page. |
|
553704 |
Find Duplicate Objects may get stuck loading. |
|
553860 |
FortiManager should have public IP for |
|
553926 |
Split-tunneling information may not be retrieved completely for managed AP. |
|
553933 |
User should be able to configure split-tunneling related information on AP profile and managed AP pages. |
|
553985 |
FortiManager incorrectly sets |
|
553991 |
When redirect after captive portal is set, verification may fail on |
|
554001 |
Configuration may modify FQDN addresses after FortiManager and FortiGate are both upgrade to version 6.0.5. |
|
554092 |
FortiManager is unable to use interface member of a zone as Source Interface filter for VIP object. |
|
554154 |
FortiManager is unable to select multiple FortiExtender units for upgrade of firmware from Extender tab. |
|
554491 |
Device Manager generates incorrect configuration for Filter MAC Addresses on SSID that causes installation to fail. |
| 554500 | Device Manager's SSID page cannot save links to authentication portal and redirect after captive capital. |
|
554761 |
FortiManager is missing to generate software switch related configurations for Quarantine Host for SSID. |
| 554778 | AP Manager may not be able to import AP Profile for FAP-421E/423E/S421E/S423E. |
| 554882 | 7000 series HA members may show up as unregistered after failover. |
| 554901 | EU country ID is available on FortiManager, but the ID is not part of latest geographic database. |
| 554946 | Sub-admin clicks View on where Used may lead to disappearance of dual panel. |
| 555159 | After deleting an SSID from Device Manager, AP Manager still shows the SSID. |
| 555257 | Search box for SSID selection within AP Profile may not work well. |
| 555730 | Install may fail if zone member is used in a Multicast policy. |
| 556192 | Resetting hitcount in ADOM 5.4 fails. |
| 556192 | FortiManager may fail to run execute fips kat all and diagnose system fips kat-error commands. |
| 556368 | FortiManager may show Device objects from another ADOM. |
|
558445 |
Per-Device mapping function may not be available for SD-WAN interface member. Workaround: Configure per-device mappings via CLI script. |
|
558482 |
FortiManager may not be able to create a LDAP user. |
|
560332 |
Some CLI widgets are not available in the root ADOM when using multiple wildcard accounts. The error Non-root ADOM user cannot access CLI is shown. |