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).
Operation Procedure (Topo Plan-based Provisioning)

Operation Procedure (Topo Plan-based Provisioning)

This section describes the operation procedure of topology plan-based provisioning of eSight, helping you quickly master topology plan deployment operations.

Table 12-33 Operation procedure of topology plan-based provisioning





Set protocol parameters on the device: SNMP and NetConf of the root device

If SNMP is used, the MIB view including ISO nodes must be configured. SNMPv2c read and write permissions are mandatory.


Add devices to eSight.

Select a proper device addition mode based on the site requirements.

For details about how to add devices to eSight, see Adding Devices to eSight.


Configure the root device as a DHCP server.

If the device to be deployed and DHCP server are on different network segments, you need to configure the DHCP relay agent in addition to the DHCP server.


Make device files.

Prepare configuration files and software packages in advance to facilitate quick deployment.


Create a deployment task.

Create a topology plan-based deployment task to add the root node and devices to be deployed.


Plan the topology based on onsite planning.

The hardware installation engineer prepares devices in advance. After planning the topology and matching files, the network administrator powers on the devices to start automatic zero touch provisioning.

Add devices to be deployed based on onsite planning to ensure topology consistency. Obtain the device interface type and number in advance and correctly configure them.


Match files for devices to be deployed.

Associate files with the devices to be deployed, facilitating file uploading during topology plan-based deployment.


Power the devices on after installation.

The hardware installation engineer installs the devices and connects them based on onsite planning and powers the devices on after confirming that the connections are correct.


Check consistency between actual topology and onsite planning.

The network administrator compares whether the actual topology on eSight is the same as onsite planning.


Select devices to be deployed and deploy them.

After you select devices to be deployed and deploy them through one click, the devices automatically upload matching files. Activate the devices. The devices then restart and upload new configuration files to complete topology plan-based deployment.

Configuring the Root Device as a DHCP Server

Before implementing ZTP, deploy the DHCP server and ensure that the device to be deployed can obtain an IP address from the DHCP server and the IP address of eSight so that the device can obtain files from eSight.

The following example configures the switch as the DHCP server. The DHCP server must support Option parameters. The basic configuration of the DHCP server is provided. To flexibly deploy DHCP, see the DHCP configuration of the corresponding device.

  1. Run the system-view command to enter the system view.
  2. Run the dhcp enable command to enable DHCP.
  3. Run the interface interface-type interface-number command to enter the interface view.
  4. (Optional) On an Ethernet interface, run the undo portswitch command to switch the interface to layer 3 mode.
  5. Run the dhcp select global command to configure the interface to use the global IP address pool.
  6. Run the quit command to return to the system view.
  7. Run the ip pool ip-pool-name command to create a global address pool and enter its view.
  8. Run the network ip-address [ mask { mask | mask-length } ] command to specify the range of IP addresses in the global address pool.
    • To prevent IP address conflicts, ensure that the configured IP address range does not include the IP addresses configured in the configuration files.
    • The DHCP server must have sufficient IP addresses to assign.
  9. Run the gateway-list ip-address &<1-8> command to set a gateway address for DHCP clients.
  10. Run the option 148 ascii ascii-string command to configure DHCP option fields.
    • The option 148 parameter must be specified first, indicating the Commander's IP address. After this parameter is specified, the clients implement EasyDeploy through the Commander.
    • The ascii-string parameter is set in the format of "ipaddr=ip-address;port=udp-port". For example, if the IP address and port number of the Commander are and 32175 respectively, the ascii-string parameter is expressed as ipaddr=;port=32175 .
  11. (Optional) Run the option 67 ascii ascii-string command to configure the Option 67 field of the DHCP server.

    The Option 67 field needs to be set during topology planning and deployment for CE devices.

    The format of ascii-string is ftp://admin/Changeme123@ In the format, admin and Changeme123 are the user name and password of the intermediate file server, is the IP address of the intermediate file server, and is the name of the preset intermediate file in the Python format.

Making Device Files

  1. Choose Resource > Network > Zero Touch Provisioning > Configuration File Making from the main menu.

  2. Make device files.
    • In the navigation tree on the left, choose Make Configuration Template and create the configuration file.

      For the commands that are not included in the predefined template, you can manually enter the commands and parameters to improve the configuration efficiency.

    • In the navigation tree on the left, choose Upload Device Software and check the device software.

      If required software is unavailable, Choose Resource > Network > Configuration > Device Software Management from the main menu and choose File Management from the navigation tree on the left to upload the corresponding files.

Creating a Deployment Task

  1. Choose Resource > Network > Zero Touch Provisioning > Topo Plan-based Provisioning from the main menu.

  2. Right-click a blank area on the page and select Create Task.

Planning the Topology Based on Onsite Planning

  1. Choose Resource > Network > Zero Touch Provisioning > Topo Plan-based Provisioning from the main menu.

  2. Double-click a deployment task to add the root node.
  3. Click the Plan Topology tab and add devices to be deployed layer by layer based on the topology planning.

    If CE switches on the live network form a stack, you also need to set them in a stack during topology plan-based provisioning. Select the CE switches, right-click them and choose Set Stack, and enter planned stack parameters in the displayed dialog box.

Matching Files for Devices to Be Deployed

  1. Choose Resource > Network > Zero Touch Provisioning > Topo Plan-based Provisioning from the main menu.

  2. Double-click the deployment task and click the Match File tab.
  3. Select devices to be deployed, right-click them, and choose Match Provisioning File from the shortcut menu.

Checking Consistency Between Actual Topology and Onsite Planning

  1. Choose Resource > Network > Zero Touch Provisioning > Topo Plan-based Provisioning from the main menu.

  2. Double-click the deployment task and click the Compare Topologies tab.

Selecting Devices to Be Deployed and Deploy Them

  1. Choose Resource > Network > Zero Touch Provisioning > Topo Plan-based Provisioning from the main menu.

  2. Double-click the deployment task, click the Start Provisioning tab, select devices to be deployed, and deploy them.

    The deployment status is described as follows:

    • To be downloaded: eSight is waiting for a device to apply for configuration file downloading.
    • Downloading Config File: A device is downloading the configuration file.
    • To be activated: A device has downloaded the configuration file and is waiting for eSight to deliver the activation command.

      For S-series switches, eSight automatically delivers the activation instruction if Auto Active is selected during deployment task creation. If Auto Active is not selected, right-click the device to be deployed and choose Active from the shortcut menu to deliver the activation instruction to the device.

      CE-series switches are activated by default.

    • To be restarted: After eSight delivers the activation command, a device automatically restarts and eSight waits for the device to report a registration message after the restart.
    • Provisioning Succeed: A device restarts successfully and is automatically added to eSight.
    • Failure: The deployment fails. The failure cause must be located for troubleshooting. Common deployment failure causes are as follows:
      • The IP address configured in the configuration template cannot be used for communication with eSight.
      • The SNMP template specified in the configuration template is modified.
      • The device to be deployed already exists on eSight and cannot be added repeatedly.

        The number of NEs connected to eSight reaches the maximum for management and the license capacity needs to be expanded.

Updated: 2019-09-12

Document ID: EDOC1100044378

Views: 79959

Downloads: 399

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