Resolved Issues
The following issues have been fixed in 6.4.1.r5. For inquires about a particular bug, please contact Customer Service & Support.
Bug ID |
Description |
---|---|
678140 |
RETRIEVE_CONFIG doesn't properly import some of existing configurations. |
681956 |
User can choose the secondary hub or link from the Dual Hub Load Mode option, only when the primary hub is down. |
682621 |
Importing SDWAN O R3 configuration into the SDWAN O R4 version changes the Hub role profile to the Edge role profile. |
681612 | ADVPN shortcuts never expire. |
633828 | The set
preserve-session-route is always set to Enable on IPsec tunnels. |
677972 | The SD-WAN Orchestrator API connection is denied if the FortiGate has a non-standard HTTPS port. |
677129 | Log shows the controller version always goes from 256 to the latest build number while upgrading. |
681618 | Unfiltered prefix advertisement between Hubs causes internal prefixes to be resolved via Internet underlays. |
670929 | Orchestrator
configures set preserve-session-route enable on interfaces by
default. |
670835 | Default static route updates in Health Checks brings down all tunnels. |
677654 |
Revised SD-WAN release numbers. |
685583 |
Sync all will cause a conflict with Blackhole when executing the backup and restoring the configuration. |
685584 |
Switching ADOM may cause the Maintenance menu to disappear. |
678142 |
Default
route via all overlays (due to static |
685747 | If an IP pool conflicts with a WAN IP address, a message should be reported, and do not allow sync all to be clicked. |
668211 |
If FortiManager tasks fail, the retrieve action will change the HA mode to Standalone mode. |