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.

Workaround: create a new service in the CLI, or move a non-IP type services to the top of the firewall service list. For example, if ALL is the first firewall service in the list:

config firewall service custom
    edit "unused"
        set tcp-portrange 1
    next
    move "unused" before "ALL"
end

On a FortiGate managed by FortiManager, after upgrading to 7.0.13, the Firewall Policy list may show separate sequence grouping for each policy because the global-label is updated to be unique for each policy.

Workaround: drag and drop the policy to the correct sequence group in the GUI, or remove the global-label for each member policy in the group except for the leading policy.

• Policy 1 (global-label "group1")

• Policy 2

• Policy 3 (global-label "group2")

• Policy 4

For local out DNAT traffic, the best output route may not be found.

On the System > FortiGuard page, the override FortiGuard server for AntiVirus & IPS Updates shows an Unknown status, even if the server is working correctly. This is a display issue only; the override feature is working properly.

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.

On the Policy & Objects > Firewall Policy page, the policy list can take around 30 seconds or more to load when there is a large number (over 20 thousand) of policies.

Workaround: use the CLI to configure policies.

System > Certificates list sometimes shows an incorrect reference count for a certificate, and incorrectly allows a user to delete a referenced certificate. The deletion will fail even though a success message is shown. Users should be able to delete the certificate after all references are removed.

When using the SSL VPN web portal in the Firefox, users cannot paste text into the SSH terminal emulator.

Workaround: use Chrome, Edge, or Safari as the browser.

When upgrading firmware from 7.0.1 to 7.0.2, the GUI incorrectly displays a warning saying this is not a valid upgrade path.

An undefined error is displayed when changing an administrator password for the first time. Affected models: NP7 platforms.

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.

On the Network > Routing Objects page, editing a prefix list with a large number of rule entries fails with an error notification that The integer value is not within valid range.

Workaround: edit a prefix list with a large number of rule entries in the CLI.

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.

Workaround: use the CLI to configure two-factor-authentication under config system admin.

FortiGate 4200F, 4201F, 4400F, and 4401F HA1, HA2, AUX1, and AUX2 interfaces cannot be added to an LAG.

Sessions being processed by hyperscale firewall policies with hardware logging may be dropped when dynamically changing the log-processor setting from hardware to host for the hardware log sever added to the hyperscale firewall policy. To avoid dropping sessions, change the log-processor setting during quiet periods.

Hit count not ticking for implicit deny policy for hardware session in case of NAT46 and NAT64 traffic.

srcaddr-negate and dstaddr-negate are not working properly for IPv6 traffic with FTS.

Access control list (ACL) policies added to a hyperscale firewall VDOM that is processing traffic may take longer than expected to become effective. During a transition period, traffic that should be blocked by the new ACL policy will be allowed.

Output of diagnose sys npu-session list/list-full does not mention policy route information.

Diagnose command should be available to show hit_count/last_used for policy route and NPU session on hyperscale VDOM.

Get PARSE SKIP ERROR=17 NPD ERR PBR ADDRESS console error log when system boots up.

The diagnose firewall ippool list command does not show the correct output for overload type IP pools.

NPD/LPMD process killed by out of memory killer after running mixed sessions and HA failover.

Hardware session synchronization does not work on FG-480xF devices in hyperscale.

IPsec aggregate static route is not marked inactive if the IPsec aggregate is down.

Disabling src-check (RPF) on the parent tunnel is not inherited by ADVPN shortcuts.

Logs are not seen for traffic passing through the firewall caused by numerous simultaneous configuration changes.

Slow GUI performance in large Fabric topology with over 50 downstream devices.

Security Rating report for Rogue AP Detection and FortiCare Support checks show incorrect results.

Console may display mce: [Hardware Error] error message after fresh image burn or reboot.

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.

In a certain edge case, traffic directed towards a VLAN interface could cause a kernel interruption.

The cmdbsvr could not secure the var_zone lock due to another process holding it indefinitely.

FortiGate 200F experiences slow download and upload speeds when traversing from a 1G to a 10G interface.

On SoC3/SoC4 platforms, a kernel interruption may occur when running WAD monitoring scripts.

ESXi VLAN interface based on LACP does not work.

When there are extra large number of managed FortiAP devices (over 500) and large number of WiFi clients (over 5000), the Managed FortiAPs page and FortiAP Status widget can take a long time to load. This issue does not impact FortiAP operation.

Physical and logical topology is slow to load when there are a lot of managed FortiAP devices (over 50). This issue does not impact FortiAP management and operation.

An kernel interruption occurs on FWF-40F/60F models when WiFi stations connect to SSID on the local radio.

FortiWiFi reboots or becomes unresponsive when connecting to SSID after upgrading to 7.0.14.

SMB drive mapping made through a ZTNA access proxy is inaccessible after rebooting.