ALM-303046690 CPU Usage Reached the Threshold
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 reached the alarm threshold.
Attribute
Alarm ID |
Alarm Severity |
Alarm Type |
---|---|---|
303046690 |
Critical |
equipmentAlarm |
Parameters
Name |
Meaning |
---|---|
OID |
Indicates the MIB object of the alarm. |
Index |
Indicates the entity index. |
HwEntityPhysicalIndex |
Indicates the 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
- The alarm threshold of the CPU usage was low.
- The traffic volume was high. For example, STAs frequently roam or go online or offline.
- The device provided too many services.
- The device was attacked, causing high CPU usage.
Procedure
- Run the display cpu-usage configuration command to check the alarm threshold for CPU usage to determine whether the alarm threshold is set properly.
- If so, go to step 3.
- If not, go to step 2.
- Run the set cpu-usage threshold command to set a proper alarm threshold for CPU usage. After that, check whether the alarm persists.
- If so, go to step 3.
- If not, no further action is required.
- Check whether the traffic volume is high (for example, STAs frequently roam or a large number of STAs frequently go online or offline) and check whether the system runs properly if the traffic volume is high.
- If the traffic volume is high and the system runs normally, no further action is required.
- If the traffic volume is low, go to step 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.
- If the alarm persists after some services are deleted, go to step 4.
- If the alarm is cleared, no further action is required.
- Collect trap, log, and configuration information, as well as the CPU usage information in step 4, and contact technical support engineers.
Related Information
None
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot