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).
Application Scenarios for Auto-Config

Application Scenarios for Auto-Config

This section describes application scenarios for the Auto-Config feature.

Configuring Auto-Config on Devices that are on the Same Network Segment with the DHCP Server

If a device with no configuration file is on the same network segment as the DHCP server, you can configure Auto-Config based on the networking diagram as shown in Figure 2-3. The configuration file (mandatory), system software (optional), patch file (optional), and intermediate file (optional) are saved on the FTP/TFTP/SFTP server. Routes between the FTP/TFTP/SFTP server, devices to be configured (devices have obtained IP addresses), and the DHCP server are reachable. After software engineers configure the DHCP server and FTP/TFTP/SFTP server, devices can use Auto-Config to load version files including the configuration file (mandatory), system software (optional), and patch file (optional) from the FTP/TFTP/SFTP server.

This configuration method applies to a small network where devices are densely distributed.

Figure 2-3  Auto-Config networking on the same network segment

Configuring Auto-Config on Devices That are on Different Network Segments than the DHCP Server

If a device with no configuration file is on a different network segment than the DHCP server, you can configure Auto-Config based on the networking diagram as shown in Figure 2-4. The configuration file (mandatory), system software (optional), patch file (optional), and intermediate file (optional) are saved on the FTP/TFTP/SFTP server. Routes between the FTP/TFTP/SFTP server, devices with no configuration file (devices have obtained IP addresses), the DHCP relay agent, and DHCP server are reachable. After software engineers configure the DHCP relay agent, DHCP server and FTP/TFTP/SFTP server, devices can use Auto-Config to obtain version files including the configuration file (mandatory), system software (optional), and patch file (optional) from the FTP/TFTP/SFTP server and load version files.

This configuration method applies to a large network where devices with no configuration file are sparsely distributed. Devices on multiple network segments share one DHCP server, reducing costs and facilitating centralized management.

Figure 2-4  Auto-Config networking across different network segments

Translation
Download
Updated: 2019-05-20

Document ID: EDOC1100034225

Views: 45087

Downloads: 100

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