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.


Event Reference

OceanStor Dorado V3 Series V300R001

This document is applicable to OceanStor Dorado5000 V3, Dorado6000 V3 and Dorado18000 V3. This document describes the basic knowledge about the events of storage system in terms of event definition, event level, impact on the system, possible cause, and handling procedure. The document that you browse online matches the latest C version of the product. Click Download to download documents of other C versions.

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).
0xF03360002 Usage Exceeded The Threshold

0xF03360002 Usage Exceeded The Threshold


Usage exceeded the threshold.

Applicable Model

Applicable to all models.



Event Level

Automatically Cleared




Impact on the System

The service latency is prolonged if the performance index is too high.

Possible Causes

The service load on the storage device is heavy or the threshold is improperly configured.


  1. Check whether the threshold is properly configured.

    1. If no, set the threshold to a proper range. If the alarm persists=> Step2.
    2. If yes=> Step2.

  2. Check whether the alarms are generated from disks.

    1. If yes=> Step3.
    2. If no=> Step5.

  3. Log in to DeviceManager of the device and check whether alarms about disks exist.

    1. If yes=> Step4.
    2. If no=> Step8.

  4. Fixed the disk alarms on DeviceManager and check whether the alarms are cleared.

    1. If no=> Step8.

  5. Log in to DeviceManager of the device and check whether alarms about ports, disks, or power supplies exist.

    1. If yes, troubleshoot the problem by following the corresponding alarm clearing suggestions. After the operation is complete, if the alarm persists=> Step6.
    2. If no=> Step6.

  6. View the usage of other front-end ports and check whether there is an idle port with 0 usage.

    1. If yes, migrate part of services to the idle front-end port and enable load balancing of services on the port. If the alarm persists=> Step7.
    2. If no=> Step7.

  7. Add a front-end Interface module, migrate part of services to the new port, and enable load balancing of services on the port to check whether the alarm is cleared.

    1. If no=> Step8.

  8. Collect related information and contact technical support engineers.
Updated: 2018-10-19

Document ID: EDOC1000141827

Views: 95130

Downloads: 181

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next