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).
NETCONF Protocol Framework

NETCONF Protocol Framework

Like the open systems interconnection (OSI) model, the NETCONF protocol framework also uses a hierarchical structure. A lower layer provides services for the upper layer.

The hierarchical structure enables each layer to focus only on a single aspect of NETCONF and reduces the dependencies between different layers.

Table 3-2 describes the layers of the NETCONF protocol framework.

Table 3-2 NETCONF protocol framework




Layer 1: transport

Blocks Extensible Exchange Protocol (BEEP), Secure Shell (SSH), and Secure Sockets Layer (SSL)

The transport layer provides a communication path for interaction between a NETCONF client and the server.

NETCONF can be carried on any transport protocol that meets all of the following requirements:
  • The transport protocol is connection-oriented. A permanent link is established between the NETCONF client and server. After the permanent link is established, data is transmitted reliably and sequentially.
  • The transport layer provides user authentication, data integrity, and security encryption for NETCONF.
  • The transport protocol provides a mechanism for distinguishing the session type (client or server) for NETCONF.

Currently, the device can use only SSH as the transport protocol of NETCONF.

Layer 2: RPC

<rpc> and <rpc-reply>

The RPC layer provides a simple RPC request and response mechanism independent of transport protocols. The client uses the <rpc> element to encapsulate RPC request information and sends the RPC request information to the server through a secure and connection-oriented session. The server uses the <rpc-reply> element to encapsulate RPC response information (content at the operation and content layers) and sends the RPC response information to the client.

In normal cases, the <rpc-reply> element encapsulates data required by the client or information about a configuration success. If the client sends an incorrect request or the server fails to process a request from the client, the server encapsulates the <rpc-error> element containing detailed error information in the <rpc-reply> element and sends the <rpc-reply> element to the client.

Layer 3: operations

<get-config>, <edit-config>, and <notification>

The operations layer defines a series of basic operations used in RPC. The basic operations constitute basic capabilities of NETCONF.

Layer 4: content

Configuration data

The content layer describes configuration data involved in network management. The configuration data depends on vendors' devices.

So far, only the content layer has not been standardized for NETCONF. The content layer has no standard NETCONF data modeling language or data model.

Updated: 2019-04-20

Document ID: EDOC1100075365

Views: 41076

Downloads: 127

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