HP StorageWorks Fabric OS 5.X Diagnostics and System Error Messages Reference Guide (AA-RVHZB-TE, September 2005)

Fabric OS 5.x diagnostics and system error messages reference guide 89
Gathering information
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:
•Is the switch down?
• Is it a standalone switch?
• How large is the fabric?
• Is the fabric redundant?
5. Run the errDump command on each logical switch.
6. Run supportFtp (as needed) to set up automatic FTP transfers, and then run the supportSave
command.
7. 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?
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 )
13.What and when were the last actions or changes made to the system?
System module descriptions
<Link>Table 4 provides a summary of the system modules for which messages are documented in this
reference guide; the system modules are listed alphabetically by name.
Table 4 System module descriptions
System
module
Description
AUTH Authentication error messages indicate problems with the authentication
module of the Fabric OS.
BL Blade error messages are a result of faulty hardware, transient
out-of-memory conditions, ASIC errors, or inconsistencies in the software
state between a blade and the EM (environment monitor) module.
BLL Bloom is the name of the ASIC used as the building block for
third-generation hardware platforms.
CER This is the core edge routing module on the SilkWorm director platforms.