Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53-1000853-01, June 2008)

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
1During
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.
2During
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.
3During
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.
4During
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.
5During
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
6During
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.