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).
Auto-Config Commands

Auto-Config Commands

NOTE:
  • Only Layer 3 Ethernet interfaces support the Auto-Config function.

  • AR500 series support the Auto-Config function.

  • AR510 series (Only ) support the Auto-Config function. But in V200R007C02 version, all device of AR510 series do not support the Auto-Config function.

  • AR530 series support the Auto-Config function.

autoconfig enable

Function

The autoconfig enable command enables Auto-Config.

The undo autoconfig enable command disables Auto-Config.

By default, Auto-Config is enabled on the device.

Format

autoconfig enable

undo autoconfig enable

Parameters

None

Views

System view

Default Level

2: Configuration level

Usage Guidelines

You can configure the Auto-Config function only after it is enabled. The autoconfig enable command is used in the following scenarios:
  • Auto-Config is disabled on the device (You can run the display autoconfig enable command to check whether Auto-Config is enabled). In such a case, you can use the autoconfig enable command to enable Auto-Config.

  • If the Auto-Config function cannot be automatically recovered after an error occurs in the Auto-Config process, run the undo autoconfig enable command to disable the Auto-Config function. After Auto-Config stops, run the autoconfig enable command to enable Auto-Config again. You can use the display autoconfig-status command to check whether Auto-Config is enabled.

Example

# Enable Auto-Config.
<Huawei> system-view
[Huawei] autoconfig enable
Info: Enable autoconfig successfully. 

autoconfig getting-file restart

Function

The autoconfig getting-file restart command enables the device to re-obtain the intermediate file, the system software, patch file and configuration file from the file server.

Format

autoconfig getting-file restart

Parameters

None

Views

System view

Default Level

2: Configuration level

Usage Guidelines

If the device fails to obtain the intermediate file, system software, patch file or configuration file, the Auto-Config process is suspended and needs to be restarted. The autoconfig getting-file restart command restarts the Auto-Config process, enabling the device to re-obtain the intermediate file, system software, patch file and configuration file. The display autoconfig-status command displays whether the Auto-Config process is suspended.

NOTE:

This command can be executed only when obtaining files failed and the Auto-Config process is suspended.

Example

# Configure the device to re-obtain files from the file server and continue the AutoConfig process.

<Huawei> system-view
[Huawei] autoconfig getting-file restart

display autoconfig activating-config delay

Function

The display autoconfig activating-config delay command displays the delay in restarting a device after a configuration file is downloaded using Auto-Config.

Format

display autoconfig activating-config delay

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

After a user uses the Option 146 parameter to set the delay in restarting a device, there is a delay in restarting the device after the version file, patch file, and configuration file are downloaded using Auto-Config. After the device is restarted, loaded files can take effect. Run the display autoconfig activating-config delay command to check the configured delay in restarting a device.

Precautions

By default, the device is restarted immediately if no delay is set using the Option 146 parameter.

Example

# Display the delay in restarting a device after a configuration file is downloaded using Auto-Config.

<Huawei> display autoconfig activating-config delay
The delay in activating configuration is 0 seconds.    

display autoconfig activating-config remanent-time

Function

The display autoconfig activating-config remanent-time command displays the remaining delay in restarting a device after a configuration file is downloaded using Auto-Config.

Format

display autoconfig activating-config remanent-time

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

After a user uses the Option 146 parameter to set the delay in restarting a device, there is a delay in restarting the device after the version file, patch file, and configuration file are downloaded using Auto-Config. After the device is restarted, loaded files can take effect. Run the display autoconfig activating-config remanent-time command to check the remaining delay in restarting a device.

Precautions

By default, the device is restarted immediately if no delay is set using the Option 146 parameter.

Example

# Display the remaining delay in restarting a device after a configuration file is downloaded using Auto-Config.

<Huawei> display autoconfig activating-config remanent-time
The remanent time of activating configuration is 10 seconds.

display autoconfig enable

Function

The display autoconfig enable command displays whether Auto-Config is enabled.

Format

display autoconfig enable

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Auto-Config runs only after it is enabled. You can run the display autoconfig enable command to check whether Auto-Config is enabled to ensure that Auto-Config runs properly.

Example

# Check whether Auto-Config is enabled.

<Huawei> display autoconfig enable
Autoconfig is enabled.   
Related Topics

display autoconfig-status

Function

The display autoconfig-status command displays the Auto-Config configuration and running status.

Format

display autoconfig-status

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

None

Example

# Display the configuration and running status of Auto-Config.

<Huawei> display autoconfig-status
                                                                                
Running: No                                                                     
                                                                                
Can deploy configurations with a USB disk: Yes                                                             
                                                                                
Stop   : Yes                                                                    
Reason : Current startup configuration file already exists.                                    
                                                                                
Suspend: No                                                                     
Reason : --                                                                     
                                                                                
The status of DHCP phase:                                                       
Operation result: --                                                            
Failed reason   : --                                                            
                                                                                
The status of setting ACS phase:                                                
URL             : --                                                            
User name       : --                                                            
Password        : --                                                            
Operation result: --                                                            
Failed reason   : --                                                            
                                                                                
The status of getting middle file phase:                                        
File name       : --                                                            
Operation result: --                                                            
Failed reason   : --                                                            
                                                                                
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:                                   
Remained time   : --                                                            
Operation result: --                                                            
Failed reason   : --                                                            
                                                                                
<Huawei> display autoconfig-status

Running: Yes                                                                    
                                                                                
Can deploy configurations with a USB disk: No                                   
                                                                               
Stop   : No                                                                     
Reason : --                                                                     
                                                                                
Suspend: Yes                                                                    
Reason : Only CWMP can be used for system software upgrade                      
                                                                                
The status of DHCP phase:                                                       
Operation result: Successful                                                    
Failed reason   : --                                                            
                                                                               
The status of setting ACS phase:                                                
URL             : --                                                            
User name       : --                                                            
Password        : --                                                            
Operation result: --                                                            
Failed reason   : --                                                            
                                                                                
The status of getting middle file phase:                                        
File name       : --                                                            
Operation result: --                                                            
Failed reason   : --                                                             
                                                                                
The status of getting system software phase:                                    
File name       : auto_V200R008C90.cc                                           
Operation result: Suspend                                                       
Failed reason   : Only CWMP can be used for system software upgrade             
                                                                               
The status of getting patch file phase:                                         
File name       : --                                                            
Operation result: --                                                            
Failed reason   : --                                                            
                                                                               
The status of getting configuration file phase:                                 
File name       : ar_V200R008C50.cfg                                            
Operation result: --                                                            
Failed reason   : --                                                             
                                                                              
The status of activating configuration phase:                                   
Remained time   : --                                                            
Operation result: --                                                            
Failed reason   : --                                                             
                                                                                 
Table 2-5  Description of the display autoconfig-status command output

Item

Description

Running

Whether Auto-Config is running.

  • Yes
  • No

Can deploy configurations with a USB disk

Whether a USB disk can be used for deployment.

  • Yes
  • No
NOTE:
The device can be configured using Auto-Config or USB deployment. However, two deployment methods cannot be used together.

Stop

Whether Auto-Config stops.

  • Yes
  • No

Reason

Reason that Auto-Config stops:
  • AutoConfig is disabled.

  • Current startup configuration file already exists.

Suspend

Whether Auto-Config is suspended.

  • Yes
  • No

Reason

Reason that Auto-Config is suspended:
  • Autoconfig is completed.

  • Connecting to file server failed.

  • Deploying configurations with a USB disk.

  • Failed to get the TFTP server address from the host.

  • 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.

  • Option 147 check failed.

  • Option 147 does not exist or check is successful, but check of other information fails.

  • Option 141 is too long.

  • Option 142 is too long.

  • Option 67 is too long.

  • Option 66 is too long.

  • Option 15 is too long.

  • Option 145 is too long.

  • Option 146 is too long.

  • Option 43 is too long.

  • Space is not insufficient.

  • Specifying startup patch file failed.

  • Specifying startup system software failed.

  • Specifying startup configuration file failed.

  • Some ACS information is empty.

  • Setting ACS URL failed.

  • Setting ACS user name failed.

  • Setting ACS password 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 user name 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 TFTP server cannot be found.

  • The length of some ACS information is wrong.

  • The format of ACS URL is wrong.

  • The format of ACS user name is wrong.

  • The format of ACS password is wrong.

  • 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 delaytime is too long.

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

The status of DHCP phase

DHCP exchange phase.

Operation result

Result of interaction between the device and the DHCP server:
  • --: The DHCP exchange phase is not started.
  • Running: Auto-Config is running.
  • Successful: Auto-Config is successful.
  • Suspend: Auto-Config is suspended.
  • Stop: Auto-Config stops.

Failed reason

Reason for interaction failure between the device and the DHCP server:
  • AutoConfig is disabled.

  • Current startup configuration file already exists.

  • Deploying configurations with a USB disk.

  • Failed to get the TFTP server address from the host.

  • Getting file server information failed.

  • Option 147 check failed.

  • Option 147 does not exist or check is successful, but check of other information fails.

  • Option 141 is too long.

  • Option 142 is too long.

  • Option 67 is too long.

  • Option 66 is too long.

  • Option 15 is too long.

  • Option 145 is too long.

  • Option 146 is too long.

  • Option 43 is too long.

  • The TFTP server cannot be found.

  • 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 delaytime is too long.

NOTE:

If Auto-Config keeps running during the interaction between the device and the DHCP server, The last failed reason is displayed, indicating the latest reason for failure.

The status of setting ACS phase

ACS configuration phase.

URL

ACS URL.

User name

ACS user name.

Password

ACS password.

Operation result

Operation result:
  • --: The ACS configuration phase is not started.
  • Running: Auto-Config is running.
  • Successful: Auto-Config is successful.
  • Suspend: Auto-Config is suspended.
  • Stop: Auto-Config stops.

Failed reason

Reason for a failure:
  • Autoconfig is completed.

  • AutoConfig is disabled.

  • Current startup configuration file already exists.

  • Some ACS information is empty.

  • Setting ACS URL failed.

  • Setting ACS user name failed.

  • Setting ACS password failed.

  • The length of some ACS information is wrong.

  • The format of ACS URL is wrong.

  • The format of ACS user name is wrong.

  • The format of ACS password is wrong.

NOTE:

If Auto-Config keeps running when ACS runs, The last failed reason is displayed, indicating the latest reason for failure.

The status of getting middle file phase

Phase of obtaining the intermediate file.

File name

Intermediate file name.

Operation result

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

Failed reason

Reason for failing to obtain the intermediate file:
  • AutoConfig 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 user name 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.

NOTE:

If Auto-Config keeps running during the phase of obtaining the intermediate file, The last failed reason is displayed, indicating the latest reason for failure.

The status of getting system software phase

Phase of obtaining the system software.

File name

System software name.

Operation result

Result of obtaining system software:
  • --: The phase of obtaining a version file is not started.
  • Running: Auto-Config is running.
  • Successful: Auto-Config is successful.
  • Suspend: Auto-Config is suspended.
  • Stop: Auto-Config stops.

Failed reason

Reason for failing to obtain the system software:
  • AutoConfig is disabled.

  • Current startup configuration file already exists.

  • Connecting to file server failed.

  • No file can be deleted.

  • Specifying startup system software failed.

  • Space is not insufficient.

  • The file does not exist on the file server.

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

  • 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.

NOTE:

If Auto-Config keeps running during the phase of obtaining the system software, The last failed reason is displayed, indicating the latest reason for failure.

Only V200R008C50 and later versions support the reason: Only CWMP can be used for system software upgrade.

The status of getting patch file phase

Phase of obtaining a patch file.

File name

Patch file name.

Operation result

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

Failed reason

Reason for failing to obtain the patch file:
  • AutoConfig is disabled.

  • Current startup configuration file already exists.

  • Connecting to file server failed.

  • Specifying startup patch file failed.

  • Space is not insufficient.

  • The file does not exist on the file server.

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

  • 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.

NOTE:

If Auto-Config keeps running during the phase of obtaining the patch file, The last failed reason is displayed, indicating the latest reason for failure.

The status of getting configuration file phase

Phase of obtaining a configuration file.

File name

Configuration file name.

Operation result

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

Failed reason

Reason for failing to obtain the configuration file:
  • AutoConfig is disabled.

  • Current startup configuration file already exists.

  • Connecting to file server failed.

  • Specifying startup configuration file failed.

  • Space is not insufficient.

  • The file does not exist on the file server.

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

  • 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.

NOTE:

If Auto-Config keeps running during the phase of obtaining the configuration file, The last failed reason is displayed, indicating the latest reason for failure.

The status of activating configuration phase

Phase of activating the configuration.

Remained time

Remaining relay for restarting a device.

The command output of this command is the same as that of the display autoconfig activating-config remanent-time command.

Operation result

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

Failed reason

Reason for failing to activate configurations:
  • AutoConfig is disabled.

  • Current startup configuration file already exists.

Translation
Download
Updated: 2019-05-29

Document ID: EDOC1000097293

Views: 92524

Downloads: 126

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