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


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


Alarm Handling

S9300, S9300E, and S9300X V200R010C00

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).
BASETRAP_1. hwStorageUtilizationRisingAlarm

BASETRAP_1. hwStorageUtilizationRisingAlarm


BASETRAP/2/STORAGEUSAGERISING: OID [oid] Storage utilization exceeded the pre-alarm threshold. (Index=[INTEGER], BaseUsagePhyIndex=[INTEGER], UsageType=[INTEGER], UsageIndex=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], PhysicalName="[OCTET]", RelativeResource="[OCTET]", UsageValue=[INTEGER], UsageUnit=[INTEGER], UsageThreshold=[INTEGER])

This alarm is generated when the usage of a storage device exceeds the upper threshold.


Alarm ID Alarm Severity Alarm Type Major processingErrorAlarm(4)


Name Meaning
[oid] Indicates the ID of the MIB object.
Index Indicates the index of the entity. The entity in an alarm on storage device usage is a board.
BaseUsagePhyIndex Indicates the index of the physical entity. The entity in an alarm on storage device usage is a board.
UsageType Indicates the type of the alarm on usage.
UsageIndex Indicates the index of the sub-entity of the alarm entity. In the alarm on storage device usage, the fixed value of this parameter is 0.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

151: IANAITUPROBABLECAUSE_STORAGECAPACITYPROBLEM indicates the errors of storage device usage.

EventType Indicates the alarm type:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)
PhysicalName Indicates the name of the entity.
RelativeResource Indicates the name of the resource that is associated with the alarm.
UsageValue Indicates the usage of the storage.
UsageUnit Indicates the unit of the storage device usage. The unit is percent.
UsageThreshold Indicates the alarm threshold of storage device usage.

Impact on the System

Impact 1: If this alarm is not cleared immediately, the storage space will be insufficient to record logs and diagnostic information. In this case, the system running information and fault locating information will be missing.

Impact 2: The system operations on files may fail because of insufficient storage space.

Possible Causes

Cause 1

The storage device stores too many logs and too much diagnostic information.

Cause 2

The storage device stores too many unnecessary or expired files.


  1. Check the value of hwBaseUsageType in the reported alarm. Run the cd cfcard:\ command to access the CF card directory, and then run the dir command to check the used space and remaining space of the storage device.
  2. Run the dir command to check the list of files stored in the storage device and detailed information about files and directories, such as the file size and created logs. Check whether there are unnecessary or expired files that need to be deleted.

    • If so, go to step 3.
    • If not, go to step 6.

  3. Delete the unnecessary files or run the move command to move the files to other storage devices.

    Check whether the size of log files or diagnostic log files in the storage device is too large.

    • If so, go to step 4.
    • If not, go to step 5.

  4. Delete the log files or diagnostic log files or move the files to other storage devices.
  5. Check whether the alarm recovery message is received.

    • If so, the alarm handling ends.
    • If not, collect alarm information and configuration information, and then contact technical support personnel.

Updated: 2019-08-21

Document ID: EDOC1000142054

Views: 183801

Downloads: 44

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