The CPU Usage Is High
Symptom
The CPU usage is high, affecting device performance.
Possible Causes
The common causes of high CPU usage on the AC are as follows:
- Hardware is faulty.
- The network is attacked or loop occurs.
- Service configurations are improper.
- The device is connected to too many network management systems (NMSs).
Troubleshooting Procedure
- Check whether the software and patch versions need to be updated.
Check the software and patch versions. If the latest patch contains the description of the solutions for similar problems, update the software and patch to the latest versions.
<AC6605> display version Huawei Versatile Routing Platform Software VRP (R) software, Version 5.130 (AC6605-26-PWR V200R007C20) Copyright (C) 2015-2017 HUAWEI TECH CO., LTD ... <AC6605> display patch-information Patch version : V200R007C20SPH005 Patch package name: flash:/V200R007C20SPH005.pat
- Handle the tasks that result in high CPU usage.
- Check the current CPU usage.
The following uses V200R010 as an example:
[AC6605-diagnose] display cpu-usage CPU Usage Stat. Cycle: 30 (Second) usr: 3.4% sys: 1.1% irq: 0.0% softIrq: 0.0% CPU Usage: 4.7% Max: 46.7% CPU Usage Stat. Time : 2019-10-14 10:59:16 (core 0) CPU Usage Max. Time : 2019-10-14 10:56:43 (core 0) Core-0 Usage: 4.7% usr: 3.4% sys: 1.1% irq: 0.0% softIrq: 0.0% Core-1 Usage: 3.7% usr: 2.6% sys: 1.2% irq: 0.0% softIrq: 0.0% PID ProcessName CPU% Runtime State 188 vos.o 4.7 66380 S 191 wmi 0.6 5990 S 190 wmi 0.6 6035 S 194 nac 0.5 4791 S 195 nac 0.5 4807 S 189 wmc 0.5 4675 S 196 ucm_gc 0.3 3774 S 192 dhcp 0.3 3764 S ...... [AC6605-diagnose] display cpu-usage pid 188 //The corresponding ProcessName is vos.o. The Thread CPU usage: % of ProcessId: 188 -------------------------------------------------- VosTaskId ThreadID ThreadName CPU% Runtime State 45 441 SessionWorkerTask 54.4 24499 S 54 450 bcmCNTR.0 4.9 3668 S 0 402 vos.o 4.0 2820 R 189 782 ROUT 3.2 2541 S 171 567 POE 2.8 1876 S 57 453 bmLINK.0 2.5 1897 S 3 344 TICK 2.3 1813 S 202 795 STP 1.9 1407 S 169 565 AREM 1.6 1146 S 50 446 bcmINTR 1.5 1131 S 255 1047 We0 1.4 146 S 43 439 WebT 0.9 854 S ......
Item
Description
CPU Usage
Current CPU usage of the device. The default CPU usage threshold is 80%. If the CPU usage exceeds 80%, the CPU usage is high.
Max
Maximum historical CPU usage.
CPU Usage Stat. Time
Time when the current CPU usage is measured.
CPU Usage Max. Time
Time when the maximum historical CPU usage is measured.
ProcessName
Name of the CPU processing task.
CPU%
CPU usage of the task.
Dopra tasks CPU usage: % of vos.o
Or:
The Thread CPU usage: % of ProcessId: 188
Details about the CPU usage of vos.o tasks.
ThreadName
Detailed task name in vos.o.
- Check the historical CPU usage.
[AC6605-diagnose] display cpu-usage history 100%| 95%| 90%| 85%| 80%| 75%| 70%| 65%| 60%| 55%| 50%| 45%| 40%| 35%| 30%| 25%| 20%| 15%| 10%| 5%|************************************************************************************************************************* -------------------------------------------------------------------------------------------------------------------------- 60 45 30 15 0 (minutes) - Check the CPU usage, and locate the tasks that cause high CPU usage and the causes based on logs.
View the logs to check the CPU usage and CPU recovery time, and locate the tasks that cause high CPU usage.
2018-2-24 10:52:34+00:00 AC6605 %%01MON/4/CPU_USAGE_HIGH(l)[50]:The CPU is overloaded, and the top three thread CPU occupancy are TASK1 TASK2 TASK3. (CpuUsage=xx%, Threshold=xx%)
In the preceding example, TASK1, TASK2, and TASK3 are the top three tasks that cause high CPU usage. Locate the corresponding causes and solutions by referring to Table 12-2.
Table 12-2 Common tasks that cause high CPU usage and solutionsTask Name
Description
Cause of High CPU Usage
Solution
ARP
Implements the ARP protocol stack, manages the ARP state machine, and maintains the ARP database.
- The Committed Access Rate (CAR) for packets sent to the CPU is too large, and a large number of ARP packets are received.
- The aging time is too short.
Adjust the CAR for packets sent to the CPU and the aging time.
SOCK
Implements packet receiving and sending.
When a large number of protocol packets are sent to the CPU, the CPU usage of the task increases significantly, which is an important cause of high CPU usage.
The reasons why many protocol packets are sent to the CPU include:
- The CPU is attacked.
- A network loop occurs.
- Service traffic is heavy.
- If the fault is caused by a network loop or network attack, rectify the fault accordingly.
- Contact technical support engineers to check whether the service traffic is too heavy. If so, handle the problem accordingly.
CFM
Processes configuration management services such as configuration restoration of the device and interfaces.
Configurations are restored.
No action is required.
DHCP
Implements the DHCP protocol stack and provides the functions such as DHCP snooping and DHCP relay.
The CPU experiences a DHCP attack.
Add network anti-attack configurations.
DS0/DS1
Synchronizes data from the NMS.
Synchronization is frequent.
Increase the synchronization interval on the NMS.
FIB/FIB6
Manages IPv4/IPv6 FIB entries.
When a large number of routes are delivered, route flapping continuously occurs.
No action is required.
FTPS
Provides the FTP server service and FC0 as well as FC1 services.
The CPU usage of FC tasks becomes high when large files are being transferred, for example, a software package is being transferred and even multiple software packages are being transferred concurrently.
The high CPU usage problem is automatically solved after file transfer ends. To prevent this problem, minimize concurrent transfer of multiple large files.
IC
Information center main task, which receives and outputs the logs, alarms, and debugging information generated by service modules.
Logs and debugging information are frequently triggered.
Reduce the frequency at which operations triggered by logs and debugging information are performed.
IP
Schedules IP protocol tasks in a unified manner.
A large number of IPv6 packets are sent and received.
Reduce the number of sent and received IPv6 packets by adjusting, for example, the Control Plane Committed Access Rate (CPCAR).
PM/PMS
Performance management task, which processes performance statistics data and PM configuration commands as well as reports performance statistics.
When there are many PM configurations (a large amount of statistics data), performance data collection and processing are triggered.
- Reduce the frequency at which performance statistics are collected.
- Configure different statistics collection intervals for different statistics collection tasks.
vt0/vt1/vt2 ...
Authenticates users that log in to the device with the ID of 0/1/2... and processes commands.
User operations, especially input and output operations, are frequently performed. For example, commands are copied to the screen (input) or a large number of display commands are executed (output).
Reduce the frequency at which input and output operations are performed. This problem is automatically solved after the operations end.
Co0/Co1
Authenticates users that log in to the device through the serial port with the ID of 0 or 1 and processes commands.
User operations, especially input and output operations, are frequently performed on the serial port. For example, commands are copied to the screen (input) or a large number of display commands are executed (output).
Reduce the frequency at which input and output operations are performed. This problem is automatically solved after the operations end.
We0/We1 ...WebT/SessionAdminTask/SessionWorkerTask
Web service processing task, which processes requests of all web users.
Operations are frequently performed on the web platform.
Reduce the frequency at which operations on the web platform are performed.
WMT_PM
Is used by eSight to collect PM performance data.
eSight periodically collects AP data.
Adjust the PM performance measurement interval.
_S0fSNMP/SNP6
Processes operations of IPv4/IPv6 SNMP NMSs.
A large number of SNMP NMSs are connected, or operations on SNMP NMSs are performed frequently.
Reduce the frequency at which operations on SNMP NMSs are performed.
SNMP trap task
Reports SNMP traps of the device.
A large number of device traps are generated.
No action is required.
LYNC
Interconnects with Microsoft Lync functions.
Microsoft Lync Server reports a large amount of data.
No action is required.
FM
Suppresses device alarms.
A large number of alarms are generated.
No action is required.
COMM/MFPI
Processes, forwards, and reports control-plane packets.
When a large number of protocol packets are sent to the CPU, the CPU usage of the task increases significantly, which is an important cause of high CPU usage.
The reasons why many protocol packets are sent to the CPU include:
- The CPU is attacked.
- A network loop occurs.
- Service traffic is heavy.
- If the fault is caused by a network loop or network attack, rectify the fault accordingly.
- Contact technical support engineers to check whether the service traffic is too heavy. If so, handle the problem accordingly.
WAPI_RCV_PKT
Sends and receives WAPI authentication packets.
A large number of users perform WAPI authentication concurrently.
Typically, this task does not cause high CPU usage. If high CPU usage occurs, try to reduce the number of concurrent WAPI authentication requests, or use another authentication mode.
WLAN_AgeList
Ages out WPA and WPA2 users.
Packets are retransmitted due to WPA key negotiation timeout, and there are a large number of concurrent WPA users.
This task rarely causes high CPU usage.
ArrmThread
Performs radio calibration.
During radio calibration, neighbor information reported by APs is continuously processed. However, the algorithm is complex and the calculation workload is heavy, causing high CPU usage.
Perform scheduled calibration during off-peak hours (such as late at night).
WDM_FILE_READ
Reads files during AP upgrade.
APs are upgraded in a batch in AC mode.
Use the FTP mode or upgrade a large number of APs in several batches.
WDM_MAIN_CTRL
AP upgrade control task.
APs are upgraded in a batch.
Use the FTP mode or upgrade a large number of APs in several batches.
WMT_NB
Detects neighbor information.
During radio calibration, this task processes neighbor information reported by APs. The CPU usage may be high when a large number of APs report neighbor information.
Perform scheduled calibration during off-peak hours (such as late at night).
WMT_LKM
Manages CAPWAP links.
Services such as mobility groups and wireless configuration synchronization trigger repeated CAPWAP link establishment.
Check whether the CAPWAP link triggered by the corresponding service comes up or goes down frequently. If yes, rectify the fault accordingly.
WMT_CLUS/WMT_CSP
Performs wireless configuration synchronization.
Configurations are repeatedly modified, or batch configuration synchronization operations are performed.
This task rarely causes high CPU usage.
WMT_DBG
Implements log, VAP, SSID, and traffic diagnosis.
A large amount of data is generated when VAP services are created repeatedly.
Change the log level.
WMT_WPM
Processes the performance statistics reported by APs.
A large amount of performance data is collected after the device is enabled to report performance statistics to eSight.
Adjust the PM performance measurement interval.
WMT_IDS
Wireless intrusion detection task:
- Checks the validity of detection entries, processes detection entry mappings, and generates entries for contained rogue devices.
- Generates attack detection entries and reports attack alarms.
A large number of APs are detected, or the detection interval is short.
This task rarely causes high CPU usage.
WMT_SEC
User management task:
- Processes user login/logout and roaming.
- Processes the user key negotiation procedure.
More than 20 users are concurrently connected or are roaming simultaneously per second.
When more than 20 users connect to the device simultaneously, the CPU usage of this task is about 15% and CPU resources are used to process user access, authentication, and roaming. In this case, capacity expansion is required.
WMT_SRV
WLAN component task that delivers configurations and backs up data in batches:
- Processes configuration delivery messages (MAP and timer messages).
- Processes CAPWAP messages.
- Maintains status transition of the configuration delivery module.
- Initializes the WESS, WQOS, and WGLB tasks.
- Processes messages received on the radio module from other modules.
- Processes messages reported by the WVAP.
- Processes the reported radio location information.
- Processes HSB event notifications and HSB packets.
- Notifies external modules of AP status changes.
- Configurations are delivered when APs go online in batches.
- Data is backed up in the case of dual-link or VRRP HSB.
- The HSB service frequently flaps due to link flapping. As a result, batch deletion and batch backup are performed.
- Scheduled backup is performed.
This task rarely causes high CPU usage.
WMT_DEV
Device management task:
- Periodically checks APs.
- Processes AP ping operations.
- Periodically synchronizes messages between mobility groups.
- Processes MAP messages.
- Processes CAPWAP messages.
- Processes messages of the DEV module.
- Processes status transition during AP login, maintains the state machine (including upgrade processing), batch AP login/logout, AP upgrade, and collected information periodically reported by radios.
During batch AP login/logout, upgrade, radio calibration, terminal location, a large number of messages from APs are processed.
Set the air scan interval to a larger value and check whether APs frequently go offline.
WMT_SYS
Manages WLAN components.
This task collects AP performance data statistics and processes messages between WMNG modules.
If the CPU usage is high periodically, no action is required. If the CPU usage is high continuously, collect logs.
CWP_BUP
Processes MAP messages.
In normal cases, this task does not cause high CPU usage.
Reduce service concurrency, expand capacity, or replace the device with a high-performance one.
CWP_DTLS
Performs DTLS encryption.
DTLS links are created or disabled, DTLS negotiation is performed, or APs set up DTLS links in batches.
This task is used when APs go online through DTLS links. However, high CPU usage rarely occurs in this scenario. If this task causes high CPU usage, disable DTLS based on the network requirements.
CWP_CWP
Distributes CAPWAP services, and receives or distributes CAPWAP packets.
High CPU usage occurs during message queue maintenance, packet distribution and statistics collection, or CAPWAP timer processing (retransmission, fragmentation, reassembly, and state machine), or when a large number of packets exist, traffic is sent continuously, or an attack occurs.
Reduce service concurrency, expand capacity, or replace the device with a high-performance one.
CWP_FWD
Creates CAPWAP socket, sends and receives socket packets, and rapidly sends and receives packets.
Traffic is continuously sent when there are a large number of CAPWAP control packets, or a CAPWAP attack exists.
When more than 20 users concurrently connect to the device per second, it is normal that the CPU usage of this task is within 15%. You can only expand the capacity to solve the problem
WLAN_NSTRANS
Configures and reports service venue information.
The device periodically reports information about the venue, device, and AP status to the background management system for wireless Internet access security in public places. The CPU usage may be high when a large amount of data is reported.
Disable the data reporting function, or reduce the volume of data to be reported.
WLAN_NS
Configures and reports service venue information.
The device periodically reports information about the venue, device, and AP status to the background management system for wireless Internet access security in public places. The CPU usage may be high when a large amount of data is reported.
Disable the data reporting function, or reduce the volume of data to be reported.
WLAN_SHELL
Processes HSB-related messages and data.
Frequent HSB operations are performed.
Check whether HSB links flap.
AGENT_CAPWAP/AGENT_WLAN
Implements agent message exchange between the primary and secondary cores.
A large number of agent messages are transmitted between the primary and secondary cores.
Locate the source of agent messages, for example, a large number of MIB queries by the NMS, backup, and batch AP/user login and logout. Then reduce the triggering frequency for different services.
HTPSRD
Processes Portal authentication packets.
A large number of HTTP packets for Portal authentication are sent to the CPU.
- Reduce the number of authentication users.
- Limit the rate at which HTTP packets are sent to the CPU, and check whether too many HTTP packets are caused by external attacks or network loops.
STA_TRACE_TASK
Processes the station trace diagnosis function.
The station trace function is enabled.
Disable the station trace function.
STP
Implements the STP protocol stack, manages the STP state machine, and maintains the STP database.
Incorrect connections exist after STP is deployed and the device suffers from a TC packet attack.
Check the configuration and configure TC suppression.
WADP
WLAN adaptation task.
A large number of APs go online and offline, a large number of AP interfaces change, or a large number of STAs go online or offline concurrently.
Plan the network again and limit the number of online APs and STAs.
PTAL
Implements Portal authentication.
A large number of HTTP packets for Portal authentication are sent to the CPU.
- Reduce the number of authentication users.
- Limit the rate at which HTTP packets are sent to the CPU, and check whether too many HTTP packets are caused by external attacks or network loops.
HTPD
Processes built-in Portal authentication.
A large number of HTTP packets for Portal authentication are sent to the CPU.
- Reduce the number of authentication users.
- Limit the rate at which HTTP packets are sent to the CPU, and check whether too many HTTP packets are caused by external attacks or network loops.
EAP
Performs MAC and 802.1X authentication.
Authentication is performed for a large number of MAC and 802.1X users.
Reduce the number of authentication users.
UCM
Manages authentication users.
A large number of users go online.
Reduce the number of authentication users.
UTSK
User framework task that optimizes protocol processing to ensure preferential processing of protocol packets.
This task is used to register UTASK commands and create timers during device registration. After device registration is complete, this task no longer processes messages and will not cause high CPU usage.
No action is required.
NTPT
Provides the NTP clock synchronization function.
A large number of NTP attack packets are received.
Configure NTP authentication.
POE
Detects whether PDs are in position and checks the grading status and power control policies of the PDs.
It will not cause high CPU usage.
No action is required.
ACL
Manages access control lists (ACLs).
Too many ACLs are delivered at a time.
Set the ACL interval to a larger value.
bcmDPC
Reports interrupts when chip failures occur.
There are unrecoverable soft failure entries on cards, and interrupts are not suppressed.
Upgrade the patch and restart the device.
bcmL2MOD.0
Chip 2 MAC address entry learning task.
MAC address flapping or a hash conflict occurs.
- If MAC address flapping occurs, take measures to prevent loops.
- If a hash conflict occurs, change the VLAN or replace the card.
bmLINK.0
Chip 0 linkscan task, which scans interface status and notifies the application modules of interface status changes.
A large number of link interruptions are reported or miim access is time-consuming. Link interruptions are caused by LOS of optical modules. Non-certified optical transceivers and optical transceiver failures will lead to many abnormal interruptions (non-standard optical transceivers will cause this situation).
Replace the optical transceivers with Huawei-certified ones.
bcmTX
Sends packets to the CPU.
Too many packets are sent.
No action is required.
bcmINTR
Processes kernel interrupts.
Many kernel interrupts are reported.
No action is required.
bcmCNTR.0
Collects traffic statistics on chip 0.
-
No action is required.
DEFD
Processes CPU defense events.
Too many packets are sent to the CPU.
Limit the rate of packets sent to the CPU.
RDS
Processes the RADIUS protocol.
A large number of RADIUS packets are sent to the CPU.
Reduce the number of authentication users.
Limit the rate at which RADIUS packets are sent to the CPU, and check whether too many RADIUS packets are caused by external attacks or network loops.
RMON
Monitors the system remotely.
It will not cause high CPU usage.
No action is required.
GRSA/RSA
Creates RSA and DSA key pairs.
It will not cause high CPU usage.
No action is required.
APP
Centrally schedules Layer 3 service tasks.
Multiple tasks are performed to process many service messages.
Run the display utask-info utask-id slice-time command to check which UTASK task takes a long time.
HSB
HSB service task.
It will not cause high CPU usage.
-
SNPG
Layer 2 multicast protocol stack task, which processes sent and received Layer 2 multicast packets and delivers Layer 2 multicast entries.
- The device receives a large number of Layer 2 multicast packets.
- Layer 2 multicast entries are repeatedly updated due to ring network or port flapping.
Check whether there are a large number of Layer 2 multicast attack packets.
Check whether ring network or port flapping occurs.
VRPT
Temporary timer test task during system startup. It stops after the system is properly started.
It will not cause high CPU usage.
No action is required.
VRRP
Implements the VRRP protocol stack, manages the VRRP state machine, and maintains the VRRP database.
A large number of VRRP groups are configured and interface flapping occurs.
This task rarely causes high CPU usage. If the problem occurs, shut down the interfaces where VRRP is configured, to avoid flapping.
WEB
Web authentication service task.
A large number of Portal authentication packets are sent to the CPU.
Limit the rate at which Portal packets are sent to the CPU, and check whether too many Portal packets are caused by external attacks or network loops.
BOX_Out
Exports the data stored in the black box, including error and exception information generated during system running.
The black box only provides a mechanism of recording, querying, and obtaining information. Users need to use this mechanism to record the required information.
Errors, assertions, exceptions or deadloops occur on the device.
No action is required.
FECD
Processes messages at the FECD layer.
Too much diagnostic information is printed.
No action is required.
Printu
Processes kernel printu printing information.
It will not cause high CPU usage.
No action is required.
LBS
Locates STAs and analyzes the spectrum of non-Wi-Fi devices.
The air scan interval is too short or the radio environment is complex.
Increase the air scan interval to a proper value by considering both the location precision and CPU usage.
VCLK
Wakes up the TICK clock.
-
No action is required.
TICK
Timer processing task.
-
No action is required.
MIMC
Internal communication mechanism (between the user mode and kernel mode).
-
No action is required.
SECE
Implements security functions such as ARP security, IP security, and CPU security, manages the protocol state machine, and maintains protocol databases.
A large number of protocol packets are sent to the CPU.
Configure the rate limit of protocol packets properly and deploy the attack defense function.
AAA
Manages user authentication, authorization, and accounting.
Authentication, authorization, and accounting are performed for a large number of users.
Reduce online users.
AM
Manages IP address pools and IP addresses for modules such as DHCP.
A large number of users apply for IP addresses.
Reduce the number of users who apply for IP addresses.
BFD
Implements the BFD protocol stack, manages the protocol state machine, and maintains the protocol database.
-
-
BFDA
BFD adaptation task that processes IPC messages and ARP and MAC address change messages.
-
-
BTRC
Traces the internal debugging function.
The trace function is enabled.
Disable the trace function.
COMT
Commits ACL configurations to APs.
A large number of APs go online concurrently.
Plan the network properly and prevent many APs from going online concurrently.
CSPF
Calculates paths for TE tunnels.
The TED database for CSPF frequently changes.
Check whether the link or IGP flaps. If so, rectify the fault.
EFMT
Sends 802.3ah test packets.
-
No action is required.
FCAT
Obtains packets.
Too many packets are obtained and printed frequently.
No action is required.
GRES
Task corresponding to the label and token resource modules.
It will not cause high CPU usage.
No action is required.
IFLP
Collects traffic statistics on management interfaces periodically.
A large number of interfaces are configured and the measurement interval is short.
No action is required.
IFNT
Processes interface status change events.
The interface flaps frequently.
No action is required.
IFPD
Manages interfaces, maintains the interface database, and processes interface status change events.
There are a large number of interfaces, interface link status flaps, or optical transceivers become faulty.
No action is required.
ITSK
Sends, receives, and distributes various protocol packets.
A large number of protocol packets are sent and received.
No action is required.
L2
Centrally schedules Layer 2 service tasks, and supports the MGR, ErrorDown, BPTNL, LNP, VCMP, MFLP, VLAN, and QinQ features.
- LNP: There are too many interfaces.
- VCMP: VLANs are frequently deleted or created.
- BPTNL: A large number of packets are transparently transmitted.
- LNP: This feature rarely causes high CPU usage. If the problem occurs, check the cause of interface flapping and avoid frequent flapping.
- VCMP: Do not create or delete VLANs frequently.
- BPTNL: Configure transparent transmission of protocol packets on interfaces.
L2_P
Supports LACP, HGMP, 3AH, and ELMI features.
-
-
L2_R
Supports ERPS, RRPP, and SEP features.
Incorrect connections exist after ERPS/RRPP/SEP is deployed and the device suffers from a TC packet attack.
Ensure that physical loops are closed.
L2IF
Processes real-time backup and batch backup of MAC address and VLAN information.
-
-
LLDP
Sends, receives, and processes LLDP protocol packets.
The device receives a large number of LLDP protocol packets because it has too many LLDP neighbors.
Reduce the number of LLDP neighbors on the device.
LINK
Centrally schedules link layer tasks.
Multiple tasks are performed to process many service messages.
No action is required.
PARITY_CHECK
Detects soft errors in entries.
Soft errors occur in entries.
-
QOS
Processes QoS services.
There are too many QoS messages.
Reduce QoS configurations.
SAM
Delivers authentication entries to the interface card.
A large number of users go online.
Reduce the number of authentication users.
SAPP
Manages the application layer protocol dictionary and whitelist, maintains software entries, and instructs the adaptation layer to set chip status.
It will not cause high CPU usage.
No action is required.
SPM
Manages the energy-saving function.
It will not cause high CPU usage.
No action is required.
TARP
Provides the ARP-Ping detection function.
ARP-Ping detection is manually performed.
Reduce the frequency of ARP-Ping detection.
TM
Distributes authentication entries.
A large number of users go online.
Reduce the number of authentication users.
TNLM
Manages tunnels.
Tunnel flapping occurs.
Analyze the tunnel that flaps and shield the flapping source.
TNQA
Provides the NQA client function.
Too many NQA test instances are configured and the execution period is too short.
Control the NQA specification or prolong the execution period.
TRUN
Eth-Trunk adaptation task, which processes Eth-Trunk status change events and LACP protocol packets.
There are a large number of Eth-Trunks, interface status flaps, or optical transceivers become faulty.
Ensure that the interfaces and optical transceivers are normal: Check whether an interface frequently alternates between Up and Down states according to log or alarm information. If so, check whether the optical transceiver on the interface is faulty or a non-Huawei-certified optical transceiver is used. Additionally, analyze the configuration and traffic volume on the interface.
TUNL
Processes control and configuration messages in the TUNNEL module.
The same source interface is configured for a large number of tunnels, and the interface status or configuration is checked; or keepalive is configured on a large number of GRE tunnel interfaces.
This task rarely causes high CPU usage. If the problem occurs, do not configure keepalive on many GRE tunnel interfaces.
- Check the current CPU usage.
- Collect the following information:
- Device information
Information Type
Command View
Command
Version information
Diagnostic view
vrbd
Patch information
All views
display patch-information
Startup information
All views
display startup
Configuration information
All views
display current-configuration
File system information
All views
dir flash:/
- Log files
Export all log files (in the .dblg, .log, .dblg.zip, or .log.zip format) that record the fault occurrence time in the flash:/logfile directory using FTP or through the web platform.
- Device information