| Description |
This article describes how to troubleshoot when the installation fails with a validation error after assigning a Static Route Template to a device:
Commit failed: |
| Scope | FortiManager. |
| Solution |
The issue occurs when a device already has a static route configured, and a matching route is later pushed through a Static Route Template. Instead of recognizing the existing configuration, the template attempts to add the route again as a new entry, which results in an error.
For Example, the screenshot below shows the error because a new route '3' is being added to the FortiGate, which is matching the existing route '2'.
Checking the Device Database for the FortiGate: Device Manager -> Device & Groups -> Managed FortiGates -> Select the FortiGate -> Network -> Static Routes: FortiGate has the Route 2.
Checking the Static Route Template assigned to the FortiGate: FortiManager -> Device Manager -> Provisioning Templates -> Static Route -> Select the Template having issue: Route is matching with the existing route in FortiGate.
To fix the issue. Under the Static Route Template, edit the route giving error -> Under Advanced Options -> Set the '_seq-num' value to match the sequence number of the route already present in the device, in this case '2', select OK to save.
If the value of '_seq-num' is set to '0' or is empty, then Static Route Template will add a new route; if it matches the existing route number of the FortiGate, it will overwrite that route.
Try installing again, no validation error now:
Related document: |
