Feature Requirements |
Series |
Models |
|---|---|---|
The device supports only SSH as the bearer protocol of NETCONF. This means that you must configure SSH before using NETCONF for device management. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1. If a <hello> element sent from the peer contains extended capabilities, the Huawei device replies with a schema packet. 2. The exchange capability set is advertised to identify the mode of processing high-specification data. 3. The sync capability set is advertised to determine whether the packet returned by edit-configuration carries a flow ID. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When an AP is offline, forwarder query and maintenance operations cannot be performed. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When YANG packets are used to deliver the copy-config operation, if the delivered content contains YANG configuration that requires related commands to be run on a YANG-incapable node, the YANG configuration may fail to be cleared, causing the copy-config operation to fail. In this case, you can manually cancel the dependency between the commands and perform the copy-config operation again. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The database may be locked during schema patch installation. Therefore, full synchronization or database locking cannot be performed in this case. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When a device interworks with an NMS client that notifies only the base capability in compliance with the standard, the YANG mode is used for interworking. If the exchange capability is notified, the Huawei proprietary schema mode is used for interworking. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The size of a delivered RPC packet cannot be greater than 30 MB. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When a user performs a schema operation, performing schema patch operations causes the schema operation to fail. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In the case of NETCONF operation, if no service response is received within 32 seconds, a timeout occurs. If a response is received before the timeout occurs, the timer is reset. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
An end-to-end NETCONF operation must be completed within 60 minutes. Otherwise, a timeout occurs. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |