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

Reminder

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

upgrade

Alarm Handling

CloudEngine 12800 and 12800E V200R005C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
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).
SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.4.1 hwCPUUtilizationRisingAlarm

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.4.1 hwCPUUtilizationRisingAlarm

Description

The CPU usage exceeded the pre-set overload threshold.(TrapSeverity=[TrapSeverity], ProbableCause=[ProbableCause], EventType=[EventType], PhysicalIndex=[PhysicalIndex], PhysicalName=[PhysicalName], RelativeResource=[RelativeResource], UsageType=[UsageType], SubIndex=[SubIndex], CpuUsage=[CpuUsage], Unit=[Unit], CpuUsageThreshold=[CpuUsageThreshold])

CPU usage was sampled for a period of time. In one sampling period (overload times x sampling interval), if each CPU usage sample exceeded the pre-set overload threshold, this alarm was generated.

This trap is supported only on the Admin-VS.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Alert

Mnemonic Code

hwCPUUtilizationRisingAlarm

Trap OID

1.3.6.1.4.1.2011.5.25.129.2.4.1

Alarm ID

0x00010084

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.4.2 hwCPUUtilizationResume

Parameters

Parameter Description

TrapSeverity

Alarm severity

ProbableCause

Possible cause

EventType

Alarm type

PhysicalIndex

Physical index

PhysicalName

Entity name

RelativeResource

Relevant resource name

UsageType

Overload type

SubIndex

Entity sub-index

CpuUsage

CPU usage

Unit

Unit

CpuUsageThreshold

Overload threshold

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.129.1.1

hwBaseTrapSeverity

N/A

1.3.6.1.4.1.2011.5.25.129.1.2

hwBaseTrapProbableCause

N/A

1.3.6.1.4.1.2011.5.25.129.1.3

hwBaseTrapEventType

N/A

1.3.6.1.2.1.47.1.1.1.1.7

entPhysicalName

entPhysicalIndex;

1.3.6.1.4.1.2011.5.25.129.1.4

hwBaseTrapRelativeResource

N/A

1.3.6.1.4.1.2011.5.25.129.1.7.1.3

hwBaseUsageValue

entPhysicalIndex;

hwBaseUsageType;

hwBaseUsageIndex;

1.3.6.1.4.1.2011.5.25.129.1.7.1.4

hwBaseUsageUnit

entPhysicalIndex;

hwBaseUsageType;

hwBaseUsageIndex;

1.3.6.1.4.1.2011.5.25.129.1.7.1.5

hwBaseUsageThreshold

entPhysicalIndex;

hwBaseUsageType;

hwBaseUsageIndex;

Impact on the System

If the CPU usage is high for a long period of time, services cannot be processed in time, and the system performance is affected. The system performance, for example, time taken to process user operations, neighbor status, and route convergence performance, will be affected.

Possible Causes

The CPU usage exceeded the pre-set overload threshold.

Procedure

  • Cause: The CPU usage exceeded the pre-set overload threshold.
    1. Run the display cpu threshold command to check the CPU usage and its overload threshold.

      • If CPU usage exceeds the overload threshold, go to Step 2.
      • If CPU usage is below the overload threshold, go to Step 4.

    2. Delete unnecessary services and configurations to reduce CPU usage, and then check whether the alarm is cleared.

      • If the recovery alarm is generated, the fault is rectified.
      • If this alarm persists, go to Step 3.

    3. Run the set cpu threshold threshold-value [ restore restore-threshold-value ] [ slot slot-id ] command to adjust the overload threshold, and then check whether the alarm is cleared.

      • If the recovery alarm is generated, the fault is rectified.
      • If this alarm persists, go to Step 4.

    4. Collect log messages and contact technical support personnel.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039527

Views: 69736

Downloads: 21

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