What to do when an object conflict occurs
The admin user must choose to either keep the FortiManager version of the conflicted object, or replace it with the FortiGate version.
If this is the first device that an import is being performed on in this ADOM, it is reasonable to choose the FortiGate version of the object if the syntax or value of this object is typical for other devices that will be imported.
If other devices have already been imported, choose the FortiManager version of the object so that existing managed devices are not negatively affected.
|
Shared object conflicts when auto-importing VDOMsWhen adding a new FortiGate device and choosing to automatically import VDOMs, existing FortiGate devices that share the same objects may become in conflict. This occurs if there are differences in the shared object's values between FortiGate and the FortiManager, for example when the Comments section differs. FortiManager automatically imports the object from FortiGate, overriding the existing object in the FortiManager's database which causes existing devices using that object to display a conflict. The recommended practice when adding a new FortiGate device with shared objects is to import each VDOM step by step in order to override the shared object's values with FortiManager's. |