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.


CLI-based Configuration Guide - Basic Configuration

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document provides the basic concepts, configuration procedures, and configuration examples in different application scenarios of the Basic configuration supported by the device.

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).
Understanding SMS-based Deployment

Understanding SMS-based Deployment

This section describes how SMS-based deployment is implemented.


Before SMS-based deployment, enterprise network administrators save the configuration file of devices to a specified file server. Devices need to be installed and powered on before they can receive and parse deployment short messages. According to the short messages, devices can obtain parameter information to activate 3G/LTE links, and connect to the NMS or the file server to obtain and load a configuration file for zero touch deployment.

When eSight is deployed in the enterprise headquarters to manage devices, enterprise network administrators send deployment short messages to devices through eSight after obtaining device information.

Deployment short messages and parameter information are transmitted over a carrier network. All the transmitted information will be encrypted using Advanced Encryption Standard (AES) 128 or Rivest-Shamir-Adleman (RSA) algorithm to ensure data security.

SMS-based Deployment Process

Figure 5-1 illustrates the SMS-based deployment process when eSight is available.

Figure 5-1  Device running flowchart during SMS-based deployment (when eSight is available)
The device running process involves the following phases:
  1. Enterprise network administrators save configuration files in the specified directory of a file server.
  2. Enterprise network administrators obtain device information and SIM card information and then send encrypted deployment short messages through NMS.
  3. Parse deployment short messages.

    Devices receive and parse deployment short messages to obtain parameter information. The short messages carry the following information:

    1. SIM card information: includes International Mobile Subscriber Identity (IMSI) and Access Point Name (APN) activation information (including the APN, user name, and password).
    2. NMS parameter information: includes the eSight server address.

    Deployment short messages are encrypted using AES128 algorithm to ensure user information security.

  4. Activate 3G/LTE links.

    Devices dial up to the enterprise network according to the APN activation information obtained from the parsed deployment short messages. If the dial-up is successful, they connect to the enterprise network over a 3G/LTE network, and obtain IP addresses after passing authentication.

  5. Obtain and load a configuration file.

    1. Devices connect to eSight and send deployment registration requests.

      After devices obtain IP addresses, they connect to eSight and send deployment registration requests to it. eSight authenticates the deployment registration requests. After successful authentication, eSight returns file server parameter information, including the file server IP address, user name, and password.

      The file server parameter information is encrypted using RSA algorithm to ensure data security.

    2. Devices connect to the file server to obtain and load a configuration file.

      After devices obtain file server information, they connect to the file server through SFTP, and then download and load the specified configuration file. Configurations take effect on the devices after these devices restart.

      Devices will send status notifications to eSight regardless of whether they download a configuration file successfully. If devices cannot download the configuration file, they send the failure reason to eSight for fault location.

  6. Register.

    Devices connect to eSight again for registration after configurations take effect. After devices have registered, enterprise network administrators can deploy other services on the devices through eSight, including upgrading the devices and load patches on the devices.

Updated: 2019-11-21

Document ID: EDOC1100034066

Views: 98902

Downloads: 517

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next