HP EVA P6550 HP P6300/P6500 EVA User Guide (5697-2486, September 2013) - Page 285

Table 35 iSCSI or iSCSI/FCoE module log messages, DMA Error, Status 0x%.2x

Page 285 highlights

Table 35 iSCSI or iSCSI/FCoE module log messages (continued) 41067 QLBA_CreateLunObject: App Error LunObject memory unavailable Memory unavailable for LUN object. 41077 QLBA_CreateInitiatorObject: App Error Too many initiators Unable to create an object for initiator object; exceeded the maximum number of initiators. 41096 QLBA_DisplayTargetOperationStatus: App Error PCI Error, Status 0x%.2x Process control block status indicates that a peripheral component interface/interconnect (PCI) error occurred during a target operation. 41106 QLBA_DisplayInitiatorOperationStatus: App Error DMA Error, Status 0x%.2x 41107 QLBA_DisplayInitiatorOperationStatus: App Transport Error, Status 0x%.2x Error Process control block status indicates that a direct memory access (DMA) error occurred during an initiator operation. Process control block status indicates that a transport error (protocol) occurred during an initiator operation. 41111 QLBA_DisplayInitiatorOperationStatus: App Error Data Overrun, Status 0x%.2x Process control block status indicates that a data overrun error occurred during an initiator operation. 41234 QLIS_LoginPduContinue: App Operation failed. Initiator 0x%x, TPB status 0x%x Error iSCSI login failed between receipt of protocol data unit (PDU) and request for the data segment. 41238 QLKV_ValidateLoginTransitCsgNsgVersion App Error failed (status 0x%x) iSCSI login failed due to unsupported version number in received login PDU. 41257 QLIS_LoginPduContinue: Invalid initiator name. Initiator: App Error iSCSI login PDU contains invalid initiator name. The format and character set used to form the initiator name is invalid. 41265 QLIS_LoginPduContinue: Target not configured for Portal App Error iSCSI target login was attempted to a portal (iSCSI1 or iSCSI2) on which the target is not presented. 41267 QLIS_LoginPduContinue: Target not found. Target name: App Error iSCSI login PDU received for a target with a target name unknown to the module. 41268 QLIS_LoginPduContinue: Missing target name App Error iSCSI login PDU received without a target name for a normal session. 41270 QLIS_LoginPduContinue: TSIH App is 0 but InitiatorName key/value not provided Error iSCSI login PDU received without an initiator name key/value. 41272 QLIS_LoginPduContinue: App CONN_STATE_IN_LOGIN, Unknown InitTaskTag Error iSCSI login PDU received with an incorrect initiator task tag for a session which is partially logged in. This would occur if a login PDU other than the initial login PDU used an initiator task tag which was different than the initiator task tag provided in the initial login PDU. 41283 QLIS_LoginPduContinue: TSIH App Error 0x%x out of range iSCSI login PDU was received with a target session identifying handle (TSIH) out of range. This would occur if the iSCSI initiator attempting the login failed to used the TSIH value provided in the Target Login Response PDU (module is target) in subsequent login PDUs. 41284 QLIS_LoginPduContinue: Session does not exist, invalid TSIH 0x%x App Error iSCSI login PDU was received with an invalid TSIH value. The TSIH is invalid because there is no session with that TSIH value. This would occur if the iSCSI initiator attempting the login failed to used the TSIH value provided in the target login response PDU (module is target) in subsequent login PDUs. 285

  • 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
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316

Table 35 iSCSI or iSCSI/FCoE module log messages
(continued)
Memory unavailable for LUN object.
Error
App
QLBA_CreateLunObject:
LunObject memory unavailable
41067
Unable to create an object for initiator object;
exceeded the maximum number of initiators.
Error
App
QLBA_CreateInitiatorObject:
Too many initiators
41077
Process control block status indicates that a
peripheral component interface/interconnect (PCI)
error occurred during a target operation.
Error
App
QLBA_DisplayTargetOperationStatus:
PCI Error, Status 0x%.2x
41096
Process control block status indicates that a direct
memory access (DMA) error occurred during an
initiator operation.
Error
App
QLBA_DisplayInitiatorOperationStatus:
DMA Error, Status 0x%.2x
41106
Process control block status indicates that a transport
error (protocol) occurred during an initiator
operation.
Error
App
QLBA_DisplayInitiatorOperationStatus:
Transport Error, Status
0x%.2x
41107
Process control block status indicates that a data
overrun error occurred during an initiator operation.
Error
App
QLBA_DisplayInitiatorOperationStatus:
Data Overrun, Status 0x%.2x
41111
iSCSI login failed between receipt of protocol data
unit (PDU) and request for the data segment.
Error
App
QLIS_LoginPduContinue:
Operation failed. Initiator
0x%x, TPB status 0x%x
41234
iSCSI login failed due to unsupported version
number in received login PDU.
Error
App
QLKV_ValidateLoginTransitCsgNsgVersion
failed (status 0x%x)
41238
iSCSI login PDU contains invalid initiator name. The
format and character set used to form the initiator
name is invalid.
Error
App
QLIS_LoginPduContinue:
Invalid initiator name.
Initiator:
41257
iSCSI target login was attempted to a portal (iSCSI1
or iSCSI2) on which the target is not presented.
Error
App
QLIS_LoginPduContinue:
Target not configured for
Portal
41265
iSCSI login PDU received for a target with a target
name unknown to the module.
Error
App
QLIS_LoginPduContinue:
Target not found. Target
name:
41267
iSCSI login PDU received without a target name for
a normal session.
Error
App
QLIS_LoginPduContinue:
Missing target name
41268
iSCSI login PDU received without an initiator name
key/value.
Error
App
QLIS_LoginPduContinue: TSIH
is 0 but InitiatorName
key/value not provided
41270
iSCSI login PDU received with an incorrect initiator
task tag for a session which is partially logged in.
Error
App
QLIS_LoginPduContinue:
CONN_STATE_IN_LOGIN, Unknown
InitTaskTag
41272
This would occur if a login PDU other than the initial
login PDU used an initiator task tag which was
different than the initiator task tag provided in the
initial login PDU.
iSCSI login PDU was received with a target session
identifying handle (TSIH) out of range. This would
Error
App
QLIS_LoginPduContinue: TSIH
0x%x out of range
41283
occur if the iSCSI initiator attempting the login failed
to used the TSIH value provided in the Target Login
Response PDU (module is target) in subsequent login
PDUs.
iSCSI login PDU was received with an invalid TSIH
value. The TSIH is invalid because there is no
Error
App
QLIS_LoginPduContinue:
Session does not exist,
invalid TSIH 0x%x
41284
session with that TSIH value. This would occur if the
iSCSI initiator attempting the login failed to used
the TSIH value provided in the target login response
PDU (module is target) in subsequent login PDUs.
285