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

Specific Scenarios, Host Can Not See Target (Storage or Tape Devices), Check the Logical Connection

Page 199 highlights

Troubleshooting Specific Scenarios The following sections provide specific help with some of the most common SAN problems. Host Can Not See Target (Storage or Tape Devices) When a host cannot "see" its disks, the best way to troubleshoot the problem is to start in the middle half of the data path, figure out if the problem is "above" or "below" the data path, and keep dividing the suspect path in half until the problem is identified. There are two areas to check in the process of elimination: ■ Check the Logical Connection ■ Check the Simple Name Server (SNS) ■ Check for Zoning Discrepancies ■ Check Device Communication Check the Logical Connection Check Whether the Device is Logically Connected to the Switch 1. Enter the switchShow command. 2. Review the output and determine if the device is logically connected to the switch: - A device that is logically connected to the switch will be registered as an NX_Port. - A device that is not logically connected to the switch will be registered as something besides an NX_Port. - If the missing device is logically connected, move on to Check for the Device in the SNS. - If the missing device is not logically connected, eliminate the host and everything on that side of the data path from the suspect list. This includes all aspects of the host's OS, the HBA driver settings and binaries, the HBA Basic Input Output System (BIOS) settings, the HBA SFP, the cable going from the switch to the host, the SFP on the switch side of that cable, and all switch settings related to the host. Move on to Link Initialization Failure (Loop). Fabric OS Procedures Version 3.1.x/4.1.x User Guide 199

  • 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
199
Fabric OS Procedures Version 3.1.x/4.1.x User Guide
Specific Scenarios
The following sections provide specific help with some of the most common SAN
problems.
Host Can Not See Target (Storage or Tape Devices)
When a host cannot “see” its disks, the best way to troubleshoot the problem is to
start in the middle half of the data path, figure out if the problem is “above” or
“below” the data path, and keep dividing the suspect path in half until the problem
is identified.
There are two areas to check in the process of elimination:
Check the Logical Connection
Check the Simple Name Server (SNS)
Check for Zoning Discrepancies
Check Device Communication
Check the Logical Connection
Check Whether the Device is Logically Connected to the Switch
1.
Enter the
switchShow
command.
2.
Review the output and determine if the device is logically connected to the
switch:
A device that
is
logically connected to the switch will be registered as an
NX_Port.
A device that is
not
logically connected to the switch will be registered as
something
besides
an NX_Port.
If the missing device
is
logically connected, move on to
Check for the
Device in the SNS
.
If the missing device is
not
logically connected, eliminate the host
and everything on that side of the data path from the suspect list.
This includes all aspects of the host’s OS, the HBA driver settings and
binaries, the HBA Basic Input Output System (BIOS) settings, the
HBA SFP, the cable going from the switch to the host, the SFP on the
switch side of that cable, and all switch settings related to the host.
Move on to
Link Initialization Failure (Loop).