Fortios v7.2.6 Release Notes
Fortios v7.2.6 Release Notes
Fortios v7.2.6 Release Notes
FortiOS 7.2.6
FORTINET DOCUMENT LIBRARY
https://docs.fortinet.com
FORTINET BLOG
https://blog.fortinet.com
FORTIGUARD LABS
https://www.fortiguard.com
FEEDBACK
Email: techdoc@fortinet.com
Change Log 6
Introduction and supported models 8
Supported models 8
Special branch supported models 8
FortiGate 6000 and 7000 support 9
Special notices 10
IPsec phase 1 interface type cannot be changed after it is configured 10
IP pools and VIPs are now considered local addresses 10
FortiGate 6000 and 7000 incompatibilities and limitations 10
Hyperscale incompatibilities and limitations 11
Remove support for SHA-1 certificate used for web management interface (GUI) 11
SMB drive mapping with ZTNA access proxy 11
Console error message when FortiGate 40xF boots 11
FortiGate models with 2 GB RAM cannot be a Security Fabric root 12
FortiAP-W2 models may experience bootup failure during automatic
firmware and federated upgrade process if they are powered by a managed
FortiSwitch's PoE port 13
Changes in CLI 14
Changes in default behavior 15
Changes in table size 16
New features or enhancements 17
Upgrade information 19
Fortinet Security Fabric upgrade 19
Downgrading to previous firmware versions 20
Firmware image checksums 21
Strong cryptographic cipher requirements for FortiAP 21
FortiGate VM VDOM licenses 21
VDOM link and policy configuration is lost after upgrading if VDOM and VDOM link have
the same name 21
FortiGate 6000 and 7000 upgrade information 22
IPS-based and voipd-based VoIP profiles 23
Upgrade error message 24
BIOS-level signature and file integrity checking during downgrade 25
GUI firmware upgrade does not respect upgrade path 26
Product integration and support 27
Virtualization environments 28
Language support 28
SSL VPN support 29
SSL VPN web mode 29
2023-10-03 Updated Resolved issues on page 30 and Known issues on page 50.
2023-10-04 Updated FortiGate models with 2 GB RAM cannot be a Security Fabric root on page 12.
2023-10-16 Updated Changes in default behavior on page 15, New features or enhancements on page 17,
Resolved issues on page 30, and Known issues on page 50.
2023-10-23 Updated IP pools and VIPs are now considered local addresses on page 10 and Resolved
issues on page 30.
2023-11-20 Updated Introduction and supported models on page 8, Resolved issues on page 30, and
Known issues on page 50.
2023-11-23 Updated Resolved issues on page 30 and Known issues on page 50.
2023-12-04 Updated Resolved issues on page 30 and Known issues on page 50.
2023-12-12 Updated Resolved issues on page 30 and Known issues on page 50.
2023-12-19 Updated Resolved issues on page 30 and Known issues on page 50.
2023-12-27 Updated Resolved issues on page 30 and Known issues on page 50.
2024-02-08 Updated Resolved issues on page 30, Known issues on page 50, and FortiGate models with 2
GB RAM cannot be a Security Fabric root on page 12.
2024-02-20 Updated Resolved issues on page 30 and Known issues on page 50.
2024-02-23 Added FortiAP-W2 models may experience bootup failure during automatic firmware and
federated upgrade process if they are powered by a managed FortiSwitch's PoE port on page
13 and BIOS-level signature and file integrity checking during downgrade on page 25.
2024-02-26 Updated FortiAP-W2 models may experience bootup failure during automatic firmware and
federated upgrade process if they are powered by a managed FortiSwitch's PoE port on page
13.
2024-03-18 Updated Resolved issues on page 30 and Known issues on page 50.
2024-04-01 Added GUI firmware upgrade does not respect upgrade path on page 26.
Updated Known issues on page 50.
2024-04-17 Updated Changes in CLI on page 14, Resolved issues on page 30, and Known issues on page
50.
This guide provides release information for FortiOS 7.2.6 build 1575.
For FortiOS documentation, see the Fortinet Document Library.
Supported models
The following models are released on a special branch of FortiOS 7.2.6. To confirm that you are running the correct
build, run the CLI command get system status and check that the Branch point field shows 1575.
FortiOS 7.2.6 supports the following FG-6000F, FG-7000E, and FG-7000F models:
In FortiOS 7.2.0 and later, the IPsec phase 1 interface type cannot be changed after it is configured. This is due to the
tunnel ID parameter (tun_id), which is used to match routes to IPsec tunnels to forward traffic. If the IPsec phase 1
interface type needs to be changed, a new interface must be configured.
In FortiOS 7.2.6 and later, all IP addresses used as IP pools and VIPs are now considered local IP addresses if
responding to ARP requests on these external IP addresses is enabled (set arp-reply enable, by default). For
these cases, the FortiGate is considered a destination for those IP addresses and can receive reply traffic at the
application layer.
Previously in FortiOS 7.2.0 to 7.2.5, this was not the case. For details on the history of the behavior changes for IP pools
and VIPs, and for issues and their workarounds for the affected FortiOS versions, see Technical Tip: IP pool and virtual
IP behavior changes in FortiOS 6.4, 7.0, 7.2, and 7.4.
See the following links for information about FortiGate 6000 and 7000 limitations and incompatibilities with FortiOS 7.2.6
features.
l FortiGate 6000 incompatibilities and limitations
l FortiGate 7000E incompatibilities and limitations
See Hyperscale firewall incompatibilities and limitations in the Hyperscale Firewall Guide for a list of limitations and
incompatibilities with FortiOS 7.2.6 features.
Starting in FortiOS 7.2.5, users should use the built-in Fortinet_GUI_Server certificate or SHA-256 and higher
certificates for the web management interface. For example:
config system global
set admin-server-cert Fortinet_GUI_Server
end
In FortiOS 7.2.5 and later, SMB drive mapping on a Windows PC made through a ZTNA access proxy becomes
inaccessible after the PC reboots when access proxy with TCP forwarding is configured as FQDN. When configured with
an IP for SMB traffic, same issue is not observed.
One way to solve the issue is to enter the credentials into Windows Credential Manager in the form of
domain\username.
Another way to solve the issue is to leverage the KDC proxy to issue a TGT (Kerberos) ticket for the remote user. See
ZTNA access proxy with KDC to access shared drives for more information. This way, there is no reply in Credential
Manager anymore, and the user is authenticated against the DC.
In FortiOS 7.2.5 and later, FortiGate 400F and 401F units with BIOS version 06000100 show an error message in the
console when booting up.
The message, Write I2C bus:3 addr:0xe2 reg:0x00 data:0x00 ret:-121., is shown in the console, and
the FortiGate is unable to get transceiver information.
The issue is fixed in BIOS version 06000101.
A Security Fabric topology is a tree topology consisting of a FortiGate root device and downstream devices within the
mid-tier part of the tree or downstream (leaf) devices at the lowest point of the tree.
As part of improvements to reducing memory usage on FortiGate models with 2 GB RAM, this version of FortiOS no
longer allows these models to be the root of the Security Fabric topology or any mid-tier part of the topology. Therefore,
FortiGate models with 2 GB RAM can only be a downstream device in a Security Fabric or a standalone device.
The affected models are the FortiGate 40F, 60E, 60F, 80E, and 90E series devices and their variants.
FortiGate models with 2 GB RAM running FortiOS 7.4.2 or later can be used as the Security
Fabric root. See FortiGate models with 2 GB RAM can be a Security Fabric root.
To confirm if your FortiGate model has 2 GB RAM, enter diagnose hardware sysinfo conserve in the CLI and
check that the total RAM value is below 2000 MB (1000 MB = 1 GB).
In the GUI on the Security Fabric > Fabric Connectors page when editing the Security Fabric Setup card, the Security
Fabric role can only be configured as Standalone or Join Existing Fabric.
In the CLI, the following error messages are displayed when attempting to configure a FortiGate model with 2 GB RAM
as a Security Fabric root:
config system csf
set status enable
end
...
Disable automatic firmware upgrades and the federated upgrade feature if you have FortiAP-W2 devices that are
exclusively powered by a PoE port from a FortiGate or FortiSwitch.
The federated upgrade feature starts the upgrades of managed FortiSwitch and FortiAP devices start at approximately
the same time. Some FortiAP-W2 devices take a longer time to upgrade than the FortiSwitch devices. When the
FortiSwitch finishes upgrading, it reboots, and can disrupt the PoE power to the FortiAP devices. If a FortiAP device is
still upgrading when the power is disrupted, it can cause the FortiAP device to experience a bootup failure.
Both automatic firmware upgrade and manually triggering federated upgrade can cause this issue.
For more information about federated upgrade and automatic firmware upgrades, see Upgrading all device firmware by
following the upgrade path (federated update) and Enabling automatic firmware updates.
Bug ID Description
896333 You can use the diagnose span-sniffer packet command to sniff traffic on internal
FortiGate 6000 or 7000 interfaces in the same way as using the diagnose sniffer packet
command to sniff traffic on data or management interfaces. The diagnose span-sniffer
packet syntax is similar to the diagnose sniffer packet command syntax. Internal FortiGate
6000 or 7000 interfaces includes internal switch ports (for example, sw:1-P1, sw:7-P4) and the
DP processor (dp).
Command syntax for the packet sniffer part of the command is:
diagnose span-sniffer packet <interface> <filter> <verbose> <count>
<timestamp> <frame-size>
The <filter> option does not work for internal switch (sw:) interfaces. You can work around this
problem by using the default filter (which is "") and using grep to display the information you are
looking for. For example, use the following command to see echo request packets:
diagnose span-sniffer packet dp "" 4 | grep echo
913040 The config vpn ssl settings option tunnel-addr-assigned-method is now available
again in the FortiGate 6000 and 7000 CLI. This option had been removed in a previous release
because setting this option to first-available and configuring multiple IP pools was found to
reduce FortiGate 6000 and 7000 SSL VPN load balancing performance. However, some users may
want the ability to use multiple IP pools for their SSL VPN configuration, even if performance is
reduced. So the change has been reverted.
Bug ID Description
864035 When the auto-firmware-upgrade setting is enabled, the FortiGate checks for updates every
day between the firmware upgrade time interval. When a newer firmware is found, the installation is
scheduled after the upgrade delay in days (0-14, default = 3) between the firmware upgrade time
interval. After a successful update, an email is sent to the account owner.
config system fortiguard
set auto-firmware-upgrade {enable | disable}
set auto-firmware-upgrade-delay <integer>
end
Where:
l auto-firmware-upgrade is enabled by default upon upgrade.
930122 Automatic firmware upgrades are now enabled by default on entry-level FortiGates (lower than 100
series). Upgrades will be made to the next stable patch. However, if a FortiGate is part of a Fabric or
managed by FortiManager, the Automatic image upgrade option is disabled.
Bug ID Description
858877 Increase the number of supported dynamic FSSO IP addresses from 100 to 3000 per dynamic
FSSO group. The dynamic FSSO type addresses can be pointed to FortiManager's Universal
Connector, which imports the addresses from Cisco ACI or Guardicore Centra.
891426 Increase the Geneve table size to 1024 entries, and the virtual wire pair table size to 512 entries.
This enhancement provides greater flexibility and scalability for network configurations.
Feature ID Description
814242 The FortiGate 7000F platform supports setting a custom load balancing method for an individual
VDOM. All of the traffic destined for that VDOM will be distributed to FPMs by the NP7 load
balancers according to the following setting:
config system settings
set dp-load-distribution-method {derived | to-master | src-ip | dst-ip |
src-dst-ip | src-ip-sport | dst-ip-dport | src-dst-ip-sport-dport}
end
The default load balancing method, derived, means traffic for that VDOM uses the global load
balancing method set by the dp-load-distribution-method option of the global config
load-balance setting command.
Add password field to BGP neighbor group to be used for the neighbor range.
config router bgp
config neighbor-group
edit <name>
set password <password>
next
end
end
864021 Introduce the new Firmware Virtual Patch (FMWP) database to support local-in virtual patching. To
install the FMWP database, the FortiGate must have a valid Firmware (FMWR) license. The FMWP
database can be viewed by running the diagnose autoupdate versions command.
875306 Add new command to compute the SHA256 file hashes for each file in a directory.
# diagnose sys filesystem hash
884772 Securely exchange serial numbers between FortiGates connected with IPsec VPN. This feature is
supported in IKEv2, IKEv1 main mode, and IKEv1 aggressive mode. The exchange is only
performed with participating FortiGates that have enabled the exchange-fgt-device-id setting
under config vpn ipsec phase1-interface.
Feature ID Description
897240 The Any/All GUI selector for ZTNA tags is added back to the simple and full ZTNA policy
configuration page. The setting is defaulted to Any.
899827 Improve the client-side settings of the SD-WAN network bandwidth monitoring service to increase
the flexibility of the speed tests, and to optimize the settings to produce more accurate
measurements. The changes include:
l Support UDP speed tests.
904189 FortiOS can synchronize the FortiOS interface description with the VLAN description on the
FortiSwitch. Previously, only the FortiOS interface name could be synchronized as the VLAN
description on the FortiSwitch, and it was limited to 15 characters. This enhancement extends the
VLAN description length on the FortiSwitch from 15 characters to a new maximum of 64 characters.
config switch-controller global
set vlan-identity {name | description}
end
909935 FortiOS now includes a built-in entropy source, which eliminates the need for a physical USB
entropy token when booting up in FIPS mode on any platform. This enhancement continues to meet
the requirements of FIPS 140-3 Certification by changing the source of entropy to CPU jitter
entropy.
Supported upgrade path information is available on the Fortinet Customer Service & Support site.
1. Go to https://support.fortinet.com.
2. From the Download menu, select Firmware Images.
3. Check that Select Product is FortiGate.
4. Click the Upgrade Path tab and select the following:
l Current Product
5. Click Go.
FortiOS 7.2.6 greatly increases the interoperability between other Fortinet products. This includes:
FortiAnalyzer l 7.2.4
FortiManager l 7.2.4
*
If you are using FortiClient only for IPsec VPN or SSL VPN, FortiClient version 6.0 and later are supported.
When upgrading your Security Fabric, devices that manage other devices should be upgraded first.
When using FortiClient with FortiAnalyzer, you should upgrade both to their latest versions.
The versions between the two products should match. For example, if using FortiAnalyzer
7.2.0, use FortiClient 7.2.0.
Upgrade the firmware of each device in the following order. This maintains network connectivity without the need to use
manual steps.
1. FortiAnalyzer
2. FortiManager
3. Managed FortiExtender devices
4. FortiGate devices
5. Managed FortiSwitch devices
6. Managed FortiAP devices
7. FortiClient EMS
8. FortiClient
9. FortiSandbox
10. FortiMail
11. FortiWeb
12. FortiNAC
13. FortiVoice
14. FortiDeceptor
15. FortiNDR
16. FortiTester
17. FortiMonitor
18. FortiPolicy
If Security Fabric is enabled, then all FortiGate devices must be upgraded to 7.2.6. When
Security Fabric is enabled in FortiOS 7.2.6, all FortiGate devices must be running FortiOS
7.2.6.
Downgrading to previous firmware versions results in configuration loss on all models. Only the following settings are
retained:
l operation mode
l interface IP/management IP
l static route table
l DNS settings
l admin user account
l session helpers
l system access profiles
The MD5 checksums for all Fortinet software and firmware releases are available at the Customer Service & Support
portal, https://support.fortinet.com. After logging in, go to Support > Firmware Image Checksums (in the Downloads
section), enter the image file name including the extension, and click Get Checksum Code.
FortiOS 7.0.0 has removed 3DES and SHA1 from the list of strong cryptographic ciphers. To satisfy the cipher
requirement, current FortiAP models whose names end with letter E or F should be upgraded to the following firmware
versions:
l FortiAP (F models): version 6.4.3 and later
l FortiAP-S and FortiAP-W2 (E models): version 6.2.4, 6.4.1, and later
l FortiAP-U (EV and F models): version 6.0.3 and later
l FortiAP-C (FAP-C24JE): version 5.4.3 and later
If FortiGates running FortiOS 7.0.1 and later need to manage FortiAP models that cannot be upgraded or legacy FortiAP
models whose names end with the letters B, C, CR, or D, administrators can allow those FortiAPs' connections with
weak cipher encryption by using compatibility mode:
config wireless-controller global
set tunnel-mode compatible
end
FortiGate VMs with one VDOM license (S-series, V-series, FortiFlex) have a maximum number or two VDOMs. An
administrative type root VDOM and another traffic type VDOM are allowed in 7.2.0 and later. After upgrading to 7.2.0 and
later, if the VM previously had split-task VDOMs enabled, two VDOMs are kept (the root VDOM is an administrative
type).
Affected versions:
l FortiOS 6.4.9 and later
l FortiOS 7.0.6 and later
Upgrade FortiGate 6000 firmware from the management board GUI or CLI. Upgrade FortiGate 7000 firmware from the
primary FIM GUI or CLI. The FortiGate 6000 management board and FPCs or the FortiGate 7000 FIMs and FPMs all run
the same firmware image. Upgrading the firmware copies the firmware image to all components, which then install the
new firmware and restart. A FortiGate 6000 or 7000 firmware upgrade can take a few minutes, the amount of time
depending on the hardware and software configuration and whether DP or NP7 processor software is also upgraded.
On a standalone FortiGate 6000 or 7000, or an HA cluster with uninterruptible-upgrade disabled, the firmware
upgrade interrupts traffic because all components upgrade in one step. These firmware upgrades should be done during
a quiet time because traffic can be interrupted for a few minutes during the upgrade process.
Fortinet recommends running a graceful firmware upgrade of a FortiGate 6000 or 7000 FGCP HA cluster by enabling
uninterruptible-upgrade and session-pickup. A graceful firmware upgrade only causes minimal traffic
interruption.
Fortinet recommends that you review the services provided by your FortiGate 6000 or 7000
before a firmware upgrade and then again after the upgrade to make sure that these services
continue to operate normally. For example, you might want to verify that you can successfully
access an important server used by your organization before the upgrade and make sure that
you can still reach the server after the upgrade and performance is comparable. You can also
take a snapshot of key performance indicators (for example, number of sessions, CPU usage,
and memory usage) before the upgrade and verify that you see comparable performance after
the upgrade.
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 uninterruptible-upgrade, then perform a
normal firmware upgrade. During the upgrade process the FortiGates in the cluster will not
allow traffic until all components (management board and FPCs or FIMs and FPMs) are
upgraded and both FortiGates have restarted. This process can take up to 30 minutes.
2. Download the FortiOS 7.2.6 FG-6000F, FG-7000E, or FG-7000F firmware from https://support.fortinet.com.
3. Perform a normal upgrade of your HA cluster using the downloaded firmware image file.
4. When the upgrade is complete, verify that you have installed the correct firmware version.
For example, check the FortiGate dashboard or use the get system status command.
5. Confirm that all components are synchronized and operating normally.
For example, go to Monitor > Configuration Sync Monitor to view the status of all components, or use diagnose
sys confsync status to confirm that all components are synchronized.
Starting in FortiOS 7.2.5, the new IPS-based VoIP profile allows flow-based SIP to complement SIP ALG while working
together. There are now two types of VoIP profiles that can be configured:
config voip profile
edit <name>
set feature-set {ips | voipd}
next
end
A voipd-based VoIP profile is handled by the voipd daemon using SIP ALG inspection. This is renamed from proxy in
previous FortiOS versions.
An ips-based VoIP profile is handled by the IPS daemon using flow-based SIP inspection. This is renamed from flow in
previous FortiOS versions.
Both VoIP profile types can be configured at the same time on a firewall policy. For example:
config firewall policy
edit 1
set voip-profile "voip_sip_alg"
set ips-voip-filter "voip_sip_ips"
next
end
Where:
l voip-profile can select a voip-profile with feature-set voipd.
l ips-voip-filter can select a voip-profile with feature-set ips.
The VoIP profile selection within a firewall policy is restored to pre-7.0 behavior. The VoIP profile can be selected
regardless of the inspection mode used in the firewall policy. The new ips-voip-filter setting allows users to select
an IPS-based VoIP profile to apply flow-based SIP inspection, which can work concurrently with SIP ALG.
Upon upgrade, the feature-set setting of the voip profile determines whether the profile applied in the firewall
policy is voip-profile or ips-voip-filter.
When downgrading to a version of FortiOS prior to 6.4.13, 7.0.12, and 7.2.5 that does not support BIOS-level signature
and file integrity check during bootup, the following steps should be taken if the BIOS version of the FortiGate matches
the following versions:
l 6000100 or greater
l 5000100 or greater
To downgrade or upgrade to or from a version that does not support BIOS-level signature and file
integrity check during bootup:
1. If the current security level is 2, change the security level to 0. This issue does not affect security level 1 or below.
2. Downgrade to the desired FortiOS firmware version.
3. If upgrading back to 6.4.13, 7.0.12, 7.2.5, 7.4.0, or later, ensure that the security level is set to 0.
4. Upgrade to the desired FortiOS firmware version.
5. Change the security level back to 2.
When performing a firmware upgrade that requires multiple version jumps, the Follow upgrade path option in the GUI
does not respect the recommended upgrade path, and instead upgrades the firmware directly to the final version. This
can result in unexpected configuration loss. To upgrade a device in the GUI, upgrade to each interim version in the
upgrade path individually.
For example, when upgrading from 7.0.7 to 7.0.12 the recommended upgrade path is 7.0.7 -> 7.0.9 -> 7.0.11 -> 7.0.12.
To ensure that there is no configuration loss, first upgrade to 7.0.9, then 7.0.11, and then 7.0.12.
The following table lists FortiOS 7.2.6 product integration and support information:
Other browser versions have not been tested, but may fully function.
Other web browsers may function correctly, but are not supported by Fortinet.
Other browser versions have not been tested, but may fully function.
Other web browsers may function correctly, but are not supported by Fortinet.
Fortinet Single Sign-On l 5.0 build 0312 and later (needed for FSSO agent support OU in group filters)
(FSSO) l Windows Server 2022 Standard
l Windows Server 2022 Datacenter
l Windows Server 2019 Standard
l Windows Server 2019 Datacenter
l Windows Server 2019 Core
l Windows Server 2016 Datacenter
l Windows Server 2016 Standard
l Windows Server 2016 Core
l Windows Server 2012 Standard
l Windows Server 2012 R2 Standard
l Windows Server 2012 Core
l Windows Server 2008 64-bit (requires Microsoft SHA2 support
package)
l Windows Server 2008 R2 64-bit (requires Microsoft SHA2 support
package)
l Windows Server 2008 Core (requires Microsoft SHA2 support package)
l Novell eDirectory 8.8
AV Engine l 6.00293
Virtualization environments
Language support
Language support
Language GUI
English ✔
Chinese (Simplified) ✔
Chinese (Traditional) ✔
French ✔
Japanese ✔
Korean ✔
Portuguese (Brazil) ✔
Spanish ✔
The following table lists the operating systems and web browsers supported by SSL VPN web mode.
Microsoft Windows 7 SP1 (32-bit & 64-bit) Mozilla Firefox version 113
Google Chrome version 113
Other operating systems and web browsers may function correctly, but are not supported by Fortinet.
The following issues have been fixed in version 7.2.6. To inquire about a particular bug, please contact Customer
Service & Support.
Anti Spam
Bug ID Description
870052 Error condition in scanunitd occurs when email filter profile and proxy inspection are applied to a
firewall policy.
Anti Virus
Bug ID Description
908706 On the Security Profiles > AntiVirus page, a VDOM administrator with a custom administrator profile
cannot create or modify an antivirus profile belonging to the VDOM.
911332 When UTM status is enabled and the AV profile has no configuration, all SLL traffic is dropped and
there is no WAD output.
923883 The FortiGate may display an error log in the crash log due to AV delta update. In case of failure, a
full successful AV update is done.
Application Control
Bug ID Description
913529 The firewall policy dialog should show the no-inspection profile and the warning should be
consistent with the policy list.
939565 can not query meta rules list seen on graceful/non-graceful upgrade.
DNS Filter
Bug ID Description
931998 DNS filter flow external domain AAAA query can still check the default category but not the remote
category.
Endpoint Control
Bug ID Description
897048 FortiOS should support EMS 7.2.1 auth API status code changes.
913324 GUI repeated calls to the EMS API, which can cause EMS to not authorize the FortiGate correctly.
Explicit Proxy
Bug ID Description
817582 When there are many users authenticated by an explicit proxy policy, the Firewall Users widget can
take a long time to load. This issue does not impact explicit proxy functionality.
859693 Sessions between the explicit proxy and server stay in SYN_SENT state when using IP pools in the
explicit proxy policy for source NAT, even though the sessions have established. Traffic is not
impacted.
866316 Explicit web proxy fails to forward HTTPS request to a Squid forward server when certificate
inspection is applied.
888078 Enabling http-ip-header on virtual server changes the log produced for transparent web proxy.
889300 Wrong source IP address used for packets through explicit proxy routed to a member of SD-WAN
interface.
908989 The Enabled On should display the listening interfaces rather than None in explicit proxy policy on
the GUI.
934094 Some websites through explicit proxy randomly getting blocked after upgrade.
Firewall
Bug ID Description
843554 If the first firewall service object in the service list (based on the order in the command line table) has
a protocol type of IP, the GUI may incorrectly modify its protocol number whenever a new firewall
service of the same protocol type IP is created in the GUI.
This silent misconfiguration can result in unexpected behavior of firewall policies that use the
impacted service. For example, some 6K and 7K platforms have firewall service ALL (protocol type
IP) as the first service, and this can cause the ALL service to be modified unexpectedly.
872312 Unable to add more MAC addresses once the MAC address group object for a VWP policy
referenced.
879225 Egress interface cannot be intermittently matched for Wake-on-LAN (broadcast) packets.
895946 Access to some websites fails after upgrading to FortiOS 7.2.3 when the firewall policy is in flow-
based inspection mode.
909763 Wrong TOS field value in NetFlow report when there is no traffic.
912089 Optimize CPU usage caused by a rare error condition which leads to no data being sent to the
collector.
914939 UDP fragments dropped due to DF being set. Only the set honor-df global option.
926029 New sessions are created and evaluated after a certain number of UDP packets, even if set
block-session-timer 300 is set.
927009 When running tests with SNAT PBA source and destination IP addresses, octets are shown in
reverse order.
928896 set fixedport enable in a firewall policy does not preserve the source port for SNAT with IP
pool.
Bug ID Description
758078 After system synchronization, primary blades' reboot command did not take effect on the
secondaries.
888310 The FortiGate 6000 or 7000 front panel does not appear on the Network > Interfaces and System
> HA GUI pages.
888447 In some cases, the FortiGate 7000F platform cannot correctly reassemble fragmented packets.
Bug ID Description
891430 The FortiGate 6000 and 7000 System Information dashboard widget incorrectly displays the
management board or primary FIM serial number instead of the chassis serial number. Use get
system status to view the chassis serial number.
891642 FortiGate 6000 and 7000 platforms do not support managing FortiSwitch devices over FortiLink.
896758 Virtual clustering is not supported by FortiGate 6000 and 7000 platforms.
897629 The FortiGate 6000 and 7000 platforms do not support EMAC VLANs.
898191 Support SLBC integrated memory and disk logging in the new local logd framework.
899905 Adding a FortiAnalyzer to a FortiGate 6000 or 7000 Security Fabric configuration from the FortiOS
GUI is not supported.
901695 On FortiGate 7000F platforms, NP7-offloaded UDP sessions are not affected by the udp-idle-
timer option of the config system global command.
906481 The GUI becomes unresponsive, and sometimes may work after rebooting.
907140 Authenticated users are not synchronized to the secondary FortiGate 6000 or 7000 chassis when
the secondary chassis joins a primary chassis to form an FGCP cluster.
908576 On a FortiGate 7000F, after a new FPM becomes the primary FPM, IPsec VPN dynamic routes are
not synchronized to the new primary FPM.
908674 Sessions for IPsec dialup tunnels that are configured to be handled by a specific FPC or FPM may
be incorrectly sent to a different FPC or FPM, resulting in traffic being blocked.
909160 The FortiGate 7000E and 7000F platforms do not support GTP and PFCP load balancing.
910095 FGCP session synchronization may not synchronize all sessions on FortiGate 6000 and 7000
models.
911244 FortiGate 7000E IPv6 routes may not be synchronized correctly among FIMs and FPMs.
918795 An uncertified warning appears only on the secondary chassis' FIM02 and FPMs.
920925 Graceful upgrade from 7.0.12 to 7.2.5 fails sometimes due to the primary chassis not being
switched over.
947936 On the FortiGate 7060E, only four of six PSUs are shown sometimes.
FortiView
Bug ID Description
894957 On FortiView Websites, the real time view is always empty if disk logging is disabled.
920241 GUI shows Failed to retrieve FortiView data while accessing FortiView Sources and FortiView
Destination.
950137 FortiView Application widget cannot show data for explicit proxy traffic.
GUI
Bug ID Description
825598 The FortiGate may display a false alarm message TypeError [ERR_INVALID_URL]:
Invalid URL in the crashlog for the node process. This error does not affect the operation of the
GUI.
863126 In an environment where the Security Fabric is enabled and there are more than 100 firewall object
conflicts between the root and downstream FortiGates, the Firewall Object Synchronization pane
does not list the details.
892364 Incorrect interface is being selected in the SD-WAN Rules GUI page, but the correct one is
displayed in the CLI.
893560 When private data encryption is enabled, the GUI may become unresponsive and HA may fail to
synchronize the configuration.
898902 In the System > Administrators dialog, when there are a lot of VDOMs (over 200), the dialog can
take more than one minute to load the Two-factor Authentication toggle. This issue does not affect
configuring other settings in the dialog.
903856 When using configuration save mode with VDOMs, the GUI still shows unsaved changes after
another administrator commits their changes with SSH.
904817 Changing the IPv4/IPv6 version in the dropdown of one widget will also impact other Session Rate
widgets.
907041 Network > SD-WAN > SD-WAN Zones and SD-WAN Rules pages do not load if a shortcut tunnel is
triggered.
919390 Disabling gui-wireless-controller on the root VDOM impacts other VDOMs (unable to add
or show WiFi widgets on first load).
931486 Unexpected behavior in httpsd when the user has a lot of FQDN addresses.
HA
Bug ID Description
703614 HA secondary synchronization fails and keeps rebooting when the primary has a split port
configuration.
771316 Platforms in an HA environment get stuck in a reboot loop while attempting to synchronize
configurations that differ in split ports.
818432 When private data encryption is enabled, all passwords present in the configuration fail to load and
may cause HA failures.
870312 On a FortiGate HA cluster, both primary and secondary units are displayed as the Primary on the
GUI top banner, and as Current HA mode in the CLI.
875984 FortiGate is going to out-of-sync after changing parameters of VDOM link interfaces.
880786 Running diagnose sys ha vlan-hb-monitor incorrectly shows inter-VDOM VLANs inactive.
881337 Adding a VLAN interface on any VDOM causes BGP flapping and VIP connectivity issues on
VDOMs in vcluster2.
883546 In HA, sending lot of CLI configurations causes the creation of a VDOM on the secondary unit.
896608 HA cluster became out-of-sync after enabling a password policy and logging on to FortiGate.
897865 When NP7 platforms enable the GTP enhanced mode it does not use uninterruptible upgrade.
901292 When entering the psksecret under config system standalone-cluster, no verifications
are done against the password policy IPsec preshared key.
902945 Lost management connectivity to the standby node via in-band management.
904318 FortiGate sent ARP request with loopback IP address as the source address.
906036 Secondary blade hostname and mgmt1 IP were changed after a restored configuration on the
primary blade.
906367 When upgrading a cluster of four FortiGate 2200E devices, each secondary forms a cluster with the
primary only and causes an outage.
908062 FortiGate VM Azure HA cluster goes out-of-sync due to dynamic firewall address type.
916216 When adding a new interface, some other interfaces have the wrong virtual MAC address.
916903, When an HA management interface is configured, the GUI may not show the last interface entry in
919982, config system interface on several pages, such as the interface list, policy list, address list,
922867 and DNS servers page. This is a GUI-only display issue and does not impact the underlying
operation of the affected interface.
Bug ID Description
920233 The System > HA page is missing from the GUI on 5K models.
942502 Unexpected behavior occurred in the kernel when creating EMAC VLAN interfaces based on an
aggregate interface with the new kernel 4.1.9.
946878 When configuring an HA management interface, the GUI does not allow the same interface to be
used for multiple management interfaces.
Hyperscale
Bug ID Description
854933 The IPv6 neighbor cache configuration is missing after executing a reboot or flush command.
915796 With an enabled hyperscale license, in some cases with exception traffic (like ICMP error traverse),
the FortiGate may experience unexpected disruptions when handling the exception traffic.
919977 First-time HA failover after upgrading causes long service interruption to NAT44.
920405 Problem with synchronizing a high amount of routes to NP7 for hyperscale firewall.
932317 Hyperscale firewall creates a separate session and uses a different source port for IP fragment
packets.
Intrusion Prevention
Bug ID Description
823583 Failover on clustered web application using keepalived daemon does not work seamlessly.
842523 IPv6 with hardware offloading and IPS drops traffic (msg="anti-replay check fails,
drop).
845944 Firewall policy change causes high CPU spike with IPS engine.
860315 Unexpected behavior in IPS engine when executing diagnose test application
ipsmonitor 44.
Bug ID Description
873975 Source MAC changes and the packet drops due to both sides of the session using the same source
MAC address.
874877 IPS engines do not release memory after stopping traffic more than one hour.
886685 IPS daemon usage issue when notifying device vulnerability information to WAD.
892302 Constant reloading of the external domain table is causing high CPU due to lock contention when
reloading the table.
926639 Constant reloading of the shared memory external domain table is causing high CPU usage due to
lock contention when reloading the table.
968367 IPS engine high memory usage can cause FortiOS to go into conserve mode.
IPsec VPN
Bug ID Description
803010 The vpn-id-ipip encapsulated IPsec tunnel with NPU offloading cannot be reached by IPv6.
872769 Proxy ARP stops working for a client connected to a dialup IPsec when the previous VPN was
established and is deleted.
883138 VM running FIPS cipher mode does not show AES-CBC ciphers when configuring IPsec in the GUI.
921691 In FGSP, IKE routes are not removed from the kernel when secondary-add-ipsec-routes is
disabled.
928774 IPsec VPN connection should allow % in FortiClient Connect REG_PASSWD field.
Bug ID Description
831441 The forward traffic log show exabytes of data being sent and received from external to external IP
addresses in multiple VDOMs.
Bug ID Description
860822 When viewing logs on the Log & Report > System Events page, filtering by domain\username does
not display matching entries.
865794 Log Viewer: filter by Date/Time does not show correct result.
879446 diagnose sys logdisk smart does not work for NVME disk models.
893199 The FortiGate does not generate deallocate/allocate logs of the first IP pool when the first IP pool
has been exhausted.
902797 IPS alert email not being sent when IPS attack event has triggered.
908856 Traffic log can show exabytes of data sent and received when generating log task is triggered from
userspace.
929338 Secondary FortiGate log cannot be viewed from primary FortiGate in HA.
932817 Forward traffic log has unexpected symbols in the end for some logs.
940814 Administrators without read permissions for the threat weight feature cannot see the event log
menu.
Proxy
Bug ID Description
783549, An error condition occurs in WAD caused by multiple outstanding requests sent from client to server
902613, with UTM enabled.
921247
820096 CPU usage issue in Proxyd caused by the absence of TCP Teardown.
882182 Unexpected behavior in WAD due to the activation of firewall protocol options with both client and
server comfort features enabled.
883504 Emails are blocked when proxy-based policy with either AntiVirus or Email Filter security profiles
enabled.
897347 Memory usage issue caused by the WAD user info process while authenticating the LDAP users.
932487 Memory usage issue caused by WAD while using access proxy.
REST API
Bug ID Description
948356 An error condition occurs in HTTPSD when a REST API request is sent with invalid parameters.
Routing
Bug ID Description
820407 Auto-link fails if the FortiGate device initiating the FGFM connection is using an interface with a VRF
not set to the default, 0.
858248 OSPF summary address for route redistribution from static route via IPsec VPN always persists.
858299 Redistributed BGP routes to the OSPF change its forward address to the tunnel ID.
875668 SD-WAN SLA log information has incorrect inbound and outbound bandwidth values.
892704 SD-WAN performance SLA statistics on secondary unit's GUI section are not synchronized with the
primary and has stale data.
896891 With ICMP asymmetric routing enabled, ICMP local-in/local-out reply packets will still only return
through the original path, in order to maintain the ping SLA.
900226 High CPU due to PIMD/NSM and multicast session not being offloaded.
900941 config redistribute routing subsections cannot be configured when in workspace mode.
907386 BGP neighbor group configured with password is not working as expected.
913338 FortiGate removing SD-WAN routes when network address is specified as the gateway of an SD-
WAN member.
914497 SD-WAN rules list in the GUI should show the interface members in priority order instead of
alphabetical order.
914815 FortiGate 40F-3G4G not adding LTE dynamic route to route table.
922491 Static routes are installed on hub FortiGate with add-route disabled in ADVPN scenario.
924598 The Network dashboard may not load if the administrator disables SD-WAN Interface under System
> Feature Visibility.
924940 When there are a lot of policies (several thousands), the interface member selection for the SD-
WAN Zone dialog may take up to a minute to load.
Security Fabric
Bug ID Description
831311 When using automation email action to reference the result of a previously executed automation
CLI script action, there is a 16 KB size limit for the script output.
874822 In a configuration with a connected FortiAP-U, the FortiAP & FortiAP-S & FortiAP-W2 & FortiAP-U
Command Injection in CLI security rating test fails and suggests an upgrade to 7.0.4, even though
the FortiAP is on the latest version (7.0.0).
907819 Advanced GCP connector does not resolve if one element does not exists.
912592 Allow comments and IP addresses to be on the same line for external IP address threat feeds.
917024 Unexpected behavior in Security Fabric daemon (CSFD) caused by triggering HA failover while
using Security Fabric.
918230 Threat feeds with name starting with "g-" are not allowed on non-VDOM FortiGate.
922896 Azure SDN connector always uses HA management port for DNS resolve. This might not work on
premises where the HA management port does not have a public IP address assigned.
926202 Unable to authorize downstream FortiGate with the Security Fabric after upgrade.
SSL VPN
Bug ID Description
631809 Configuring thousands of mac-addr-check-rule in portal makes the CPU spike significantly if
several hundreds of users are connecting to the FortiGate, thus causing SSL VPN packet drops.
833934 SSL VPN fails to connect to graph.microsoft.com when doing Azure auto-login.
843756 Customer bookmark (*.tr***.pt) is not accessible when using SSL VPN web mode.
851976 PC cannot get IP from DHCP server due to find duplicate ip and causes the dialup SSL VPN
to fail.
856194 Problem loading some graphs trough SSL VPN web mode after upgrading.
858478 SSL VPN DTLS tunnel is unavailable after changing the SSL VPN listening port.
859088 FortiGate adds extra parenthesis and causes clicking all links to fail in SSL VPN web mode.
868491 SSL VPN web mode connection to VMware vCenter 7 is not working.
871039 Internal website is not displaying user-uploaded PDF files when visited through SSL VPN web
mode.
871229 SSL VPN web mode does not load when connecting to customer's internal site.
Bug ID Description
872745 SSL VPN web mode to RDP broker leads to connection being closed.
873516 FortiGate misses the closing parenthesis when running the function to rewrite the URL.
875167 Webpage opened in SSL VPN web portal is not displayed correctly.
877124 RDP freezes in web mode with high CPU usage of SSL VPN process.
878833 Decrease in download speeds observed for SSL VPN users when over 2000 users are connected.
880791 Internal website access issue with SSL VPN web portal.
881220 Found bad login for SSL VPN web-based access when enabling URL obscuration.
881268 Disconnecting from SSL VPN using the SSL-VPN widget does not disconnect the SSL VPN tunnel.
885978 Some buttons in URL are not working in SSL VPN web mode.
886989 SSL VPN process reaches 99% CPU usage when HTTP back-end server resets the connection in
the middle of a post request.
887345 When a user needs to enter credentials through a pop-up window, the key events for modification
key detected by SDL were ignored.
887674 FortiGate will intermittently stop accepting new SSL VPN connections across all VDOMs.
889736 The HPE iLO 5 web server is not able to load properly from the SSL VPN portal.
894704 FortiOS check would block iOS and Android mobile devices from connecting to the SSL VPN
tunnel.
895120 SSL VPN web portal not loading internal web page.
896007 Specific SAP feature is not working with SSL VPN web mode.
896343 SSL VPN web mode is not working as expected for customer's web server.
896396 SSL VPN web portal HTTP bookmark forwarded site throws Java error.
897385 Internal website keeps asking for credential with SSL VPN web mode.
897665 The external DHCP server is not receiving hostnames in SSL VPN and DHCP relay.
904919 DHCP option 12 hostname needed for SSL VPN with external DHCP servers.
906756 Update SSL VPN host check logic for unsupported OS.
922446 SSL VPN service over PPPoE interface does not work as expected if the PPPoE interface is
configured with config system pppoe-interface.
config system pppoe-interface
edit <name>
set device <string>
set username <string>
set password <password>
next
Bug ID Description
end
927475 SSL VPN tunnel down log message not generated when an IP address is disassociated before the
old tunnel times out.
933985 FortiGate as SSL VPN client does not work on NP6 and NP6XLite devices.
Switch Controller
Bug ID Description
848632 Upon upgrade, the link to FortiSwitch stays down with QSFP.
858749 Redirected traffic should not hit the firewall policy when allow-traffic-redirect is enabled.
893405 One discovery one transmit buffer was allocated and was not released on connection terminations.
894735 Unable to configure more than one NAC policy using the same EMS tag for different FortiSwitch
groups.
902338 WiFi & Switch Controller > FortiSwitch Ports page does not show VLANs exported to another tenant
VDOM, which results in the VLAN being removed if saved from the GUI.
904640 When a FortiSwitch port is reconfigured, the FortiGate may incorrectly retain old detected device
data from the port that results in an unexpected number of detected device MACs for the port. Using
diagnose switch-controller mac-cache show to check the device data can result in the
Device Information column being blank on the WiFi & Switch Controller > FortiSwitch Ports page or
in the Assets widget.
911232 Security rating shows an incorrect warning for unregistered FortiSwitches on the WiFi & Switch
Controller > Managed FortiSwitches.
941673 FortiSwitch event log displays serial number under name when CAPWAP is up or down.
System
Bug ID Description
631046 diagnose sys logdisk smart does not work for NVMe disk models.
656138 GUI shows conflicts error message when configuring a secondary IP address after allow-
subnet-overlap is enabled.
708964 CPU usage issue is observed caused by reloading the system when the system has cfg-save set
to revert.
713951 Not all ports are coming up after an LAG bounce on 8 × 10 GB LAG with ASR9K. Affected platforms:
FG-3960E and FG-3980E.
820559 When backing up the configuration to a USB disk, if the file name is the same as specified under
System > Settings > Start Up Settings > USB auto-install, an Invalid file name error is displayed.
821000 QSFP and QSFP+ Fortinet transceivers are not operational on FG-3401E.
836748 FG-100F fails to boot when FortiOS image binary is larger than 94 MB.
842159 FortiGate 200F interfaces stop passing traffic after some time.
855573 False alarm of the PSU2 occurs with only one installed.
867663 The FEC configuration under the interface is not respected when port23 and port24 are members of
an LACP and the connection is 100G. Affected platforms: FGT-340xE, FGT-360xE.
869044 If the original packet was forwarded with NAT, generated ICMP error is routed back to SNAT'ed
address.
869113 If a device is rebooted that has an ipsec-STS-timeout configured or the user configures the
ipsec-STS-timeout before any NPU tunnel is created, NPU will send random STS messages
that have an invalid tunnel index and trigger NP6XLite error messages.
869726 When an IPsec tunnel is configured with a different VRF than the underlying physical interface, and
traffic is offloaded, the session expires even when traffic is flowing through it.
874603 Dashboard loads slowly and csfd process has high CPU usage.
879769 If the firewall session is in check-new mode, FortiOS will not flush its NPU offload entry when there
is a MAC address update of its gateway.
881060 Host TX dropped counter incrementing and connections failing when throughput reaches 40 Gbps.
884023 When a user is logged in as a VDOM administrator with restricted access and tries to upload a
certificate (System > Certificates), the Create button on the Create Certificate pane is greyed out.
Bug ID Description
884970 Unbalanced throughput on LAG members with LAG enhancement feature enabled.
885837 Traffic dropped as the matching SessionID is being deleted from session table in 20 seconds.
892195 LAG interface has NOARP flag after interface settings change.
892274 Daylight saving time is not applied for Cairo time zone.
894202 Incorrect temperature calculation appears in sensor list on FG-8xF, FWF-8xF, FG-9xE, FG-10xE,
FG-20xE, and FG-14xE.
897905 IPv6 addresses configured on EMAC VLAN interfaces showing FTP flag after upgrade.
904414 Port speed 1000auto could not link up with a Cisco switch.
904485 The crashlog might show a Node.JS restarted error, Failed to fetch web-ui.node-
exports: Error: connect ECONNREFUSED, if the HTTPSD is being killed during conserve
mode, stuck in some API calls, or slow response during system super busy.
904486 The FortiGate may display a false alarm message and subsequently initiate a reboot.
906964 DST changes not reflected for timezone 16. The dates are incorrect on the DST for this specific
timezone (Santiago-Chile).
907339 dnsproxy process aborts due to stack buffer overflow being detected upon function return.
909225 ISP traffic is failing with the LAG interfaces on upstream switches.
910269 Unexpected behavior caused by the Linux Out of Memory (OOM) killer when memory is very low.
910273 Last reboot reason: power cycle after rebooting due to a kernel panic is misleading.
910616 When a non-zero DSCP copied from ingress to egress packet for NAT64, the IP checksum is
calculated incorrectly.
910677 Transparent mode FortiGate does not reply to SYN ACK when communicating with FortiManager.
911396 High system CPU and multiple daemons enter D state on the FortiGate 4401F.
Bug ID Description
913355 GUI and CLI time mismatch for Central America (Mexico) time zone.
919901 For FIPS-CC mode, the strict check for basic constraints should be removed for end entity
certificates.
920085 CPU usage issue observed in dnsproxyd caused by unused wildcard FQDN.
922458 Administrator with read-only access to management permissions cannot perform a configuration
backup in the GUI.
922920 When performing factoryreset2, the IP addresses on "a" and "b" are set to default.
922965 CPU usage issue observed in hasync daemon when session count is large.
922982 FortiGate does not respond to ARP requests for the IP address on the WAN port when the interface
is configured as EMAC.
923364 System goes into halt state with Error: Package validation failed... message in cases
where there are no engine files in the FortiGate when the BIOS security level is set to 2.
923834 The DSL modem on the firewall does not work after the device starts.
924395 IPv6 local-in ping6 to management interface failed when newly configured.
924654 MAC flapping on switch when UDP packets passthrough VWP multiple times with ASIC offload.
925657 After a manual system administrator password change, the updated password-expire is not
received by the FortiManager auto-update.
925966 Running diagnose sniffer filter with blank or empty quotation marks ("" or " ") is not
working.
926035 On D-series FortiGates, a false alarm during system integrity check failure causes the firewall to
reboot.
928858 Traffic over vpn-id-ipip tunnel is blocked when npu-offload is disabled in the VPN phase 1
interface and the policy has UTM enabled.
929821 An error condition occurred in httpsd and newcli when trying to generate a TAC report from the GUI
and CLI, respectively.
929904 When L3 or L4 hashing algorithm is used, traffic is not forwarded over the same aggregate member
after being offloaded by NP7.
935562 NAT port is out of range, causing the PBA index to be out of range.
937500, FortiOS does not accept an installation script from FortiManager when creating an extender-profile
969083 with login-password-change is set to yes.
Bug ID Description
942502 Kernel panic occurs when creating EMAC VLAN interfaces based on an aggregate interface with
new kernel 4.1.9.
Bug ID Description
794477 When a user's membership in AD or port range is changed, all of the user sessions are cleared.
850473 SSL VPN and firewall authentication SAML does not work when the application requires SHA-256.
854114 Some embedded SSL certificates entered the Error state after enabling FIPS-CC.
858877 Dynamic address only has 100 IP addresses while FSSO group lists all 56K ACI endpoints.
872814 The SAML assertion is truncated in samld when the payload size is huge.
883006 Adding a new group membership to an FSSO user terminates all the user's open sessions.
899852 FortiGate is sending Class(25) AVP with wrong length in RADIUS accounting when using 2FA with
PUSH or external tokens.
900591 When generating guest users according to the settings in the guest group, the expiration time of
guest users will automatically add an extra two hours.
901743 An Error condition occurs during the processing of the UDP packets when device identification is
activated on an interface.
915192 Device detection sometimes does not identify the correct IP addresses of devices.
922345 CA bundle (CRDB) to support DigiCert second-generation (G2) full CA and intermediate CA chain.
923164 EAP proxy daemon may keep reloading after updating the certificate bundle.
939517 On the System > Replacement Messages page, the guest user email template cannot restore to the
to default value.
943087 After creating a new guest user, the administrator cannot view the user's password in plaintext in the
GUI.
946116 On a FortiGate managed by FortiManager, when a guest administrator logs in with read-only
permissions, the administrator can still create and edit the guest user.
VM
Bug ID Description
913696 In the periodic status check of the OCI VM status, too many API calls caused a lot of 429 errors.
916027 Copy of files between a physical server and Windows Server is slow.
924689 FortiGate VMs in an HA cluster deployed on the Hyper-V platform may get into an unresponsive
state where multiple services are impacted: GUI management, CLI commands, SSL VPN sessions,
DHCP assignment, traffic throughput, and reboot function.
927323 Event log alert Write Permission Violation to read-only file on VMware after taking
snapshot.
928952 VPN errors after upgrade: Malformed Packets, AUTHENTICATION_FAILED messages, and
INVALID_KE_PAYLOAD.
933003 FortiGate-VM KVM with MLX5 not responding to ARP in RHEL environment.
935086 VLAN interface is not reachable on FortiGate-VM running on KVM with SR-IOV interface.
VoIP
Bug ID Description
887384 SIP session is dropped by ALG with media type doesn't match message.
Bug ID Description
939380 User cannot set the match ALL pattern to deny traffic for the web application firewall profile in the
GUI.
Web Filter
Bug ID Description
873086 In a policy-based VDOM, changes are not applied when adding an external threat feed category in
the URL Category field.
887699 Web filter override expiry date in the GUI may be one hour off if daylight saving time (DST) is
observed.
916140 An error condition occurs in WAD caused by the mismatch between the SNI host and CNAME.
WiFi Controller
Bug ID Description
814541 When there are extra large number of managed FortiAP devices (500+) and large number of WiFi
clients (5000+), the Managed FortiAP page and FortiAP Status widget in the GUI can take a long
time to load. This issue does not impact FortiAP operation.
875382 When accessing the Managed FortiAP/Switch view with a large number of devices in the topology,
the page would take a long time to load.
891804 After initial packets, FG-101F stops forwarding wired traffic over FAP-23JF LAN tunneled with a
dynamic VLAN VAP.
904349 Unable to create FortiAP profile in the GUI for dual-5G mode FortiAP U231F/U431F models.
905406 In auth-logon and auth-logout logs, Wi-Fi users with random public IP addresses are
observed.
921456 FAP-431F is deauthenticating clients after roaming when DHCP enforcement is enabled on the
SSID, even when the client gets IP from DHCP.
926676 Enable DFS channels on wtp-profile for FortiAP 431G and FortiAP 433G in region A/S/N(No-Brazil).
937826 An error case occurs in CAPWAP when the SSID interface, which has a VLAN interface over it, is
deleted.
944465 On the WiFi & Switch Controller > Managed FortiAPs page of a non-management VDOM, the
Register button is unavailable in the Device Registration pane.
945356 FortiOS fails to get all of the configured MAC ACL entries.
ZTNA
Bug ID Description
889994 After client device information is updated, the session is closed even though all information from the
session still matches the policy.
923804 ZTNA logs are showing the log message Denied: failed to match a proxy-policy when
client device information matches the policy.
The following issues have been identified in version 7.2.6. To inquire about a particular bug or report a bug, please
contact Customer Service & Support.
Explicit Proxy
Bug ID Description
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
942612 Web proxy forward server does not convert HTTP version to the original version when sending them
back to the client.
Firewall
Bug ID Description
958311 Firewall address list may show incorrect error for an unresolved FQDN address. This is purely a GUI
display issue; the FQDN address can be resolved by the FortiGate and traffic can be matched.
Workaround: run the following command to check if an FQDN address is being resolved properly.
# diagnose test application dnsproxy 7
951984 The best output route may not be found for local out DNAT traffic.
Bug ID Description
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.
907695 The FortiGate 6000 and 7000 platforms do not support IPsec VPN over a loopback interface or an
NPU inter-VDOM link interface.
910883 The FortiGate 6000s or 7000s in an FGSP cluster may load balance FTP data sessions to different
FPCs or FPMs. This can cause delays while the affected FortiGate 6000 or 7000 re-installs the
sessions on the correct FPC or FPM.
937879 FortiGate 7000F chassis with FIM-7941Fs cannot load balance fragmented IPv6 TCP and UDP
traffic. Instead, fragmented IPv6 TCP and UDP traffic received by the FIM-7941F interfaces is sent
directly to the primary FPM, bypassing the NP7 load balancers. IPv6 ICMP fragmented traffic load
balancing works as expected. Load balancing fragmented IPv6 TCP and UDP traffic works as
expected in FortiGate 7000F chassis with FIM-7921Fs.
941944 CPU usage data displayed on the FortiGate 6000 GUI is actually CPU usage data for the
management board. CPU usage data displayed on the FortiGate 7000 GUI is actually the CPU
usage for the primary FIM.
Use the global get system performance status command to display CPU usage and other
performance information for all components (on the FortiGate 6000 the management board and all
FPCs, or on the FortiGate 7000 the FIMs and FPMs).
This command also displays global performance information including:
Dataplane CPU states: 1%
Dataplane memory states: 21%
Dataplane average sessions: 8720 sessions in 1 minute
Dataplane average session setup rate: 4632 sessions per second in last 1
minute
946943 On 6K and 7K platforms, the management VDOM GUI should not show the WiFi & Switch Controller
menu.
948750 When EMAC VLAN interfaces are removed spontaneously from the configuration, TCP traffic
through their underlying VLAN interface fails.
949175 During FIM failover from FIM2 to FIM1, the NP7 PLE sticks on a cache invalidation, stopping traffic.
949240 SLBC special ports will not match local-in policy in the management path.
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.
Bug ID Description
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 uninterruptible-upgrade, then perform a normal
firmware upgrade. During the upgrade process the FortiGates in the cluster will not allow traffic until
all components (management board and FPCs or FIMs and FPMs) are upgraded and both
FortiGates have restarted. This process can take up to 30 minutes.
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.
954862 Graceful upgrade from 7.0.12 to 7.2.6 or 7.2.7, or from 7.0.12 to 7.4.2 or 7.4.3 will fail on the
FortiGate 6501F/6500F, FortiGate 7060E with slot6 occupied, and FortiGate 7121F with slot12
occupied.
Workaround: Disable uninterruptible-upgrade before performing the firmware upgrade:
config system ha
set uninterruptible-upgrade disable
end
Note that traffic will be interrupted for 15 to 45 minutes, depending on the size of the configurations.
954881 Image synchronization failure happened after a factory reset on FortiGate 7000E/F .
973407 FIM installed NPU session causes the SSE to get stuck.
978241 FortiGate does not honor worker port partition when SNATing connections using a fixed port range
IP pool.
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.
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
848660 Read-only administrator may encounter a Maximum number of monitored interfaces reached error
when viewing an interface bandwidth widget for an interface that does not have the monitor
bandwidth feature enabled.
Workaround: super_admin users can enable the monitor bandwidth feature on the interface first,
then the widget can work for read-only administrators.
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.
934644 When the FortiGate is in conserve mode, node process (GUI management) may not release
memory properly causing entry-level devices to stay in conserve mode.
974988 FortiGate GUI should not show a license expired notification due to an expired device-level
FortiManager Cloud license if it still has a valid account-level FortiManager Cloud license (function
is not affected).
Hyperscale
Bug ID Description
802182 After successfully changing the VLAN ID of an interface from the CLI, an error message similar to
cmdb_txn_cache_data(query=log.npu-server,leve=1) failed may appear.
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 diagnose sys npu-session list/list-full does not mention policy route
information.
853258 Packets drop, and different behavior occurs between devices in an HA pair with ECMP next hop.
872146 The diagnose sys npu-session list command shows an incorrect policy ID when traffic is
using an intra-zone policy.
Bug ID Description
920228 NAT46 NPU sessions are lost and traffic drops when a HA failover occurs.
949188 With NAT64 HS policy, ICMP reply packets are dropped by FortiOS.
958066 Observed TCP sessions timing out with a single hyperscale VDOM configuration after loading
image from BIOS.
IPsec VPN
Bug ID Description
852051 Unexpected condition in IPsec engine on SoC4 platforms leads to intermittent IPsec VPN operation.
Bug ID Description
932537 If Security Rating is enabled to run on schedule (every four hours), the FortiGate can unintentionally
send local-out traffic to fortianalyzer.forticloud.com during the Security Rating run.
Workaround: disable on-schedule Security Rating run.
config system global
set security-rating-run-on-schedule disable
end
960661 FortiAnalyzer report is not available to view for the secondary unit in the HA cluster on the Log &
Report > Reports page.
Workaround: view the report directly in FortiAnalyzer.
965247 FortiGate syslog format in reliable transport mode is not compliant with RFC 6587.
Proxy
Bug ID Description
790426 An error case occurs in WAD while redirecting the web filter HTTPS sessions.
828917 Unexpected behavior in WAD when there are multiple LDAP servers configured on the FortiGate.
845361 A rare error condition occurred in WAD caused by compounded SMB2 requests.
Bug ID Description
954104 An error case occurs in WAD when WAD gets the external authenticated users from other
daemons.
Routing
Bug ID Description
903444 The diagnose ip rtcache list command is no longer supported in the FortiOS 4.19 kernel.
Security Fabric
Bug ID Description
902344 When there are over 30 downstream FortiGates in the Security Fabric, the root FortiGate's GUI may
experience slowness when loading the Fabric Management page and prevents the user from
upgrading firmware in the GUI.
Workaround: perform the firmware upgrade in the CLI. To perform the firmware upgrade using the
GUI, temporarily disable the Security Fabric on the root FortiGate.
SSL VPN
Bug ID Description
795381 FortiClient Windows cannot be launched with SSL VPN web portal.
879329 Destination address of SSL VPN firewall policy may be lost after upgrading when dstaddr is set to
all and at least one authentication rule has a portal with split tunneling enabled.
947210 Application sslvpnd *** code requested backtrace *** was observed during graceful
upgrade.
System
Bug ID Description
861962 When configuring an 802.3ad aggregate interface with a 1 Gbps speed, the port's LED is off and
traffic cannot pass through. Affected platforms: 110xE, 220xE, 330xE, 340xE, and 360xE.
Bug ID Description
882187 Optimize memory usage caused by the high volume of disk traffic logs.
887940 Status light is not showing on the FortiGate 60F or 100F after a cold and warm reboot.
901621 Setting the interface configuration inbandwidth or outbandwidth commands stops traffic flow.
901721 In a certain edge case, traffic directed towards a VLAN interface could trigger a kernel panic.
931299 When the URL filter requests the FortiGuard (FGD) rating server address using DNS, it will try to get
both A (IPv4) and AAAA (IPv6) records.
937982 High CPU usage might be observed on entry-level FortiGates if the cache size reaches 10% of the
system memory.
947240 FortiGate is not able to resolve ARPs of few hosts due to their ARP replies not reaching the primary
FPM.
958437 An error message is shown when attempting to create a FortiExtender WAN extension interface.
967171 The speed 1000auto setting on ports X1 to X4 disappears after upgrading from 7.2.5 to 7.2.6.
Affected platforms: FG-40xF and FG-60xF.
967436 DAC cable between FortiGate and FortiSwitch stops working after upgrading from 7.2.6 to 7.2.7.
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.
939011 On the FortiGate 6000F, the ALL TP VDOM cannot synchronize because of switch-
controller.auto-config.policy.
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
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.
Web Filter
Bug ID Description
885222 HTTP session is logged as HTTPS in web filter when VIP is used.
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 acd-process-count is not zero).
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.
ZTNA
Bug ID Description
819987 SMB drive mapping made through a ZTNA access proxy is inaccessible after rebooting.
Built-in AV Engine
AV Engine 6.00293 is released as the built-in AV Engine. Refer to the AV Engine Release Notes for information.
IPS Engine 7.00326 is released as the built-in IPS Engine. Refer to the IPS Engine Release Notes for information.
l VHD
l OVF
l The XVA format comes pre-configured with default configurations for VM name, virtual CPU, memory, and virtual
NIC. Other formats will require manual configuration before the first power on process.
When using Linux Ubuntu version 11.10, XenServer version 4.1.0, and libvir version 0.9.2, importing issues may arise
when using the QCOW2 format and existing HDA issues.
Copyright© 2024 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet, Inc., and other Fortinet names herein
may also be registered and/or common law trademarks of Fortinet. All other product or company names may be trademarks of their respective owners. Performance and other metrics contained herein were
attained in internal lab tests under ideal conditions, and actual performance and other results may vary. Network variables, different network environments and other conditions may affect performance
results. Nothing herein represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written contract,
signed by Fortinet’s Chief Legal Officer, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified performance metrics and, in such event, only
the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For absolute clarity, any such warranty will be limited to performance in the same ideal
conditions as in Fortinet’s internal lab tests. Fortinet disclaims in full any covenants, representations, and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change,
modify, transfer, or otherwise revise this publication without notice, and the most current version of the publication shall be applicable.