Troubleshooting Tip: Import policy fails due to 'create mapping fail'
| Description | This article describes troubleshooting steps when importing a policy package fails due to an interface mapping issue in FortiManager. |
| Scope | FortiManager. |
| Solution | The issue happens when FortiGate has previously been imported, and the policy package is removed, but the interface mapping to FortiGate is still in the FortiManager database. The following pop-up will show that none or some of the firewall policies are being imported into the FortiManager:
When downloading the Import Report, the following error is shown:
Since the same firewall was previously imported, the object and mapping have already existed in the FortiManager database
Removing the existing mapping will solve the issue.
The following KB ARTICLE may be used in the case the object type is 'Interface Subnet': Technical Tip: Editing Firewall Address Object with "Type of Interface Subnet" |
