When importing policy and objects from a FortiGate currently selected revision history config file, before actually importing the policies and objects, a summary of the objects that will be updated, imported, renamed and skipped (duplicates) will be listed and shown.
This article will define the different actions that will be taken on the objects listed in this summary page.
When importing into FortiManager, all FortiGates in a given ADOM have a shared database for their objects.
2) Updates to Existing FortiManager Objects:
- The FortiManager will first rename the object's name (by adding a '_001' to the original name) on the unit database on the FotiManager in Device Manager (not on actual device), but the actual import to the 'Policy & Objects' database will not be imported just yet.
- Now that the object name is renamed, to be imported to the 'Policy & Objects' database, if another import is performed, then the new renamed object will be imported, such that the already existing object on the FortiManager in the 'Policy & Object' database but of a different type of object is not affected and is not in conflict.
-To reflect the new name of the object on the device itself, an install will need to follow.
FortiManager has a Firewall address group named 'OBJ' and the FortiGate being imported has a firewall address object named 'OBJ', since both have the same name but the object type is different, the FortiManager will import the OBJ as a firewall address as OBJ_001.