Message Severity Levels; Responding To A System Message; Looking Up A System Message - Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base Reference Manual

Message Severity Levels

There are four levels of severity for messages, ranging from Critical (1) to Info (4). In general, the
definitions are wide ranging and are to be used as general guidelines for troubleshooting. For all
cases, you should look at each specific error message description thoroughly before taking action.
System messages have the following severity levels.
1 = CRITICAL
2 = ERROR
3 = WARNING
4 = INFO

Responding to a System Message

This section provides procedures on gathering information on system messages, including:

Looking Up a System Message

Error messages in this manual are arranged alphabetically. To look up an error message, copy
down the module (see
Contents to determine the location of the information for that error message.
The following information is provided for each message:
•
•
•
•
•
Fabric OS Message Reference
53-1000600-02
Critical-level messages indicate that the software has detected serious problems that will
cause a partial or complete failure of a subsystem if not corrected immediately; for example, a
power supply failure or rise in temperature must receive immediate attention.
Error-level messages represent an error condition that does not impact overall system
functionality significantly. For example, error-level messages might indicate time-outs on
certain operations, failures of certain operations after retries, invalid parameters, or failure to
perform a requested operation.
Warning-level messages highlight a current operating condition that should be checked or it
might lead to a failure in the future. For example, a power supply failure in a redundant system
relays a warning that the system is no longer operating in redundant mode unless the failed
power supply is replaced or fixed.
Info-level messages report the current non-error status of the system components: for
example, detecting online and offline status of a fabric port.
•
Looking Up a System Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
•
Gathering Information About the Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
•
Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
•
Panic Dump and Core Dump Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
•
Trace Dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
•
supportSave Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 5
Module and code name for the error
Message text
Probable cause
Recommended action
Message severity

Responding to a System Message

on page 13) and the error code and compare this with the Table of
1
11