Fortinet white logo
Fortinet white logo

FortiGate-6000 Release Notes

Known issues

Known issues

The following issues have been identified in FortiGate-6000 and FortiGate-7000 FortiOS 6.0.18 Build 0429. For inquires about a particular bug, please contact Customer Service & Support. The Known Issues described in the FortiOS 6.0.18 release notes also apply to FortiGate-6000 and 7000 FortiOS 6.0.18 Build 0429.

Bug ID Description

594258

FortiSwitch management over FortiLink does not work as expected on a FortiGate-7000E system when the FIM in slot 2 is the primary FIM.

684425 716377

707785

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.

697097

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

703185

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.

711324

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

716230

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

718917

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.

740432

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.

742271 742171

The nsm process may crash or become unresponsive.

801594

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

Known issues

Known issues

The following issues have been identified in FortiGate-6000 and FortiGate-7000 FortiOS 6.0.18 Build 0429. For inquires about a particular bug, please contact Customer Service & Support. The Known Issues described in the FortiOS 6.0.18 release notes also apply to FortiGate-6000 and 7000 FortiOS 6.0.18 Build 0429.

Bug ID Description

594258

FortiSwitch management over FortiLink does not work as expected on a FortiGate-7000E system when the FIM in slot 2 is the primary FIM.

684425 716377

707785

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.

697097

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

703185

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.

711324

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

716230

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

718917

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.

740432

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.

742271 742171

The nsm process may crash or become unresponsive.

801594

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