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).
Licensing Requirements and Limitations for NETCONF

Licensing Requirements and Limitations for NETCONF

Involved Network Elements

The switch needs to work with a network management system.

Licensing Requirements

NETCONF is a basic feature of a switch and is not under license control.

Version Requirements

Table 3-13 Products and minimum version supporting NETCONF

Product Model

Minimum Version Required

CE12804/CE12808/CE12812

V100R001C00

CE12816

V100R003C00

CE12804S/CE12808S

V100R005C00

CE12800E

V200R002C50

Feature Limitations

  • The device can use only the SSH protocol to carry the NETCONF protocol. Before configuring the NETCONF protocol to manage a device, configure the SSH protocol first.

  • In V200R002C50 and V200R003C00, you can run the snetconf [ ipv4 | ipv6 ] server enable or protocol inbound ssh [ ipv4 | ipv6 ] port 830 command to enable the NETCONF function. If the current version is downgraded to V200R001C00 or an earlier version, this configuration will be lost, so you need to run the snetconf server enable or protocol inbound ssh port 830 command again.

  • In V200R005C00, you can run the snetconf ipv4 server enable or protocol inbound ssh ipv4 port 830 command to enable the IPv4 NETCONF function, or run the snetconf ipv6 server enable or protocol inbound ssh ipv6 port 830 command to enable the IPv6 NETCONF function (IPv4 NETCONF and IPv6 NETCONF functions are not enabled simultaneously). If the current version is downgraded to V200R001C00 or an earlier version, this configuration will be lost, so you need to run the snetconf server enable or protocol inbound ssh port 830 command again.

NETCONF Schema

  • Upgrade from V200R001C00 or an earlier version to V200R002C50:

    It is recommended that you load the patch of V200R002SPH011 after the upgrade. In this case, the Hello message sent from the NETCONF client needs to carry the extended capabilities (not all preview, compare, and rollback capabilities). Otherwise, the NETCONF schema capability is unavailable. If you do not upload the patch of V200R002SPH011 after the upgrade, the Hello message sent by the NETCONF client needs to carry the exchange capabilities. Otherwise, the NETCONF schema capability is unavailable.

  • Upgrade from V200R001C00 or an earlier version to V200R003C00:

    After the upgrade, the Hello message sent from the NETCONF client needs to carry the extended capabilities (not all preview, compare, and rollback capabilities). Otherwise, the NETCONF schema capability is unavailable.

NETCONF YANG

Upgrade from V200R002C50 to V200R003C00:

After the upgrade, the Hello message sent from the NETCONF client does not carry the extended capabilities. Otherwise, the YANG capability after the upgrade is unavailable.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075344

Views: 28510

Downloads: 29

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