Known issues
The following issues have been identified in version 7.2.8. To inquire about a particular bug or report a bug, please contact Customer Service & Support.
Anti Virus
Bug ID |
Description |
---|---|
937375 |
Unable to delete malware threat feeds using the CLI. |
Explicit Proxy
Bug ID |
Description |
---|---|
865828 |
The |
890776 |
The GUI-explicit-proxy setting on the System > Feature Visibility page is not retained after a FortiGate reboot or upgrade. |
894557 |
In some cases, the explicit proxy policy list can take a long time to load due to a delay in retrieving the proxy statistics. This issue does not impact explicit proxy functionality. Workaround: restart the WAD process, or update the number of WAD processors. config system global set wad-worker-count <integer> end |
1001700 |
If explicit webproxy uses SAML authentication and the PAC file is enabled at the same time, the browser will report a too many redirects error when trying to visit any websites. |
Firewall
Bug ID |
Description |
---|---|
935034 |
The clock skew tolerance is not reflected. |
951984 |
The best output route may not be found for local out DNAT traffic. |
FortiGate 6000 and 7000 platforms
Bug ID |
Description |
---|---|
638799 |
The DHCPv6 client does not work with vcluster2. |
790464 |
Existing ARP entries are removed from all slots when an ARP query of a single slot does not respond. |
885205 |
IPv6 ECMP is not supported for the FG-6000F and FG-7000E platforms. IPv6 ECMP is supported for the FG-7000F platform. |
940541 |
A permanent MAC address is used instead of an HA virtual MAC address during automation. |
951135 |
Graceful upgrade of a FortiGate 6000 or 7000 FGCP HA cluster is not supported when upgrading from FortiOS 7.0.12 to 7.2.6. Upgrading the firmware of a FortiGate 6000 or 7000 FGCP HA cluster from 7.0.12 to 7.2.6 should be done during a maintenance window, since the firmware upgrade process will disrupt traffic for up to 30 minutes. Before upgrading the firmware, disable |
951193 |
SLBC for FortiOS 7.0 and 7.2 uses different FGCP HA heartbeat formats. Because of the different heartbeat formats, you cannot create an FGCP HA cluster of two FortiGate 6000s or 7000s when one chassis is running FortiOS 7.0.x and the other is running FortiOS 7.2.x. Instead, to form an FGCP HA cluster, both chassis must be running FortiOS 7.0.x or 7.2.x. If two chassis are running different patch releases of FortiOS 7.0 or 7.2 (for example, one chassis is running 7.2.5 and the other 7.2.6), they can form a cluster. When the cluster is formed, FGCP elects one chassis to be the primary chassis. The primary chassis synchronizes its firmware to the secondary chassis. As a result, both chassis will be running the same firmware version. You can also form a cluster if one chassis is running FortiOS 7.2.x and the other is running 7.4.x. For best results, both chassis should be running the same firmware version, although as described above, this is not a requirement. |
954881 |
Image synchronization failure happened after a factory reset on FortiGate 7000E/F . |
983236 |
Under normal conditions, a FortiGate 6000 or 7000 may generate event log messages due to a known issue with a feature added to FortiOS 7.2 and 7.4. The feature is designed to create event log messages for certain DP channel traffic issues but also generates event log messages when the DP processor detects traffic anomalies that are part of normal traffic processing. This causes the event log messages to detect false positives that don't affect normal operation. For example, DP channel 15 RX drop detected! messages can be created when a routine problem is detected with a packet that would normally cause the DP processor to drop the packet. Similar discard message may also appear if the DP buffer is full. |
994241 |
On FortiGate 7000F using FGSP and FGCP, when TCP traffic takes an asymmetric path, the TCP ACK and data packets might be dropped in NP7. |
1003879 |
Incorrect SLBC traffic-related statistics may be displayed on the FortiGate 6000 or FortiGate 7000 GUI (for example, in a dashboard widgets). This can occur if an FPC or FPM is not correctly registered for statistic collection during startup. This is purely a GUI display issue and does not impact system operation. To work around this display issue, enter the command |
1025652 |
On the FortiGate 7000E platform, after upgrading firmware from 7.2.8 to 7.4.x, the CLI of the secondary FIM and the FPMs in the secondary chassis of an FGCP cluster may display This firmware failed signature validation. This error message is displayed because of a known issue. The firmware is valid and the FortiGate 7000E cluster will operate normally. |
FortiView
Bug ID |
Description |
---|---|
941521 |
On the FortiView Web Sites page, the Category filter does not work in the Japanese GUI. |
GUI
Bug ID |
Description |
---|---|
853352 |
On the View/Edit Entries slide-out pane (Policy & Objects > Internet Service Database dialog), users cannot scroll down to the end if there are over 100000 entries. |
854180 |
On the policy list page, all policy organization with sequence and label grouping is lost. |
974988 |
FortiGate GUI should display a license expired notification due to an expired FortiManager Cloud license if it still has a valid account level FortiManager Cloud license (function is not affected). |
996379 |
The address objects page is not loading the content. |
999972 |
Edits that are made to IP Exemptions in IPS Signatures and Filters more than once on the Security Profiles > Intrusion Prevention page are not saved. |
HA
Bug ID |
Description |
---|---|
825380 |
When workspace configuration save mode is set to manual in the System > Settings, configuration changes made on the primary unit and then saved do not synchronize with the secondary unit when one of the cluster units are rebooted or shutdown after the change. Workaround: set the workspace configuration mode to automatic. |
858683 |
FortiGate in A-P HA mode with |
929486 |
When Configuration save mode is set to Manual, any firewall policy change will make the cluster out-of-sync. |
940400 |
SCTP traffic is not forwarded back to the session owner (FGSP asymmetric traffic with IPS , NAT mode, and SCTP). |
988944 |
On the Fabric Management page, the HA Secondary lists both primary and secondary FortiGate units. |
998004 |
When the HA management interface is set a LAG, it is not synchronized to newly joining secondary HA devices. |
1000001 |
A secondary HA unit may go into conserve mode when joining an HA cluster if the FortiGate's configuration is large. |
1011674 |
Upgrading from 7.0.14 or 7.2.8 on the HA secondary device will fail with BIOS security level 2. The image is marked |
Hyperscale
Bug ID |
Description |
---|---|
802182 |
After successfully changing the VLAN ID of an interface from the CLI, an error message similar to |
817562 |
NPD/LPMD cannot differentiate the different VRF's, considers as VRF 0 for all. |
824071 |
ECMP does not load balance IPv6 traffic between two routes in a multi-VDOM setup. |
843197 |
Output of |
853258 |
Packets drop, and different behavior occurs between devices in an HA pair with ECMP next hop. |
872146 |
The |
920228 |
NAT46 NPU sessions are lost and traffic drops when a HA failover occurs. |
936747 |
Connections per second (CPS) performance of SIP sessions accepted by hyperscale firewall policies with EIM and EIF disabled that include overload with port block allocation (PBA) GCN IP pools is lower than expected. Workaround: enter the following command for each NP7 processor to resolve the performance issue. # diagnose npu np7 setreg <npu_#> nss.nss_thrd_ctrl.thrd_ctrl 0xF Where The configuration changes from entering these diagnose commands are reset if the FortiGate restarts. After a system restart, just re-enter the diagnose commands. |
994019 |
Hairpin is not working. |
IPsec VPN
Bug ID |
Description |
---|---|
944600 |
CPU usage issues occurred when IPsec VPN traffic was received on the VLAN interface of an NP7 vlink. |
954614 |
IPsec phase 2 negotiation fails with |
Log & Report
Bug ID |
Description |
---|---|
872493 |
Disk logging files are cached in the kernel, causing high memory usage. Fixed in FortiOS 7.2.8: Issue with Disk log has rolled case. |
938396 |
|
1001583 |
The GUI is slow and reverts the input when multiple ports are added to a filter for destination ports. |
Proxy
Bug ID |
Description |
---|---|
910678 |
CPU usage issue in WAD caused by a high number of devices being detected by the device detection feature. |
922093 |
CPU usage issue in WAD caused by source port exhaustion when using WAN optimization. |
REST API
Bug ID |
Description |
---|---|
859680 |
In an HA setup with vCluster, a CMDB API request to the primary cluster does not synchronize the configuration to the secondary cluster. |
920260 |
SD-WAN interfaces should be denoted in the interface statistics API. |
1004136 |
Unable to fetch more than 1000 logs using an REST API GET request. |
Routing
Bug ID |
Description |
---|---|
896090 |
SD-WAN members can be out-of-sla after some retrieve times. |
903444 |
The |
910656 |
Router information in the BGP summary still shows removed BGP neighbor/peer configuration. |
924693 |
On the Network > SD-WAN > SD-WAN Rules page, member interfaces that are down are incorrectly shown as up. The tooltip on the interface shows the correct status. |
1003756 |
When creating a rule on the Network > Routing Objects page, the Prefix-list is set to 0.0.0.0 0.0.0.0 when an incorrect format is entered in the Prefix field. |
Security Fabric
Bug ID |
Description |
---|---|
958429 |
The webhook request header does not contain |
SSL VPN
Bug ID |
Description |
---|---|
795381 |
FortiClient Windows cannot be launched with SSL VPN web portal. |
905050 |
SSL VPN users are dropped due the samld process stopping. |
941676 |
Japanese key input does not work correctly during RDP in SSL VPN web mode. |
947210 |
Application sslvpnd |
Switch Controller
Bug ID |
Description |
---|---|
947351 |
The FortiSwitch topology is not loading correctly on the GUI. |
951721 |
The FortiGate GUI shows incorrect port statuses for managed FortiSwitches. |
961142 |
An interface in FortiLink is flapping with MCLAG with DAC on an OPSFPP-T-05-PAB transceiver. |
1000663 |
The switch-controller managed-switch ports' configurations are getting removed after each reboot. |
System
Bug ID |
Description |
---|---|
782710 |
Traffic going through a VLAN over VXLAN is not offloaded to NP7. |
861144 |
|
882862 |
LAG interface members are not shutting down when the remote end interface (one member in the LAG) is down. |
885189 |
Control the server host key algorithm in the CLI. |
887940 |
Status light is not showing on the FortiGate 60F or 100F after a cold and warm reboot. |
901621 |
Setting the interface configuration |
901721 |
In a certain edge case, traffic directed towards a VLAN interface could trigger a kernel panic. |
921134 |
GUI is inaccessible when using a SHA1 certificate as |
921604 |
On the FortiGate 601F, the ports (x7) have no cables attached but the link LEDs are green. |
925554 |
On the Network > Interfaces page, hardware and software switches show VLAN interfaces as down instead of up. The actual status of the VLAN interface can be verified using the command line. |
939013 |
SNMP walk of the entire MIB fails when the configuration has split-port and a large number of interfaces. |
967436 |
DAC cable between FortiGate and FortiSwitch stops working after upgrading from 7.2.6 to 7.2.7. |
1006024 |
On FortiOS, administrator accounts using |
1012518 |
Some FortiGate models on NP6/NP6Lite/NP6xLite platforms experience kernel panics due to certain traffic conditions after upgrading to 7.2.8. Traffic may be interrupted momentarily. Workaround: Users impacted by this issue can contact Fortinet Support to request a special build with a fix for this issue. Alternatively, users can disable the processing of traffic by the IPS engine’s nTurbo using the following command: config ips global set np-accel-mode none end |
1014624 |
On the FortiGate 1800F, the 40G interface's status is DOWN after upgrading to 7.2.8. |
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. |
977281 |
After the FortiGate in an HA environment is upgraded using the Fabric upgrade feature, the GUI might incorrectly show the status Downgrade to 7.2.X shortly, even though the upgrade has completed. This is only a display issue; the Fabric upgrade will not recur unless it is manually scheduled. Workaround: Confirm the Fabric upgrade status to make sure that it is not enabled: config system federated-upgrade set status disabled end |
User & Authentication
Bug ID |
Description |
---|---|
667150 |
When a remote LDAP user with Two-factor Authentication enabled and Authentication type 'FortiToken' tries to access the internet through firewall authentication, the web page does not receive the FortiToken notification or proceed to authenticate the user. Workaround: click the Continue button on the authentication page after approving the FortiToken on the mobile device. |
933622 |
The FortiGate does not send the user's IP address to the TACACS+ server during an authorization request. |
1003405 |
When there are over 5000 firewall users, the minimized Firewall Users widget on the dashboard does not display the donut chart or number of users. Expanding the widget to full screen displays all users. |
1012337 |
Administrator authentication using RADIUS is not working with Cisco ACS. |
VM
Bug ID |
Description |
---|---|
899984 |
If FGTVM was deployed in UEFI boot mode, do not downgrade to any GA version earlier than 7.2.4. |
923061 |
IPsec tunnels on AWS have TX errors incremented every 30 seconds. |
Web Filter
Bug ID |
Description |
---|---|
885222 |
HTTP session is logged as HTTPS in web filter when VIP is used. |
1004985 |
The webfilter cookie override trigger process had no issue observed and an override entry was created in the FortiGate, but client access was kept blocked by the old profile and the client received a replacement message with an override link just like the initial access to trigger the override. |
WiFi Controller
Bug ID |
Description |
---|---|
869106 |
The layer 3 roaming feature may not work when the wireless controller is running multiple cw_acd processes (when the value of |
869978 |
CAPWAP tunnel traffic over tunnel SSID is dropped when offloading is enabled. |
873273 |
The Automatically connect to nearest saved network option does not work as expected when FWF-60E client-mode local radio loses connection. |
903922 |
Physical and logical topology is slow to load when there are a lot of managed FortiAP (over 50). This issue does not impact FortiAP management and operation. |
938840 |
Excessive |
941691 |
Managed FortiSwitch detects multiple MACs using the same IP address. |
949682 |
Intermittent traffic disruption observed in cw_acd caused by a rare error condition. |
1001104 |
Some FortiAP 231F units show join/leave behavior after the FortiGate is upgraded to 7.2.7. |
ZTNA
Bug ID |
Description |
---|---|
819987 |
SMB drive mapping made through a ZTNA access proxy is inaccessible after rebooting. |