Known issues
The following issues have been identified in version 7.2.1. To inquire about a particular bug or report a bug, please contact Customer Service & Support.
Anti Virus
|
Bug ID |
Description |
|---|---|
| 869398 |
FortiGate sends too many unnecessary requests to FortiSandbox and causes high resource usage. |
Explicit Proxy
|
Bug ID |
Description |
|---|---|
|
803228 |
When converting an explicit proxy session to SSL redirect, traffic may be interrupted inadvertently in some situations. |
GUI
|
Bug ID |
Description |
|---|---|
|
677806 |
On the Network > Interfaces page when VDOM mode is enabled, the Global view incorrectly shows the status of IPsec tunnel interfaces from non-management VDOMs as up. The VDOM view shows the correct status. |
|
719476 |
FortiLink NAC matched device is displayed in the CLI but not in the GUI under WiFi & Switch Controller > NAC Policies > View Matched Devices. |
|
825598 |
The FortiGate may display a false alarm message |
|
833306 |
Intermittent error, Failed to retrieve FortiView data, appears on real-time FortiView Sources and FortiView Destination monitor pages. |
|
835089 |
Unable to move SD-WAN rule ordering in the GUI (FortiOS 7.2.1). Workaround: move the SD-WAN rule ordering in the CLI. |
HA
|
Bug ID |
Description |
|---|---|
|
823687 |
A cluster is repeatedly out-of sync due to external files (SSLVPN_AUTH_GROUPS) when there are frequent user logins and logouts. |
Hyperscale
|
Bug ID |
Description |
|---|---|
|
824071 |
ECMP does not load balance IPv6 traffic between two routes in a multi-VDOM setup. |
|
824733 |
IPv6 traffic continues to pass through a multi-VDOM setup, even when the static route is deleted. |
IPsec VPN
|
Bug ID |
Description |
|---|---|
|
763205 |
IKE crashes after HA failover when the |
Proxy
|
Bug ID |
Description |
|---|---|
|
799237 |
WAD crash occurs when TLS/SSL renegotiation encounters an error. |
Routing
|
Bug ID |
Description |
|---|---|
|
833399 |
Static routes are incorrectly added to the routing table, even if the IPsec tunnel type is static. |
Security Fabric
|
Bug ID |
Description |
|---|---|
| 825291 |
Security rating test for FortiAnalyzer fails when connected to FortiAnalyzer Cloud. |
SSL VPN
|
Bug ID |
Description |
|---|---|
|
795381 |
FortiClient Windows cannot be launched with SSL VPN web portal. |
|
819754 |
Multiple DNS suffixes cannot be set for the SSL VPN portal. |
System
|
Bug ID |
Description |
|---|---|
|
798303 |
The threshold for conserve mode is lowered. |
|
832429 |
Random kernel panic may occur due to an incorrect address calculation for the internet service entry's IP range. |
|
837730 |
Trusted hosts are not working correctly in FortiOS 7.2.1. |
|
847077 |
|
|
1041457 |
The kernel 4.19 cannot concurrently reassemble IPv4 fragments for a source IP with more than 64 destination IP addresses. |
Upgrade
|
Bug ID |
Description |
|---|---|
| 925567 |
When upgrading multiple firmware versions in the GUI, the Follow upgrade path option does not respect the recommended upgrade path. |
User & Authentication
|
Bug ID |
Description |
|---|---|
|
825505 |
After a few days, some devices are not displayed in the Users & Devices > Device Inventory widget and WiFi & Switch Controller > FortiSwitch Ports page's Device Information column due to a mismatch in the device count between the following commands.
Workaround: restart the WAD process or reboot the FortiGate to recover the device count for the user device store list. |
VM
|
Bug ID |
Description |
|---|---|
| 1082197 | The FortiGate-VM on VMware ESXi equipped with an Intel E810-XXV network interface card (NIC) using SFP28 transceivers at 25G speed is unable to pass VLAN traffic when DPDK is enabled. |
Web Filter
|
Bug ID |
Description |
|---|---|
|
766126 |
Block replacement page is not pushed automatically to replace the video content when using a video filter. |
ZTNA
|
Bug ID |
Description |
|---|---|
|
832508 |
The EMS tag name (defined in the EMS server's Zero Trust Tagging Rules) format changed in 7.2.1 from After upgrading from 7.2.0 to 7.2.1, the EMS tag format was converted properly in the CLI configuration, but the WAD daemon is unable to recognize this new format, so the ZTNA traffic will not match any ZTNA policies with EMS tag name checking enabled. Workaround: unset the |