HP StorageWorks 6000 HP StorageWorks 6000-series Virtual Library System User G - Page 317

Using Command View TL on the, The Identity tab of Command View

Page 317 highlights

Symptom Possible causes Solution 5. Repeat this procedure for each server visible to each SDLT tape drive. At reboot, there are spurious critical FC port failures reported as notification alerts, usually on every port. Later, Info notification alerts for each FC host port are generated, indicating the FC ports are operating normally. This is expected behavior and does not indicate a problem. None The Identity tab of Command View VLS reports Total Usable Capacity of 0 GB, even though there are working disk arrays available to the VLS system. Whenever the VLS detects more array enclosures than there are correctly installed licenses, the VLS system will disable ALL array storage and report 0 GB of Total Usable Capacity. Using Command View TL on the management station for this VLS, go to the "License Key Summary" tab and verify the following: • There is a License folder labeled "VLS at..." with the Ethernet IP address for this VLS system. • The number of license instances in this folder ("Quantity (LTU)") is equal to or greater than the number of array enclosures connected to this VLS system in addition to the minimum configuration. For example, a VLS6100-series system has a minimum configuration of 1 array enclosure and a VLS6800-series has a minimum configuration of 4 array enclosures. There must be at least 1 LTU for every array enclosure over the minimum configuration. A VLS6800-series with 16 connected array enclosure needs 12 correctly installed LTU license keys. • Verify the correct VLS system Identifier was used and entered correctly when the license key was created. If licenses that were installed for this system show up under the "Un-managed Licenses" license folder, then Command View TL can not match the Identifier for that licence to any known library device. After replacing drive 0 in a node, the system will not boot. A blank drive was installed in drive bay 0. If a blank drive is installed in drive bay 0, the system will not boot. To remedy this, switch the drive located in bay 0 with the drive located in bay 1. HP StorageWorks 317

  • 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

Solution
Possible causes
Symptom
5.
Repeat this procedure for each
server visible to each SDLT
tape drive.
None
This is expected behavior and does
not indicate a problem.
At reboot, there are spurious critical
FC port failures reported as notific-
ation alerts, usually on every port.
Later, Info notification alerts for
each FC host port are generated,
indicating the FC ports are operat-
ing normally.
Using Command View TL on the
management station for this VLS,
go to the "License Key Summary"
tab and verify the following:
There is a License folder labeled
"VLS at..." with the Ethernet IP
address for this VLS system.
The number of license instances
in this folder ("Quantity (LTU)")
is equal to or greater than the
number of array enclosures
connected to this VLS system in
addition to the minimum config-
uration. For example, a
VLS6100
series system has a
minimum configuration of 1 ar-
ray enclosure and a
VLS6800
series has a minimum
configuration of 4 array enclos-
ures. There must be at least 1
LTU for every array enclosure
over the minimum configuration.
A VLS6800
series with 16
connected array enclosure
needs 12 correctly installed LTU
license keys.
Verify the correct VLS system
Identifier was used and entered
correctly when the license key
was created. If licenses that
were installed for this system
show up under the "Un-man-
aged Licenses" license folder,
then Command View TL can not
match the Identifier for that li-
cence to any known library
device.
Whenever the VLS detects more
array enclosures than there are
correctly installed licenses, the VLS
system will disable ALL array stor-
age and report 0 GB of Total Us-
able Capacity.
The Identity tab of Command View
VLS reports Total Usable Capacity
of 0 GB, even though there are
working disk arrays available to
the VLS system.
If a blank drive is installed in drive
bay 0, the system will not boot. To
remedy this, switch the drive loc-
ated in bay 0 with the drive located
in bay 1.
A blank drive was installed in drive
bay 0.
After replacing drive 0 in a node,
the system will not boot.
HP StorageWorks
317