Correct. When changes are made to a policy package on FortiManager and the managed device independently of each other, this can lead to conflicts. The system recognizes discrepancies between the configurations stored on FortiManager and those active on the device, marking the status as Conflict because it cannot reconcile these differences without manual intervention.
C manual page 222
Conflict: If you make policy configuration changes locally on FortiGate and don’t import the changes into
the policy package, and you also made the changes on FortiManager, the status enters conflict state.
Depending on the configuration changes, you can either import a policy package or install the changes from FortiManager.
A policy package status of "Conflict" indicates that:
C. The policy package configuration has been changed on both FortiManager and the managed device independently.
This status arises when there are discrepancies between the policy configurations on FortiManager and the FortiGate device, due to changes being made locally on the FortiGate and also on the FortiManager, without synchronizing these changes. As a result, FortiManager cannot reconcile the differences automatically, leading to a conflict status. This requires manual intervention to resolve the differences and ensure the policy configurations are consistent across both platforms.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
erzestxgyhlji
3 months agosugar12
3 months, 3 weeks agoerzestxgyhlji
4 months agored_sparrow_Gr
4 months, 1 week ago