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)
Use the diagnose dvm device list command to display details of all managed and unregistered devices Each FortiGate is assigned an object ID (OID), and its configuration is stored in its own device-level database (dev-db)
In this example, changes have been made in FortiManager to the device-level settings. That is why the CLI output is showing dev-db: modified and the cond is showing as pending. After you install the changes on FortiGate, the output displays dev-db: not modified and cond: OK
This command also shows wheter the FGFM tunnel between FortiGate and FortiManager is up or down.
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 8Â months, 4Â weeks agoLito
Most Recent 1Â month, 2Â weeks ago53a24e2
4Â months, 2Â weeks agolmptcne
8Â months, 1Â week agoLAFNELL
8Â months agolmptcne
8Â months agoTigerL
8Â months, 1Â week agoLAFNELL
8Â months, 1Â week agoRadicalcactus
8Â months, 2Â weeks agoeamstar
8Â months, 2Â weeks agoMaDeInBe
8Â months, 2Â weeks agoMahfoud_31
8Â months, 3Â weeks ago