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).
Candidate Configuration

Candidate Configuration

The candidate configuration capability indicates the device supports the <candidate/> configuration database storing configuration data that will be committed to it.

This database stores complete device configuration data. Operating this configuration data does not affect the running configuration data of the device.

Additions, deletions, and changes can be made to the data in the <candidate/> configuration database to construct the desired configuration data. The following operations can be performed at any time:

  • <commit>: converts all configuration data in the <candidate/> configuration database into running configuration data.

    If the device is unable to commit all of the changes in the <candidate/> configuration database, the running configuration data remains unchanged.

  • <discard-changes>: discards configuration data that has not been committed from the <candidate/> configuration database. After this operation is performed, the configuration data in the <candidate/> configuration database remains the same as that in the <running/> configuration database.

A device establishes an independent <candidate/> configuration database for each NETCONF session.

Capability ID

  • RPC request:

    <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
          <ifm xmlns="" content-version="1.0" format-version="1.0">
  • RPC reply:

    <rpc-reply message-id="596" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> 
Updated: 2019-04-20

Document ID: EDOC1100075365

Views: 40075

Downloads: 127

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