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

Reminder

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

upgrade

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).
Operation Procedure (Device ID-based Provisioning)

Operation Procedure (Device ID-based Provisioning)

This section describes the operation procedure of device ID-based provisioning of eSight, helping you quickly master device ID-based provisioning operations.

Table 12-35 Operation procedure of device ID-based provisioning

Step

Operation

Description

1

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

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

    For details about how to configure the SNMP protocol on the device, see Configuring the SNMP Protocol on Devices.

  • The Telnet privilege mode on eSight must be the same as that on the device.

    For details about how to set Telnet parameters on the device, see Setting Telnet Parameters on Devices.

2

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.

3

Make device files.

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

4

Record MAC addresses and ESNs of the devices.

The hardware installation engineer collects MAC addresses and ESNs of the devices, sends the information to the network administrator, and powers the devices on.

5

Create a device ID-based deployment task.

The network administrator enters received MAC addresses and ESNs in an Excel template and uploads the template to eSight.

Associate files with the devices to be deployed, facilitating file uploading during device ID-based provisioning.

6

Trigger deployment and activate devices.

After device deployment is triggered, the devices automatically upload matching files. Activate the devices. The devices then restart and upload new configuration files to complete device ID-based provisioning.

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 10.10.10.1 and 32175 respectively, the ascii-string parameter is expressed as ipaddr=10.10.10.1;port=32175 .
  11. (Optional) Run the option 43 sub-option 1 ascii ascii-string command to configure DHCP Option fields.

    AR routers can use these Option fields to implement device ID-based provisioning through DHCP.

    The ascii-string parameter is in the format of "URL=https://ip-address:udp-port/eSightZTP/services/acs". For example, if the Commander IP address is 10.10.10.1 and port number is 32176, ascii-string represents URL=https://10.10.10.1:32176/eSightZTP/services/acs.

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 Device ID-based Deployment Task

  1. Choose Resource > Network > Zero Touch Provisioning > Device ID-based Provisioning from the main menu.

  2. Click Create to import devices in batches.
  3. Select the devices and click Match Provisioning File to associate devices with provisioning files.

Triggering Deployment and Activating Devices

  1. Choose Resource > Network > Zero Touch Provisioning > Device ID-based Provisioning from the main menu.

  2. Select a deployment task and click Start.
  3. In the dialog box that is displayed, select I have understood the consequence of the operation and confirm to perform the operation. and click OK.
  4. After the deployment is complete, click Active.

    The devices then restart and upload new configuration files to complete device ID-based provisioning.

Translation
Download
Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 311249

Downloads: 635

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