HP NetServer AA 4000 HP NetServer AA 6200 Solution Release 3.0 Messages - Page 106

IOPn.MtcDsl Status Message Summary

Page 106 highlights

Chapter 6 MtcDsl Messages IOPn.MtcDsl Status Message Summary The following table lists the HP NetServer AA server MtcDsl messages in the order that they are documented. Table 6-1 IOPn.MtcDsl Message Summary Message IOPn.MtcDsl status: A packet with an invalid transport command was received (offendingValue). IOPn.MtcDsl status: A provider has an invalid Registry entry (provName). IOPn.MtcDsl status: A provider has attempted to register more than once (provName). IOPn.MtcDsl status: A request contained an invalid provider ID (offendingValue). IOPn.MtcDsl status: A request for provider provName used an invalid logical device ID. IOPn.MtcDsl status: A request for provider provName used an invalid physical device ID. IOPn.MtcDsl status: A tack timeout condition was not cleared properly. IOPn.MtcDsl status: A tacked flush packet has an unknown flush type (offendingValue). IOPn.MtcDsl status: An invalid client callback ID was encountered (offendingValue). IOPn.MtcDsl status: An invalid component state was encountered (offendingValue). IOPn.MtcDsl status: An invalid component type was encountered (offendingValue). IOPn.MtcDsl status: An invalid DSL packet ID was encountered (offendingValue). IOPn.MtcDsl status: An invalid IOP state was encountered (offendingValue). IOPn.MtcDsl status: An invalid logical device operation type was encountered (offendingValue). IOPn.MtcDsl status: An invalid packet descriptor was encountered. IOPn.MtcDsl status: An invalid reset reason code was encountered (offendingValue). IOPn.MtcDsl status: An invalid resync flush state was encountered (offendingValue). IOPn.MtcDsl status: An invalid subprovider ID was encountered (offendingValue). IOPn.MtcDsl status: An invalid transaction ID was encountered (offendingValue). IOPn.MtcDsl status: Invalid device entries in the IOP's configuration were pruned. This indicates an improperly set up device configuration. This problem may have occurred due to hand modifications of the Windows NT Registry. The problem may be fixed by re-running the HP NetServer AA Configuration Utility. Page page 98 page 98 page 98 page 99 page 99 page 100 page 100 page 100 page 101 page 101 page 101 page 102 page 102 page 103 page 103 page 103 page 104 page 104 page 104 page 105 96

  • 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
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386

Chapter 6
MtcDsl Messages
96
IOP
n
.MtcDsl Status Message Summary
The following table lists the HP NetServer AA server MtcDsl messages in the order that they
are documented.
Table 6-1
IOP
n.
MtcDsl Message Summary
Message
Page
IOPn.MtcDsl status: A packet with an invalid transport command was received (offendingValue).
page 98
IOPn.MtcDsl status: A provider has an invalid Registry entry (provName).
page 98
IOPn.MtcDsl status: A provider has attempted to register more than once (provName).
page 98
IOPn.MtcDsl status: A request contained an invalid provider ID (offendingValue).
page 99
IOPn.MtcDsl status: A request for provider provName used an invalid logical device ID.
page 99
IOPn.MtcDsl status: A request for provider provName used an invalid physical device ID.
page 100
IOPn.MtcDsl status: A tack timeout condition was not cleared properly.
page 100
IOPn.MtcDsl status: A tacked flush packet has an unknown flush type (offendingValue).
page 100
IOPn.MtcDsl status: An invalid client callback ID was encountered (offendingValue).
page 101
IOPn.MtcDsl status: An invalid component state was encountered (offendingValue).
page 101
IOPn.MtcDsl status: An invalid component type was encountered (offendingValue).
page 101
IOPn.MtcDsl status: An invalid DSL packet ID was encountered (offendingValue).
page 102
IOPn.MtcDsl status: An invalid IOP state was encountered (offendingValue).
page 102
IOPn.MtcDsl status: An invalid logical device operation type was encountered (offendingValue).
page 103
IOPn.MtcDsl status: An invalid packet descriptor was encountered.
page 103
IOPn.MtcDsl status: An invalid reset reason code was encountered (offendingValue).
page 103
IOPn.MtcDsl status: An invalid resync flush state was encountered (offendingValue).
page 104
IOPn.MtcDsl status: An invalid subprovider ID was encountered (offendingValue).
page 104
IOPn.MtcDsl status: An invalid transaction ID was encountered (offendingValue).
page 104
IOPn.MtcDsl status: Invalid device entries in the IOP
s configuration were pruned. This indicates an
improperly set up device configuration. This problem may have occurred due to hand modifications
of the Windows NT Registry. The problem may be fixed by re-running the HP NetServer AA
Configuration Utility.
page 105