HP StorageWorks 8/80 Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53- - Page 56

Brocade DCX error handling, Scenario, Error handling, Required Action

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

Page 56 highlights

5 Brocade DCX error handling TABLE 9 Brocade DCX CP Error Handling Scenario When No. Scenario Error handling Required Action 1 During During downloading to 1. When the main CPU boots up, Restart step 1 the main CPU of the firmwareDownload is aborted. firmwareDownload standby CP, if an error occurs and the main CPU reboots. 2. The firmwareCommit command will be initiated on the main CPU and the after the repair is done. original firmware is restored on that CPU. 3. Both CPUs on both CPs will have the original firmware. 2 During During downloading to 1. When the co CPU boots up, Restart step 2 the co CPU of the firmwareDownload is aborted. firmwareDownload standby CP, if an error occurs and the co CPU reboots. 2. The firmwareCommit command will be initiated on both CPUs on the standby CP. after the repair is done. 3. Both CPUs on both CPs will have the original firmware. 3 During During downloading to 1. The firmwareCommit command will Restart step 1 or any of the CPUs on the be initiated on both CPU on the firmwareDownload 2 standby CP, if the standby CP and the original firmware after the repair is downloading takes too is restored on both CPUs. done. long and exceeds the 30 minute timeout for the firmwareDownload 2. Both CPUs on both CPs will have the original firmware. process. 4 During Active CP fails over 1. The firmwareCommit command will Restart step 1 or during the downloading be initiated on both CPU on the new firmwareDownload 2 to any of the CPUs on active CP and the original firmware is after the repair is the standby CP. restored on both CPUs. done. 2. Both CPUs on both CPs will have the original firmware. 5 During If the standby CP failed 1. Active CP will wait for 10 minutes and Determine why the step 4 to reboot or unable to abort firmwareDownload. CPs fail to gain HA synchronize with the active CP. 2. If the standby CP boots up, firmwareCommit will start on both CPUs on the standby CP. sync and remedy it before restarting firmwaredownload 3. Both CPUs on the standby CP will have the new firmware, and both CPUs on the active CP will have the old firmware. 6 During When downloading to 1. When the main CPU on the standby Restart step 6 the main CPU of the CP boots up, firmwareDownload is firmwareDownload standby CP, if an error aborted. after the repair is occurs and the main 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. 42 Fabric OS Troubleshooting and Diagnostics Guide 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
42
Fabric OS Troubleshooting and Diagnostics Guide
53-1000853-01
Brocade DCX error handling
5
TABLE 9
Brocade DCX CP Error Handling
Scenario
No.
When
Scenario
Error handling
Required Action
1
During
step 1
During downloading to
the main CPU of the
standby CP, if an error
occurs and the main
CPU reboots.
1.
When the main CPU boots up,
firmwareDownload
is aborted.
2.
The
firmwareCommit
command will
be initiated on the main CPU and the
original firmware is restored on that
CPU.
3.
Both CPUs on both CPs will have the
original firmware.
Restart
firmwareDownload
after the repair is
done.
2
During
step 2
During downloading to
the co CPU of the
standby CP, if an error
occurs and the co CPU
reboots.
1.
When the co CPU boots up,
firmwareDownload
is aborted.
2.
The
firmwareCommit
command will
be initiated on both CPUs on the
standby CP.
3.
Both CPUs on both CPs will have the
original firmware.
Restart
firmwareDownload
after the repair is
done.
3
During
step 1 or
2
During downloading to
any of the CPUs on the
standby CP, if the
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 the
standby CP and the original firmware
is restored on both CPUs.
2.
Both CPUs on both CPs will have the
original firmware.
Restart
firmwareDownload
after the repair is
done.
4
During
step 1 or
2
Active CP fails over
during the downloading
to any of the CPUs on
the standby CP.
1.
The
firmwareCommit
command will
be initiated on both CPU on the new
active CP and the original firmware is
restored on both CPUs.
2.
Both CPUs on both CPs will have the
original firmware.
Restart
firmwareDownload
after the repair is
done.
5
During
step 4
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
.
2.
If the standby CP boots up,
firmwareCommit
will start on both
CPUs on the standby CP.
3.
Both CPUs on the standby CP will
have the new firmware, and both
CPUs on the active CP will have the
old firmware.
Determine why the
CPs fail to gain HA
sync and remedy it
before restarting
firmwaredownload
6
During
step 6
When downloading to
the main CPU of the
standby CP, if an error
occurs and the main
CPU reboots.
1.
When the main 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.