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.

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 3-86 Making required files

Topology Plan-based Provisioning

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

Only V300R010C00CP5030 and earlier versions support topology plan-based provisioning.

Figure 3-87 Topology planning

Figure 3-88 File matching

Figure 3-89 Topology comparison

Figure 3-90 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 3-91 Creating devices

Figure 3-92 Matching required files

Figure 3-93 Deploying devices

Figure 3-94 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 3-95 Creating undeployed devices

Figure 3-96 Matching deployment files

Figure 3-97 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.

Only V300R010C00CP5030 and earlier versions support zero touch re-provisioning.

Figure 3-98 Zero touch re-provisioning entrance

Figure 3-99 Zero touch re-provisioning configuration

Figure 3-100 Zero touch re-provisioning task

During zero-touch provisioning, the interaction process between the device to be deployed, DHCP address pool, and eSight is as follows:

1. After the device to be deployed is powered on and enters the zero-touch provisioning state, the device requests a temporary IP address from the DHCP server.

2. The DHCP server assigns a temporary IP address to the device to be deployed and specifies the address for the device to communicate with eSight.

3. The device sends a request to eSight to obtain information required for deployment. The request carries information such as the IP address, MAC address, ESN, model, and type of the device.

4. eSight sends a deployment interaction packet to the device. The packet contains parameters such as the SFTP server address, user name, password, and download file.

5. The device obtains the relevant files from eSight through SFTP and reports the deployment status.

6. After the files are downloaded successfully, the device restarts for the files to take effect. (S switches need to be restarted after eSight sends the activation packet.)

7. After being restarted, the device reports registration information. After receiving the information, eSight adds the device. (CE switches do not report registration information and eSight polls the device status.)

None