Fortinet white logo
Fortinet white logo

Known Issues

Known Issues

The following issues have been identified in 7.0.4. To inquire about a particular bug or to report a bug, please contact Customer Service & Support.

Device Manager

Bug ID

Description

771417

Cannot overriding system template settings.

764369

FortiManager tries to install Security Fabric trusted list to all downstream FGs when a new one is added.

830105

When two or more IPsec phase1-interfaces have same remote-gw IP address, FMG tries to install 1.0.0.0 as remote-gw.

Others

Bug ID

Description

823294

SSH connection between FortiGate and FortiManager v7.0.4 fails due to server_host_key_algorithms mismatch.

Policy & Objects

Bug ID

Description

585177

FortiManager is unable to create VIPv6 virtual server objects.

724011

FortiManager needs to support multiple server certificate list in ssl/ssh profile.

751168

Installation to FortiGate may fail when installing some specific applications.

793240

FortiManager fails to retrieve FortiGate's configuration when external-resource objects include a "g-" prefix.

There are two workarounds; use the approach that works best for your environment. If it is possible, create a new backup of your FMG and FGT(s) before making any changes:

First workaround approach:

  1. Re-create all threat feeds locally in VDOM configuration and update policies and security profiles that reference them to the local threat feed vs. the global feed.

  2. Delete the global threat feed objects.

Second workaround approach:

  1. Perform policy reinstallation. FMG adds original threat feed objects within the VDOM configuration without the 'g' prefix.

  2. FMG reports 'install OK/verify FAIL' at the end of the policy installation.

  3. Run scripts to delete the global threat feed objects (objects with the 'g' prefix) from the FGT.

  4. Retrieve the FGT configuration from FMG.

  5. Perform another policy installation to update the configuration synchronization status between the FGT and FMG. No commands are pushed during this stage according to the install wizard.

822843

FortiManager displays an error when using the access-proxy type VIP and normal VIP in firewall policies as they are both using the same external IP.

838648

"Rename objects to import" inconsistency with "datasrc duplicate" error.

System Settings

Bug ID Description

780245

Install Wizard shows all devices are selected even-though "Default Device Selection for Install" is set to "Deselect All".

Known Issues

Known Issues

The following issues have been identified in 7.0.4. To inquire about a particular bug or to report a bug, please contact Customer Service & Support.

Device Manager

Bug ID

Description

771417

Cannot overriding system template settings.

764369

FortiManager tries to install Security Fabric trusted list to all downstream FGs when a new one is added.

830105

When two or more IPsec phase1-interfaces have same remote-gw IP address, FMG tries to install 1.0.0.0 as remote-gw.

Others

Bug ID

Description

823294

SSH connection between FortiGate and FortiManager v7.0.4 fails due to server_host_key_algorithms mismatch.

Policy & Objects

Bug ID

Description

585177

FortiManager is unable to create VIPv6 virtual server objects.

724011

FortiManager needs to support multiple server certificate list in ssl/ssh profile.

751168

Installation to FortiGate may fail when installing some specific applications.

793240

FortiManager fails to retrieve FortiGate's configuration when external-resource objects include a "g-" prefix.

There are two workarounds; use the approach that works best for your environment. If it is possible, create a new backup of your FMG and FGT(s) before making any changes:

First workaround approach:

  1. Re-create all threat feeds locally in VDOM configuration and update policies and security profiles that reference them to the local threat feed vs. the global feed.

  2. Delete the global threat feed objects.

Second workaround approach:

  1. Perform policy reinstallation. FMG adds original threat feed objects within the VDOM configuration without the 'g' prefix.

  2. FMG reports 'install OK/verify FAIL' at the end of the policy installation.

  3. Run scripts to delete the global threat feed objects (objects with the 'g' prefix) from the FGT.

  4. Retrieve the FGT configuration from FMG.

  5. Perform another policy installation to update the configuration synchronization status between the FGT and FMG. No commands are pushed during this stage according to the install wizard.

822843

FortiManager displays an error when using the access-proxy type VIP and normal VIP in firewall policies as they are both using the same external IP.

838648

"Rename objects to import" inconsistency with "datasrc duplicate" error.

System Settings

Bug ID Description

780245

Install Wizard shows all devices are selected even-though "Default Device Selection for Install" is set to "Deselect All".