Created on
10-10-2024
10:08 PM
Edited on
01-21-2025
12:23 PM
By
RMarqeshi
Description | This article describes what is the impact of removing a provisioning template that was previously applied to a device in FortiManager. |
Scope | FortiManager |
Solution |
Provided that the FortiGate is synchronized with FortiManager, removing a previously applied provisioning template has different impact depending on type of the template:
If the VPN settings are required to remain in place, either assign the template back to the FortiGate or remove the comment (Created by IPSec template) from the IPsec phase1 and phase2 config and related static routes which will allow FortiManager to ignore them. Refer to this KB article: Technical Tip: Remove comment (Created by IPSec Template)...using TCL Script.
The other templates' (for example: SD-WAN, BGP, Static, etc) changes are device-database level and do not remove any config from FortiGate if the templates are unassigned/removed.
Related documents: Technical Tip: Remove comment (Created by IPSec Template)...using TCL Script. Technical Tip: How to create IPSec Template and assign to a device using JSON API |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.