Troubleshooting Tip: Useful workaround when FortiManager does not install configuration as expected

Description

This article describes useful workarounds in circumstances where, due to known issues, FortiManager does not install the configuration as expected.

Scope

FortiManager/FortiManager Cloud.

Solution

Before trying the workaround, confirm that FortiGate and FortiManager have synced configuration, or perform a Retrieve+Import operation as described in Technical Tip: When a retrieve is not enough, it requires an import.

Option 1:

In some scenarios, due to problems with the Device or ADOM DB, running the script against the Device or ADOM DB may fix the problem. Navigate to: Device Manager -> Scripts -> Create New.

After creating the desired config, specify 'Run script on' for 'Device Database' or 'ADOM database' and select 'Run Script'.

Verify with the installation if the issue is fixed.

Option 2:

As the Templates take precedence over the Device or ADOM DB, creating a CLI Template with the correct config can help to fix the problem.

Navigate to Device Manager -> Provisioning Templates -> CLI -> Create New.

After creating the desired configuration, assign the device to the CLI Template. Verify with the installation if the issue is fixed.

Option 3:

If the CLI template does not correct the Installation configuration, the option 'Schedule a script' can be used.

As explained in the Schedule a script, the option 'Enable Automatic execute after each device install' should be used. This means that initially, the incorrect configuration will still be pushed: however, within a few seconds, a corrected automatic script will be executed.