| Description | This article describes what happens when a metavariable's per-device mapping is incorrectly configured. |
| Scope | FortiManager v7.2, v7.4, v7.6. |
| Solution |
FortiManager's metavariables allow the configuration of per-device mappings to accommodate distinct configurations for multiple devices.
In this scenario, FortiManager is currently managing one device with VDOM mode disabled:
A System Template has been assigned to this device, with a metavariable set to the Host Name field:
The metadata variable setting allows either the global or root VDOM to be mapped to the variable:
In this case, the root VDOM is selected to be mapped:
This will result in an error when trying to load the device's Install Preview:
This is because the hostname set belongs to the global VDOM (all settings in the System Template belong to the global VDOM). To correct this, change the metavariable's per-device mapping to the global VDOM:
The Install Preview can then be loaded successfully after that:
Related article: Technical Tip: New Meta Variables and their usage including Jinja scripting |
