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


To have a better experience, please upgrade your IE browser.


AR Router Troubleshooting Guide

This Product Documentation provides guidance for maintaining AR Enterprise Router, covering common information collection and fault diagnostic commands, typical fault troubleshooting guide, and troubleshooting.
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).
What Can I Do If the CPU Usage Is High?

What Can I Do If the CPU Usage Is High?


When a device has a high CPU usage, perform the following operations:
  1. Check whether the CPU usage keeps increasing or increases instantly. If the CPU usage increases instantly, an operation may be performed, for example, the device just starts, information about all optical modules is queried at a time, and traffic volume increases instantly. This situation does not affect the device operation.
  2. Run the display cpu-usage command to display CPU usage statistics and to check which task process causes a high CPU usage and analyze the task.
    <Huawei> display cpu-usage
    CPU   Usage Stat. Cycle: 10 (Second)                                            
    CPU   Usage Stat. Time : 2013-09-24  10:11:55                                   
    Control Plane              
        CPU Usage: 23.3%   Max: 100%                                                
        User: 10.7%   System:  6.9%   SoftIrq:  0.0%   HardIrq:  5.5%   Idle: 76.7% 
        CPU utilization for ten seconds: 23.3%  one minute:  22.0%  five minutes:  2
    3.0% .                     
    Data    Plane              
        CPU Usage:  1.7%   Max: 100%                                                
        CPU utilization for ten seconds:  1.7%  one minute:   1.6%  five minutes:   
    1.6% .                     
    PID   ProcessName         CPU%     CoreIndex      Runtime     State             
    194   cap32               1.7%      CPU1           26132042    R                
    193   vrp                20.0%      CPU0           11216335    S                
    191   monitor             0.0%      CPU0           2324        S                
    74    loop0               0.0%      CPU0           1913        S                
    13    bdi-default         0.0%      CPU0           977         S                
    7     events/0            0.0%      CPU0           708         S                
    138   k3gdevd             0.0%      CPU0           423         S                
    192   cap32               0.0%      CPU0           211         S                
    12    sync_supers         0.0%      CPU0           204         S                
    56    VFDS                0.0%      CPU0           166         S                
    1     init                0.0%      CPU0           90          S                
    19    kswapd0             0.0%      CPU0           63          S                
    30    mtdblockd           0.0%      CPU0           35          S                
    16    khubd               0.0%      CPU0           10          S                
    2     kthreadd            0.0%      CPU0           0           S                
    3     migration/0         0.0%      CPU0           0           S                
    4     ksoftirqd/0         0.0%      CPU0           0           S                
    5     migration/1         0.0%      CPU0           0           S                
    6     ksoftirqd/1         0.0%      CPU0           0           S                
    8     events/1            0.0%      CPU0           0           R                
    9     cpuset              0.0%      CPU0           0           S                
    10    khelper             0.0%      CPU0           0           S                
    11    async/mgr           0.0%      CPU0           0           S                
    14    kblockd/0           0.0%      CPU0           0           S                
    15    kblockd/1           0.0%      CPU0           0           S                
    20    aio/0               0.0%      CPU0           0           S                
    21    aio/1               0.0%      CPU0           0           S                
    22    crypto/0            0.0%      CPU0           0           S                
    23    crypto/1            0.0%      CPU0           0           S                
    29    sdcardqueue         0.0%      CPU0           0           S                
    139   k3gtxd              0.0%      CPU0           0           S                
    153   udpsvd              0.0%      CPU0           0           S                
    271   loop1               0.0%      CPU0           0           S                
    486   flush-mtd-unmap     0.0%      CPU0           0           S  
  3. Check log information and alarm information to determine whether a hardware fault alarm is generated.
  4. Check whether an interface frequently alternates between Up and Down states according to log information and alarm information. If so, check whether the optical module of the interface is faulty or a non-Huawei-certified optical module is used. Additionally, analyze the configuration and traffic volume of the interface.
  5. Check whether network management operations are frequently performed on the device.
  6. Check whether STP flaps or routing protocols flap.
  7. Check whether the network structure changes and whether a loop occurs on the network.
  8. Check whether malicious attacks exist.

More Information

If you find it difficult to determine or solve the problem during maintenance or troubleshooting by referring to related documents, you can collect the fault information and then contact the technical support.

Updated: 2019-05-10

Document ID: EDOC1000079719

Views: 453565

Downloads: 4311

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