HP StorageWorks MSA 2/8 HP StorageWorks Fabric OS Procedures V3.1.x/4.1.x User - Page 219

Check Switch Components, Cursory Debugging of Media Components

Page 219 highlights

Troubleshooting Check Switch Components The following sections describe how to troubleshoot the switch components. Cursory Debugging of Media Components The following procedure describes basic steps that can help to narrow down faulty media. 1. Log into the switch as admin. 2. Enter switchshow at the command line. Look for a known good portstate online or insync. 3. (Optional) Enter version at the command line. The version can be used to check the known buglist in the appropriate Release Notes. 4. Enter portErrShow at the command line. A error summary of all ports is displayed. 5. Glance over the port statistics. - Most numbers should be small. An excessively large number (such as one over 100,000) could indicate a bad transceiver. - Also check for rapidly rising error counts. Tip: The LLI_errs (Low Level Interrupt_errors) are the sum of the port's eight statistical error counters: ENC_in, CRC_err, TruncFrm, FrmTooLong, BadEOF, Enc_out, BadOrdSet, and DiscC3. Check portErrShow output to determine what generated the LLI_errs. 6. (Optional) Run tests if you still suspect a media problem. - To test components to and from a neighbor switch, see "Test Cascaded Switch ISL Links" on page 220. - To test a port's external transmit and receive path, see "Check Port's External Transmit and Receive Path" on page 225. - To test the internal components of a suspect switch, see "Test a Switches Internal Components" on page 222. - To test the components between a switch and a hub (and back), see "Test Components To and From the HBA" on page 222. Fabric OS Procedures Version 3.1.x/4.1.x User Guide 219

  • 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
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270

Troubleshooting
219
Fabric OS Procedures Version 3.1.x/4.1.x User Guide
Check Switch Components
The following sections describe how to troubleshoot the switch components.
Cursory Debugging of Media Components
The following procedure describes basic steps that can help to narrow down faulty
media.
1.
Log into the switch as admin.
2.
Enter
switchshow
at the command line.
Look for a known good portstate online or insync.
3.
(Optional) Enter
version
at the command line.
The version can be used to check the known buglist in the appropriate Release
Notes.
4.
Enter
portErrShow
at the command line.
A error summary of all ports is displayed.
5.
Glance over the port statistics.
Most numbers should be small. An excessively large number (such as one
over 100,000) could indicate a bad transceiver.
Also check for rapidly rising error counts.
Tip: The LLI_errs (Low Level Interrupt_errors) are the sum of the port's eight
statistical error counters:
ENC_in, CRC_err, TruncFrm, FrmTooLong,
BadEOF, Enc_out, BadOrdSet, and DiscC3. Check
portErrShow
output
to determine what generated the LLI_errs.
6.
(Optional) Run tests if you still suspect a media problem.
To test components to and from a neighbor switch, see “
Test Cascaded
Switch ISL Links”
on page 220.
To test a port’s external transmit and receive path, see “
Check Port’s
External Transmit and Receive Path”
on page 225.
To test the internal components of a suspect switch, see “
Test a Switches
Internal Components”
on page 222
.
To test the components between a switch and a hub (and back), see “
Test
Components To and From the HBA”
on page 222.