Hi Sirs,
Is there any information on the following parameters? thanks.
STATUS: db: modified; conf: in sync; cond:pending ; dm: retrieved; conn: up
db:modified ??
conf:in sync ??
cond:pending ??
Hi Libra,
db:modified = This is the device setting status which indicates that configuration changes were made on FortiManager.
conf:in sync = This is the sync status which shows that the latest revision history is in sync with Fortigate's configuration.
cond:pending = This is the configuration status which says that configuration changes need to be installed.
I hope that helps.
NSE5, CCSE, CCNA R&S, CompTIA A+, CompTIA Network+, CompTIA Security+, MTA Security, ITIL v3
Hi Sir,
Is the following description correct? The latest revision history for the managed FortiGate does match with the FortiGate running configuration, but the latest revision history for the managed FortiGate does not match with the device-level database.
After an Auto-Update or Retrieve: device database = latest revision = FGT
Then after a manual change on FMG end (but no install yet):
latest revision = FGT (still) but now device database has been modified (is different).
After reverting to a previous revision in revision history:
device database = reverted revision != FGT
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1749 | |
1114 | |
765 | |
447 | |
241 |
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.