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

Event Reference for File

OceanStor Dorado V3 Series V300R002

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.
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).
0xF03360003 Service Time Exceeded The Threshold

0xF03360003 Service Time Exceeded The Threshold

Description

Service time exceeded the threshold.

Applicable Model

Applicable to all models.

Attribute

ID

Event Type

Event Level

Automatically Cleared

0xF03360003

Alarm

Warning

Yes

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.

Procedure

  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.

  1. 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 is not cleared=> Step3.
    2. If no=> Step3.

  2. Continue to check whether there are alarms of Avg. CPU usage on controllers.

    1. If yes, troubleshoot the problem by following the corresponding alarm clearing suggestions of controller Avg. CPU usage. If the alarm persists=> Step4.
    2. If no=> Step4.

  3. Check whether there are performance alarms about front-end port usage.

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

  4. Check whether there are performance alarms about disk usage.

    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.

  5. Collect related information and contact technical support engineers.
Translation
Download
Updated: 2019-07-17

Document ID: EDOC1100076630

Views: 20350

Downloads: 5

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