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).
Sync

Sync

The sync capability indicates that the device allows the NMS to perform data synchronization.

The NETCONF client sends an RPC request to the NETCONF server to synchronize data from the server to the destination directory.

Capability ID

<capability>http://www.huawei.com/netconf/capability/sync/1.0</capability>
<capability>http://www.huawei.com/netconf/capability/sync/1.1</capability>
<capability>http://www.huawei.com/netconf/capability/sync/1.2</capability>
<capability>http://www.huawei.com/netconf/capability/sync/1.3</capability>

The synchronization capability supports the following operations:

  • <sync-full>: synchronizes all data from the device to the destination folder.

    After a NETCONF server receives an <rpc> element containing a <sync-full> element, the NETCONF server performs a syntax check on the element. If the element fails the syntax check, the NETCONF server returns an <rpc-reply> element containing an <rpc-error> element. If the element passes the syntax check, the NETCONF agent encapsulates the required data into XML files (one XML file for one feature) and compresses all the XML files into a .zip file. Then, the NETCONF agent transfers the .zip file to the NETCONF manager using a file transfer protocol (FTP or SFTP). Meanwhile, the NETCONF agent sends an <rpc-reply> element containing an <ok> element to the NETCONF manager.

    Only a device with the synchronization capability supports the <sync-full> operation.

    If the <sync-full> operation is successful, the NETCONF server sends an <rpc-reply> element containing an <ok> element. Otherwise, the NETCONF server sends an <rpc-reply> element containing an <rpc-error> element.

    Example of a full data synchronization operation: The NETCONF server uses FTP to transfer AAA module configurations in the data to be synchronized to the home directory of user root ( with the password being root ) on a server with the IP address 10.1.1.1. The data is saved as a file named Multi_App_sync_full.zip.

    • RPC request:

      <?xml version="1.0" encoding="utf-8"?>
      <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
        <sync-full xmlns="http://www.huawei.com/netconf/capability/base/1.0">
          <target>
            <user-name>root</user-name>
            <password>root</password>
            <target-addr>10.1.1.1</target-addr>
            <path>/home</path>
          </target>
          <transfer-protocol>ftp</transfer-protocol>
          <transfer-method>auto</transfer-method>
          <filename-prefix>Multi_App_sync_full</filename-prefix>
          <app-err-operation>stop-on-error</app-err-operation>
          <filter>
            <aaa xmlns="http://www.huawei.com/netconf/vrp" content-version="1.0" format-version="1.0"/>
          </filter>
        </sync-full>
      </rpc>
      
    • RPC reply:

      The RPC reply message carries a full data synchronization identifier assigned by the NETCONF server, which is returned using the <sync-full-id> parameter.

      <rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
        <nc-sync:sync-full-id>185</nc-sync:sync-full-id>
      </rpc-reply>
  • <sync-increment>: incrementally synchronizes data from a device to the destination folder.

    Only a device with the synchronization capability supports the <sync-increment> operation.

    If the <sync-increment> operation succeeds, the NETCONF server replies with an <rpc-reply> packet that contains the <data> parameter. The <data> parameter contains the data changed between two configuration committing operations. If the <sync-increment> operation fails, the NETCONF server replies with an <rpc-reply> packet that contains the <rpc-error> parameter.

    Example of an incremental data synchronization operation that synchronizes IFM module configurations between change points 6 and 7:

    • RPC request:

      <rpc message-id="102" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> 
       <sync-increment xmlns=" http://www.huawei.com/netconf/capability/base/1.0"> 
          <target> 
            <flow-id>7</flow-id> 
          </target> 
          <source> 
            <flow-id>6</flow-id> 
          </source> 
          <filter type="subtree"> 
            <ifm xmlns="http://www.huawei.com/netconf/vrp" content-version="1.0" format-version="1.0">
          </filter> 
       </sync-increment> 
      </rpc>
    • RPC reply:

      <rpc-reply message-id="102" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
       <data> 
        <ifm> 
         <interfaces> 
          <interface difference="create"> 
           <interfaceName>ethernet 1/1/1.1</interfaceName> 
           <mtu>15000</mtu> 
           <adminStatus>down</adminStatus> 
          </interface> 
          <interface difference="delete"> 
           <interfaceName>ethernet 1/1/2.1</interfaceName> 
          </interface> 
          <interface difference="modify"> 
           <interfaceName>ethernet 1/1/3</interfaceName> 
           <mtu>15000</mtu> 
           <adminStatus>up</adminStatus> 
          </interface> 
          <interface difference="modify"> 
           <interfaceName>ethernet 1/1/4</interfaceName> 
            <ifAm4s> 
             <ifAm4 difference="create"> 
              <ipAddress>10.164.11.10</ipAddress > 
              <netMask>255.255.255.0</netMask> 
              <addressType></addressType> 
             </ifAm4> 
           </ifAm4s> 
          </interface> 
         </interfaces>
        </ifm> 
       </data> 
      </rpc-reply>
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075344

Views: 20345

Downloads: 22

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