Nowa aktualizacja FortiManager 6.4.12 została udostępniona przez producenta. FortiManager 6.4.12 zawiera poprawki błędów i usprawnienia w module Device Manager, takie jak błędy tworzenia interfejsów i brak wyświetlania urządzeń. W module Policy and Objects wprowadzono poprawki dotyczące listy reguł, usuwania wpisów użytkowników i wyboru interfejsów. Więcej informacji w artykule poniżej.
Aktualnie wspierane modele:
FortiManager | FMG-200F, FMG-200G, FMG-300E, FMG-300F, FMG-400E, FMG-400G, FMG-1000F, FMG-2000E,
FMG-3000F, FMG-3000G, FMG-3700F, FMG-3700G, FMG-3900E, and FMG-4000E. |
FortiManager VM | FMG-VM64, FMG-VM64-Ali, FMG-VM64-AWS, FMG-VM64-AWSOnDemand, FMG-VM64-Azure, FMG-VM64-GCP, FMG-VM64-HV (including Hyper-V 2016, 2019), FMG-VM64-KVM, FMG-VM64-OPC, FMG-VM64-XEN (for both Citrix and Open Source Xen). |
Naprawione problemy:
Device Manager
Bug ID | Description |
---|---|
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 |
---|---|
832351 | FortiManager does not allow users to enter to the „root” ADOM; it displays the „ADOM license was expired…” message. |
840395 | FortiManager does not support the FGT/FOS 6.4.11 Syntax. |
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 and 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. |
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, and Inserting Above or Below actions for a deny policy with a „Log Violation Traffic” disabled. |
Revision History
Bug ID | Description |
---|---|
738376 | Config revision diff check may highlight the differences in config even though the both revision are exactly same |
Znane problemy:
Known Issues
The following issues have been identified in 6.4.12. 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. |
Others
Bug ID | Description |
---|---|
770040 | FortiManager’s web interface and especially API calls are very slow if object-revision-status feature is enabled. |
Policy & Objects
Bug ID | Description |
---|---|
845022 | SDN Connector failed to import objects from VMware VSphere. |
855073 | The „where used” feature does not function properly. |
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. |
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. |
Notatki producenta: FortiManager 6.4.12
Pozdrawiamy,
Zespół B&B
Bezpieczeństwo w biznesie