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

CLI-based Configuration Guide - Basic Configuration

AR500, AR510, AR531, AR550, AR1500, and AR2500 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).
Configuring SMS-based Deployment

Configuring SMS-based Deployment

This section describes the process of configuring SMS-based deployment through eSight.

Pre-configuration Tasks

  • Onsite installation personnel install, power on, and perform self-check on devices.
  • Enterprise network administrators obtain device information and SIM card information.
  • Devices support 3G/LTE functions and have SIM cards installed. Ensure that areas where devices reside have 3G/LTE signals.
  • eSight can send messages normallly.

Procedure

  1. Create an SNMP template.

    Log in to eSight, and choose Resource > Protocol Template > SNMP Template. The SNMP Template page is displayed. Click Create to create an SNMP template, as shown in Figure 5-3. Configure the SNMP template according to the SNMP version. You are advised to configure Template Name and Parameter Type before configuring other parameters, as shown in Table 5-2. Click OK to save the configuration.
    NOTE:
    • SMS-based deployment requires high security, so SNMPv3 is recommended.

    • Configure parameters in the SNMP template according to SNMP information on devices. When using SNMPv3, you are advised to set Privacy protocol to AES_128 to improve security because authentication protocols HMAC_SHA and HMAC_MD5 cannot ensure high security.

    Figure 5-3  Creating an SNMP template

    Table 5-2  Parameters
    Parameter Description

    Parameter Type

    Specifies an SNMP version:
    • V1: SNMPv1
    • V2c: SNMPv2c
    • V3: SNMPv3, which applies to scenarios requiring high security

    Authentication protocol

    Specifies the protocol used to authenticate messages, which can be HMAC_SHA or HMAC_MD5.

    NOTE:
    • HMAC_MD5 may have information security risks. HMAC_SHA is more secure and so is recommended.

    • This parameter can be configured only when Parameter Type is set to SNMPv3.

    Authentication password

    Specifies the authentication password.

    NOTE:
    • When using HMAC_MD5 or HMAC_SHA, you need to set an authentication password.

    • This parameter can be configured only when Parameter Type is set to SNMPv3.

    Privacy protocol

    Specifies the encryption protocol used in data encapsulation, which can be CBC_DES or AES_128.

    NOTE:
    • CBC_DES may have information security risks. AES_128 is more secure and so is recommended.

    • This parameter can be configured only when Parameter Type is set to SNMPv3.

    Encryption password

    Specifies the encryption password used in data encapsulation.

    NOTE:
    • This parameter needs to be configured when Privacy protocol is CBC_DES or AES_128.

    • This parameter can be configured only when Parameter Type is set to SNMPv3.

    User name

    Specifies the login user name.

    NOTE:

    This parameter can be configured only when Parameter Type is set to SNMPv3.

    Context

    Specifies the context engine name. This parameter must be empty by default. If it needs to be modified, ensure that it is consistent with that on devices.

    NOTE:

    This parameter can be configured only when Parameter Type is set to SNMPv3.

    Engine ID

    Specifies the entity engine ID. To view the context engine ID on a device, run the display snmp-agent local-engineid command on the device.

    Port

    Specifies the SNMP port.

    Timeout period

    Specifies the time during which eSight waits for a response to an operation request.

    Retries

    Specifies the maximum number of times eSight resends an operation request upon timeout events. If eSight does not receive any response after sending the request the maximum number of times, eSight considers that this operation fails.

  2. Create a configuration template.
    1. Log in to eSight, and choose Configuration > Zero Touch Provisioning > Configuration File Making. The Configuration File Making page is displayed, as shown in Figure 5-4.

      Figure 5-4  Making a version file

    2. Choose Make Configuration Template and click Create to set parameters in the configuration template, as shown in Figure 5-5. Select Router from the Device Type drop-down list box, and click to select the device type, as shown in Figure 5-13. Set parameters in the configuration template according to service requirements, as shown in Table 5-3. Click Next to save the configuration, as shown in Figure 5-6.

      Figure 5-5  Making a configuration template (1)

      Table 5-3  Parameters
      Parameter Description

      Template Name

      Specifies the configuration template name.

      Description

      Specifies a description for the configuration template.

      Device Type

      Specifies the type of devices to be deployed.

      SNMP Protocol Template

      Specifies the SNMP template.

      SNMP Mib View Configuration

      Indicates SNMP MIB view parameter information, including the type, SNMP view name, and OID/MIB subtree.

      SNMP V3 Parameters

      Indicates SNMPv3 parameter information, including group name, read view, write view, and notify view.

      SNMP Trap Configuration

      Indicates SNMP trap configuration. If you click ON, the SNMP trap function is enabled. Parameters include:
      • Destination host IP address
      • Destination host UDP port number
      • User security name
      Figure 5-6  Making a configuration template (2)

    3. Click OK to save the made configuration template.
  3. Create SIM card information and short messages.
    1. Choose Configuration > Zero Touch Provisioning > Short Message-based Provisioning > Manage SIM Card. The Manage SIM Card page is displayed.

      Click Batch Import to import SIM card information in a batch, as shown in Figure 5-7. Click Template.xls to download a template, and then enter multiple mobile phone numbers and IMSIs in the template. Click to select the template file to be uploaded. Click to upload the template file. After the template file has been uploaded, view the import results under Detail. Click Create to finish batch import.
      Figure 5-7  Batch import

    2. Choose Short Message-based Provisioning > Manage Short Message. The Manage Short Message page is displayed. Click Create and configure parameters in the displayed dialog box, as shown in Table 5-4. Click OK to save the configuration, as shown in Figure 5-8.

      Figure 5-8  Creating short messages

      Table 5-4  Parameters
      Parameter Description

      Message name

      Specifies the short message name.

      APN name

      Specifies the APN used to identify the GPRS service type.

      NOTE:
      • APNs are provided by carriers.
      • For example, APNs of China Mobile, China Telecom, and China Unicom are CMNET, CTNET, and 3GNET respectively.

      User name

      Specifies the user name for 3G/LTE dial-up.

      NOTE:
      User names can be obtained from carriers.

      Password

      Specifies the password for 3G/LTE dial-up.

      NOTE:
      Passwords can be obtained from carriers.

      Service IP (eSight Server)

      Specifies the eSight server IP address.

      Port number (eSight Server)

      Specifies the eSight server port number.

      Server IP (FTP Server)

      Specifies the file server IP address.

      Port number (FTP Server)

      Specifies the filer server port number.

  4. Configure SMS-based deployment.
    1. Choose Configuration > Zero Touch Provisioning > Short Message Deployment. The Short Message Deployment page is displayed, as shown in Figure 5-9.

      Figure 5-9  Short message deployment (1)

    2. Choose Short Message Deployment > Create. The short message creation page is displayed, as shown in Figure 5-10.

      Figure 5-10  Short message deployment (2)

    3. Click Create Device and select Single Create from the drop-down list. The Single Create page is displayed, as shown in Figure 5-11.

      Figure 5-11  Single create

      (Optional) Click Batch Import to import short message deployment information in a batch. Click Template.xls to download a template, and then enter short message deployment information in the template. Click to select the template file to be uploaded. Click to upload the template file. After the template file has been uploaded, view the import results under Detail. Click Create to finish batch import, as shown in Figure 5-12.
      Figure 5-12  Batch import

    4. Enter information such as the device name and SIM card on the Single Create page. Click behind the Device Type text box. The Select Device Type page is displayed. Select the device types to be deployed, as shown in Figure 5-13. Click OK to save the configuration.

      Figure 5-13  Select device type

    5. Click behind the Mobile number text box. The Select mobile number page is displayed. Select the imported mobile phone numbers, and click OK to save the configuration, as shown in Figure 5-14.

      Figure 5-14  Select mobile number

    6. Click behind the Message name text box. The Select short message page is displayed. Select the created short messages, and click OK to save the configuration, as shown in Figure 5-15.

      Figure 5-15  Select short message

    7. Click OK to save the configuration, and then the created short messages will be displayed on the Short Message Deployment page, as shown in Figure 5-16. Select the devices to be deployed and click Match Provisioning File to select the created configuration template, as shown in Figure 5-17. Click OK to save the configuration.

      Figure 5-16  Created deployment information

      Figure 5-17  Matching deployment files

    8. After the configuration has been saved, information about the configuration template will be displayed on the Short Message Deployment page, as shown in Figure 5-18. Click OK to finish SMS-based deployment configuration.

      Figure 5-18  Short message deployment

    9. Select the SMS-based deployment task and click Send Message for SMS-based deployment, as shown in Figure 5-19.

      Figure 5-19  Sending messages

  5. (Option) Configure a mobile phone number whitelist.

    After devices are deployed successfully, you can perform the following operations to allow modifying device configurations according to short messages sent from some mobile phone numbers:

    1. Run the system-view command to enter the system view.
    2. Run the sms config caller tel-number command to configure a mobile phone number whitelist.

      By default, no mobile phone number whitelist is configured.

      NOTE:

      This step is recommended if you want to prevent device configurations from being modified according to short messages sent from unauthorized phone numbers. Subsequently, device configurations can be modified only according to short messages sent from phone numbers in the configured mobile phone number whitelist.

  6. (Optional) Run the undo sms config autodeploy enable command to disable SMS-based deployment.

    By default, SMS-based deployment is enabled.

    NOTE:

    After devices are deployed successfully, you are advised to disable SMS-based deployment to prevent unauthorized users from forging deployment short messages to modify device configurations.

Translation
Download
Updated: 2019-05-20

Document ID: EDOC1100034225

Views: 44942

Downloads: 100

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