Fortinet black logo

FortiGate-6000 and FortiGate-7000 Release Notes

Resolved issues

Resolved issues

The following issues have been fixed in FortiGate-6000 and FortiGate-7000 FortiOS 6.2.11 Build 1223. For inquires about a particular bug, please contact Customer Service & Support. The Resolved issues described in the FortiOS 6.2.11 release notes also apply to FortiGate-6000 and 7000 FortiOS 6.2.11 Build 1223.

Bug ID

Description

697423

FortiGate-7121F cross-FIM LAGs now work as expected.

705958

Dialup server IPsec VPN tunnels are now successfully synchronized to all FPCs or FPMs when mode-cfg is enabled.

792717 783153

Resolved an issue that caused large numbers of IPsec VPN clients with dead peer detection (DPD) enabled to temporarily block dialup IPsec VPN tunnel traffic.

803585 Resolved memory leak issues that could cause a FortiGate-6000 or 7000 to enter conserve mode and become unresponsive because of high memory utilization.
813352 The get vpn ssl monitor command now works as expected to accurately show all active SSL VPN tunnels.
819521 818058

Resolved an issue that prevented the miglogdisk_info file from being updated correctly when a FortiGate-7121F starts up or restarts.The miglogdisk_info file that is present on all FIMs and FPMs should be updated by reading current log disk information every time a FortiGate-7121F chassis restarts. This problem also caused FortiGate-7121F FPMs to be out of synchronization.

822433

The diagnose sys link-monitor status command now displays correct information.

822976 Resolved an issue that caused some routes used by IPsec VPNs to be unexpectedly missing from the kernel routing table.
824106 Resolved an issue that could cause a kernel panic in an HA cluster with fortilink interfaces. For example, the kernel panic could occur if an interface has been configured to be a fortilink interface, the fortilink interface is set to be down, and one of the FortiGates is removed from the cluster and then added back to the cluster.

825086

Resolved an issue how virtual MAC address were calculated that caused local in and local out traffic to be blocked after configuring virtual clustering and enabling virtual cluster 2.

Resolved issues

The following issues have been fixed in FortiGate-6000 and FortiGate-7000 FortiOS 6.2.11 Build 1223. For inquires about a particular bug, please contact Customer Service & Support. The Resolved issues described in the FortiOS 6.2.11 release notes also apply to FortiGate-6000 and 7000 FortiOS 6.2.11 Build 1223.

Bug ID

Description

697423

FortiGate-7121F cross-FIM LAGs now work as expected.

705958

Dialup server IPsec VPN tunnels are now successfully synchronized to all FPCs or FPMs when mode-cfg is enabled.

792717 783153

Resolved an issue that caused large numbers of IPsec VPN clients with dead peer detection (DPD) enabled to temporarily block dialup IPsec VPN tunnel traffic.

803585 Resolved memory leak issues that could cause a FortiGate-6000 or 7000 to enter conserve mode and become unresponsive because of high memory utilization.
813352 The get vpn ssl monitor command now works as expected to accurately show all active SSL VPN tunnels.
819521 818058

Resolved an issue that prevented the miglogdisk_info file from being updated correctly when a FortiGate-7121F starts up or restarts.The miglogdisk_info file that is present on all FIMs and FPMs should be updated by reading current log disk information every time a FortiGate-7121F chassis restarts. This problem also caused FortiGate-7121F FPMs to be out of synchronization.

822433

The diagnose sys link-monitor status command now displays correct information.

822976 Resolved an issue that caused some routes used by IPsec VPNs to be unexpectedly missing from the kernel routing table.
824106 Resolved an issue that could cause a kernel panic in an HA cluster with fortilink interfaces. For example, the kernel panic could occur if an interface has been configured to be a fortilink interface, the fortilink interface is set to be down, and one of the FortiGates is removed from the cluster and then added back to the cluster.

825086

Resolved an issue how virtual MAC address were calculated that caused local in and local out traffic to be blocked after configuring virtual clustering and enabling virtual cluster 2.