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 System Startup Files

Configuring System Startup Files

Pre-configuration Tasks

Specify the system software and configuration file for system startup so that the device will start and initialize with the specified software and configuration file. Specify new patch file if the system needs to load new patches.

Before configuring the system startup files, complete the following tasks:
  • Start the device and logging in to the device locally or remotely.
  • Save the system startup files in the root directory of the device.
NOTE:

After downloading the system startup files from the server to the device, you can check whether the system startup files are damaged during the download process, for example, whether the files are completely downloaded. You can use a piece of third-party software (for example, HashMyFiles) on the server to calculate the MD5 or SHA256 value of the system software files, run the display system { file-md5 | file-sha256 } filename command on the device to calculate the MD5 or SHA256 value of the downloaded system software files, and compare the two values calculated on the server and device. If the two values are the same, the system startup files are not damaged. If the two values are different, the system startup files are damaged, and you need to download the files again.

Context

Before specifying the files for next startup, you can run the display startup command to view the specified files for next startup.
  • If no system software is specified for next startup, the device will start with current system software. To change the system software to be loaded for next startup (during an upgrade for example), upload the new system software to the device and specify it as the system file for next startup. The system software package must use .cc as the file name extension and be saved to the root directory of the storage device.
  • If no configuration file is specified for next startup, the device will start with the default configuration file (vrpcfg.zip for example). If no configuration file is stored in the default directory, the device uses the default parameters for initialization. The configuration file name extension must be .cfg or .zip. In addition, the configuration file must be saved to the root directory of the storage device.
  • A patch file uses .pat as the file name extension. The specified patch file to be loaded for next startup must also be saved to the root directory of the storage device.

Procedure

  • Run startup system-software filename [ verify | signature sign-filename ]

    The system software to be loaded for next startup is specified.

    NOTE:
    You cannot start the system software package in the system using an external hard disk.

    If the device has dual SRUs, run the startup system-software filename [ slave-board | all ] command to specify the system software for the slave SRU to load during the next startup.
    NOTE:

    Specify the same system software for the master and slave SRUs.

    For AR500 series, after the system software to be loaded for next startup is specified, run the nv configuration check command to check whether the existing radio and IMEI configurations on the device are the same as those in the backup area. If the configurations are different, run the startup system-software filename [ verify ] command to back up the existing radio and IMEI configurations on the device.

    The AR510 series (except AR515CGW-L) does not support the signature parameter.

    Specify the verify parameter to check the validity of the system software. If the verification fails, you cannot specify it as the system software to be loaded for next startup. This avoids startup failures caused by invalid system software.

    If signature sign-filename is specified, the device checks validity of the system software's digital signature file. If the check failed, the system software cannot be specified as the system software to be loaded for next startup. This configuration enhances device security.

  • (Optional) Run startup system-software filename backup

    The backup system startup software is specified.

    When the startup software is damaged, the system uses the backup system software to start.

    By default, the device has no backup software system.

    NOTE:

    The AR510 series (except AR515CGW-L) does not support this command.

  • Run startup saved-configuration configuration-file

    The configuration file for next startup is specified.

    The device reads the configuration file from the root directory of the storage device for initialization when powered on.

  • (Optional) Run startup patch patch-name

    The patch file for next startup is specified.

    To make the patch file take effect after the device restarts, run this command to specify the patch file for next startup.

Verifying the Configuration

After the configuration is complete, run the display startup command to view the system software, backup system software, configuration file and patch file for next startup.

Translation
Download
Updated: 2019-05-20

Document ID: EDOC1100034225

Views: 44827

Downloads: 100

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