HP AM866A Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53-1000853-01, - Page 57

Scenario, Error handling, Required Action, to reboot or unable

Get HP AM866A - StorageWorks 8/8 Base SAN Switch PDF manuals and user guides
UPC - 884420064602
View all HP AM866A manuals
Add to My Manuals
Save this manual to your list of manuals

Page 57 highlights

Brocade DCX error handling 5 TABLE 9 Brocade DCX CP Error Handling Scenario When No. Scenario Error handling Required Action 7 During When downloading to 1. When the co-CPU on the standby CP Restart step 7 the co CPU of the boots up, firmwareDownload is firmwareDownload standby CP, if an error aborted. after the repair is occurs and the co CPU reboots. 2. The firmwareCommit command will be initiated on both CPUs on both done. CPs. 3. Both CPUs on the standby CP will have the old firmware and both CPUs on the active CP will have the new firmware. 8 During When downloading to 1. The firmwareCommit command will Restart step 6 or any of the CPUs on the be initiated on both CPU on both CPs. firmwareDownload 7 standby CP, 2. Both CPUs on the standby CP will after the repair is downloading takes too long and exceeds the 30 minute timeout for the firmwareDownload have the old firmware and both CPUs on the active CP will have the new firmware. done. process. 9 During The active CP fails over 1. The standby CP will become the new Restart step 6 or during the downloading active CP. firmwareDownload 7 to any of the CPUs on the standby CP. 2. The firmwareCommit command will be initiated on both CPUs on the after the repair is done. active CP and they will have the old firmware. 3. The firmwareCommit will be initiated on both CPUs on the standby CP and they will have the new firmware. 10 During If the standby CP failed 1. Active CP will wait for 10 minutes and Determine why the step 8 to reboot or unable to abort firmwareDownload. CPs fail to gain HA synchronize with the active CP. 1 The firmwareCommit command will be initiated on both CPUs and they will have the new firmware. sync and remedy it before restarting the firmwareDownload 2. If the standby CP boots up, command. firmwareCommit will start on both CPUs and they will have new firmware. 11 During If commit fails step 10 The affected CPUs will have different versions of firmware on its partitions. An error message is logged. Run the firmwareCommit -f command on the switch or each CP that fails. If the problem persists, contact your switch support provider. Fabric OS Troubleshooting and Diagnostics Guide 43 53-1000853-01

  • 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
Fabric OS Troubleshooting and Diagnostics Guide
43
53-1000853-01
Brocade DCX error handling
5
7
During
step 7
When downloading to
the co CPU of the
standby CP, if an error
occurs and the co CPU
reboots.
1.
When the co-CPU on the standby CP
boots up,
firmwareDownload
is
aborted.
2.
The
firmwareCommit
command will
be initiated on both CPUs on both
CPs.
3.
Both CPUs on the standby CP will
have the old firmware and both CPUs
on the active CP will have the new
firmware.
Restart
firmwareDownload
after the repair is
done.
8
During
step 6 or
7
When downloading to
any of the CPUs on the
standby CP,
downloading takes too
long and exceeds the
30 minute timeout for
the
firmwareDownload
process.
1.
The
firmwareCommit
command will
be initiated on both CPU on both CPs.
2.
Both CPUs on the standby CP will
have the old firmware and both CPUs
on the active CP will have the new
firmware.
Restart
firmwareDownload
after the repair is
done.
9
During
step 6 or
7
The active CP fails over
during the downloading
to any of the CPUs on
the standby CP.
1.
The standby CP will become the new
active CP.
2.
The
firmwareCommit
command will
be initiated on both CPUs on the
active CP and they will have the old
firmware.
3.
The
firmwareCommit
will be initiated
on both CPUs on the standby CP and
they will have the new firmware.
Restart
firmwareDownload
after the repair is
done.
10
During
step 8
If the standby CP failed
to reboot or unable to
synchronize with the
active CP.
1.
Active CP will wait for 10 minutes and
abort
firmwareDownload
.
1
The
firmwareCommit
command will
be initiated on both CPUs and they
will have the new firmware.
2.
If the standby CP boots up,
firmwareCommit
will start on both
CPUs and they will have new
firmware.
Determine why the
CPs fail to gain HA
sync and remedy it
before restarting
the
firmwareDownload
command.
11
During
step 10
If commit fails
The affected CPUs will have different
versions of firmware on its partitions. An
error message is logged.
Run the
firmwareCommit -f
command on the
switch or each CP
that fails. If the
problem persists,
contact your switch
support provider.
TABLE 9
Brocade DCX CP Error Handling
Scenario
No.
When
Scenario
Error handling
Required Action