No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Configuration Guide - Network Management and Monitoring

S1720, S2700, S5700, and S6720 V200R011C10

This document provides the configurations of network management and monitoring features supported by the product, including SNMP, RMON and RMON2, LLDP, Performance Management, iPCA, NQA, Service Diagnosis, Mirroring, Packet Capture, NetStream, sFlow, TWAMP Light, and NETCONF.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Databases Supported by NETCONF

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 14-3.

Table 14-3  NETCONF databases



Relationship Among Three Databases


Stores the running configuration on the device. 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/> can 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.


Stores ineffective candidate configurations on the device. The data in this database can be modified, and the modifications will not take effect immediately.

This database is supported by Candidate Configuration.


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.

Updated: 2020-02-06

Document ID: EDOC1000178174

Views: 206464

Downloads: 824

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next