Licensing Requirements and Limitations for NETCONF

Involved Network Elements

Third-party NMSs that support the NETCONF over SSH mode or Huawei iMaster NCE-Campus

Licensing Requirements

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

Feature Support in V200R019C10

NETCONF Mode	Product Model
NETCONF over SSH Callhome	S5720-EI, S5720-HI, S5720I-SI, S5720-LI, S5735-L, S5735S-L, S5735S-L-M, S5720S-LI, S5720S-SI, S5720-SI, S5735-S, S5735S-S, S5735-S-I, S5730-HI, S5730-SI, S5730S-EI, S5731-H, S5731S-H, S5732-H, S5731-S, S5731S-S, S6730-S, S6730S-S, S6720-EI, S6720-HI, S6720S-EI, S6720S-LI, S6720-LI, S6730-H, S6730S-H, S6720S-SI, and S6720-SI
NETCONF over SSH	All models

For details about software mappings, use the Hardware Query Tool.

Feature Limitations

Precautions related to iMaster NCE-Campus

In V200R012C00SPC600, a stack of S5720-LI or S5720-SI switches can register with iMaster NCE-Campus. In V200R013C00, a stack of switches supporting cloud-based management can register with iMaster NCE-Campus. In V200R019C00 and later versions, a stack of switches supporting the NETCONF over SSH Callhome mode can register with iMaster NCE-Campus.
For the switch models that do not support RTC, if the system time of a NETCONF-enabled switch is not within the PKI certificate validity period, the system time is automatically set to the start time of the PKI certificate validity period. In this way, the switch can register with iMaster NCE-Campus successfully. After the registration is complete, iMaster NCE-Campus changes the device system time to the correct time. For details about the switches that do not support RTC, see "Licensing Requirements and Limitations for NTP".
After NETCONF is enabled on a switch, the management interface of the switch automatically generates the management IP address 192.168.1.253/24. If the DHCP server allocates an IP address on the 192.168.1.0/24 network segment to a switch running a version earlier than V200R019C10, the switch cannot register with iMaster NCE-Campus for authentication. In V200R019C10 and later versions, a switch deletes the IP address automatically generated by the management interface and uses the IP address allocated by the DHCP server to register with iMaster NCE-Campus for authentication.
After a switch has NETCONF enabled, in versions earlier than V200R011C10, the management IP address of the switch can only be dynamically assigned by a DHCP server. In V200R011C10 and later versions, the management IP address of the switch can either be dynamically assigned by a DHCP server or use the static IP address of the VLANIF interface used to communicate with the DHCP server. If the switch is configured with a static IP address, you must configure the iMaster NCE-Campus IP address on the switch using a command. Otherwise, the switch cannot register with iMaster NCE-Campus.

Precautions for NETCONF-enabled switches

After a switch has NETCONF enabled, a virtual management interface Meth0/0/2 is automatically generated for iMaster NCE-Campus to locate faults on the switch. This interface has a fixed IP address configured, which is 169.254.2.1/30. In versions earlier than V200R011C10, this fixed IP address is 192.168.2.1/30. In V200R011C10 and later versions, this fixed IP address is 169.254.2.1/30. After a switch is upgraded to V200R011C10 or later, this fixed IP address becomes 169.254.2.1/30.

The following message is displayed when you attempt to access the virtual management network interface of a NETCONF-enabled switch:
```
Error: This command cannot be executed in netconf mode.
```
The following message is displayed when you attempt to access the virtual management network interface of a NETCONF-disabled switch:
```
Error: This interface is used only by the cloud management platform to diagnose device faults.
```
A NETCONF-enabled switch that runs V200R012C00 or a later version supports PnP VLAN auto-negotiation to implement plug and play in the Huawei CloudCampus Solution.
After NETCONF is enabled, the trust dscp configuration is automatically generated on all service interfaces.
For security purposes, in V200R019C00 and later versions, a static ARP entry will be automatically generated after the switch goes online through a service interface. The IP address and MAC address in this ARP entry are those of an upstream gateway. This ARP entry cannot be manually modified or deleted, and can only be automatically updated or deleted based on the changes of the upstream gateway.
If an error occurs in the NETCONF service process of the switch, detailed error information of the process will be saved in the flash:/core_dump directory.
The switch is disconnected from and then reconnected to iMaster NCE-Campus during patch activation if the switch needs to have patches installed and the patch file contains the NETCONF-related process patch of the .bin type.
To ensure that the configurations recorded by the NMS (for example, iMaster NCE-Campus) are consistent with those in the configuration file of a switch, do not specify a new configuration file for the switch, for example, using the BootLoad menu to specify a new configuration file. Otherwise, the configurations in the existing configuration file of the switch may be lost.
When the delete-config operation is performed on the NMS to clear configurations in a NETCONF database, the switch automatically runs the reset saved-configuration command to clear the next startup configuration file and cancel the configuration file used for next startup.
After NETCONF is enabled, Eth-Trunk 0 is exclusively used by the PnP module. You are advised to use Eth-Trunks other than Eth-Trunk 0 for other services; otherwise, functions of the PnP module may be affected.
On a NETCONF-enabled switch running V200R019C00 or an earlier version, VCMP and LNP cannot be configured. On a NETCONF-enabled switch running a version later than V200R019C00, LNP cannot be configured, and VCMP also cannot be configured if the management-vlan or callhome command has been run.

Table 1 describes the function configuration restrictions on a NETCONF-enabled switch.

**Table 1** Function configuration restrictions
Category	Switch Processing
Functions that can be configured only using NETCONF on the NMS, but cannot be configured using commands on the switch	In versions earlier than V200R013, the following message is displayed when you configure these functions using commands on the switch: Error: This command cannot be executed in netconf status.
	In V200R013 and later versions, you can configure these functions using NETCONF on the NMS or by running commands on the switch.
Functions that can be configured using NETCONF on the NMS or by running commands on the switch	When you configure these functions using commands on the switch, a warning message is displayed. Continue the configuration after confirming that no conflict will occur. Versions earlier than V200R019C00: Warning: This command may cause confliction in netconf status. Continue? [Y/N]: V200R019C00 and later versions: Warning: This command may cause a configuration conflict in NETCONF mode. Continue? [Y/N]:
Functions that can be configured using NETCONF or SNMP on the NMS	No warning message will be displayed. Ensure that no conflict will occur before configuring these functions.