HP XP20000/XP24000 HP StorageWorks MPX200 Multifunction Router User Guide (569 - Page 236

Status: PCI Error, Status, tionStatus: Transport Error

Page 236 highlights

41058 QLBA_CreateTargetDeviceOb- App ject: Too many devices 41060 QLBA_CreateTargetNodeObject: App Too many devices 41067 QLBA_CreateLunObject: LunOb- App ject memory unavailable 41077 QLBA_CreateInitiatorObject: App Too many initiators 41096 QLBA_DisplayTargetOperationStatus: PCI Error, Status App 0x%.2x 41106 QLBA_DisplayInitiatorOpera- tionStatus: DMA Error, App Status 0x%.2x 41107 QLBA_DisplayInitiatorOperationStatus: Transport Error, App Status 0x%.2x 41111 QLBA_DisplayInitiatorOperationStatus: Data Overrun, App Status 0x%.2x 41234 QLIS_LoginPduContinue: Oper- ation failed. Initiator App 0x%x, TPB status 0x%x 41238 QLKV_ValidateLoginTransitCsgNsgVersion failed (status App 0x%x) 41257 QLIS_LoginPduContinue: Invalid initiator name. Initiat- App or: 41265 QLIS_LoginPduContinue: Tar- get not configured for App Portal 41267 QLIS_LoginPduContinue: Tar- App get not found. Target name: 41268 QLIS_LoginPduContinue: Miss- App ing target name Error Error Error Error Error Error Error Error Error Error Error Error Error Error Unable to create an object for the target device; exceeded the maximum number of target devices. Unable to create an object for the target node; exceeded the maximum number of target devices. Memory unavailable for LUN object. Unable to create an object for initiator object; exceeded the maximum number of initiators. Process control block status indicates that a peripheral component interface/interconnect (PCI) error occurred during a target operation. 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. Process control block status indicates that a data overrun error occurred during an initiator operation. iSCSI login failed between receipt of protocol data unit (PDU) and request for the data segment. iSCSI login failed due to unsupported version number in received login PDU. iSCSI login PDU contains invalid initiator name. The format and character set used to form the initiator name is invalid. iSCSI target login was attempted to a portal (iSCSI1 or iSCSI2) on which the target is not presented. iSCSI login PDU received for a target with a target name unknown to the router. iSCSI login PDU received without a target name for a normal session. 236 Log messages

  • 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

Unable to create an object for the
target device; exceeded the max-
imum number of target devices.
Error
App
QLBA_CreateTargetDeviceOb-
ject: Too many devices
41058
Unable to create an object for the
target node; exceeded the maxim-
um number of target devices.
Error
App
QLBA_CreateTargetNodeObject:
Too many devices
41060
Memory unavailable for LUN ob-
ject.
Error
App
QLBA_CreateLunObject: LunOb-
ject memory unavailable
41067
Unable to create an object for initi-
ator object; exceeded the maxim-
um number of initiators.
Error
App
QLBA_CreateInitiatorObject:
Too many initiators
41077
Process control block status indic-
ates that a peripheral component
interface/interconnect (PCI) error
occurred during a target operation.
Error
App
QLBA_DisplayTargetOperation-
Status: PCI Error, Status
0x%.2x
41096
Process control block status indic-
ates that a direct memory access
(DMA) error occurred during an
initiator operation.
Error
App
QLBA_DisplayInitiatorOpera-
tionStatus: DMA Error,
Status 0x%.2x
41106
Process control block status indic-
ates that a transport error (pro-
tocol) occurred during an initiator
operation.
Error
App
QLBA_DisplayInitiatorOpera-
tionStatus: Transport Error,
Status 0x%.2x
41107
Process control block status indic-
ates that a data overrun error oc-
curred during an initiator opera-
tion.
Error
App
QLBA_DisplayInitiatorOpera-
tionStatus: 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: Oper-
ation failed. Initiator
0x%x, TPB status 0x%x
41234
iSCSI login failed due to unsuppor-
ted version number in received lo-
gin PDU.
Error
App
QLKV_ValidateLoginTransitC-
sgNsgVersion failed (status
0x%x)
41238
iSCSI login PDU contains invalid
initiator name. The format and
character set used to form the initi-
ator name is invalid.
Error
App
QLIS_LoginPduContinue: Inval-
id initiator name. Initiat-
or:
41257
iSCSI target login was attempted
to a portal (iSCSI1 or iSCSI2) on
which the target is not presented.
Error
App
QLIS_LoginPduContinue: Tar-
get not configured for
Portal
41265
iSCSI login PDU received for a
target with a target name unknown
to the router.
Error
App
QLIS_LoginPduContinue: Tar-
get not found. Target name:
41267
iSCSI login PDU received without
a target name for a normal ses-
sion.
Error
App
QLIS_LoginPduContinue: Miss-
ing target name
41268
Log messages
236