Editing interface with normalized interface mapping displays some unnecessary messages for mapping change.

FortiManager should highlight device consisting of specific IP address under Fabric View.

FortiManager is unable to create VIPv6 virtual server objects.

Rule list order may not be saved under File Filter Profile.

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.

If policy changes are made directly on the FortiGates, the subsequent PP 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 this 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.