FortiManager
FortiManager supports network operations use cases for centralized management, best practices compliance, and workflow automation to provide better protection against breaches.
madhan
Staff
Staff
Article Id 424286
Description

This article describes FortiManager behavior where per-device mappings suddenly appear even when no such configuration has been made.

Scope FortiManager.
Solution

In FortiManager, there are a feature called per-device mapping where an object with the same name can be shared across managed devices as a different value. For example, create an object for health check address:

  • Object type: Address
  • Default Value: 1.1.1.1
  • Mapped device: FortiGate-A (8.8.8.8)

 

GPicture1.png

 

More information can be found in Per-device and per-platform dynamic mapping.

 

In the provided example, when the object is installed in FortiGate-A, the value will become 8.8.8.8/32 while other managed devices will have the default value, 1.1.1.1/32.

 

The sudden appearance of a per-device mapping is because there has been an import done and the name of the object already exists in the FortiManager.

 

It is important to notice the per-device mapping configuration as if there are changes to the object configurations. For example, the default value changed to 2.2.2.2/32, but the value for the mapped device will remain as-is (in this case, 8.8.8.8/32) and may affect the network upon installation.
Contributors