The problem is a timing issue, so sometimes traffic will be unaffected when making this configuration change and other times it may be blocked.Īfter factory resetting an FPM, if the configuration synchronized to it contains EMAC VLAN interfaces, the MAC addresses of the EMAC VLAN interfaces on the FPM may be different from the MAC addresses of the same EMAC VLAN interfaces on the primary FIM. Operating a FortiGate-6000 or 7000 as an SSL VPN client is not supported.Ĭhanging the FPC or FPM that an IPsec tunnel is using can cause traffic in the tunnel to be blocked.
Policy statistics data that appear on the GUI firewall policy pages and in FortiView may be incorrect.Īfter successfully resetting a managed FortiSwitich from the FortiGate-6000 or 7000 GUI, a Failed to factory reset FortiSwitich message may appear. The FPM will continue to operate normally after fully starting. Even when these error messages appear the FortiGate should start up normally, running the newer firmware version, and should be able to join the cluster.Īn FPM may display an incorrect checksum message on the console while restarting. After the firmware is downloaded and before the FortiGate restarts, the console may display incorrect error messages. During cluster formation, the newer firmware version is installed on FortiGate running the older firmware version. When setting up a FortiGate-6000 or 7000 FGCP HA cluster, one of the FortiGates in the cluster may be running an older firmware version. Interface bandwidth dashboard widgets show incorrect outbound bandwidth usage.
Some GUI pages may randomly take longer to load than expected or not load at all. The Known issues described in the FortiOS 7.0.5 release notes also apply to FortiGate-60 FortiOS 7.0.10 Build 0117. For inquires about a particular bug, please contact Customer Service & Support. The following issues have been identified in FortiGate-6000 and FortiGate-7000 FortiOS 7.0.10 Build 0117. Known issues | FortiGate / FortiOS 7.0.10
0 kommentar(er)
