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

E9000 Server V100R001 HMM Alarm Handling 19

This document describes E9000 server alarms in terms of the meaning, impact on the system, possible causes, and solutions.
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).
SEM

SEM

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.

Attributes

Attribute

Description

Trap OID

1.3.6.1.4.1.2011.5.25.129.2.4.1

Trap severity

Critical

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

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 Huawei technical support personnel.

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.4.2 hwCPUUtilizationResume

Description

The CPU usage falls below the pre-set clear 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 every sampled CPU usage is below the pre-set clear threshold, this alarm was generated.

Attributes

Attribute

Description

Trap OID

1.3.6.1.4.1.2011.5.25.129.2.4.2

Trap severity

Major

Alarm type

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.4.1 hwCPUUtilizationRisingAlarm

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

Impact on the System

Services are not affected.

Possible Causes

The CPU usage fell below the pre-set overload threshold.

Procedure
  • This alarm message is informational only, and no action is required.

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.6.1 hwStorageUtilizationRisingAlarm

Description

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

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

Attributes

Attribute

Description

Trap OID

1.3.6.1.4.1.2011.5.25.129.2.6.1

Trap severity

Minor

Match trap

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.6.2 hwStorageUtilizationResume

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

UsageValue

Storage usage

Unit

Unit

UsageThreshold

Overload threshold

Impact on the System
  1. If services cannot successfully obtain memory resources, the system automatically restarts.
  2. If the remaining space in the storage is insufficient, the log function and software upgrade are affected.
Possible Causes

Cause 1: The memory usage exceeded the pre-set overload threshold.

Cause 2: The storage usage exceeded the pre-set overload threshold.

Procedure
  • Cause 1: The memory usage exceeded the pre-set overload threshold.
    1. Run the display memory threshold command to check the memory usage and its upper threshold.
      • If memory usage exceeds the overload threshold, go to Step 2.
      • If memory usage is below the overload threshold, go to Step 4.
    2. Delete unnecessary services and configurations to reduce memory 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 memory threshold threshold-value [ restore restore-threshold-value ] [ slot slot-id ] command to adjust the memory 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 Huawei technical support personnel.
  • Cause 2: The storage usage exceeded the pre-set overload threshold.
    1. Run the cd flash: command to access the directory, and then run the dir command to view the storage usage.
      • If storage usage is higher than the overload threshold, go to Step 2.
      • If storage usage is lower than the overload threshold, go to Step 3.
    2. Run the delete /unreserved *.cc command and the delete /unreserved *.PAT command to delete the unnecessary .cc and .PAT files. Run the reset recycle-bin command to clear the cache and reduce storage usage.Then check whether the alarm is cleared.
      • For a stack system, you need to perform this step on both the master and slave devices. Before performing this step, run the cd Stack_ID#flash: command to access the directory of the corresponding storage medium.
      • If the recovery alarm is generated, the fault is rectified.
      • If this alarm persists, go to Step 3.
    3. Collect log messages and contact Huawei technical support personnel.

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.6.2 hwStorageUtilizationResume

Description

The storage usage falls below the pre-set clear threshold.(TrapSeverity=[TrapSeverity], ProbableCause=[ProbableCause], EventType=[EventType], PhysicalIndex=[PhysicalIndex], PhysicalName=[PhysicalName], RelativeResource=[RelativeResource], UsageType=[UsageType], SubIndex=[SubIndex], UsageValue=[UsageValue], Unit=[Unit], UsageThreshold=[UsageThreshold])

Memory or storage space usage was sampled for a period of time. In one sampling period (overload times x sampling interval), if every sampled memory or storage space usage was below the pre-set clear threshold, this alarm was generated.

Attributes

Attribute

Description

Trap OID

1.3.6.1.4.1.2011.5.25.129.2.6.2

Trap severity

Major

Match trap

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.6.1 hwStorageUtilizationRisingAlarm

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

UsageValue

Storage usage

Unit

Unit

UsageThreshold

Overload threshold

Impact on the System

Services are not affected.

Possible Causes

Cause 1: The memory usage fell below the pre-set overload threshold.

Cause 2: The storage usage fell below the default overload threshold.

Procedure
  • This alarm message is informational only, and no action is required.

SYSTEM_1.3.6.1.4.1.2011.5.25.219.2.11.1 hwSystemConfigError

Description

A system configuration error occurs. ( EntityTrapFaultID = [EntityTrapFaultID])

The system configuration was incorrect.

Attributes

Attribute

Description

Trap OID

1.3.6.1.4.1.2011.5.25.219.2.11.1

Trap severity

Critical

Match trap

SYSTEM_1.3.6.1.4.1.2011.5.25.219.2.11.2 hwSystemConfigResume

Parameters

Parameter

Description

EntityTrapFaultID

Trap error codes.

  • EntityTrapFaultID=144130 indicates that the package versions of the master and slave boards were inconsistent.
Impact on the System

The slave board cannot be activated when the package versions of the master and slave boards are inconsistent.

Possible Causes

The package versions of the master and slave boards were inconsistent.

Procedure
  1. Run the startup system-software system-file [ all | slave-board | slot slot-id ] command to configure the slave board version to be consistent with the master board version. Run the reset command to reset the slave board. Wait for a period of time, and then check whether the alarm is cleared.
  • If yes, go to Step 3.
  • If No, go to Step 2.
  1. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.
  2. End.

SYSTEM_1.3.6.1.4.1.2011.5.25.219.2.11.2 hwSystemConfigResume

Description

The system configuration error has been rectified. ( EntityTrapFaultID = [EntityTrapFaultID])

The system configuration was corrected.

Attributes

Attribute

Description

Trap OID

1.3.6.1.4.1.2011.5.25.219.2.11.2

Trap severity

Warning

Match trap

SYSTEM_1.3.6.1.4.1.2011.5.25.219.2.11.1 hwSystemConfigError

Parameters

Parameter

Description

EntityTrapFaultID

Trap error codes.

  • EntityTrapFaultID=144130 indicates that the package versions of the master and slave boards were inconsistent.
Impact on the System

Services are not affected.

Possible Causes

Cause 1: The package versions of the master and slave boards changed from being inconsistent to being consistent.

Cause 2: The versions of the PAF and startup package changed from being inconsistent to being consistent.

Procedure
  • This alarm message is informational only, and no action is required.
Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 192932

Downloads: 1565

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