FortiManager 7.4: Interface Mapping Issue During Policy Installation

[5q46n2te8jPWJY]

Hello everyone,

I'm currently using FortiManager 7.4 with two connected FortiGate devices. I had two separate firewall policies for each device, and I am trying to merge them into a single policy package. My goal is to push this policy package to both FortiGates, ensuring that only the necessary rules are applied to each device.

However, during the policy installation process, I encounter the following error message:

"The following ADOM interfaces have no mapping. All ADOM interfaces should be mapped before continuing with installation."

In each block I have framed, the interfaces do not exist locally, but they are present in the remote device. What is wrong?

Any ideas?

Thanks for your help!

[asrour]

hi @5q46n2te8jPWJY 

- The policy package interacts with Normalized interface not with the physical interfaces.

- each interface in the FortiGate should have a mapping to a normalized interface

- the install wizard is requesting you to map the listed normalized interfaces that are used in the policy to the corresponding physical interfaces in the FortiGate

find the details of the normalized interfaces in the admin guide

https://docs.fortinet.com/document/fortimanager/7.4.4/administration-guide/36781

Thank You!

[5q46n2te8jPWJY · Accepted solution]

Hi,

I found the solution. In policy package datagrid, I have a column to choose where the rules apply. I have to select in this column, the correct device for each rules.

Since I did it, I don't have error !

[sw2090]

yes exactly. If one policy has no specific installation target (column install to in Policy view) it will be deployed to all FGT in that adom (or to all if it is global). So FMG wants a mapping of normalized interfaces for all FGT (either per device or per model). Also all address objects would need that because missing addressmapping will not cause an error but the default address of the object will be deployed. If the address is the same on the FGT you don't need to create mappings here.

So you either have to map your interfaces or - better  if that policy applies to a specific FGT - set that as installation target.