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


To have a better experience, please upgrade your IE browser.


eSight V300R009C00 Operation Guide 10

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


This section describes precautions on using the zero-touch provisioning function so that eSight can be used properly.

License Support

Basic functions and features are not controlled by licenses.

Component Dependency

The zero-configuration deployment depends on the Network Device Management Component.

Protocol Support

SNMP, FTP/SFTP, TR069, and HTTPS are required.

Device Support

For details, see the Specification List.

Version Support

For details, see the Specification List.

Application Scenario

Zero-configuration deployment.

Feature Limitation and Dependency

  • Topology Plan/Device ID Deployment
    • Ensure that the device to be deployed can obtain the IP address allocated by the temporary address pool of the DHCP server and can interconnect with the eSight server.
    • The configuration file supports only the standard format. For details, see the device configuration file format. Ensure that the device to be deployed is interconnected with the eSight server after the basic network configuration in the configuration file of the device is activated and the device is restarted.
    • When the topology plan deployment is used, it is recommended that the number of planned device nodes be less than 200. If the number of planned device nodes is greater than 200, the root device of the topology plan deployment receives a large number of protocol packets, which may lead to packet loss and affect topology plan deployment. For details about the processing method, see the guide at the device side.
  • Networking Restriction
    • Zero-touch deployment only supports tree-shaped network and does not support other network modes such as the ring network.
    • Link aggregation port on the upstream device of the device to be deployed: During the deployment, the configuration of the device to be deployed is empty. If a link aggregation port is configured on the upstream device (such as S127) of the device to be deployed, the link aggregation port is configured at one end but is not at the other end when the device is interconnected with the device to be deployed.

      This networking has problems such as loops and MAC address flapping. Therefore, only one member interface of the link aggregation group can be in the working state. Other member interfaces need to be manually disabled during deployment and then enabled after the deployment is complete.

  • Other Restriction
    • The configurations to be deployed must pass the verification on real devices and be piloted in a small scope. Then, zero-touch deployment can be performed at large scale.
    • Due to the limitation on the concurrent performance of eSight, you are advised to perform zero-touch deployment for a maximum of 100 devices at a time, preventing the configuration delivery from taking a long time.
Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 331641

Downloads: 660

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