The following issues have been identified in 6.2.2. For inquires about a particular bug or to report a bug, please contact Customer Service & Support.
Unable to retrieve device due to data not exist (g-xxxx firewall object).
SD-WAN monitor is blank when the monitor interface data does not match the configuration data.
FortiManager shows an incorrect firmware upgrade path for the FortGate. See Special Notices.
Global v5.2 assigned to ADOM v5.4 and
|Some hardware specific SNMP traps are missing from the device SNMP settings and the system provisioning templates.
|Central Management FortiSwitch Template GUI cannot assign VLANs with Microsoft Edge.
|The event log should may show the correct username.
|In the FortiGate’s GUI, the VPN Phase2 selectors can be managed separately, which is completely missing in FMG -> VPN Manager -> Monitor.
|VPN Manager’s dpd-retryinterval range is too small.
|Import policy package does not add interfaces in dynamic mapping for zone if the zone mapping is already empty.
|FortiManager should grey out the 'Next' button when zone validation occurs while "Re-install Policy".
|Deleting an unused object may change the policy package status.
|The policy interface colors are different in Device Manager and Policy & Objects.
|FortiManager does not show Global Icon for global Objects assigned to ADOMs.
|The warning message “input must be a number” should be displayed if an unexpected value is entered into “Heart Beat Interval” for HA.
|Workflow Session List menu seems to always match the first wildcard TACACS admin.
|FortiManager tries to delete replacemsg-group that is auto-created by adding tunnel SSID.
|Signature "Apache.Optionsbleed.Scanner" cannot be selected as IPS Signature anymore but only "Rate based Signature".
|Saving configuration with an incorrect IP or net mask format does not trigger an error.
|LVM information may show disk unused.
|The FmDeviceEntPolicyPackageState SNMP always returns (-1), which indicates never installed, regardless of the actual policy package status.
|Handling of custom Application Control signatures may not be consistent between FortiManager and FortiGate.
|Interface Validation may display the interface mapping prompt multiple times for the same unmapped interface.
|Sorting Extenders by device Name does not work.
|In workflow mode, changes to the SSL VPN portals do not trigger policy package status to "Modified".
|SD-WAN monitor may show a visual gap when monitoring traffics.
|FortiManager may install duplicated members during device install.
|License information for FortiAnalyzer shown in Device Manager is not correct.
|FortiManager may not correctly keep router access-list rule default value causing subsequent installation to fail.
|Admin user with read-only profile should not be allowed to "Revoke Release" in DHCP query and "Bring Tunnel Down/Up" in Query IPsec.
|Adding or modifying rate based signature within IPS profile, FortiManager resets all rate-based signatures to default setting.
|SD-WAN Monitor shows No Data for Performance SLA Statistics.
|FortiManager should display zone icon based on existing and non-existing dynamic mappings.
|Policy package difference does not show user or admin details.
|FortiManager should check if a script is applicable to global and report an error if the script cannot be ran.
|Workflow session removes user group for FortiSwitch Security Policy.
|VPN Manager may set add-route to disable when creating a managed gateway in dial-up topology as spoke and the option to select "Add Route" is set "off".
|FortiManager Event Log may show policy package installed on different units.
Re-install policy on FortiGate with multiple VDOMs wipes config when different VDOM in different package.
When an external gateway is defined within VPN Manager, the change cannot be installed to FortiGate with the error: no hub configured for vpn XXX.
VPN Manager GUI cannot select a VDOM when adding a managed gateway.
Workaround: Use a CLI script to configure a managed gateway with the desired VDOM.
When upgrading FortiGate, FortiManager may upgrade the device to version 6.0.3 prior to upgrading to version 6.2.2.
Workaround: Please select the Skip All Intermediate Steps in Upgrade Path if Possible option when upgrading FortiGate.