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).
Capabilities and Operations Supported by NETCONF

Capabilities and Operations Supported by NETCONF

Device information is stored in the database, so the NETCONF protocol defines its basic capability base. The base includes a set of operations that modify database configuration and access information from the database. The operations included in base must be a minimal set of functions supported by NETCONF, but not all functions of NETCONF. Table 14-4 lists the operations included in the base.

Table 14-4  Operations included in the base




Obtains all or specified configuration data from the <running/>, <candidate/>, and <startup/> databases.


Obtains some or all running configuration data and status data from the <running/> database.


Adds, modifies, and deletes configuration data in the <running/> or <candidate/> database.


Replaces the target database with the source database. If no target database has been created, this operation creates a database and then replaces the database.


Deletes a database. The <running/> database cannot be deleted.


Locks a database. A locked database cannot be modified by other users, preventing multi-user configuration conflicts.


Unlocks a database. Users can unlock only the databases they have locked.


Closes a NETCONF session.


Forcibly closes a NETCONF session. Only an administrator can perform this operation.

In addition to the basic capabilities, NETCONF also provides a series of standard capabilities. These standard capabilities enhance the NETCONF functionality and strengthen the fault tolerance and scalability. This facilitates the implementation of the NETCONF-based open network management architecture and provides an efficient method for equipment manufacturers to develop new functions. Table 14-5 lists the standard capabilities of NETCONF and operations.

Table 14-5  Standard capabilities and operations of NETCONF




This capability allows a device to perform the <edit-config> and <copy-config> operations on the <running/> database.


Candidate Configuration

This capability indicates that a device supports the <candidate/> database.

This capability allows the device to operate the <candidate/> database without affecting the <running/> database.

<commit>: commits all configuration data in the <candidate/> database. The committed data is the running configuration data.

<discard-changes>: discards uncommitted configuration data from the <candidate/> database. After this operation is performed, the configuration data in the <candidate/> database remains the same as the data in the <running/> database.

Rollback on Error

This capability allows a device to perform a rollback when an error occurs. If an error occurs and the <rpc-error> element is generated, the server stops performing the <edit-config> operation and restores the specified configuration to the status before the <edit-config> operation is performed.


Distinct Startup

This capability indicates that the device is capable of starting independently and supports the <startup/> database.



This capability indicates that the device can send traps and events to the NMS. The NMS manages the device based on the received traps and events.

<notification>: actively sends traps and events to the NMS.


This capability indicates that the device supports NETCONF session reuse for multiple purposes. You can use one NETCONF session to maintain the device and manage the traps and events, improving management efficiency.


Updated: 2020-02-06

Document ID: EDOC1000178174

Views: 206445

Downloads: 824

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next