Description
This article describes how to solve an issue where the 'Device Manager' page in FortiManager indicates the FortiGate status is Out-of-sync.
Scope
FortiManager v5.6 and above, FortiGate.
Solution
First check your FOS compatibility with FMG
Retrieve Config on the device, as shown below:
It is also possible to use the FortiManager CLI to retrieve the configuration:
diag test deploymanager reloadconf <OID>
To find the device OID, use the following command:
diag dvm device list
If the changes were applied to policies or objects used in any policy, import the policies again:
Select the unit in the Device Manager page and select Import Policy to launch the import wizard. Use the wizard to import the policies and objects.
Select the unit in the Device Manager page and select Import Policy to launch the import wizard. Use the wizard to import the policies and objects.
In FortiManager v7. x.x, the wizard additionally grants the option to import FortiAP and FortiSwitch profiles.
Select the policy profile name to use:
Choose one of the following options:
- Keep and import the FortiGate object entity into the FortiManager policy package database.
- Keep the FortiManager database as-is. (It is common practice to import the object from the FortiGate if the one running in the live network is trusted.)
Policy differences may result if the FortiGate object is imported multiple times and the content is different in each one. For example, the object printer_server may have different IP addresses in the first FortiGate and the second FortiGate.
If the FortiAP and FortiSwitch profiles were selected to be imported from the FortiGate, the following screen will appear:
Afterward, the device database and policy package will be fully synchronized:
Run a policy package Install Wizard on the FortiGate(s) to finalize the sync process:
Related articles:
