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

Link Initialization Failure (Loop)

Page 231 highlights

Troubleshooting 1 Gig example: 14:38:51.976 SPEE sn 2 Gig example: NC 00000001,00000000,00000001 14:39:39.227 SPEE sn NC 00000002,00000000,00000001 - The sn field indicates a speed negotiation. - The NC field indicates Negotiation Complete. - The 01 or 02 fields indicate the speed that has been negotiated. If these fields do not appear, move on to step 3. 3. Correct the negotiation by entering the portCfgSpeed [slotnumber/]portnumber, speed_level command if the fields above do not appear. Link Initialization Failure (Loop) 1. Verify the port is an L_Port. a. Enter the switchShow command. b. Check the comment field of the output to verify that the switch port indicates an L_Port. If a loop device is connected to the switch, the switch port must be initialized as an L_Port. 2. Verify the loop initialization if the port is not an L_port. a. Enter the portLogShow or portLogDump command. b. Check the event area for a loopscn entry with command code BMP. Example: 14:35:12.866 tReceive loopscn BMP 10f5cbc0 The loopscn entry display indicates that the loop initialization is complete. 3. Skip point-to-point initialization. StorageWorks SAN switches switch the point-to-point initialization after the Loop Initialization Soft Assigned (LISA) phase of the loop initialization. This behavior sometimes causes trouble with old HBAs. If this is the case: - Skip point-to-point initialization by using the portCfgLport Command. Fabric OS Procedures Version 3.1.x/4.1.x User Guide 231

  • 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
231
Fabric OS Procedures Version 3.1.x/4.1.x User Guide
1 Gig example:
2 Gig example:
The sn field indicates a speed negotiation.
The NC field indicates Negotiation Complete.
The 01 or 02 fields indicate the speed that has been negotiated.
If these fields do not appear, move on to
step 3
.
3.
Correct the negotiation by entering the
portCfgSpeed
[slotnumber/]portnumber, speed_level
command if the fields
above do not appear.
Link Initialization Failure (Loop)
1.
Verify the port is an L_Port.
a.
Enter the
switchShow
command.
b.
Check the comment field of the output to verify that the switch port
indicates an L_Port. If a loop device is connected to the switch, the switch
port must be initialized as an L_Port.
2.
Verify the loop initialization
if
the port is not an L_port.
a.
Enter the
portLogShow
or
portLogDump
command.
b.
Check the event area for a loopscn entry with command code BMP.
Example:
The loopscn entry display indicates that the loop initialization is complete.
3.
Skip point-to-point initialization.
StorageWorks SAN switches switch the point-to-point initialization after the
Loop Initialization Soft Assigned (LISA) phase of the loop initialization. This
behavior sometimes causes trouble with old HBAs. If this is the case:
Skip point-to-point initialization by using the
portCfgLport
Command.
14:38:51.976
SPEE
sn
<Port#>
NC
00000001,00000000,00000001
14:39:39.227
SPEE
sn
<Port#>
NC
00000002,00000000,00000001
14:35:12.866
tReceive
loopscn
<Port#>
BMP
10f5cbc0