FortiGate-7000 FGSP session synchronization does not work if the session synchronization interface is on the secondary FIM instead of the primary FIM.

The mechanism for synchronizing the FIB to FPCs or FPMs when a FPC or FPM reboots or after an HA failover should be more efficient and cause fewer errors. This problem can cause BGP routing to stop working. BGP can be restarting by shutting down and restarting BGP neighbors.

Under some conditions, after a FortiGate-7000 factory reset, one of the FIMs can't synchronize.

When an API user, created with the config system api-user command, is deleted from the FortiGate-6000 management board or FortiGate-7000 primary FIM, the user may not be deleted from the FPCs and FPMs, resulting in configuration synchronization errors.

FortiView VPN pages may not show any data even when VPNs are active.

Entering the command diagnose vpn tunnel up <tunnel-name> returns an error message similar to Command fail. Return code -1.

In some cases, license information is incorrectly synchronized from the primary FortiGate-6000 or 7000 to the FPCs or FPMs in the secondary FortiGate-6000 or 7000.

Error messages similar to config error: "global.webfilter.profile.g-sniffer-profile:failed command" may appear on the console when a FortiGate-6000 or 7000 starts up.