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 V300R010C00SPC200, 300, and 500 Operation Guide 09

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).
Zero Touch Provisioning Introduction

Zero Touch Provisioning Introduction

This section describes the definition, functions, application restrictions, and key indicators of zero-touch provisioning.


Zero-touch provisioning provides a simple and reliable deployment solution to implement full lifecycle management of NEs.


After new switches and routers meeting zero-touch provisioning conditions are installed and powered on, they start the zero touch provisioning process to automatically load system files such as configuration files, software version packages, and patch files. The network administrator does not need to commission the switches and routers on site.

Making Required Files

After required files including configuration templates, software version packages, patch files, and license files are made, eSight can match required files with devices to implement topology plan-based or device ID-based deployment.

Figure 12-28 Making required files

Topology Plan-based Deployment

eSight allows users to draw and modify network topologies and matches and delivers required files to deploy unconfigured devices.

Figure 12-29 Topology planning
Figure 12-30 File matching
Figure 12-31 Topology comparison
Figure 12-32 Device deployment

Device ID-based Deployment

Users can create devices, match required files, and then perform deployment and activation operations to deploy unconfigured devices by the MAC address or ESN. S switches can be activated automatically or manually. CE switches and AR routers are activated automatically by default.

Figure 12-33 Creating devices
Figure 12-34 Matching required files
Figure 12-35 Deploying devices
Figure 12-36 Activating devices

Short Message-based Deployment

Users can create undeployed devices, match deployment files, and send short messages to implement short message-based deployment.

Figure 12-37 Creating undeployed devices
Figure 12-38 Matching deployment files
Figure 12-39 Sending short messages

Zero Touch Re-provisioning

Users can redeploy faulty devices in the physical topology using configuration files of faulty devices or ZTP templates.

Figure 12-40 Zero touch re-provisioning entrance
Figure 12-41 Zero touch re-provisioning configuration
Figure 12-42 Zero touch re-provisioning task

Application Restrictions

  • 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-12

Document ID: EDOC1100044378

Views: 72072

Downloads: 378

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