Description
This article describes how to import a system template between the ADOMs. The method is only supported over CLI and is not available in GUI for now.
Scope
FortiManager.
Solution
The use case is to import a system template when the administrator wants to move the managed device from one ADOM to another ADOM.
When the managed device is moved from one ADOM to another, by default the system template is not moving along.
To ease the issue of re-configure the same system template in the new ADOM. The administrator can use the following CLI commands to accomplish this by copying the settings from one ADOM to another ADOM.
execute fmprofile export-profile <adom> <profile-id> <filename>
execute fmprofile import-profile <adom> <profile_id> <filename>
execute fmprofile list-profiles <adom_name>
Use Case Example.
ADOM:
root has a system template named 'globalSystemTemplate' and the administrator needs to copy the exact setting to a new ADOM: adom74.
Steps:
- It can be accomplished by exporting the intended system template from ADOM: root into a /tmp folder as an output filename 'configRoot'.
execute fmprofile export-profile root ?
<id> profile name
10298 default
10437 powerRanger
10465 globalSystemTemplate
execute fmprofile export-profile root 10465 configRoot
output dump to file: [/tmp/configRoot]
- Go to ADOM: adom74, then create a blank system template named the same as 'globalSystemTemplate', and other settings left it unconfigured.
- As the settings are dumped as /tmp/configRoot, the administrator then can run the following CLI to import the settings into another ADOM: adom74.
execute fmprofile import-profile adom74 ?
<id> profile name
5144 default
5239 globalSystemTemplate
execute fmprofile import-profile adom74 5239 /tmp/configRoot
Successfully import from file [/tmp/configRoot] to profile [globalSystemTemplate]
- Go back into ADOM: adom74, then check whether the settings are successfully imported.
