HP StorageWorks 2/16V HP StorageWorks Fabric OS 5.X Procedures User Guide (AA- - Page 145

Analyzing connection problems, Checking the logical connection

Page 145 highlights

• Commands pdShow and save Core output 2. Determine the following host information: • OS version and patch level • HBA type • HBA firmware version • HBA driver version • Configuration settings 3. Determine the following storage information: • Disk/tape type • Disk/tape firmware level • Controller type • Controller firmware level • Configuration settings • Storage software (such as EMC Control Center, Veritas SPC, and the like) Analyzing connection problems If a host is unable to detect its target (for example, a storage or tape device), begin troubleshooting the problem in the middle of the data path. Determine whether the problem is above or below the starting point, and then continue to divide the suspected problem path in half until you can pinpoint the problem. Use the following procedures to analyze the problem: Checking the logical connection 1. Issue the switchShow command. 2. Review the output and determine whether the device is logically connected to the switch: • A device that is logically connected to the switch is registered as an F_Port or L_Port. • A device that is not logically connected to the switch is registered as something other than an Nx_Port. 3. If the missing device is logically connected, proceed to the next troubleshooting procedure "Checking the Simple Name Server (SNS)" on page 147. 4. If the missing device is not logically connected, check the device and everything on that side of the data path. Also see "Correcting link failures" on page 157. Check all aspects of the host OS, the driver settings and binaries, the device Basic Input/Output System (BIOS) settings, the SFP, the cable going from the switch to the device, the SFP on the switch side of that cable, and all switch settings related to the device. See "Checking for a loop initialization failure" on page 158 as the next potential trouble spot. Checking for Fibre Channel connectivity problems Issue the fcPing command, which: • Checks the zoning configuration for the two ports specified. • Generates an ELS frame ECHO request to the source port specified and validates the response. • Generates an ELS ECHO request to the destination port specified and validates the response. Regardless of the device's zoning, the fcPing command sends the ELS frame to the destination port. A device can take any one of the following actions: • Send an ELS Accept to the ELS request. • Send an ELS Reject to the ELS request. • Ignore the ELS request. There are some devices that do not support the ELS ECHO request. In these cases, the device either does not respond to the request or it sends an ELS reject. When a device does not respond to the ELS request, further debugging is required; however, do not assume that the device is not connected to the Fibre Channel. Fabric OS 5.x administrator guide 145

  • 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

Fabric OS 5.x administrator guide
145
Commands
pdShow
and
save Core
output
2.
Determine the following host information:
OS version and patch level
HBA type
HBA firmware version
HBA driver version
Configuration settings
3.
Determine the following storage information:
Disk/tape type
Disk/tape firmware level
Controller type
Controller firmware level
Configuration settings
Storage software (such as EMC Control Center, Veritas SPC, and the like)
Analyzing connection problems
If a host is unable to detect its target (for example, a storage or tape device), begin troubleshooting the
problem in the middle of the data path. Determine whether the problem is above or below the starting
point, and then continue to divide the suspected problem path in half until you can pinpoint the problem.
Use the following procedures to analyze the problem:
Checking the logical connection
1.
Issue the
switchShow
command.
2.
Review the output and determine whether the device is logically connected to the switch:
A device that is logically connected to the switch is registered as an F_Port or L_Port.
A device that is not logically connected to the switch is registered as something other than an
Nx_Port.
3.
If the missing device is logically connected, proceed to the next troubleshooting procedure
Checking
the Simple Name Server (SNS)
” on page 147.
4.
If the missing device is not logically connected, check the device and everything on that side of the
data path. Also see ”
Correcting link failures
” on page 157.
Check all aspects of the host OS, the driver settings and binaries, the device Basic Input/Output
System (BIOS) settings, the SFP, the cable going from the switch to the device, the SFP on the switch
side of that cable, and all switch settings related to the device. See ”
Checking for a loop initialization
failure
” on page 158 as the next potential trouble spot.
Checking for Fibre Channel connectivity problems
Issue the
fcPing
command, which:
Checks the zoning configuration for the two ports specified.
Generates an ELS frame ECHO request to the source port specified and validates the response.
Generates an ELS ECHO request to the destination port specified and validates the response.
Regardless of the device’s zoning, the
fcPing
command sends the ELS frame to the destination port. A
device can take any one of the following actions:
Send an ELS Accept to the ELS request.
Send an ELS Reject to the ELS request.
Ignore the ELS request.
There are some devices that do not support the ELS ECHO request. In these cases, the device either does
not respond to the request or it sends an ELS reject. When a device does not respond to the ELS request,
further debugging is required; however, do not assume that the device is not connected to the Fibre
Channel.