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

Update firmware on standby CP, Failover to standby CP, Verify failover, firmwareDownload -s

Page 162 highlights

2. Update firmware on standby CP a. Start a telnet session, log in as admin to the standby CP. b. Enter the firmwareDownload -s command and respond to the prompts as follows: switch:admin> firmwaredownload -s Server Name or IP Address: 10.1.2.3 FTP User Name: JaneDoe File Name: /pub/v5.2.x FTP Password: Do Auto-Commit after Reboot [Y]: n Reboot system after download [N]: y Firmware is being downloaded to the switch. This step may take up to 30 minutes. Checking system settings for firmwaredownload... At this point the firmware should download to the standby CP only and reboot it. The telnet session will be disconnected. 3. Failover to standby CP a. Start a telnet session on the active CP. b. Enter the haShow command to verify that HA synchronization is complete. It will take a minute or two for the standby CP to reboot and synchronize with the active CP. If the CPs do not achieve synchronization, stop here; log in to the standby CP, and enter the firmwareRestore command to restore your original firmware. c. Enter the firmwareShow command to confirm that the primary partition of the standby CP contains the new firmware. d. Enter the haFailover command. The active CP will reboot and the telnet session will be disconnected. If there is an AP blade is present: At the point of the failover an auto-leveling process is activated. Refer to step 8 in the "SAN Director 2/128 and 4/256 SAN Director firmware download procedure" on page 156 for details about auto-leveling. 4. Verify failover a. Start a telnet session on the active CP (which is the old standby CP). b. Enter the haShow command to verify that the HA synchronization is complete. It will take a minute or two for the standby CP (which is the old active CP) to reboot and synchronize with the active CP. NOTE: If the CPs fail to synchronize, you can still proceed because the version being tested is already present on the active CP, and subsequent steps will ensure that the standby CP is updated to the same version as the active CP. c. The test version of firmware is now running on the active CP (you can confirm this by entering the firmwareShow command). 162 Installing and maintaining firmware

  • 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

162
Installing and maintaining firmware
2. Update firmware on standby CP
a.
Start a telnet session, log in as admin to the standby CP.
b.
Enter the
firmwareDownload -s
command and respond to the prompts as follows:
At this point the firmware should download to the standby CP only and reboot it. The telnet session will
be disconnected.
3. Failover to standby CP
a.
Start a telnet session on the active CP.
b.
Enter the
haShow
command to verify that HA synchronization is complete. It will take a minute or
two for the standby CP to reboot and synchronize with the active CP.
If the CPs do not achieve synchronization,
stop here
; log in to the standby CP, and enter the
firmwareRestore
command to restore your original firmware.
c.
Enter the
firmwareShow
command to confirm that the primary partition of the standby CP
contains the new firmware.
d.
Enter the
haFailover
command. The active CP will reboot and the telnet session will be
disconnected.
If there is an AP blade is present
: At the point of the failover an
auto-leveling
process is
activated. Refer to
step 8
in the ”
SAN Director 2/128 and 4/256 SAN Director firmware download
procedure
” on page 156 for details about auto-leveling.
4. Verify failover
a.
Start a telnet session on the active CP (which is the old standby CP).
b.
Enter the
haShow
command to verify that the HA synchronization is complete. It will take a minute
or two for the standby CP (which is the old active CP) to reboot and synchronize with the active CP.
NOTE:
If the CPs fail to synchronize, you can still proceed because the version being tested is already
present on the active CP, and subsequent steps will ensure that the standby CP is updated to the same
version as the active CP.
c.
The test version of firmware is now running on the active CP (you can confirm this by entering the
firmwareShow
command).
switch:admin>
firmwaredownload -s
Server Name or IP Address:
10.1.2.3
FTP User Name:
JaneDoe
File Name:
/pub/v5.2.x
FTP Password:
Do Auto-Commit after Reboot [Y]:
n
Reboot system after download [N]:
y
Firmware is being downloaded to the switch. This step may take up to 30
minutes.
Checking system settings for firmwaredownload...