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).
Understanding USB-based Deployment

Understanding USB-based Deployment

This section describes the implementation of USB-based deployment.

USB-based Deployment Process

Before a USB-based deployment, make an index file, save the index file in the root directory of a USB flash drive, and save the upgrade files in the directory specified in the index file. When you connect the USB flash drive to a device, the device downloads the specified files to complete software upgrade.

Figure 4-1 shows the USB-based deployment flowchart.
Figure 4-1  USB-based deployment flowchart

Upgrade File Types

The device to be upgraded automatically loads the required files according to description in the index file.
  • Mandatory file

    • Index file: The file name must be USB_AR.ini or usb_ar.ini.

  • Optional files

    • System software: The file name extension is .zip.

      The supported system software format and file name extension vary depending on the AR router model.

    • Configuration file: The file name extension is .cfg, .db, or .zip.

    • Patch file: The file name extension is .pat.

    • License file: The file name extension is .dat.

    • Voice file: The file name extension is .res.

    • Executable file: The file name extension is .sh.

      During USB-based deployment, the standby MPU does not support executable files.

    • User-defined files

Users can select one or more types of optional file based on the site requirements.

Device Running Process

Figure 4-2 shows the device running flowchart during USB-based deployment.
Figure 4-2  Device running flowchart

  1. A user inserts a USB flash drive to a device.
  2. The system detects the USB flash drive and checks whether an index file exists in the USB flash drive.
    • If an index file exists, the process goes to step 3.
    • If no index file exists, the USB-based deployment process ends.
  3. The system checks whether the index file is valid.
    • If the index file is valid, the process goes to step 4.
    • If the index file is invalid, the deployment fails.
  4. The system checks whether USB-based deployment can be performed.
    • If USB-based deployment can be performed, the process goes to step 5.
    • If USB-based deployment cannot be performed, the deployment fails.

    When the current configuration file of the device is not empty, the USB-based deployment function must be enabled using the autoupdate enable command in the deployment configuration file and the password used for USB-based deployment must be configured. Otherwise, the device cannot be configured using the USB flash drive.

  5. The system obtains deployment files from the USB flash drive and saves them in specified storage media.
    • If files are obtained successfully, the process goes to step 6.

    • If files are not obtained successfully, the deployment fails.

    If the system software package fails verification during USB-based deployment, the upgrade process will not be terminated immediately. Instead, the system continues to verify other types of files and loads these files for the upgrade if the files pass verification.

  6. The system specifies the loaded files for next startup.
  7. The device restarts.
  8. The system checks whether the loaded files are the same as the specified upgrade files.

    • If so, the deployment succeeds.
    • If not, the deployment fails.
  9. The USB-based deployment process ends. The user removes the USB flash drive from the device.

USB-based Android Operating System Upgrade

You can upgrade the Android operating system versions of AR161-FW-P-M5 using a USB flash drive. Before a USB-based upgrade, save the Android operating system version update.zip and configuration file once.cfg or unlmt.cfg in the dload folder in the root directory of a USB flash drive.

once.cfg and unlmt.cfg are two empty text documents, indicating one-time upgrade and unlimited upgrade. The two files cannot co-exist. After an upgrade begins, the green indicator blinks every 1 second. If the upgrade fails, the device restarts after the red indicator remains steady on for 30 seconds.

  • One-time upgrade: After a USB flash drive is inserted in a device, the device compares the sizes (accurate to bytes) of two update.zip files: one in use and the other in the USB flash drive. If the two files have different sizes, the device begins to upgrade. If the upgrade succeeds, the device restarts after the green indicator remains steady on for 3 seconds. After the device restarts, the device runs the update.zip file copied from the USB flash drive. In this situation, the size of the update.zip file currently used by the device is the same as that in the USB flash drive, and the restarted device is not upgraded again.
  • Unlimited upgrade: After a USB flash drive is inserted in a device, the device restarts and upgrades without comparing the sizes of two update.zip files: one in use and the other in the USB flash drive. After an unlimited upgrade succeeds, the device does not restart or continues to upgrade. After the USB flash drive is removed from the device, the device restarts to complete the upgrade.

Removing a USB flash drive from a device during an upgrade may cause the device unable to start. You can insert the USB flash drive in the device again to rectify this fault.

On the AR161FW-P-M5 only the OSP daughter card supports the Android operating system. Therefore, you can check whether the OSP daughter card is upgraded successfully only through the connected screen because the USB-based deployment indicator cannot show whether the OSP daughter card is upgraded successfully.

Translation
Download
Updated: 2019-11-21

Document ID: EDOC1100034066

Views: 89005

Downloads: 486

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