Resolved Issues
The following issues have been fixed in 6.4.1 r1. For inquires about a particular bug, please contact Customer Service & Support.
|
Bug ID |
Description |
|---|---|
| 592819 | [Project_6.4.0] IP Pool disordered in Global Routing table. |
| 599725 | [Project_6.4.0] When dragging a device to move its position, the icon often moves back to its original position. |
| 600436 | [Project_6.4.0] Set WAN port type for MPLS and Private Line to enabled, and no underlay information is displayed in single device monitor. |
| 601534 | [Project_6.4.0] Path down does not trigger log. |
| 604355 | [Project_6.4.0] Sometimes path lines disappear especially when synchronizing configurations. |
| 606420 | [Project_6.4.0] Dynamic sync is sometimes not triggered. |
| 614296 | [Project_6.4.0_Stress env] The page gets stuck when the region device is expanded in stress environment. |
| 618438 | [Project_6.4.0] Unknown reason causes Internal Server Error. |
| 618894 | [Project_6.4.0](FortiAP) Unable to add AP profile on hardswitch interface. |
| 619673 | [Project_6.4.0] Unable to add FortiGate device by serial number. |
| 620184 | [Project_6.4.0] ADOM 6.4 should remove profile for 30E/50E/51E/52E. |
| 621599 | [Project_6.4.0] After FortiGate is added to SD-WAN Orchestrator MEA, there is a chance to be offline. |
| 622605 | [Project_6.4.0] Synchronization conflict occurs when an SDWAN member is used by an SDWAN rule, but the interface is set to disabled on profile. |
| 622606 | [Project_6.4.0] Synchronization failed, if device has static ports with enabled DHCP server, but control what changes them to DHCP or PPoE mode. |
| 622688 | [Project_6.4.0] Set tunnel IP failed as Subnets overlap between 'port1-E' with primary IP of 'port3-E'. |
| 623440 | [Project_6.4.0] When click SD-WAN Orchestrator MEA GUI Maintenance > Upgrade > Check for updates, sometimes it logs out and skips to FortiManager main page. |
| 623679 | [Project_6.4.0] Conflict
held while synchronizing FortiGate 80D. Set switch-controller-feature none
[invalid value]. |
| 623686 | [Project_6.4.0_Stress env] Failed to back up configuration in stress environment. |
| 623694 | [Project_6.4.0_Stress env] The device will automatically flash in Topology view > Region view. |
| 623824 | [Project_6.4.0] Synchronization conflict occurs when deleting a device and the device is referred by a custom internet service on other device. |
| 624115 | [Project_6.4.0] Unset IP address on a port will fail if there is a secondary IP on the port. |
| 624553 | [Project_6.4.0] SD-WAN Orchestrator MEA installation failed due to FortiManager script deleting IPsec interface failure. |
| 624842 | [Project_6.4.0] Synchronization conflict occurs if device already has a VPN tunnel and the VPN interface is referred by firewall policy. |
| 624943 | [Project_6.4.0](FortiAP) It
is Unable to create an SSID with security mode WPA3_SAE. |
| 624964 | [Project_6.4.0](FortiAP) It is unable to delete SSIDs. |
| 625537 | [Project_6.4.0] If business rule includes some applications, there will be conflict. |
| 625572 | [Project_6.4.0](FortiAP) While binding the wrong AP model profile, the AP is still automatically authorized on FortiGate. |
| 625617 | [Project_6.4.0] Specifying a region for "Backhaul to Group" in a business rule, but links to all the regions are added. |
| 625745 | [Project_6.4.0] From Device page, configure SSID static IP, and it is unable to deploy the IP address to FortiGate. |
| 625748 | [Project_6.4.0] Delete the SSID from Device page, and it won't synchronize to FortiGate. |
| 625757 | [Project_6.4.0] While importing device from csv file, FortiGate VM always fails. |
| 625966 | [Project_6.4.0] Change business rule from SLA=Default_Google Search to others causes synchronization conflict. |
| 626051 | [Project_6.4.0] Business rule cannot see script, if it contains special ISDBs. |
| 626457 | [Project_6.4.0](FortiSwitch) While adding more than 1 Switch and AP to SD-WAN Orchestrator MEA, binding of switch template and AP profile will fail. |
| 627570 | [Project_6.4.0] Failed to deploy device dynamically: dynamic deploy(FGT tunnel api) error. |
| 627600 | [Project_6.4.0] After adding unauthorized devices, the setting page won't close. |
| 627972 | [Project_6.4.0] Failed to install business rule when selecting some destination address objects. |
| 628235 | [Project_6.4.0] When Device WAN port override is enabled, Estimated upstream bandwidth and downstream will be restored to 0 Kbps. |
| 628818 | [Project_6.4.0](FortiAP) Unable to automatically authorize FortiAP. |
| 629178 | [Project_6.4.0](FortiSwitch) It should not allow users to set the same VLAN to both native VLAN and allow VLAN. |
| 629522 | [Project_6.4.0] When the page window is reduced, the right-side content of a webpage cannot be seen. |
| 629566 | [Project_6.4.0] Delete a device and install configuration. A conflict is triggered as reason(> delete "DEVICE_6" [used. detail: delete. |
| 629884 | [Project_6.4.0](FortiSwitch) While creating a FSW VLAN, it only deploys to FortiManager; it does not deploy to FortiGate. |
| 630341 | [Project_6.4.0] While turning off SW/AP Configuration, SD-WAN Orchestrator MEA won't unbind SW/AP template. |
| 630818 | [Project_6.4.0] Once the configuration is synchronized, FortiGate sometimes goes offline and online again. |
| 631032 | [Project_6.4.0] Change profiles for devices in a region for many times, and sometimes a device will be deleted. |
| 631090 | [Project_6.4.0] While disabling device LAN override, SSID IP address won't set by profile setting. |
| 631149 | [Project_6.4.0]
If the auto-generated address or addrgrp is referenced in business rule,
deleting the device will cause conflict. |
| 631359 | [Project_6.4.0] SD-WAN Orchestrator MEA does not work normally in AWS. |
| 631782 |
/32
Is not allowed for IP Address field in WAN Interfaces. |
| 631991 | [Project_6.4.0] When a device is referenced in business rules by other devices, moving it from one ADOM to another will fail. |
| 632153 | [Project_6.4.0_Stress env] First online synchronization failed sometimes. |
| 632863 | [Project_6.4.0] Dynamic interface update failed. |
| 633793 | [Project_6.4.0] Manual password should not allow special characters. |
| 633797 | [Project_6.4.0] While adding a device, the profile won't display immediately. |
| 634756 | [Project_6.4.0] In single device > Underlay Link of port2, click Drilldown & show overlay and port1 overlay info is displayed. |
| 634867 | [Project_6.4.0] While setting the Password function to No Change, the password field changes to read-only and can't be edited. |
| 635507 | [Project_6.4.0] While changing FortiGate profile, it should unbind template first. |
| 635544 | [Project_6.4.0] Some AP prefixes are not mapping, and AP can't successfully authorize. |
| 635772 | If the key of cookies in FMG GUI API changes, then SD-WAN Orchestrator MEA may not start up. |
| 636660 | [Project_6.4.0] After enabling fortilink and managed FortiSwitch, changing the profile with default settings will cause conflict. |
| 636758 | [Project_6.4.0] While enabling client limit, the maximum client count cannot be set to 4294967295. |
| 637182 | [Project_6.4.0] AP profile is unable to be removed in FortiGate 200E. |
| 637224 | [Project_6.4.0] (SW/AP) Change Auto Power Level to Auto TX Power on SW/AP Profile GUI. |
| 637239 | [Project_6.4.0] Unable to add KVM FortiGate to SD-WAN Orchestrator MEA. |
| 637297 | [Project_6.4.0] Several filters do not work well in Business rule view page. |
| 637304 | [Project_6.4.0] Create nearly all FortiManager objects in business rule, and dropdown list will fail due to the reference page error. |
| 637629 | [Project_6.4.0] (SW/AP) While enabling Auto TX Power, the TX Power High cannot be less than TX Power Low. |
| 637800 | [Project_6.4.0] Cannot unselect after the user selects a device filter. |
| 638106 | [Project_6.4.0] Script execution misalignment causes conflict. |
| 639004 | [Project_6.4.0] The max clients value should not be set over 4294967295. |
| 639017 | [Project_6.4.0] While adding multiple FortiSwitch units, the configuration will be out of order. |
| 639347 | [Project_6.4.0] Adding FortiGate 60E to SD-WAN Orchestrator MEA will cause conflict. |
| 639390 | [Project_6.4.0] Restored FortiManager failed to recover SD-WAN Orchestrator MEA configuration. |
| 639438 | [Project_6.4.0] Several filters do not work well in Business rule view page. |
| 639666 | [Project_6.4.0] Due to unknown reasons, Synchronizing status is always displayed after synchronizing all. |