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

AR500, AR510, and AR530 V200R007 Commands Reference

This document describes all the configuration commands of the device, including the command function, syntax, parameters, views, default level, usage guidelines, examples, and related commands.
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).
display autostart status

display autostart status

Function

The display autostart status command displays the running status of Auto-Start.

Format

display autostart status

Parameters

None

Views

System view

Default Level

3: Management level

Usage Guidelines

None

Example

# Display the running status of Auto-Start.
[Huawei] display autostart status

Enable : Yes

Running: No

Can deploy configurations by USB disk or AutoConfig: Yes

Suspend: No
Reason : --

The status of getting middle file phase:
File name       : arstart.ini
Operation result: Suspend
Failed reason   : The unknown reason cause getting file from file server failed

The status of getting system software phase:
File name       : --
Operation result: --
Failed reason   : --

The status of getting patch file phase:
File name       : --
Operation result: --
Failed reason   : --
                                          
The status of getting configuration file phase:
File name       : --
Operation result: --
Failed reason   : --

The status of activating configuration phase:
Operation result: --
Failed reason   : --

Table 2-6  Description of the display autostart status command output

Item

Description

Enable

Whether Auto-Start is enabled:
  • Yes: enabled
  • No: disabled

Running

Whether Auto-Start is running:
  • Yes: running
  • No: not running

Can deploy configurations by USB disk or AutoConfig

Whether site deployment using a USB flash drive or Auto-Config is available:
  • Yes: available
  • No: unavailable
NOTE:
The device can be deployed using a USB flash drive, Auto-Config, or Auto-Start. The three deployment modes are mutually exclusive and only one of them can be used at a time.

Suspend

Whether Auto-Start is suspended:
  • Yes: suspended
  • No: not suspended

Reason

Reason why Auto-Start is suspended.
  • Autostart is completed.
  • Connecting to file server failed.
  • Getting file server information failed.
  • Getting system MAC address and ESN failed.
  • Getting system MAC address failed and the ESN is wrong.
  • Getting system ESN failed and the MAC address is wrong.
  • No file can be deleted.
  • Space is not insufficient.
  • Specifying startup patch file failed.
  • Specifying startup system software failed.
  • Specifying startup configuration file failed.
  • The obtained version is different from the version in the system software name.
  • The system software already exists and is the current startup file.
  • The username or password used to connect to the file server is wrong.
  • The file does not exist on the file server.
  • The extension name of the system software is wrong.
  • The extension name of the patch file is wrong.
  • The extension name of configuration file is wrong.
  • The configuration file already exists and is the current startup file.
  • The patch file already exists and is the current startup file.
  • The length of the middle file is incorrect.
  • The MAC address and ESN do not match.
  • The system software name or version is not received.
  • The system software name is too long.
  • The patch file name is too long.
  • The version is too long.
  • The configuration file name is too long.
  • The opervalue is too long.
  • The middle file does not have a configuration file name.

The status of getting middle file phase

Phase of obtaining the intermediate file.

File name

Name of the intermediate file, system software, configuration file, or patch file.

Operation result

Result of the file obtaining phase.
  • --: The phase is not started.
  • Running: The phase is running.
  • Successful: The phase is successful.
  • Suspend: The phase is suspended.
  • Stop: The phase stops.

Failed reason

Reason for failing to obtain a file.
  • AutoStart is disabled.

  • Current startup configuration file already exists.

  • Connecting to file server failed.

  • Getting system MAC address and ESN failed.

  • Getting system MAC address failed and the ESN is wrong.

  • Getting system ESN failed and the MAC address is wrong.

  • Space is not insufficient.

  • The username or password used to connect to the file server is wrong.

  • The file does not exist on the file server.

  • The length of the middle file is incorrect.

  • The MAC address and ESN do not match.

  • The middle file does not have a configuration file name.

  • The system software name is too long.

  • The patch file name is too long.

  • The version is too long.

  • The configuration file name is too long.

  • Specifying startup system software failed.

  • The obtained version is different from the version in the system software name.

  • The system software already exists and is the current startup file.

  • The extension name of the system software is wrong.

  • The system software name or version is not received.

  • The system software already exists and is the rollback startup file.

  • Specifying startup patch file failed.

  • The extension name of the patch file is wrong.

  • The patch file already exists and is the current startup file.

  • The patch file already exists and is the rollback startup file.

  • Current startup configuration file already exists.

  • Specifying startup configuration file failed.

  • The extension name of configuration file is wrong.

  • The configuration file already exists and is the current startup file.

  • The configuration file already exists and is the rollback startup file.

The status of getting system software phase

Phase of obtaining the system software.

The status of getting patch file phase

Phase of obtaining the patch file.

The status of getting configuration file phase

Phase of obtaining the configuration file.

The status of activating configuration phase

Phase of activating the configuration.

Operation result

Result of the configuration activation phase.
  • --: The phase is not started.
  • Running: The phase is running.
  • Successful: The phase is successful.
  • Suspend: The phase is suspended.
  • Stop: The phase stops.

Failed reason

Reason for failing to activate the configuration.
  • AutoStart is disabled.

  • Current startup configuration file already exists.

Translation
Download
Updated: 2019-05-29

Document ID: EDOC1000097293

Views: 49472

Downloads: 102

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