Error Condition Reporting Characteristics - HP StorageWorks 6100 - Enterprise Virtual Array User Manual

The error conditions are prioritized by severity—from most severe to least. The most severe condition
takes precedence and is reported first when multiple errors are detected. The reporting characteristics
for each error condition are listed in
Table 18 Error condition reporting characteristics
Error condition
UNRECOVERABLE
CRITICAL
NONCRITICAL
INFORMATION
1
The pattern occurs when the condition is the most severe active condition.
Error queue
The EMU maintains an internal error queue for storing error conditions. Each error condition remains
in the error queue until the problem is corrected, or for at least 15 seconds after the error is reported.
This ensures that, when there are multiple errors or a recurring error, each can be displayed. Each
entry in the error queue can be displayed using a combination of the top and bottom buttons. Each
error entry in the queue contains the element type, the element number, and the error code.
Correcting the error removes the associated condition from the error queue. Replacing the EMU will
also clear the error conditions. The order in which the EMU displays the error queue information is
based on two factors:
• The severity of the error
• The time the error occurred
The most severe error in the queue always has precedence, regardless of how long less severe errors
have been in the queue. This ensures that the most severe errors are displayed immediately.
NOTE:
When viewing an error, the occurrence of a more severe error takes precedence and the display
changes to the most severe error.
The earliest reported condition within an error type has precedence over errors reported later. For
example, if errors at all levels have occurred, the EMU displays them in the following order:
1.
UNRECOVERABLE errors in the sequence they occurred.
2. CRITICAL errors in the sequence they occurred.
3.
NONCRITICAL errors in the sequence they occurred.
4. INFORMATION conditions in the sequence they occurred.
Error condition report format
Each EMU detected condition generates a condition report containing three pieces of information.
Element type The first two-digit hexadecimal display defines the element type reporting the problem.
•
The format for this display is e.t. with a period after each character. Valid element types are 0.1.
through F.F.
Table 18.
Takes precedence over
All other conditions
NONCRITICAL and INFORMATION
INFORMATION
No other conditions
HP StorageWorks 4x00/6x00/8x00 Enterprise Virtual Array user guide
Audible alarm pattern
On continuously
Sounds three times per alarm
cycle
Sounds two times per alarm
cycle
Sounds once per alarm cycle
1
73