HP StorageWorks 2/16V HP StorageWorks Fabric OS 5.3.x administrator guide (569 - Page 199

Blade troubleshooting tips, Synchronizing firmware versions on partitions, FTP server recommendations

Page 199 highlights

Remove all DCC policies containing more than 256 ports using the secPolicyDelete and secPolicyActivate commands. Retry the firmware download operation. Blade troubleshooting tips Typically, issues that evolve during firmware downloads to the B-Series MP Router blade do not require explicit actions on your part. However, if any of the following events occur, perform the suggestion action to correct: • The blade is faulty (issue slotShow to confirm) If the blade is faulty, enter the slotPowerOff and slotPowerOn commands for the blade. If the blade still appears to be faulty, remove it and re-insert it into the chassis. • The blade is stuck in the "LOADING" state (issue slotShow to confirm) If the blade remains in the loading state for a significant period of time, the firmware download will time-out. Remove the blade and re-insert it. When it boots up, auto-leveling will be triggered and the firmware download will be attempted again. If you experience frequent failovers between CPs that have different versions of firmware, then you may notice multiple blade firmware downloads and a longer start-up time. Synchronizing firmware versions on partitions It is possible for firmware to become out of sync on the partitions. This can occur when a user issues the firmwareDownload -s command to test drive the firmware, but does not issue the firmwareRestore and firmwareCommit commands-in such a case the user ends up with different levels of firmware on the two partitions. If you have different versions of firmware on one of your partitions, for example, CP0 is running v5.0.1 on the primary and secondary partitions, and CP1 is running v5.0.1 on the primary partition and v4.4.0e on the secondary partition, then synchronize the partitions on CP1 as follows: 1. Start a telnet session on the CP with the out-of-sync partitions. 2. Enter the firmwareCommit command, which copies the primary partition to the secondary partition. If there is a discrepancy in the number of switches or attached devices in the fabric after a firmware download it may be due to a fabric segmentation or a device that failed to log in. For assistance refer to "Troubleshooting" on page 307 for basic troubleshooting steps, or contact HP. FTP server recommendations The firmwareDownload command has a time-out of ten minutes for v4.0 and v4.1 and thirty minutes for v4.2 and later. The following tips may be of help if you are having problems with the firmware download timing out before the process is complete: • Verify that you can ping the FTP server from another host on the LAN, prior to running the firmwareDownload command. • Disable any VPN, firewall or anti-virus applications on the FTP server. • Remove any Ethernet hub between the FTP server and the switch. • Optionally, set the switch's autonegotiating Ethernet port to match the speed and duplex setting of the IP environment. For example, enter the ifModeSet command to change the switch settings to match both ends of the Ethernet link. Enter help ifModeSet and help ifModeShow on the switch to view more details about these commands). • Enable session logging on the FTP server so that the log can be viewed during the execution of the firmwareDownload command. • Set the FTP server's time-out value to sixty minutes. • Ensure that the decompress process created multiple SWBDxx folders (where xx is a number) in the main folder. If the files are unpacked without folder creation, then the firmwareDownload command will be unable to locate the .plist file. Fabric OS 5.3.0 administrator guide 201

  • 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
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435
  • 436
  • 437
  • 438
  • 439
  • 440
  • 441
  • 442
  • 443
  • 444
  • 445
  • 446
  • 447
  • 448
  • 449
  • 450
  • 451
  • 452
  • 453
  • 454
  • 455
  • 456
  • 457
  • 458
  • 459
  • 460
  • 461
  • 462
  • 463
  • 464
  • 465

Fabric OS 5.3.0 administrator guide
201
Remove all DCC policies containing more than 256 ports using the
secPolicyDelete
and
secPolicyActivate
commands. Retry the firmware download operation.
Blade troubleshooting tips
Typically, issues that evolve during firmware downloads to the B-Series MP Router blade do not require
explicit actions on your part. However, if any of the following events occur, perform the suggestion action
to correct:
The blade is faulty (issue
slotShow
to confirm)
If the blade is faulty, enter the
slotPowerOff
and
slotPowerOn
commands for the blade. If the
blade still appears to be faulty, remove it and re-insert it into the chassis.
The blade is stuck in the “LOADING” state (issue
slotShow
to confirm)
If the blade remains in the loading state for a significant period of time, the firmware download will
time-out. Remove the blade and re-insert it. When it boots up, auto-leveling will be triggered and the
firmware download will be attempted again.
If you experience frequent failovers between CPs that have different versions of firmware, then you may
notice multiple blade firmware downloads and a longer start-up time.
Synchronizing firmware versions on partitions
It is possible for firmware to become out of sync on the partitions. This can occur when a user issues the
firmwareDownload -s
command to test drive the firmware, but does not issue the
firmwareRestore
and
firmwareCommit
commands—in such a case the user ends up with different levels of firmware on
the two partitions.
If you have different versions of firmware on one of your partitions, for example, CP0 is running v5.0.1 on
the primary and secondary partitions, and CP1 is running v5.0.1 on the primary partition and v4.4.0e on
the secondary partition, then synchronize the partitions on CP1 as follows:
1.
Start a telnet session on the CP with the out-of-sync partitions.
2.
Enter the
firmwareCommit
command, which copies the primary partition to the secondary partition.
If there is a discrepancy in the number of switches or attached devices in the fabric after a firmware
download it may be due to a fabric segmentation or a device that failed to log in. For assistance refer
to ”
Troubleshooting
” on page 307 for basic troubleshooting steps, or contact HP.
FTP server recommendations
The
firmwareDownload
command has a time-out of ten minutes for v4.0 and v4.1 and thirty minutes for
v4.2 and later. The following tips may be of help if you are having problems with the firmware download
timing out before the process is complete:
Verify that you can ping the FTP server from another host on the LAN, prior to running the
firmwareDownload
command.
Disable any VPN, firewall or anti-virus applications on the FTP server.
Remove any Ethernet hub between the FTP server and the switch.
Optionally, set the switch's autonegotiating Ethernet port to match the speed and duplex setting of the
IP environment.
For example, enter the
ifModeSet
command to change the switch settings to match both ends of the
Ethernet link. Enter
help
ifModeSet
and
help ifModeShow
on the switch to view more details
about these commands).
Enable session logging on the FTP server so that the log can be viewed during the execution of the
firmwareDownload
command.
Set the FTP server's time-out value to sixty minutes.
Ensure that the decompress process created multiple
SWBDxx
folders (where
xx
is a number) in the
main folder. If the files are unpacked without folder creation, then the
firmwareDownload
command
will be unable to locate the
.plist
file.