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

Identifying Media-Related Issues, Component Tests Overview, Table 17: Component Test Descriptions

Page 218 highlights

Troubleshooting Identifying Media-Related Issues Use the following section to narrow down media-related issues in the fabric. Component Tests Overview Hardware diagnostics available on switches can be classified into two different types of tests: ■ Structural tests - do basic tests of the switch circuit. When structural tests fail, replace the main board. ■ Functional tests - verify the intended operational behavior of the switch by running frames through ports or bypass circuitry. Table 17: Component Test Descriptions Test Name crossporttest fporttest loopporttest spinfab Operands [-nframes count] [-lb_mode mode][-spd_mode mode] [-gbic_mode mode] [-norestore mode] [-ports itemlist] [-nframes count] [-ports itemlist] [-seed payload_pattern] [-width pattern_width] [-size pattern_size] [-nframes count] [-ports itemlist][-seed payload_pattern] [-width pattern_width] [ nMillionFrames [, ePortBeg [, ePortEnd [, setFail]]]] Checks Functional test of port external transmit and receive path. The crossport is set to loopback using an external cable by default. However, this command can be used to check internal components by setting the lb operand to 5. Tests component to/from HBA. Used to test online F_Port devices, N_Port devices and SFPs/GBICs. Only tests components attached to switch that are on a FC arbitrated loop. Tests components to/from a neighbor switch, such as ISLs and SFPs/GBICs between switches. 218 Fabric OS Procedures Version 3.1.x/4.1.x User Guide

  • 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
218
Fabric OS Procedures Version 3.1.x/4.1.x User Guide
Identifying Media-Related Issues
Use the following section to narrow down media-related issues in the fabric.
Component Tests Overview
Hardware diagnostics available on switches can be classified into two different
types of tests:
Structural tests - do basic tests of the switch circuit. When structural tests fail,
replace the main board.
Functional tests - verify the intended operational behavior of the switch by
running frames through ports or bypass circuitry.
Table 17:
Component Test Descriptions
Test Name
Operands
Checks
crossporttest
[
-nframes
count
]
[
-lb_mode
mode
][
-spd_mode
mode
]
[
-gbic_mode
mode
] [
-norestore
mode
]
[
-ports
itemlist
]
Functional test of port external transmit
and receive path.
The
crossport
is set to loopback using
an external cable by default. However,
this command can be used to check
internal components by setting the
lb
operand to 5.
fporttest
[-
nframes
count
] [-
ports
itemlist
]
[-
seed
payload_pattern
]
[-
width
pattern_width
] [-
size
pattern_size
]
Tests component to/from HBA.
Used to test online F_Port devices,
N_Port devices and SFPs/GBICs.
loopporttest
[
-nframes
count
]
[
-ports
itemlist
][
-seed
payload_pattern
]
[
-width
pattern_width
]
Only tests components attached to
switch that are on a FC arbitrated loop.
spinfab
[
nMillionFrames
[,
ePortBeg
[,
ePortEnd
[,
setFail
]]]]
Tests components to/from a neighbor
switch, such as ISLs and SFPs/GBICs
between switches.