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

Performing USB-based Deployment

Before using a USB flash drive to upgrade or configure a device, make an index file, save the index file to the root directory of the USB flash drive, and save files to be loaded to the directory specified in the index file. Then connect the USB flash drive to the device to start the upgrade process. You can use a USB flash drive to upgrade the Android system software versions of the AR161FW-P-M5 running Android versions.

Background

The USB-based deployment process varies according to the deployment file type and whether the device has the configuration.
File Type Unconfigured Device Configured Device
Configuration file (including the Android configuration file) Connect the USB flash drive to the device to start the USB-based deployment process. The Android configuration file supports the database file format (with a fixed file name settings.db) and password-free ZIP file format (with any file name). Enable the USB-based deployment function on the device before connecting the USB flash drive to it. Otherwise, the device cannot be configured using the USB flash drive. The Android configuration file supports only the ZIP file format with any file name. The file settings.db (with a fixed file name) is encrypted and compressed into a .zip file, and the encryption password is the same as the authentication password for USB-based deployment.
Non-configuration file (system software and patches) Connect the USB flash drive to the device to start the USB-based deployment process.
  • Connect the USB flash drive to the device to start the USB-based deployment process without any check.
  • Enable the USB-based deployment function on the device before connecting the USB flash drive to it.
On the AR161FW-P-M5 running an Android version, the OSP daughter card has different system software than the device. You can only save the Android system software (with the file name fixed as update.zip) and configuration file (once.cfg or unlmt.cfg) to the dload folder in the root directory of a USB flash drive to directly upgrade the Android system software version of the OSP daughter card. The USB flash drive can only be connected to the USB port of the OSP daughter card, as shown in Figure 4-10. You can only make an index file USB_AR.ini to upgrade the system software of the AR161FW-P-M5. The USB flash drive needs to be connected to the USB port of the device, as shown in Figure 4-11.
Figure 4-10  USB port on the AR161FW-P-M5 OSP daughter card

Figure 4-11  USB port on the AR161FW-P-M5

Pay attention to the following points during a USB-based deployment:
  • The USB flash drive must support the FAT32 file system and comply with the USB2.0 and USB3.0 interface standards.
    • If the file system format of the USB flash drive is not FAT32, convert the format into FAT32 (format the USB flash drive) before using the USB flash drive.
    • The AR169W-P-M9, AR169RW-P-M9 support USB-based VM creation. If the size of the VM installation package (OVA file) is greater than 4 GB, the file system format of the USB flash drive must be ext4 (or you can convert the format into ext4).
    • The USB3.0 interface is running on the AR169CVW-4B4S, AR161EW, AR161EW-M1, AR169EW, AR169EGW-L, AR169CVW.
  • To ensure compatibility between USB flash drives and devices, use Huawei-certified USB flash drives to upgrade the Huawei devices. Currently, the following USB flash drives have passed Huawei certification and support the USB2.0 interface:
    • Netac: U208 (4 GB), U208S (16 GB)
    • Kingston: DT108, DT101 (8 GB), DTSE9 (8 GB, 16 GB)
    • SanDisk: CZ50 (8 GB, 16 GB), CZ36 (8 GB, 16 GB), CZ43 (16 GB)

      AR129CGVW-L does not support CZ36.

    • HP: V250W (8 GB, 16 GB)
    • TOSHIBA: UHYBS-016GH/008GH

      AR129CGVW-L does not support this USB flash drives.

    • PNY: HOOK Gold Edition (16 GB, 32 GB)
    Currently, the following USB flash drives have passed Huawei certification and support the USB3.0 interface:
    • Kingston: DT100 G3 (32 GB, 64 GB), DT SE9G2 (64 GB)
    • SanDisk: CZ73
    • SAMSUNG: Bar (32 GB, 64 GB)
  • Before saving files to a USB flash drive, disable the write-protection function of the USB flash drive.
  • Before performing a USB-based deployment, ensure that the device is working properly and its flash memory or SD card has sufficient space for files to be loaded.
  • The device can start using system software in the USB flash drive. When the device cannot start, for example, the storage medium is formatted, power off the device, install the USB flash drive with system software on the device, and then power on the device.
  • Only one USB flash drive can be connected to a device.
  • Files used for USB-based deployment include index file, system software, configuration file, patch file, voice file, license file, executable file, and User-defined files. The index file is mandatory. Among the other files, at least one must be saved in the USB flash drive.
  • Do not power off the device when the device is copying files. Otherwise, the upgrade fails or the device cannot start.
  • Do not remove the USB flash drive before the upgrade is finished. Otherwise, data in the USB flash drive may be damaged.

Pre-configuration Tasks

Before performing a USB-based deployment, power on the device and ensure that the device runs normally.

Procedure

  1. Make an index file.

    For details on how to make an index file, see Making an Index File.

  2. Save the index file and the resource file to be loaded to the device to the root directory of the USB flash drive and save the files specified in the index file to the specified directory.

    The DIRECTORY field to the index file specifies the directory for files to be loaded:
    • If DIRECTORY is set to DEFAULT, save the files to the root directory of the USB flash drive.
    • If DIRECTORY is set to /abc, save the files to the abc directory.
  3. Enable the USB-based deployment function on the device. Skip this step if the device has no configuration. If the device is deployed using non-configuration files, you can skip this step.
    1. Run the set usb autoupdate password password command in the system view to configure an authentication password for USB-based deployment.

      The password configured using the set usb autoupdate password command must contain at least two types of characters, uppercase and lowercase characters, digits, and special characters excluding spaces and question marks (?).

      The authentication password configured by this command is used in the following scenarios:
      • When hash-based message authentication code (HMAC) check is enabled, the device uses this password as the key to calculate the HMAC.

        Currently, the HMAC can only be calculated using the HMAC-SHA256 algorithm.

      • When downloading an encrypted configuration file from the USB flash drive, the device uses this password to decrypt the configuration file.

        Currently, configuration files can be encrypted only when they are being compressed into a .zip format. The following encryption methods can be used:
        • Simple text encryption: For example, when you compress a .cfg configuration file into a .zip file, you can enter a password in the compression software to encrypt the configuration file.

        • AES256 encryption algorithm: For example, when you compress a .cfg configuration file into a .zip file, you can select the AES256 mode and enter a password in the compression software to encrypt the configuration file. This encryption method is recommended because it is more secure.

        It is recommended that you encrypt the configuration file to enhance security. The password used to encrypt the configuration file must be the same as the password configured by the set usb autoupdate password command.

    2. (Optional) Run the hmac enable command in the system view to enable HMAC check for USB-based deployment.

      After HMAC check is configured for USB-based deployment, the device uses the password configured by the set usb autoupdate password command as the key to calculate an HMAC based on the HMAC-SHA256 algorithm for a specific file. Then the device compares the calculated HMAC with the value of the HMAC field in the index file. If the two HMAC values are the same, the device considers the file to be downloaded valid.

      After HMAC check is configured for USB-based deployment, the device performs HMAC check for all the files used for startup. If this function is not enabled, the device does not perform HMAC check when downloading files from the USB flash drive.

      If HMAC check is enabled, the HMAC field in the index file must contain the HMAC.

      It is recommended that you enable HMAC check for USB-based deployment to enhance security.

    3. (Optional) Run the usb autoupdate generate encrypted boot-password command in the system view to encrypt a Boot password in plain text into one in cipher text.

    4. Run the autoupdate enable command in the system view to enable the USB-based deployment function.

      This command can take effect only after an authentication password for USB-based deployment is configured by the set usb autoupdate password command.

  4. Connect the USB flash drive to the device to start the USB-based deployment process.

    During the deployment, the system obtains the required files according to content in the index file (USB_AR.ini) and saves the files in the default storage medium. Then the device specifies the new system software and configuration file as the files for next startup, and restarts.

Procedure for Using a USB Flash Drive to Upgrade the Android System Software

  1. Make the configuration file.

    Create a text file and name it once.cfg or unlmt.cfg according to requirements. For details, see Understanding USB-based Deployment.

  2. Create the dload folder in the root directory of the USB flash drive and save the Android system software update.zip and made configuration file to the root directory.

  3. Connect the USB flash drive to the device to start the upgrade process.

    • To upgrade the Android system software of the AR161FW-P-M5, you can only connect the USB flash drive to the USB port of the OSP daughter card, as shown in Figure 4-10.

Removing the USB flash drive during an upgrade may cause the device unable to start. You can install the USB flash drive again to solve the problem.

After the upgrade succeeds, you can use the USB flash drive to roll back to the previous Android system software version.

Verifying the Configuration

  • Run the display usb usb-id autoupdate state command to check the progress of USB-based deployment.
  • Observe the USB indicator on the device to determine the progress of USB-based deployment:
    • Steady green: The USB-based deployment succeeded.

    • Blinking green: The system USB-based deployment is ongoing.

    • Steady red: USB-based deployment has failed.

After the USB-based deployment succeeds, remove the USB flash drive from the device.

Translation
Download
Updated: 2019-11-21

Document ID: EDOC1100034066

Views: 88317

Downloads: 486

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