fortimanager-v7.2.8-release-notes
fortimanager-v7.2.8-release-notes
FortiManager 7.2.8
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.2.8 Release 7
Supported models 7
FortiManager VM subscription license 7
Management extension applications 7
Supported models for MEA 8
Minimum system requirements 8
Special Notices 10
Shell access has been removed 10
Enable fcp-cfg-service for Backup Mode ADOMs 10
Custom certificate name verification for FortiGate connection 10
Configuration backup requires a password 11
Additional configuration required for SSO users 11
IPSEC VPN CA certificates must be re-issued to all devices after upgrade 11
Apache-mode changed from prefork to event 12
FortiGuard web filtering category v10 update 12
Install On column for policies 12
FortiManager 7.2.3 and later firmware on FortiGuard 13
Option to enable permission check when copying policies 13
Management Extensions visibility in the GUI 13
FortiManager creates faulty dynamic mapping for VPN manager interface during PP
import 13
SD-WAN Orchestrator removed in 7.2 14
Changes to FortiManager meta fields 14
Setup wizard requires FortiCare registration 14
Access lists as ADOM-level objects 14
View Mode is disabled in policies when policy blocks are used 15
Reconfiguring Virtual Wire Pairs (VWP) 15
Fortinet verified publisher docker image 15
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
Upgrade Information 19
Downgrading to previous firmware versions 19
Firmware image checksums 19
FortiManager VM firmware 20
SNMP MIB files 21
This document provides information about FortiManager version 7.2.8 build 1634.
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 53.
The following section describes supported models and minimum system requirements for management extension
applications (MEA) in FortiManager 7.2.8.
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.2.3, 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.2.8.
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
FortiManager 7.2.5 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.2.5, 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.2.5 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.
As of FortiManager 7.2.5, 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.
Beginning in 7.2.5, 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.2.5 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.2.5 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 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.2.5 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.
Before version 7.2.3, the default "apache-mode" utilized the "prefork" mode. However, starting from version 7.2.4, the
default configuration switches to the "event" mode.
This change is aimed at supporting the HTTP/2.0 protocol. With HTTP/2.0, there is no limit on the maximum concurrency
of HTTP requests, potentially leading to slower GUI performance if the client's environment imposes restrictions ,
whether network or implementation-related. HTTP/2 may face issues such as head-of-line blocking and resource
prioritization, leading to slower performance compared to HTTP/1. Additionally, server push and intermediaries
struggling with encrypted headers can further complicate matters. Implementing HTTP/2 requires more computational
resources, which may affect response times. These complexities highlight scenarios where HTTP/1 might outperform
HTTP/2.
If customers experience GUI slowness, they have the option to revert to the "prefork" mode using the following
commands:
config system global
(global)# set apache-mode prefork
(global)# end
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
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 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.
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.2.3, 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.
If policy changes are made directly on the FortiGates, the subsequent PP import creates faulty dynamic mappings for
VPN Manager.
It is strongly recommended to create a fresh backup of the FortiManager's configuration prior to this workaround.
Perform the following command to check & repair the FortiManager's configuration database:
diagnose cdb check policy-packages <adom>
After executing this command, FortiManager will remove the invalid mappings of vpnmgr interfaces.
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 list firewall policies as ADOM-level object configurations
from FortiGate. Previously, these 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 firewall policy (config firewall acl/acl6), 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 firewall policy 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.
FortiManager docker images are available for download from Fortinet’s Verified Publisher public repository on
dockerhub.
1. Go to dockerhub at https://hub.docker.com/.
The dockerhub home page is displayed.
4. Click fortinet/fortimanager.
The fortinet/fortimanager page is displayed, and two tabs are available: Overview and Tags. The Overview tab is
selected by default.
5. On the Overview tab, copy the docker pull command, and use it to download the image.
The CLI command from the Overview tab points to the latest available image. Use the Tags tab to access different
versions when available.
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.
See FortiManager 7.2.8 Upgrade Guide.
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.0 supports ADOM versions 6.2, 6.4, and 7.0, but FortiManager
7.2 supports ADOM versions 6.4, 7.0, and 7.2. Before you upgrade FortiManager 7.0 to 7.2,
ensure that all ADOM 6.2 versions have been upgraded to ADOM version 6.4 or later. See
FortiManager 7.2.8 Upgrade Guide.
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.
After upgrading FortiManager on Azure Stack from version 7.2.3 to 7.2.4, the instance will become unreachable. To re-
establish connectivity, dissociate the Public IP of the instance and then re-associate it via the Azure Stack client portal.
This section lists FortiManager 7.2.8 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 28
l Supported models on page 29
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.2.8 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.2.8 supports the following versions of FortiOS and FortiOS Carrier:
l 7.2.0 to 7.2.10
l 7.0.0 to 7.0.16
l 6.4.0 to 6.4.15
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
FortiClient
FortiDDoS
FortiDeceptor
FortiMail
FortiPAM
FortiProxy
FortiManager 7.2.8 supports configuration management for the following versions of FortiProxy:
l 7.2.9
l 7.2.7
l 7.2.6
l 7.2.3
l 7.2.2
l 7.0.12 to 7.0.17
l 7.0.7 to 7.0.10
FortiSandbox
FortiSOAR
FortiSwitch ATCA
FortiTester
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.2.8.
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.2.8 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.0
FortiOS 6.4
FortiCarrier models
For information about supported FortiCarrier models on special branch releases of FortiCarrier firmware, see
FortiCarrier special branch models on page 36.
The following FortiCarrier models are released on special branches of FortiOS Carrier. FortiManager version 7.2.8
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
FortiCarrier 6.4
FortiADC models
FortiAnalyzer models
FortiAnalyzer-BigData models
FortiAuthenticator models
FortiAuthenticator: FAC-200D, FAC-200E, FAC-300F, FAC-400C, FAC-400E, FAC-800F, 6.4, 6.5, 6.6
FAC-1000C, FAC-1000D, FAC-2000E, FAC-3000D, FAC-3000E, FAC-3000F
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.2.8 supports these models on the identified FortiFirewall firmware version and build number.
FortiFirewall 7.2
FortiFirewall 7.0
FortiFirewall 6.4
FortiFirewallCarrier models
Some of the following FortiFirewallCarrier models are released on special branches of FortiFirewallCarrier firmware.
FortiManager version 7.2.8 supports these models on the identified FortiFirewallCarrier firmware version and build
number.
FortiFirewallCarrier 7.2
FortiFirewallCarrier 7.0
FortiFirewallCarrier 6.4
FortiFirewallCarrier 6.2
FortiMail models
FortiMail: FE-60D, FE-200D, FE-200E, FE-200F, FE-400E, FE-400F, FE-900F, FE-2000F, 7.2
FE-3000F
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
FortiMail: FE-60D, FE-200D, FE-200E, FE-200F, FE-400E, FE-400F, FE-900F, FE-1000D, 6.4
FE-2000E, FE-3000D, FE-3000E, FE-3200E
FortiMail VM: FML-VM, FortiMail Cloud
FortiPAM models
FortiProxy models
FortiSandbox models
FortiSOAR models
FortiTester models
FortiWeb models
This section highlights compatibility issues that administrators should be aware of in FortiManager 7.2.8.
This section identifies interoperability issues that have been identified with FortiManager 7.2.8 and FortiOS 7.0.16.
FortiOS 7.0.16 includes syntax changes not supported by FortiManager 7.2.8.
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.
No resolved issues have been reported for FortiManager version 7.2.8. To inquire about a particular bug, please contact
Customer Service & Support.
The following issues have been identified in a previous version of FortiManager and remain in FortiManager 7.2.8.
AP Manager
Bug ID Description
1010632 Floor Map shows wrong AP status and does not show the rest of APs when adding a new AP.
l U231F
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.
1082873 FortiManager keeps creating and deleting the VAP interface address with every install.
Device Manager
Bug ID Description
894948 FortiManager fails to push the FortiAnalyzer override settings to the FortiGate.
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.
980362 The Firmware Version column in Device Manager incorrectly shows "Upgrading FortiGate
from V1 to V2" even after a successful upgrade has been completed.
1004220 The SD-WAN Overlay template creates route-map names that exceed the 35-character limit.
1024552 SD-WAN Monitor (Map View) and Network Monitor SD-WAN (on device DB) keep loading
indefinitely.
1030685 Unable to export metadata variables if the metadata's per-device-mapping value is empty.
1062545 When using the backslash "\" in the preshared key of IPSEC settings, the install may fail.
1063835 FortiManager ZTP installation to FortiGate versions 7.2.8 and lower may fail due to differing
default "ssh-kex-algo" settings between FortiManager and FortiGate.
1070943 Unable to upgrade the devices via 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.
Others
Bug ID Description
703585 FortiManager may return 'Connection aborted' error with JSON API request.
777831 When FortiAnalyzer is added as a managed device to FortiManager, "Incidents & Events" tile
will be displayed instead of the "FortiSoC".
1003261 FortiManager displays the Vulnerability notification alert but the device list is blank.
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.
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.
Bug ID Description
971065 When the number of Custom Internet Services exceeds 256, installation fails due to this
limitation.
1004929 FortiManager removes the Web Filter Profile from the Profile Group for Policy-Based
FortiGates.
Workaround:
Use individual profiles in the policy instead of the profile group.
1005161 The policy package status changes for all devices even when an address object is opened
and saved without any modifications. This issue is particularly observed in objects utilizing the
per-device mapping feature.
1029921 Under the "Web Application Firewall" security profiles,users are unable to disable the
signatures via GUI.
1030914 Copy and paste function in GUI removes name of the policy rule and adds unwanted default
security profiles (SSL-SSH no-inspection and default PROTOCOL OPTIONS).
1037861 ADOM versions (7.0 & 7.2) do nothave "ie-allow-list" option available to create GTP object.
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".
Script
Bug ID Description
931088 Unable to delete VDOMs using the FortiManager script. Interfaces remain in the device
database, causing the installation to fail.
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
the Primary.
VPN Manager
Bug ID Description
784385 If policy changes are made directly on the FortiGates, the subsequent policy package import
creates faulty dynamic mappings for VPN Manager.
Workaround:
It is strongly recommended to create a fresh backup of the FortiManager's configuration prior
to the workaround. Perform the following command to check & repair the FortiManager's
configuration database.
diagnose cdb check policy-packages <adom>
After running this command, FortiManager will remove the invalid mappings of vpnmgr
interfaces.
1042701 The traffic view page for the full mesh does not display the FortiGate and the external
gateway.
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 ✓
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© 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.