Fortinet Document Library

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

Administration Guide

Import configuration

The Import Configuration operation copies policies and policy-related objects from the device layer into the ADOM and policy later, creating a policy package that reflects the current configuration of the FortiGate device. The import operation does not modify the FortiGate configuration.

The imported objects go into the shared object database.

If you are importing an object that already exists in the object database (same object type and name), you have the following choices:

  1. Update the definition for the object in the database.

    When you update the definition for an object in the database, it affects all FortiGates that reference the object. All FortiGates that reference the object go out of sync, and the updated object is considered a pending change. This action is equivalent to manually updating an object.

  2. Keep the definition for the object that is already in the database.

    When you keep the definition for an object in the database, all FortiGates that reference the object remain synchronized. The next time that you install to the FortiGate, the definition for the object from the FortiManager database is pushed to the device.

Note

After you import policies and objects from FortiGate to FortiManager, you might see some objects deleted the first time that you install a policy package to the FortiGate. The objects are on FortiGate because the objects are unused. FortiManager does not need to keep unused objects. You can always install the objects back to the FortiGate by adding them to a policy rule.

For more information, see Importing policies and objects.

Import configuration

The Import Configuration operation copies policies and policy-related objects from the device layer into the ADOM and policy later, creating a policy package that reflects the current configuration of the FortiGate device. The import operation does not modify the FortiGate configuration.

The imported objects go into the shared object database.

If you are importing an object that already exists in the object database (same object type and name), you have the following choices:

  1. Update the definition for the object in the database.

    When you update the definition for an object in the database, it affects all FortiGates that reference the object. All FortiGates that reference the object go out of sync, and the updated object is considered a pending change. This action is equivalent to manually updating an object.

  2. Keep the definition for the object that is already in the database.

    When you keep the definition for an object in the database, all FortiGates that reference the object remain synchronized. The next time that you install to the FortiGate, the definition for the object from the FortiManager database is pushed to the device.

Note

After you import policies and objects from FortiGate to FortiManager, you might see some objects deleted the first time that you install a policy package to the FortiGate. The objects are on FortiGate because the objects are unused. FortiManager does not need to keep unused objects. You can always install the objects back to the FortiGate by adding them to a policy rule.

For more information, see Importing policies and objects.