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

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).
Working Process of Auto-Config

Working Process of Auto-Config

Figure 2-2 shows the Auto-Config working process.

Figure 2-2  Basic process of Auto-Config
The Auto-Config process involves three phases:
  • Parse the Option field in the DHCP Reply packet.

    1. Obtain information about the IP address and configuration of the file server.

      1. The device automatically enables the DHCP client function on uplink Ethernet interfaces in Up state and broadcasts DHCP Request packets (the IP address pool, Option parameters, and gateway have been configured on the DHCP server).
      2. The DHCP server sends DHCP Reply packets to the device. These packets contain information about IP addresses of the device to be configured and the FTP/TFTP/SFTP server, FTP/SFTP user name, password, and default gateway.

        If no DHCP Reply packet is received or the received DHCP Reply packet is invalid, a DHCP Request packet is sent every 5 minutes. After 24 hours, a DHCP Request packet is sent every one hour.

    2. Parse Option parameters.

      1. If the received DHCP Reply packet contains Option 43, Auto-Configuration server (ACS) needs to be configured. After ACS configuration is complete, the device is configured using the Auto-Configuration server.

        If the DHCP server assigns ACS configuration to devices that needs to be configured, remote deployment of devices is realized through the Auto-Configuration server (for details about Auto-Config implementation through ACS, see CWMP) not the Auto-Config process. For details about CWMP, see "CWMP" in Feature Description-Network Management.

      2. If the received DHCP Reply packet does not contain Option 67, the intermediate file is required. Then the device downloads the intermediate file from the FTP/TFTP/SFTP server and obtains information about version files that need to be downloaded from the intermediate file. The process of obtaining files is started. If the received DHCP Reply packet contains Option 67, the process of obtaining version files is started directly.

  • Obtain version files.

    1. (Optional) Download the system software.

      1. Obtain the system software name and version ID from the intermediate file or the DHCP server.

      2. Download system software from the file server and set the downloaded file as the startup file for the next startup.

      • This Auto-Config process runs when the following conditions are met: System software needs to be upgraded; information about system software is configured on the DHCP server or the intermediate file; system software is saved on the file server.

      • You can configure Option 146 on the DHCP server to determine whether to delete system software when the space is insufficient. The device deletes system software when the space is insufficient based on the setting of Option 146.

    2. (Optional) Download the patch file.

      1. Obtain information about the patch file from the intermediate file or the DHCP Reply packets.

      2. Download the patch file from the file server and set the downloaded file as the startup file for the next startup.

      This Auto-Config process runs when the following conditions are met: The patch file needs to be upgraded; information about the patch file is configured on the DHCP server or the intermediate file; the patch file is saved on the file server.

    3. Download the configuration file.

      1. Obtain information about the configuration file from the intermediate file or the DHCP Reply packets.

      2. Download the configuration file from the file server and set the downloaded file as the startup file for the next startup.

      • If the system fails to obtain the intermediate file, system software, patch file, and configuration file, the system suspends the Auto-Config process and waits for human intervention. After handing the reason for the Auto-Config failure, run the autoconfig getting-file restart command to obtain the intermediate file, system software, patch file, and configuration file and resume the Auto-Config process.

      • The Auto-Config process triggers the startup of the device through the configuration file. Therefore, the configuration file is mandatory, and the version file and patch file are optional.

  • Restart the device.

    You can configure Option 146 on the DHCP server to specify the delay in restarting the device. After the configuration file is downloaded successfully, the device is restarted according to the setting of Option 146. If no Option 146 is configured, the device is restarted immediately after the configuration file is downloaded.

Translation
Download
Updated: 2019-11-21

Document ID: EDOC1100034066

Views: 90385

Downloads: 487

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