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).
Understanding Auto-Start

Understanding Auto-Start

This section describes how Auto-Start is implemented.

Auto-Start Principles

Before using Auto-Start for site deployment, make an intermediate file and save it to a specified directory on the file server. Save version files to be loaded to the specified directory on the file server. After configuring an IP address and file server parameters on a device, enable Auto-Start. The device then automatically downloads and loads version files based on the intermediate file after the start.

The intermediate file contains the mapping between the device's MAC address + equipment serial number (ESN) and the system software, version, patch file, and configuration file. A device uses the file server's IP address, a user name, and a password to set up a connection with the file server, downloads and parses the intermediate file. After successfully parsing the intermediate file, the device downloads corresponding version files from the file server and loads the files. For details about how to make the intermediate file, see Making the Intermediate File.

Site deployment files consist of mandatory and optional files.
  • Mandatory file
    • Intermediate file: The file name must be arstart.ini.
  • Optional file
    • System software: The file name extension is .cc or .zip.
    • Patch file: The file name extension is .pat.
    • Configuration file: The file name extension is .cfg or .zip.
You can select at least one optional file for site deployment using Auto-Start.

Site Deployment Process Using Auto-Start

Figure 3-2 shows the site deployment process using Auto-Start.

Figure 3-2  Site deployment process using Auto-Start
  1. Make an intermediate file.
  2. Save the intermediate file and version files to a specified directory on the file server.
  3. Configure the device's IP address and file server parameters.
  4. Enable Auto-Start.
  5. The device starts the Auto-Start process.
  6. The site deployment process using Auto-Start ends.

Auto-Start Process on a Device

Figure 3-3 shows the Auto-Start process on a device.

Figure 3-3  Auto-Start process on a device
  1. The device connects to the file server to obtain and parse the intermediate file.
    • If the device successfully parses the file, go to step 2.
    • If the device fails to obtain or parse the file, the site deployment fails.
  2. The device obtains site deployment files from the file server and saves the files to a specified storage medium according to description in the intermediate file.
    • If the device successfully obtains the files, go to step 3.
    • If the device fails to obtain the files, the site deployment fails.
  3. The device specifies the system software, configuration file, and patch file as next startup files.
  4. The device restarts.
Translation
Download
Updated: 2019-05-20

Document ID: EDOC1100034225

Views: 44846

Downloads: 100

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