fortimanager-v7.4.5-release-notes
fortimanager-v7.4.5-release-notes
FortiManager 7.4.5
FORTINET DOCUMENT LIBRARY
https://docs.fortinet.com
FORTINET BLOG
https://blog.fortinet.com
FORTIGUARD LABS
https://www.fortiguard.com
FEEDBACK
Email: [email protected]
Change Log 6
FortiManager 7.4.5 Release 7
Supported models 7
FortiManager VM subscription license 7
Management extension applications 8
Supported models for MEA 8
Minimum system requirements 8
Special Notices 10
Upgrading from 7.4.3 to 7.4.5 with FIPS mode enabled 10
Device blueprint header 10
Shell access has been removed 10
Enable fcp-cfg-service for Backup Mode ADOMs 11
System Templates include new fields 11
Custom certificate name verification for FortiGate connection 11
Additional configuration required for SSO users 12
When using VPN Manager, IPSEC VPN CA certificates must be re-issued to all devices
after upgrade 12
FortiGuard web filtering category v10 update 12
FortiManager 7.2.3 and later firmware on FortiGuard 13
Configuration backup requires a password 13
FortiManager-400E support 13
Serial console has changed for FortiManager deployments on Xen 14
OpenXen in PV mode is not supported in FortiManager 7.4.1 14
Default GUI theme changed 14
Option to enable permission check when copying policies 14
Management Extensions visibility in the GUI 15
Install On column for policies 15
SD-WAN Orchestrator removed in 7.2 15
Changes to FortiManager meta fields 15
Setup wizard requires FortiCare registration 16
Access lists as ADOM-level objects 16
View Mode is disabled in policies when policy blocks are used 16
Reconfiguring Virtual Wire Pairs (VWP) 16
Scheduling firmware upgrades for managed devices 16
Modifying the interface status with the CLI 17
SD-WAN with upgrade to 7.0 17
Citrix XenServer default limits and upgrade 17
Multi-step firmware upgrades 18
Hyper-V FortiManager-VM running on an AMD CPU 18
SSLv3 on FortiManager-VM64-AWS 18
2024-10-18 Updated Resolved issues on page 47 and Known issues on page 48.
2024-12-10 Updated Supported models on page 7 with information about access to FortiManager
container versions.
2025-01-31 Updated:
l FortiManager 7.4.5 and FortiOS 7.0.16 compatibility issues on page 46
This document provides information about FortiManager version 7.4.5 build 2553.
The recommended minimum screen resolution for the FortiManager GUI is 1920 x 1080.
Please adjust the screen resolution accordingly. Otherwise, the GUI may not display properly.
Supported models
The FortiManager VM subscription license supports FortiManager version 6.4.1 and later. For information about
supported firmware, see FortiManager VM firmware on page 20.
See also Appendix B - Default and maximum number of ADOMs supported on page 54.
The following section describes supported models and minimum system requirements for management extension
applications (MEA) in FortiManager7.4.5.
FortiManager uses port TCP/443 or TCP/4443 to connect to the Fortinet registry and
download MEAs. Ensure that the port is also open on any upstream FortiGates. For more
information about incoming and outgoing ports, see the FortiManager 7.0 Ports Guide.
As of FortiManager 7.4.0, the Management Extensions pane is only visible in the GUI when docker status is enabled and
at least one MEA is enabled and downloaded. For more information about enabling and using the MEAs, see the
Management Extensions documentation in the FortiManager Documents Library.
You can use any of the following FortiManager models as a host for management extension applications:
*The numbers in the Recommended system resources for production column are a combination of the default system
resource settings for FortiManager plus the minimum system requirements for the MEA.
This section highlights some of the operational changes that administrators should be aware of in 7.4.5.
When FIPS mode is enabled, upgrading from 7.4.3 to 7.4.5 might fail due to the following error message: "FIPS firmware
signature verification failed". The following steps should be taken as workaround:
1. Backup FortiManager-v7.4.3-fips-cc mode DB.
2. Disable FortiManager-v7.4.3-fips mode to normal mode.
3. Upgrade FortiManager-v7.4.3 normal mode to v7.4.5.
4. FortiManager-v7.4.5 enable fips-cc mode.
5. Restore FortiManager-v7.4.3-fips DB on FortiManager-v7.4.5-fips.
The device blueprint header is updated in FortiManager 7.4.4, and the new format is required when importing model
devices from a CSV file. If you have existing CSV files that are used as a template to import model devices, the header
must be updated to use the new format.
1. In the FortiManager 7.4.4 or later GUI, go to Device Manager > Device & Groups.
2. From the Add Device dropdown, select Device Blueprint.
3. Select an existing blueprint and click Generate CSV.
4. Open the new CSV file and copy the header.
5. Open the existing CSV file and paste the new header, replacing the old header from previous versions.
The following CLI command has been removed, which was previously used to access shell when enabled:
execute shell
When performing a configuration backup from the CLI of FortiGates managed by FortiManager in Backup Mode
ADOMs, you must enable the "fcp-cfg-service" using the following command on the FortiManager:
config system global
set fcp-cfg-service enable
end
Beginning in FortiManager 7.4.3, the Hostname, Timezone, gui-device-latitude, and gui-device-longitude fields have
been added to System Templates.
System Templates created before upgrading to 7.4.3 must be reconfigured to specify these fields following the upgrade.
If these fields are not specified in a System Template, the default settings will be applied the next time an install is
performed which may result in preferred settings being overwritten on the managed device.
FortiManager 7.4.3 introduces a new verification of the CN or SAN of a custom certificate uploaded by the FortiGate
admin. This custom certificate is used when a FortiGate device connects to a FortiManager unit. The FortiGate and
FortiManager administrators may configure the use of a custom certificate with the following CLI commands:
FortiGate-related CLI:
config system central-management
local-cert Certificate to be used by FGFM protocol.
ca-cert CA certificate to be used by FGFM protocol.
FortiManager-related CLI:
config system global
fgfm-ca-cert set the extra fgfm CA certificates.
fgfm-cert-exclusive set if the local or CA certificates should be used exclusively.
fgfm-local-cert set the fgfm local certificate.
Upon upgrading to FortiManager 7.4.3, FortiManager will request that the FortiGate certificate must contain the
FortiGate serial number either in the CN or SAN. The tunnel connection may fail if a matching serial number is not found.
If the tunnel connection fails, the administrator may need to re-generate the custom certificates to include serial number.
Alternatively, FortiManager 7.4.3 provides a new CLI command to disable this verification. Fortinet recommends to keep
the verification enabled.
config system global
fgfm-peercert-withoutsn set if the subject CN or SAN of peer's SSL certificate sent in
FGFM should include the serial number of the device.
When the CLI setting fgfm-peercert-withoutsn is disabled (default), the FortiGate device's certificate must include
the FortiGate serial number in the subject CN or SAN. When the CLI setting fgfm-peercert-withoutsn is enabled,
the FortiManager unit does not perform the verification serial number in subject CN or SAN.
Beginning in 7.4.3, additional configuration is needed for FortiManager Users declared as wildcard SSO users.
When configuring Administrators as wildcard SSO users, the ext-auth-accprofile-override and/or ext-auth-
adom-override features, under Advanced Options, should be enabled if the intent is to obtain the ADOMs list and/or
permission profile from the SAML IdP.
When FortiManager is upgraded to 7.4.2 or later, it creates a new CA <ADOM Name>_CA3 certificate as part of a fix for
resolved issue 796858. See Resolved Issues in the FortiManager 7.4.2 Release Notes. These certificates are installed
to the FortiGate devices on the next policy push. As a result, the next time any IPSEC VPNs which use FortiManager
certificates rekey, they will fail authentication and be unable to re-establish.
The old CA <ADOM Name>_CA2 cannot be deleted, as existing certificates rely on it for validation. Similarly, the new
CA <ADOM Name>_CA3 cannot be deleted as it is required for the fix. Therefore, customers affected by this change
must follow the below workaround after upgrading FortiManager to v7.4.2 or later.
A maintenance period is advised to avoid IPSEC VPN service disruption.
Workaround:
Re-issue all certificates again to all devices, and then delete the old CA <ADOM Name>_CA2 from all devices. Next,
regenerate the VPN certificates.
To remove CA2 from FortiManager, Policy & Objects > Advanced > CA Certificates must be enabled in feature visibility.
Fortinet has updated its web filtering categories to v10, which includes two new URL categories for AI chat and
cryptocurrency web sites. In order to use the new categories, customers must upgrade their Fortinet products to one of
the versions below.
l FortiManager - Fixed in 6.0.12, 6.2.9, 6.4.7, 7.0.2, 7.2.0, 7.4.0.
l FortiOS - Fixed in 7.2.8 and 7.4.1.
l FortiClient - Fixed in Windows 7.2.3, macOS 7.2.3, Linux 7.2.3.
l FortiClient EMS - Fixed in 7.2.1.
l FortiMail - Fixed in 7.0.7, 7.2.5, 7.4.1.
l FortiProxy - Fixed in 7.4.1.
Please read the following CSB for more information to caveats on the usage in FortiManager and FortiOS.
https://support.fortinet.com/Information/Bulletin.aspx
Starting in FortiManager 7.2.1, a setup wizard executes to prompt the user for various configuration steps and
registration with FortiCare. During the execution, the FortiManager unit attempts to communicate with FortiGuard for a
list of FortiManager firmware images currently available on FortiGuard – older and newer.
In the case of FortiManager 7.2.2, a bug in the GUI prevents the wizard from completing and prevents the user from
accessing the FortiManager unit. The issue has been fixed in 7.2.3 and later and a CLI command has been added to
bypass the setup wizard at login time.
config system admin setting
set firmware-upgrade-check disable
end
Fortinet has not uploaded FortiManager 7.2.3 and later firmware to FortiGuard in order to work around the GUI bug,
however, the firmware is available for download from the Fortinet Support website.
As of FortiManager 7.4.2, configuration backup files are automatically encrypted and require you to set a password. The
password is required for scheduled backups as well.
In previous versions, the encryption and password were optional.
For more information, see the FortiManager Administration Guide.
FortiManager-400E support
FortiManager 7.4.2 and later does not support the FortiManager-400E device.
FortiManager 7.4.2 introduces an upgrade of the OpenSSL library to address known vulnerabilities in the library. As a
result, the SSL connection that is setup between the FortiManager-400E device and the Google Map server hosted by
Fortinet uses a SHA2 (2048) public key length. The certificate stored on the BIOS that is used during the setup of the
SSL connection contains a SHA1 public key length, which causes the connection setup to fail. Running the following
command shows the key length.
FMG400E # conf sys certificate local
(local)# ed Fortinet_Local
(Fortinet_Local)# get
name : Fortinet_Local
password : *
comment : Default local certificate
private-key :
certificate :
As of FortiManager 7.4.1, the serial console for Xen deployments has changed from hvc0 (Xen specific) to ttyS0
(standard).
As of FortiManager 7.4.1, kernel and rootfs are encrypted. OpenXen in PV mode tries to unzip the kernel and rootfs, but
it will fail. Therefore, OpenXen in PV mode cannot be used when deploying or upgrading to FortiManager 7.4.1. Only
HVM (hardware virtual machine) mode is supported for OpenXen in FortiManager 7.4.1.
As of FortiManager 7.4.1, the default GUI theme is Jade. The default theme can be changed from System Settings >
Settings.
By default, this is set to disable. When set to enable, a check is performed when copying policies to prevent changing
global device objects if the user does not have permission.
As of FortiManager 7.4.0, the Management Extensions pane is only visible in the GUI when docker status is enabled and
at least one management extension application (MEA) is enabled and downloaded. For more information about enabling
and using the MEAs, see the Management Extensions documentation in the FortiManager Documents Library.
Prior to version 7.2.3, the 'Install-on' column for policies in the policy block had no effect. However, starting from version
7.2.3, the 'Install-on' column is operational and significantly impacts the behavior and installation process of policies. It's
important to note that using 'Install-on' on policies in the policy block is not recommended. If required, this setting can
only be configured through a script or JSON APIs.
Starting in 7.2.0, the SD-WAN Orchestrator is no longer available in FortiManager. Instead, you can use the SD-
WAN Overlay Template wizard to configure your SD-WAN overlay network.
For more information, see SD-WAN Overlay Templates in the FortiManager Administration Guide.
Starting in FortiManager 7.2.1, the FortiManager Setup wizard requires you to complete the Register with FortiCare step
before you can access the FortiManager appliance or VM. Previously the step was optional.
For FortiManager units operating in a closed environment, contact customer service to receive an entitlement file, and
then load the entitlement file to FortiManager by using the CLI.
Starting in 7.2.0, FortiManager supports IPv4 and IPv6 access lists as ADOM-level object configurations from FortiGate.
Previously, access lists were controlled by the device database/FortiGate configuration.
After upgrading to 7.2.0 from an earlier release, the next time you install changes to a FortiGate device with an IPv4 or
IPv6 access list, FortiManager will purge the device database/FortiGate configuration which may have previously
contained the access list. To address this, administrators can re-import the FortiGate policy configuration to an ADOM's
policy package or re-create the IPv4/IPv6 access list in the original package.
When policy blocks are added to a policy package, the View Mode option is no longer available, and policies in the table
cannot be arranged by Interface Pair View. This occurs because policy blocks typically contain policies with multiple
interfaces, however, View Mode is still disabled even when policy blocks respect the interface pair.
A conflict can occur between the ADOM database and device database when a Virtual Wire Pair (VWP) is installed on a
managed FortiGate that already has a configured VWP in the device database. This can happen when an existing VWP
has been reconfigured or replaced.
Before installing the VWP, you must first remove the old VWP from the device's database, otherwise a policy and object
validation error may occur during installation. You can remove the VWP from the device database by going to Device
Manager > Device & Groups, selecting the managed device, and removing the VWP from System > Interface.
Starting in FortiManager 7.0.0, firmware templates should be used to schedule firmware upgrades on managed
FortiGates. Attempting firmware upgrade from the FortiManager GUI by using legacy methods may ignore the schedule
upgrade option and result in FortiGates being upgraded immediately.
Starting in version 7.0.1, the CLI to modify the interface status has been changed from up/down to enable/disable.
For example:
config system interface
edit port2
set status <enable/disable>
next
end
Due to design change with SD-WAN Template, upgrading to FortiManager 7.0 may be unable to maintain dynamic
mappings for all SD-WAN interface members. Please reconfigure all the missing interface mappings after upgrade.
Citrix XenServer limits ramdisk to 128M by default. However the FMG-VM64-XEN image is larger than 128M. Before
updating to FortiManager 6.4, increase the size of the ramdisk setting on Citrix XenServer.
Prior to using the FortiManager to push a multi-step firmware upgrade, confirm the upgrade path matches the path
outlined on our support site. To confirm the path, please run:
dia fwmanager show-dev-upgrade-path <device name> <target firmware>
A Hyper-V FMG-VM running on a PC with an AMD CPU may experience a kernel panic. Fortinet recommends running
VMs on an Intel-based PC.
SSLv3 on FortiManager-VM64-AWS
Due to known vulnerabilities in the SSLv3 protocol, FortiManager-VM64-AWS only enables TLSv1 by default. All other
models enable both TLSv1 and SSLv3. If you wish to disable SSLv3 support, please run:
config system global
set ssl-protocol t1sv1
end
Prior to upgrading your FortiManager, please review the FortiManager Upgrade Guide in detail
as it includes all of the necessary steps and associated details required to upgrade your
FortiManager device or VM, including recommended upgrade paths.
See the FortiManager Upgrade Guide in the Fortinet Document Library.
Before upgrading FortiManager, check ADOM versions. Check the ADOM versions supported
by the destination firmware and the current firmware. If the current firmware uses ADOM
versions not supported by the destination firmware, upgrade ADOM versions in FortiManager
before upgrading FortiManager to the destination firmware version.
For example, FortiManager 7.2 supports ADOM versions 6.4, 7.0, and 7.2, but FortiManager
7.4 supports ADOM versions 7.0, 7.2, and 7.4. Before you upgrade FortiManager 7.2 to 7.4,
ensure that all ADOM 6.4 versions have been upgraded to ADOM version 7.0 or later. See the
FortiManager Upgrade Guide in the Fortinet Document Library.
FortiManager does not provide a full downgrade path. You can downgrade to a previous firmware release by using the
GUI or CLI, but doing so results in configuration loss. A system reset is required after the firmware downgrade process
has completed. To reset the system, use the following CLI commands via a console port connection:
execute reset {all-settings | all-except-ip}
execute format {disk | disk-ext4 | disk-ext3}
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 Download > Firmware Image Checksums, enter the image file
name including the extension, and select Get Checksum Code.
FortiManager VM firmware
Fortinet provides FortiManager VM firmware images for Amazon AWS, Amazon AWSOnDemand, Citrix and Open
Source XenServer, Linux KVM, Microsoft Hyper-V Server, and VMware ESX/ESXi virtualization environments.
l The 64-bit Amazon Machine Image (AMI) is available on the AWS marketplace.
l .out: Download the 64-bit firmware image to upgrade your existing FortiManager VM installation.
l .out.OpenXen.zip: Download the 64-bit package for a new FortiManager VM installation. This package contains
the QCOW2 file for the Open Source Xen Server.
l .out.CitrixXen.zip: Download the 64-bit package for a new FortiManager VM installation. This package
contains the Citrix XenServer Virtual Appliance (XVA), Virtual Hard Disk (VHD), and OVF files.
l .out: Download the 64-bit firmware image to upgrade your existing FortiManager VM installation.
l .out.gcp.zip: Download the 64-bit package for a new FortiManager VM installation.
Linux KVM
l .out: Download the 64-bit firmware image to upgrade your existing FortiManager VM installation.
l .out.kvm.zip: Download the 64-bit package for a new FortiManager VM installation. This package contains
QCOW2 that can be used by qemu.
Microsoft Azure
The files for Microsoft Azure have AZURE in the filenames, for example <product>_VM64_AZURE-v<number>-
build<number>-FORTINET.out.hyperv.zip.
l .out: Download the firmware image to upgrade your existing FortiManager VM installation.
The files for Microsoft Hyper-V Server have HV in the filenames, for example, <product>_VM64_HV-v<number>-
build<number>-FORTINET.out.hyperv.zip.
l .out: Download the firmware image to upgrade your existing FortiManager VM installation.
l .hyperv.zip: Download the package for a new FortiManager VM installation. This package contains a Virtual
Hard Disk (VHD) file for Microsoft Hyper-V Server.
l .out: Download the 64-bit firmware image to upgrade your existing FortiManager VM installation.
l .out.opc.zip: Download the 64-bit package for a new FortiManager VM installation.
VMware ESX/ESXi
l .out: Download the 64-bit firmware image to upgrade your existing VM installation.
l .ovf.zip: Download either the 64-bit package for a new VM installation. This package contains an Open
Virtualization Format (OVF) file for VMware and two Virtual Machine Disk Format (VMDK) files used by the OVF file
during deployment.
For more information see the FortiManager Data Sheet available on the Fortinet web site. VM
installation guides are available in the Fortinet Document Library.
You can download the FORTINET-FORTIMANAGER-FORTIANALYZER.mib MIB file in the firmware image file folder.
The Fortinet Core MIB file is located in the main FortiManager version 5.00 file folder.
This section lists FortiManager 7.4.5 support of other Fortinet products. It also identifies what FortiManager features are
supported for managed platforms and what languages FortiManager supports. It also lists which Fortinet models can be
managed by FortiManager.
The section contains the following topics:
l Supported software on page 22
l Feature support on page 28
l Language support on page 29
l Supported models on page 29
l FortiExtender MODEM firmware compatibility on page 45
Supported software
To confirm that a device model or firmware version is supported by the current firmware
version running on FortiManager, run the following CLI command:
diagnose dvm supported-platforms list
Always review the Release Notes of the supported platform firmware version before upgrading
your device.
Web browsers
The FortiManager Release Notes communicate support for FortiOS versions that are
available at the time of the FortiManager 7.4.5 release. For additional information about other
supported FortiOS versions, please refer to the FortiManager compatibility chart in the Fortinet
Document Library.
See FortiManager compatibility with FortiOS.
FortiManager 7.4.5 supports the following versions of FortiOS and FortiOS Carrier:
l 7.4.0 to 7.4.5
l 7.2.0 to 7.2.10
l 7.0.0 to 7.0.17
Some FortiOS versions are supported with compatibility issues. For more details, see
Compatibility with FortiOS Versions on page 46.
FortiADC
FortiAnalyzer
FortiAnalyzer-BigData
FortiAuthenticator
FortiCache
FortiCASB
FortiClient
FortiDDoS
FortiDeceptor
FortiMail
FortiPAM
FortiProxy
FortiManager 7.4.5 supports configuration management for the following versions of FortiProxy:
l 7.4.0 to 7.4.5
l 7.2.2, 7.2.3, 7.2.7, and 7.2.9
l 7.0.7 to 7.0.16
FortiSandbox
FortiSASE
For more information about compatibility, see the FortiSASE Release Notes.
FortiSOAR
FortiSwitch ATCA
FortiTester
FortiToken
FortiWeb
Virtualization
Public Cloud
Private Cloud
Feature support
The following table lists FortiManager feature support for managed platforms.
FortiGate ✓ ✓ ✓ ✓ ✓
FortiCarrier ✓ ✓ ✓ ✓ ✓
FortiADC ✓ ✓
FortiAnalyzer ✓ ✓ ✓
FortiAuthenticator ✓
FortiCache ✓ ✓ ✓
FortiClient ✓ ✓ ✓
FortiDDoS ✓ ✓ ✓
FortiDeceptor ✓
FortiFirewall ✓ ✓
FortiFirewall Carrier ✓ ✓
FortiMail ✓ ✓ ✓ ✓
FortiPAM ✓ ✓ ✓ ✓
FortiProxy ✓ ✓ ✓ ✓ ✓
FortiSandbox ✓ ✓ ✓ ✓
FortiSOAR ✓ ✓
FortiSwitch ATCA ✓
FortiTester ✓
FortiWeb ✓ ✓ ✓ ✓
Syslog ✓
Language support
English ✓ ✓
Chinese (Simplified) ✓ ✓
Chinese (Traditional) ✓ ✓
French ✓ ✓
Japanese ✓ ✓
Korean ✓ ✓
Portuguese ✓
Spanish ✓
To change the FortiManager language setting, go to System Settings > Admin > Admin Settings, in Administrative
Settings > Language select the desired language on the drop-down menu. The default value is Auto Detect.
Russian, Hebrew, and Hungarian are not included in the default report languages. You can create your own language
translation files for these languages by exporting a predefined language from FortiManager, modifying the text to a
different language, saving the file as a different language name, and then importing the file into FortiManager. For more
information, see the FortiManager Administration Guide.
Supported models
The following tables list which FortiGate, FortiCarrier, FortiDDoS, FortiAnalyzer, FortiMail, FortiSandbox, FortiSwitch
ATCA, FortiWeb, FortiCache, FortiProxy, and FortiAuthenticator models and firmware versions that can be managed by
a FortiManager or send logs to a FortiManager running version 7.4.5.
Software license activated LENC devices are supported, if their platforms are in the
supported models list. For example, support of FG-3200D indicates support of FG-
3200D-LENC.
FortiGate models
The following FortiGate models are released with FortiOS firmware. For information about supported FortiGate models
on special branch releases of FortiOS firmware, see FortiGate special branch models on page 33.
The following FortiGate models are released on special branches of FortiOS. FortiManager version 7.4.5 supports these
models on the identified FortiOS version and build number.
For information about supported FortiGate models released with FortiOS firmware, see FortiGate models on page 30.
FortiOS 7.2
FortiOS 7.0
FortiCarrier models
The following FortiCarrier models are released on special branches of FortiOS Carrier. FortiManager version 7.4.5
supports these models on the identified FortiOS Carrier version and build number.
For information about supported FortiCarrier models released with FortiOS Carrier firmware, see FortiCarrier models on
page 34.
FortiCarrier 7.0
FortiADC models
FortiAnalyzer models
FortiAnalyzer-BigData models
FortiAuthenticator models
FortiCache models
FortiDDoS models
FortiDeceptor models
FortiFirewall models
Some of the following FortiFirewall models are released on special branches of FortiFirewall firmware. FortiManager
version 7.4.5 supports these models on the identified FortiFirewall firmware version and build number.
FortiFirewall 7.4
FortiFirewall 7.2
FortiFirewall 7.0
FortiFirewallCarrier models
Some of the following FortiFirewallCarrier models are released on special branches of FortiFirewallCarrier firmware.
FortiManager version 7.4.5 supports these models on the identified FortiFirewallCarrier firmware version and build
number.
FortiMail models
FortiMail: FE-200F, FE-400F, FE-900F, FE-2000E, FE-2000F, FE-3000E, FE-3000F, FE- 7.4
3200E
FortiMail VM: FML-VM, FortiMail Cloud
FortiMail: FE-60D, FE-200D, FE-200E, FE-200F, FE-400E, FE-400F, FE-900F, FE-2000E, 7.2
FE-2000F, FE-3000E, FE-3000F, FE-3200E
FortiMail VM: FML-VM, FortiMail Cloud
FortiMail: FE-60D, FE-200D, FE-200E, FE-200F, FE-400E, FE-400F, FE-900F, FE-1000D, 7.0
FE-2000E, FE-2000F, FE-3000D, FE-3000E, FE-3000F, FE-3200E
FortiMail VM: FML-VM, FortiMail Cloud
FortiPAM models
FortiProxy models
FortiSandbox models
FortiSOAR models
FortiTester models
FortiWeb models
See the FortiOS Release Notes for a list of MODEM firmware filename and version for each FortiExtender model and
where in the world the MODEMs are compatible.
This section highlights compatibility issues that administrators should be aware of in FortiManager 7.4.5.
This section identifies interoperability issues that have been identified with FortiManager 7.4.5 and FortiOS 7.0.16.
FortiOS 7.0.16 includes syntax changes not supported by FortiManager 7.4.5.
When specific platforms are indicated, the syntax change applies to both the FortiGate and
FortiCarrier platform for the model.
For example, (4 platforms: 3980E,3960E) indicates FortiGate-3980E, FortiCarrier-
3980E, FortiGate-3960E, FortiCarrier-3960E.
This section identifies interoperability issues that have been identified with FortiManager 7.4.5 and FortiOS 7.0.17.
FortiOS 7.0.17 includes syntax changes not supported by FortiManager 7.4.5.
When specific platforms are indicated, the syntax change applies to both the FortiGate and
FortiCarrier platform for the model.
For example, (4 platforms: 3980E,3960E) indicates FortiGate-3980E, FortiCarrier-
3980E, FortiGate-3960E, FortiCarrier-3960E.
The following issues have been fixed in 7.4.5. To inquire about a particular bug, please contact Customer Service &
Support.
FortiSwitch Manager
Bug ID Description
1110598 Unable to add per device mapping config for FortiSwitch VLAN.
Workaround:
A script can be run on "Policy Package or ADOM Database". The following is an example:
config fsp vlan
edit "vlan200"
set vlanid 200
set _dhcp-status disable
config interface
set ip-managed-by-fortiipam disable
end
config dynamic_mapping
edit "FortiGate-80F-POE"-"root"
set _dhcp-status disable
config interface
set vlanid 20
end
config dhcp-server
set dns-service default
set ntp-service default
set timezone-option default
end
next
end
Bug ID Description
next
end
The following issues have been identified in a previous version of FortiManager and remain in FortiManager 7.4.5.
AP Manager
Bug ID Description
1032762 Since FortiOS 7.4.4 now supports the selection of multiple 802.11 protocols and has trimmed
the band options, importing FortiOS 7.4.3 AP profiles may result in some bands and channels
being un-matched or unset.
1050466 The 802.11ax-5g AP profile is missing for all FortiAPs that support WiFi 6.
1076200 Policy install fails due to FortiManager installs unexpected changes related to "<wifi_intf>
address".
Workaround:
Create a CLI template with all subnet addresses and assign to device.
1081136 FortiManager is trying to delete and create ssid interface subnet address after upgrade.
Device Manager
Bug ID Description
952422 IPsec templates created by SDWAN Overlay does not create tunnels for all the underlay
interfaces.
973365 FortiManager does not display the IP addresses of FortiGate interfaces configured with DHCP
addressing mode.
Workaround:
Disable Addressing Mode from DHCP to Manual in FortiManager Device DB, then retrieve
from FortiGate and IP will be updated successfully.
974925 The NTP Server setting may not display the correct configuration. This issue might occur on
managed devices running FortiOS version 7.4.2 or higher.
Workaround:
Edit NTP server setting under CLI configuration.
Bug ID Description
1004220 The SD-WAN Overlay template creates route-map names that exceed the 35-character limit.
1053194 If the "system interface speed" attribute is changed from the FortiManager, it may
potentially cause an installation failure. Modifying the "system interface speed" is not
currently supported on the FortiManager and must be done on the FortiGate side.
1070943 Unable to upgrade the devices through the Device Group Upgrade Firmware feature.
Workaround:
Upgrade devices individually by using the "Device Firmware Upgrade" feature or Create New
Firmware Template for single devices or device groups and use the "Assign to
Devices/Groups" feature.
1074717 An error might be observed when the SD-WAN template health check name contains a space,
displaying the following message: "Bad health check name...".
1075747 SD-WAN Monitor does not display the members under the SD-WAN Rules (Map View or
Table View). This issue is most likely to occur when "priority-zone" is configured.
1080414 CSV import fails to set metadata variables due to old header format ("name"). To update to
the current format, see "Device blueprint header" in Special Notices on page 10.
Others
Bug ID Description
998198 When upgrading ADOM, the upgrade process fails with the following error: "invalid value - can
not find import template 'XYZ' ".
Workaround:
Locate the scripts, delete them, upgrade the ADOM and then import the scripts.
1003711 During the FortiGate HA upgrade, both the primary and secondary FortiGates may reboot
simultaneously, which can disrupt the network. This issue is more likely to occur in FortiGates
that require disk checks, leading to longer boot times.
Workaround:
Disabling the disk check on fmupdate before the upgrade using the following command:
config fmupdate fwm-setting
set check-fgt-disk disable
end
1019261 Unable to upgrade ADOM from 7.0 to 7.2, due to the error "Do not support urlfilter-table for
global scope webfilter profile".
Bug ID Description
Workaround:
Run the following script against the ADOM DB:
config webfilter profile
edit "g-default"
config web
unset urlfilter-table
end
next
end
1029677 Unable to upgrade ADOM from v6.4 to v7.0 due to global scope error in webfilter profile.
Workaround:
Rename the "g-default" to "g-test" > save. It can be deleted after that. Once ADOM
upgraded, new g-default is created.
1049457 When FortiAnalyzer is added as a managed device, users may encounter an issue in the
FortiManager GUI when expanding the log details.
Bug ID Description
991720 FortiManager still has an option to enable the "match-vip" through the policy package for
"allow" policies. However, this is not supported anymore on the FortiGates.
Workaround:
Disable the option under advance option in Firewall Rule.
1029921 Under the "Web Application Firewall" security profiles, users are unable to disable the
signatures through the GUI.
1076659 When policy package configured with policy block, installation to multiple devices may have
copy fail errors if combined length of the Policy Block name and Policy name is greater than
35 characters and if the total number of such policies exceeds 1000.
1079678 FortiManager does not provide any warning when there is a "deny all" policy in the middle of a
Policy Package. This can be still seen on the "task monitor".
System Settings
Bug ID Description
825319 FortiManager fails to promote a FortiGate HA member (running on firmware 7.2.0 to 7.2.4) to
Bug ID Description
the Primary.
1063040 Unable to import a local certificate into FortiManager. This issue may occur if the certificate is
encrypted with a newer OpenSSL version that FortiManager does not yet support.
Workaround:
Convert the latest certificate to the legacy format before uploading it to FortiManager.
In order for FortiManager to request and retrieve updates from FDS, and for FortiManager to serve as an FDS, please
configure the necessary settings on all devices between FortiManager and FDS, or between FortiManager and
FortiGate devices based on the following items:
l FortiManager accesses FDS for antivirus and attack updates through TCP/SSL port 443.
l If there is a proxy server between FortiManager and FDS, FortiManager uses port 443 to communicate with the
proxy server in tunnel mode by default. Alternatively, you can configure web proxy to use proxy mode using port 80.
For more information, see the FortiManager Administration Guide.
You can configure FortiManager as a local FDS to provide FortiGuard updates to other Fortinet devices and agents on
your network. The following table lists which updates are available per platform:
FortiGate ✓ ✓
FortiADC ✓
FortiCache ✓
FortiCarrier ✓ ✓
FortiClient ✓
FortiDeceptor ✓ ✓
FortiDDoS ✓
FortiEMS ✓
FortiMail ✓ ✓
FortiProxy ✓ ✓
FortiSandbox ✓ ✓
FortiSOAR ✓
FortiTester ✓
FortiWeb ✓
FortiPAM ✓
This section identifies the supported number of ADOMs for FortiManager hardware models and virtual machines.
Hardware models
200G Series 30 30
For FortiManager F series and earlier, the maximum number of ADOMs is equal to the maximum devices/VDOMs as
described in the FortiManager Data Sheet.
Virtual Machines
FortiManager VM subscription license includes five (5) ADOMs. Additional ADOMs can be purchased with an ADOM
subscription license.
For FortiManager VM perpetual license, the maximum number of ADOMs is equal to the maximum number of
Devices/VDOMs listed in the FortiManager Data Sheet.
Copyright© 2025 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.