HP StorageWorks 1606 Brocade Fabric OS Troubleshooting and Diagnostics Guide v - Page 89

Working With Diagnostic Features, In this About Fabric OS diagnostics, Diagnostic information

Get HP StorageWorks 1606 - Extension SAN Switch PDF manuals and user guides View all HP StorageWorks 1606 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 89 highlights

Chapter Working With Diagnostic Features 11 In this chapter •About Fabric OS diagnostics 75 •Diagnostic information 75 •Power-on self test 76 •Switch status 78 •SpinFab and portTest 80 •Port information 81 •Equipment status 84 •System message log 86 •Port log 87 •Syslogd configuration 89 •Automatic trace dump transfers 90 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: • 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. 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 supportShow or supportSave commands and FTP'd off the switch, but when you are collecting information from commands, this information has to be captured using a Telnet client. Fabric OS Troubleshoot and Diagnostics Guide 75 53-1001340-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
Fabric OS Troubleshoot and Diagnostics Guide
75
53-1001340-01
Chapter
11
Working With Diagnostic Features
In this chapter
•
About Fabric OS diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
75
•
Diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
75
•
Power-on self test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
76
•
Switch status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
78
•
SpinFab and portTest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
80
•
Port information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
81
•
Equipment status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
84
•
System message log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
86
•
Port log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
87
•
Syslogd configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
89
•
Automatic trace dump transfers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
90
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:
•
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.
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 supportShow or supportSave commands and FTP’d off
the switch, but when you are collecting information from commands, this information has to be
captured using a Telnet client.