# Display upgrade progress of all RUs.
<Huawei> display ap update status all
FT : File Type
-------------------------------------------------------------------------------------------------------------------------------------------
ID Name AP Type AP Group AP MAC FT Update Version Last Update Time Update Status
-------------------------------------------------------------------------------------------------------------------------------------------
0 hw0 R250D-E default 60de-4476-e320 FIT V200R008C10B008 2016/08/22 18:51 succeed
1 hw1 R250D-E default 60de-4476-e340 FIT V200R008C10B008 2016/08/22 18:51 downloading(progress: 80%/0%)
2 hw2 R250D-E default 60de-4476-e360 FIT V200R008C10B008 2016/08/22 18:51 downloading(progress: 100%/50%)
3 hw3 R250D-E default 60de-4476-e380 FIT - - -
4 hw4 R250D-E default 60de-4476-e3a0 FIT - - -
5 hw5 R250D-E default 60de-4476-e3c0 FIT - - -
-------------------------------------------------------------------------------------------------------------------------------------------
Total: 6
Table 18-24 Description of the display ap update status all command
| Item |
Description |
| ID |
AP ID. |
| Name |
RU name. |
| AP Type |
RU type. |
| AP Group |
AP Group. |
| AP MAC |
MAC address of the RU.
|
| FT |
Type of the RU upgrade file.
|
| Update Version |
Target version that an RU is upgraded to.
|
| Last Update Time |
Last end time when an RU is upgraded.
|
| Update Status |
RU upgrade progress.
- Waiting download: The AP is waiting for an upgrade.
- downloading (progress: 80%/0%): The RU is downloading the system software package, with 80% downloaded.
- downloading (progress: 100%/50%): The system software package is successfully downloaded and is being written to the flash memory, with 50% written.
- failed(AC global caching): The upgrade failed. When an RU is downloading system software package during an in-service upgrade, the system displays this message if the RU starts automatic upgrade which triggers a new process for downloading the software package. When multiple RUs automatically upgrade at the same time, this message may also be displayed. In this situation, the actual RU upgrade result depends on that displayed in the display ap update status all command
output.
- failed(alloc memory for file): The upgrade failed because the RU failed to apply for memory resources.
- failed(AP type in the EFS mismatch): The upgrade failed because the RU type in the EFS file trailer of the current RU version does not match the RU.
- failed(AP type mismatch with batch upgrade AP type): The upgrade failed because the RU type is different from the batch upgrade RU type.
- failed(AP wait for fragmentation timeout): The upgrade failed because the time that the RU waits for fragment data expired.
- failed(block full): The upgrade failed because the number of RUs simultaneously upgraded in AC mode reaches the maximum.
- failed(change to standby): The upgrade failed due a revertive switchover failure.
- failed(fail to download the file): The upgrade failed because the system software failed to be downloaded.
- failed(file content error): The upgrade failed due to incorrect system software file contents.
- failed(file version inconsistent): The upgrade failed because the RU type in the EFS file trailer does not match the RU type contained in the system software package name.
- failed(invalid file name): The upgrade failed because the name of the RU version file is incorrect.
- failed(link down): The upgrade failed because the RU failed to communicate with the central AP.
- failed(mode changed): The upgrade failed because the RU upgrade mode is changed during the AP automatic upgrade.
- failed(nospace in AP memory): The upgrade failed because the RU memory resources were insufficient.
- failed(not receive update result): The upgrade failed because the Central AP receives no RU upgrade result.
- failed(over max upgrade time): The upgrade failed because the upgrade duration exceeds the maximum upgrade time allowed.
- failed(server password is too long): The upgrade failed because the FTP/SFTP server password is too long.
- failed(read file): The upgrade failed because no upgrade file is available in the flash memory.
- failed(receive file failed): The upgrade failed because fragments failed to be received.
- failed(retransfer over times): The upgrade failed because the number of fragment retransmissions exceeds the threshold.
- failed(send first file failed): The upgrade failed because the first fragment failed to be sent.
- failed(other reason): The upgrade failed due to an unknown error.
- failed(upgrade timeout): The upgrade timed out and failed.
- failed(user canceled): The upgrade failed because the user canceled the upgrade.
- failed(waited for next batch): The upgrade failed. The RU has to wait for the next upgrade.
- failed(file changed): The upgrade failed because the upgrade file was modified during the automatic upgrade.
- succeed: The upgrade succeeded.
- succeed(auto resetting): The upgrade failed, and the RU is being restarted.
- succeed(need reset): The upgrade succeeded. The RU must be restarted.
- succeed(resetting): The upgrade succeeded and the AP is being manually restarted.
- succeed(no need to update): The upgrade succeeded. There is no need to upgrade the RU.
- succeed(need mode switch): The upgrade succeeded. The RU mode needs to be switched.
- failed(send upgrade configuration): The upgrade failed because the upgrade configuration failed to be sent.
- failed(send upgrade request): The upgrade failed because the upgrade request failed to be sent.
- failed(upgrade configuration response error): The upgrade failed because there was an error in the RU's upgrade response.
- failed(process upgrade filename): The upgrade failed because the Central AP failed to process the upgrade file name.
- failed(cannot get AP type): The upgrade failed because the Central AP failed to obtain the RU type.
- failed(analyze the version by upgrade filename): The upgrade failed because the device failed to analyze the version number in the file name.
- failed(age time out): The upgrade failed because the state machine aged out.
- failed(state transition check failed for the update module): The upgrade failed because the AC failed to check the status transition of the upgrade module.
- failed(flash component change): The upgrade failed because the flash model is not supported.
- failed (Backing up the system software): The upgrade failed because the system software is being synchronized from the main area to the standby area.
- failed(patch checksum error): The upgrade failed because of a patch checksum error.
- failed(patch file error): The upgrade failed because of a patch file error.
- failed (patch active failed): The upgrade failed because of a failure to activate the patch.
- failed(vrp patch process active failed): The upgrade failed because of a failure to activate the patch on the control plane.
- failed(vfp patch active failed): The upgrade failed because of a failure to activate the patch on the forwarding plane.
- failed(kernel patch actived): The upgrade failed because of a failure to activate the kernel patch.
- failed(patch inner proc error): The upgrade failed because of an internal patch processing failure.
- failed(wifi target chip patch active failed): The upgrade failed because of a failure to activate the Wi-Fi chip patch.
- failed(the current AP version does not support patch updates) The upgrade failed because the AP version does not support the patch upgrade.
- -: The RU requires no upgrade.
|
Previous
