Looking Up A System Message; Gathering Information About The Problem - Brocade Communications Systems 8 Reference

1
Responding to a System Message

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:
•
•
•
•
•

Gathering Information About the Problem

Common steps and questions to ask yourself when troubleshooting a system message are as
follows:
1. What is the current Fabric OS level?
2. What is the switch hardware version?
3. Is the switch operational?
4. Assess impact and urgency:
5. Run the errDump command on each logical switch.
6. Run the supportFtp command (as needed) to set up automatic FTP transfers, and then run the
7.
8. Did a failover occur?
9. Was security enabled?
10. Was POST enabled?
11. Are serial port (console) logs available?
12. Which CP was master? (only applicable to the Brocade DCX, 12000, 24000, or 48000)
13. What and when were the last actions or changes made to the system?
12
Table 5
Module and code name for the error
Message text
Probable cause
Recommended action
Message severity
-
Is the switch down?
-
Is it a standalone switch?
-
How large is the fabric?
-
Is the fabric redundant?
supportSave command.
Document the sequence of events by answering the following questions:
-
What happened just prior to the problem?
-
Is the problem repeatable?
-
If so, what are the steps to produce the problem?
-
What configuration was in place when the problem occurred?
on page 14) and the error code and compare this with the Table of
Fabric OS Message Reference
53-1001767-01