A&D are correct.
– conf: in sync – This is the sync status which shows that the latest revision history is in sync with Fortigate’s configuration.
- There is a new modification on FortiManager device level DB (dev-db: modified) which wasn’t installed to FortiGate (cond: pending)
A,B
dev-db: modified - This status indicates that the device-level database in FortiManager has unsynchronized changes, meaning that the latest revision history stored in FortiManager does not match the configuration that was installed on the FortiGate.
conf: in sync - Since configuration changes have been installed successfully on the FortiGate from FortiManager, this status would show as "in sync." This status indicates that FortiGate’s running configuration now aligns with the last installed configuration, even if the device-level database in FortiManager does not match the latest revision history.^
cond: pending - FortiManager knows the change was made directly on FortiGate
B is false cause dev-db is modified so configurations changes have not been installed
C is false cause dm is retrieved and not auto-updated
A&D are correct
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.
Shashanka
Highly Voted 6Â months, 2Â weeks ago53a24e2
Most Recent 1Â month, 4Â weeks agolmptcne
5Â months, 3Â weeks agoLAFNELL
5Â months, 2Â weeks agolmptcne
5Â months, 2Â weeks agoTigerL
5Â months, 3Â weeks agoLAFNELL
5Â months, 3Â weeks agoRadicalcactus
6Â months agoeamstar
6Â months agoMaDeInBe
6Â months agoMahfoud_31
6Â months, 1Â week ago