In This Chapter; About Fabric Os Diagnostics; Diagnostic Information - Brocade Communications Systems 8 Troubleshooting And Diagnostics Manual

Working With Diagnostic Features

In this chapter

About Fabric OS diagnostics

The purpose of the diagnostic subsystem is to evaluate the integrity of the system hardware.
Diagnostics are invoked in the one of the following ways:
•
•
•
The error messages generated during these test activities are sent to the serial console and system
message logs, whose output formats may differ slightly.
Use the diagHelp command to receive a list of all available diagnostic commands.
See the Fabric OS Command Reference for a complete description of each command.

Diagnostic information

On the switch you can enter the supportShow command to dump important diagnostic and status
information to the session screen, where you can review it or capture its data. If you are using a
Telnet client, you may have to set up the client to capture the data prior to opening the session
Most information can be captured using the supportSave command and FTP'd off the switch, but
when you are collecting information from specialized commands, such as supportShow, this
information has to be captured using a Telnet client.
Fabric OS Troubleshooting and Diagnostics Guide
53-1001769-01
•
About Fabric OS diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
•
Diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
•
Power-on self test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
•
Switch status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
•
SpinFab and portTest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
•
Port information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
•
Equipment status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
•
System message log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
•
Port log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
•
Syslogd configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
•
Automatic trace dump transfers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Automatically during the power-on self test (POST).
Automatically on an individual blade whenever it is installed into a director chassis.
Manually using Fabric OS CLI commands.
Chapter
10
85