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

Reminder

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

upgrade

Configuration Guide - Network Management and Monitoring

CloudEngine 12800 and 12800E V200R005C10

This document describes the configurations of Network Management and Monitoring, including SNMP, RMON, LLDP, NQA, Service Diagnosis, Mirroring, Packet Capture, sFlow, 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).
Exchange

Exchange

This capability allows a device to send <rpc-reply> elements through the <get-next> operation.

Capability ID

<capability>http://www.huawei.com/netconf/capability/exchange/1.0</capability>
<capability>http://www.huawei.com/netconf/capability/exchange/1.2</capability>

A NETCONF client interacts with the device through the <get-next> operation.

For example, if the returned result of a <get> or <get-config> operation involves a large amount of data, the device must return the data using multiple <rpc-reply> elements. After the NETCONF client receives the first <rpc-reply> element, the NETCONF client interacts with the device through the <get-next> operation to request the next <rpc-reply> element or cancel the data query.

The following example shows how a NETCONF client sends an RPC request for interface information.

  • RPC request

    <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
      <get>
        <filter type="subtree">
          <ifm xmlns="http://www.huawei.com/netconf/vrp" content-version="1.0" format-version="1.0">
            <interfaces>
               <interface>
               </interface>
            </interfaces>
          </ifm>
        </filter>
      </get>
    </rpc> 
  • RPC reply

    <?xml version="1.0" encoding="UTF-8"?>
    <rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" set-id="989">
      <data>
        <ifm xmlns="http://www.huawei.com/netconf/vrp" format-version="1.0" content-version="1.0">
          <interfaces>
            <interface>
              <ifIndex>2</ifIndex>
              <ifName>Virtual-Template0</ifName>
              <ifPhyType>Virtual-Template</ifPhyType>
         <!-- additional <user> elements appear here... --> 
            </interface>
          </interfaces>
        </ifm>
      </data>
    </rpc-reply>

The following example shows how a NETCONF client needs to obtain the next <rpc-reply> element.

  • RPC request

    <rpc message-id="103" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
      <get-next xmlns="http://www.huawei.com/netconf/capability/base/1.0" set-id="1"> 
      </get-next>
    </rpc>
    
  • RPC reply

    <?xml version="1.0" encoding="UTF-8"?>
    <rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" set-id="989">
      <data>
        <ifm xmlns="http://www.huawei.com/netconf/vrp" format-version="1.0" content-version="1.0">
          <interfaces>
            <interface>
              <ifIndex>3</ifIndex>
              <ifName>Virtual-Template1</ifName>
              <ifPhyType>Virtual-Template</ifPhyType>
         <!-- additional <user> elements appear here... --> 
            </interface>
          </interfaces>
        </ifm>
      </data>
    </rpc-reply>

The following example shows how a NETCONF client cancels the data query.

  • RPC request

    <rpc message-id="103" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
      <get-next xmlns="http://www.huawei.com/netconf/capability/base/1.0" set-id="1"> 
        <discard/>
      </get-next>
    </rpc>
    
  • RPC reply

    <rpc-reply message-id="103" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> 
      <ok/>
    </rpc-reply>
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075344

Views: 21086

Downloads: 23

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