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

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of Network Management and Monitoring, including SNMP, RMON, NETCONF, OpenFlow, LLDP, NQA, Mirroring, Packet Capture, Packet Trace, Path and Connectivity Detection Configuration, NetStream, sFlow, and iPCA.
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).
Overview of RESTCONF

Overview of RESTCONF


RESTCONF, an HTTP-based protocol, provides RESTful programmatic interfaces and allows users to add, delete, modify, and query network device data.


The increasing network scale and complexity drive the growing demand for automated O&M. The Network Configuration Protocol (NETCONF) provides an application programmatic interface based on the remote procedure call (RPC) mechanism. However, NETCONF has fallen behind network development, which necessitates the need for standard programmatic interfaces that support web application access and operations of network devices.

RESTCONF is developed based on the combination of NETCONF and HTTP. RESTCONF provides core NETCONF functions using HTTP methods. The programmatic interface complies with the RESTful style of the IT industry and provides users with the capability of efficiently developing web O&M tools.

Table 4-1 describes the comparison between RESTCONF and NETCONF.

Table 4-1 Comparison between RESTCONF and NETCONF



Transmission channel (protocol)

NETCONF prefers to Secure Shell (SSH) at the transport layer and uses SSH to transmit XML information.

RESTCONF accesses device resources based on HTTP. The programmatic interfaces provided by RESTCONF comply with the RESTful style of the IT industry.

Packet format

XML code is used.

XML or JSON code is used.

Operation characteristics

NETCONF operations are complex. For example:

  • NETCONF supports addition, deletion, modification, and query, multiple configuration datastores, as well as configuration rollback.
  • NETCONF requires two-phase configuration validation. Parameters are configured and committed before taking effect.

RESTCONF operations are simple. For example:

  • RESTCONF can create, read, update, delete (CRUD) data only in the <running/> datastore.
  • The RESTCONF operations take effect immediately, without the need to be submitted in two phases.


  • RESTCONF provides RESTful programmatic interfaces to support web development.
  • Standard interfaces are compatible with multi-vendor devices, reducing development and maintenance costs.
  • RESTCONF provides high extensibility, allowing various vendors to define additional NETCONF operations.
  • No NMS tool is required. WWW is supported.
Updated: 2019-04-20

Document ID: EDOC1100075365

Views: 34745

Downloads: 123

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Previous Next