Known Issues
The following issues have been identified in 6.0.4. For inquires about a particular bug or to report a bug, please contact Customer Service & Support.
|
Bug ID |
Description |
|---|---|
|
462710 |
FortiManager cannot detect unauthorized FortiAP units that have been automatically added to managed FortiGate units. As a workaround, perform a manually retrieve operation on the managed FortiGate. |
| 529343 | FortiManager installation always fails on 6.0.x FGT-VMX. |
| 530493 | System Information widget on the slave FortiManager is showing both nodes as master. |
| 530717 | When adding an address via the right-click menu on the policy page, the page is stuck at the loading status. |
| 530735 | FortiManager may not be able to configure full mesh VPN among FortiGate devices with multiple VDOMS, and each VDOM containing an interface within it. |
| 530792 | When creating a Virtual Server, users cannot configure multiple Real Servers or set Real Server Mode for per-device mapping. |
| 530837 | User should not be allowed to delete default Meta fields. |
| 531338 | Unused object window size should be customizable and Column size under unused objects should stay to the set value. |
| 531963 | SSH Profile should not be allowed to enable "Allow Invalid SSL Certificates" when Inspection mode is "SSL Certificate Inspection" |
| 531968 | There should be an option to define the domain name for DHCP Server while configuring the VLANs' per device mappings with FortiSwitch. |
| 532075 | When editing comment/description, FortiManager may display the slash character, "/", as "/". |
|
533908 |
When promoting at the same time multiple FortiGates that have VDOMs, FortiManager Device Manager might fail to show the FortiGate VDOM name. As a workaround, delete and re-add the FortiGate. |