Databases Supported by NETCONF

The NMS uses NETCONF to manage network devices. The configuration and status data is stored in three standard databases, as listed in Table 1.

**Table 1** NETCONF databases
Database	Description	Relationship Among Three Databases
<running/>	Stores the running configurations on devices. The data in this database can be modified, and the modifications take effect immediately. This is the only mandatory standard database.	The modifications on <candidate/> take effect only after the modified data is committed to the <running/> database. When the system is starting, it automatically copies the data in <startup/> to <running/>. The three databases can be replaced with each other by performing the <copy-config> operation.
<candidate/>	Stores ineffective candidate configurations on devices. The data in this database can be modified, and the modifications will not take effect immediately. This database is supported by Candidate Configuration.
<startup/>	Stores the configuration that will take effect after next startup. The data in this database cannot be modified. You can only replace the database by performing the <copy-config> operation. This database is supported by Distinct Startup.