WLAN_1.3.6.1.4.1.2011.6.139.13.1.1.7 hwApCpuOverloadTrap

Description

WLAN/4/AP_CPU_OVERLOAD: OID [oid] AP CPU overload notify.(APMAC=[OPAQUE], APName=[STRING], ApCpuRate=[INTEGER], the top three thread CPU occupancy are [STRING], APID=[INTEGER])

The AP's CPU usage exceeds the upper threshold.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.6.139.13.1.1.7	Warning	equipmentAlarm(5)

Parameters

Name	Meaning
oid	Indicates the ID of a MIB object.
APMAC	Indicates the AP's MAC address.
APName	Indicates the AP name.
ApCpuRate	Indicates the AP's CPU usage.
[STRING2]	Indicates the top 3 threads with the highest CPU usage.
APID	Indicates the AP ID.

Impact on the System

The CPU usage exceeds the upper threshold. If the threshold is not high (for example, 50% or 60%), services are not affected. If the threshold is high (for example 90%), the AP reports the alarm, and packet loss may occur on the AP or the AP may be disconnected.

Possible Causes

Cause 1: The alarm threshold of the CPU usage is low.

Cause 2: The device provides too many services.

Cause 3: The device is attacked, causing high CPU usage.

Procedure

Run the display ap-system-profile command to check the alarm threshold for AP's CPU usage. Check whether the alarm threshold is set properly.
1. If so, go to 3.
2. If not, go to 2.
Run the cpu-usage threshold command to set a proper alarm threshold for CPU usage. After that, check whether the alarm persists.
1. If this alarm persists, go to 3.
2. If the alarm is cleared, go to 6.
Check whether the traffic volume is high. For example, check whether STAs frequently roam or a large number of STAs frequently go online or offline and check that the system runs normally.
1. If the traffic volume is high and the system runs normally, ignore the alarm.
2. If the traffic volume is low, go to 4.
Log in to the AP and run the display cpu-usage command in the diagnostic view to check the CPU usage of each task. Locate tasks with high CPU usage and delete unnecessary services or configurations to reduce the CPU usage.
1. If the alarm persists after some services are deleted, go to 5.
2. If the alarm is cleared, go to 6.
Collect trap, log, and configuration information, as well as the CPU usage information in 4, and contact technical support personnel.
If the alarm is cleared, no further action is required.

Related Information

None