Technical Tip: How to fix synchronization issue in FortiManager

[akamath]

Description

This article describes how to synchronize FortiGate’s configuration to FortiManager’s database.

Scope

FortiManager.

Solution

FortiGate’s configuration synchronization to FortiManager can be verified by the config and policy package status in the FortiManager.

Config status in FortiManager:

1. Conflict.
2. Out-of-sync.
3. Modified.
4. Unknown.

Config status:

1. Conflict:
   
   

   Conflict status of the Config Status. It can happen because of two reasons:

   1. If in the advance settings the option 'Configuration Changes Received from FortiGate' is set to 'Prompt Administrator to Accept'.
   2. If installation fails due to verification fail.

Solution: To fix the conflict status in the FortiManager's config status follow the below steps.

Navigate to Device Manager -> Double-click on the FortiGate -> Configuration and installation -> Revision history -> Select revision -> View diff.

To update the current configuration running on the FortiGate to FortiManager follow the below steps:

Retrieve: under Device Manager -> Managed Devices -> Select the FortiGate -> Dashboard -> Summary -> 'Configuration and Installation' widget -> Revision -> select the menu icon  -> Retrieve.

To retrieve via the CLI:

diagnose test deploymanager reloadconf <OID>

       diagnose dvm device list -> In the output, find the OID of the FortiGate that is being added to FortiManager.

See Technical Note: Retrieve configuration file using CLI from a FortiManager.

Import configuration: To synchronize the ADOM database of FortiManager, import the configuration. Navigate to Device Manager -> Import configuration -> Check if the name of the policy is the same -> Overwrite -> Check the interface mapping -> Next.

To push the configuration changes made from FortiManager to FortiGate, install the configuration so the changes will be updated on FortiGate. Before following this step take the FortiGate configuration backup.

Navigate to FortiGate -> Dashboard -> Admin -> Configuration -> Backup.

Install: Navigate to FortiManager -> Device Manager -> Install -> Install Wizard -> Install Device Settings (only) -> Check the install preview.

 

2. Auto-update: For any configuration changes made on the FortiGate locally, it will automatically update the changes to the FortiManager’s device database. To enable this, navigate to System Settings -> Advanced -> Advance settings / Misc Settings -> 'Configuration changes Receive from FortiGate' -> Set it to 'Automatically accept'.
   
   

From the CLI:

config sys admin setting

    set auto-update enable

end

Note:

The user needs to manually 'Import configuration' to synchronize the policy package status.

3. Out-of-sync: See this article for troubleshooting steps.
4. Modified: When the config status is modified, verify it by checking the difference before pushing the changes to FortiGate: Navigate to Device Manager -> Double-click on the FortiGate -> Configuration and installation -> Revision history -> Select revision -> View diff.

To push these changes to the FortiGate: navigate to Device Manager -> Install -> Install Wizard -> Install Device Settings (only) -> Check the install preview.

Policy-package status:

1. Conflict: To update the configuration running on the FortiGate to FortiManager, follow the steps below:

Retrieve: By retrieving, the complete configuration of FortiGate will be updated on the FortiManager’s device database. Device Manager -> Managed Devices -> Select the FortiGate -> Dashboard -> Summary -> 'Configuration and Installation' widget -> Revision -> Select the icon in front of that and choose Retrieve.

Import configuration: navigate to Device Manager -> Import configuration -> Check if the name of the policy is the same -> Overwrite -> Check the interface mapping -> Next.

To push the configuration changes made from FortiManager to FortiGate install the configuration so the changes will be updated on FortiGate. Before following this step, take the FortiGate configuration backup:

Navigate to FortiGate -> Dashboard -> Admin -> Configuration -> Backup.

Install: navigate to FortiManager -> Device Manager -> Install -> Install Wizard -> Install Policy Package & Device Settings -> Check the install preview -> Install.

If any errors are seen in the preview, review and fix that error before installing to FortiGate.

2. Modified: If the policy-package status is modified, first verify by checking the difference before pushing the changes to FortiGate:
   navigate to Device Manager -> Select the FortiGate -> Configuration and installation -> Revision history -> Select revision -> View diff.

To push these changes to the FortiGate: Navigate to Device Manager -> Install -> Install Wizard -> Install Policy Package & Device Settings -> Check the install preview.

3. Out-of-sync:  Troubleshooting Tip: FortiGate is Out-of-sync in the Device Manager.

Troubleshooting: 

If users are still facing any issues, stop til the preview and raise a case with the Fortinet technical support to troubleshoot the issue further. Share the output of the following debug commands with them:

diagnose debug application securityconsole 255

diagnose debug app depmanager 255

diagnose debug application fgfmsd 255 <FortiGate's IP>

diagnose debug enable

diagnose debug time enable

To stop debugging:  

di de di

di de reset

Note: Sometimes, just refreshing the device status might also help. To refresh the device status, navigate to:

Device Manager -> Right-click to device -> Refresh Device or

Device Manager -> Select all devices -> More -> Refresh Device

Related articles:

• Technical Tip: How to troubleshoot the 'copy' error while install Policy
• Technical Tip: Configuration import from the device to the ADOM DB / Policy & Objects
• Troubleshooting Tip: FortiGate is Out-of-sync in the Device Manager
• Technical Tip: FortiManager data configuration and synchronization procedures