ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.14.1 hwCPUUtilizationRising

Description

ENTITYTRAP/2/CPUUSAGERISING: OID [oid] CPU utilization exceeded the pre-alarm threshold.(Index=[INTEGER], HwEntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityThresholdType=[INTEGER], EntityThresholdWarning=[INTEGER], EntityThresholdCurrent=[INTEGER], EntityTrapFaultID=[INTEGER])

The CPU usage exceeds the alarm threshold.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.219.2.14.1	Major	equipmentAlarm(5)

Parameters

Name	Meaning
OID	Indicates the ID of a MIB object.
Index	Indicates the entity index.
HwEntityPhysicalIndex	Indicates a physical entity index.
PhysicalName	Indicates the physical entity name.
EntityThresholdType	Indicates the threshold type.
EntityThresholdWarning	Indicates the alarm threshold.
EntityThresholdCurrent	Indicates the current value.
EntityTrapFaultID	Indicates the error code.

Impact on the System

The CPU usage exceeds the alarm threshold.

If the threshold is not high (for example, 50% or 60%), services are not affected. If the threshold is high (for example 80%), high CPU usage in a very short period does not affect services; however, long-term high CPU usage may delay service processing.

Possible Causes

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

Cause 2: Currently, the traffic volume is high. For example, STAs frequently roam or go online or offline.

Cause 3: The device provides too many services.

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

Procedure

Run the display cpu-usage configuration command to check the alarm threshold for CPU usage. Check whether the alarm threshold is set properly.
1. If so, go to 3.
2. If not, go to 2.
Run the set cpu-usage threshold command to set a proper alarm threshold for CPU usage. After that, check whether the alarm persists.
1. If the 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.
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 4.
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

ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.14.2 hwCPUUtilizationResume