Dell PowerVault 50F Dell PowerVault 51F 8-Port Fibre Channel Switch Insta - Page 105

Troubleshooting, Diagnostic Overview, Diagnostic Error Messages

Page 105 highlights

CHAPTER 5 Troubleshooting support.dell.com This chapter discusses troubleshooting, diagnostic testing, and error messages, including the following sections: • Diagnostic overview • Status and activity indicators Diagnostic Overview The switch is designed for maintenance-free operation. When there is a suspected failure, the switch has self-diagnostic capabilities to aid in isolating any equipment or fabric failures. The switch supports power-on self-tests (POSTs) and diagnostic tests. The diagnostic tests determine the switch's status and isolate problems. Telnet commands are used to determine the switch's status, error conditions, and switch operating statistics. Diagnostic Error Messages Error messages are stored in volatile random-access memory (RAM) and are lost whenever power is removed from the switch. Access the error message log to view error messages before removing power from the switch. Error messages are available both via the switch's front panel RS-232 serial port and through a Telnet session. These messages are also stored in the system log and are displayed when the errShow command is executed. If you run the portStatsShow or the diagShow command prior to running a test on the switch, errors may appear as a result of the normal synchronization process. These errors should be addressed if the number of errors found increases when running the portStatsShow command again. Where multiple probable cause and corrective actions are listed following an error message, they are listed with the most probable first and the least probable last. If any port fails during a diagnostic test, it is marked BAD in the status display and is ignored (not tried) until the system is rebooted. Troubleshooting 5-1

  • 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
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156

support.dell.com
Troubleshooting
5-1
CHAPTER 5
Troubleshooting
This chapter discusses troubleshooting, diagnostic testing, and error messages,
including the following sections:
Diagnostic overview
Status and activity indicators
Diagnostic Overview
The switch is designed for maintenance-free operation. When there is a suspected
failure, the switch has self-diagnostic capabilities to aid in isolating any equipment or
fabric failures.
The switch supports power-on self-tests (POSTs) and diagnostic tests. The diagnostic
tests determine the switch’s status and isolate problems.
Telnet commands are used to determine the switch’s status, error conditions, and
switch operating statistics.
Diagnostic Error Messages
Error messages are stored in volatile random-access memory (RAM) and are lost
whenever power is removed from the switch. Access the error message log to view
error messages before removing power from the switch.
Error messages are available both via the switch’s front panel RS-232 serial port and
through a Telnet session. These messages are also stored in the system log and are
displayed when the
errShow
command is executed.
If you run the
portStatsShow
or the
diagShow
command prior to running a test on
the switch, errors may appear as a result of the normal synchronization process.
These errors should be addressed if the number of errors found increases when run-
ning the
portStatsShow
command again.
Where multiple probable cause and corrective actions are listed following an error
message, they are listed with the most probable first and the least probable last.
If any port fails during a diagnostic test, it is marked
BAD
in the status display and is
ignored (not tried) until the system is rebooted.