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 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).
(Optional) Enabling Proactive NETCONF Registration

(Optional) Enabling Proactive NETCONF Registration

Proactive NETCONF registration enables a device to send a NETCONF connection request to the NMS when the device goes online.

Context

If an NMS does not support automatic device discovery, it cannot manage devices in time. To address this problem, you can configure proactive NETCONF registration for a device to send a NETCONF connection request to the NMS when the device goes online so that the NMS can manage the device.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run netconf

    The NETCONF user interface view is displayed.

  3. Run callhome callhome-name

    A callhome template is created, and the callhome template view is displayed.

    By default, no callhome template is created.

  4. (Optional) Run reconnection interval interval

    An interval at which the device sends NETCONF connection requests to the NMS is configured.

    By default, the interval is 5s.

  5. Run endpoint endpoint-name

    A NETCONF connection instance is created, and the NETCONF connection instance view is displayed.

    By default, no NETCONF connection instance is created.

  6. Select one of the following commands based on the type of a source interface to be configured:

    • Run the peer-ip ipv4-address port port-number [ local-address source-ip | [ vpn-instance vpn-instance | public-net ] ] * command to configure the IPv4 address and TCP port number of the NMS with which the device is to establish a NETCONF connection and to configure the device source IPv4 address and VPN instance.
    • Run the peer-ip ipv6-address port port-number [ local-address source-ipv6 | [ vpn-instance vpn-instance | public-net ] ] * command to configure the IPv6 address and TCP port number of the NMS with which the device is to establish a NETCONF connection and to configure the device source IPv6 address and VPN instance.

  7. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075365

Views: 36308

Downloads: 123

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