Brocade Error Message Reference Guide v6.0.0 (53-1000600-01, April 2008)

Fabric OS Message Reference 443
53-1000600-01
SULB-1022
69
Recommended
Action
Run the firmwareDownloadStatus command to monitor the firmwareDownload progress. After it
finishes, run the firmwareShow command to verify the firmware versions.
Severity WARNING
SULB-1022
Message <timestamp>, [SULB-1022], <sequence-number>,, WARNING, <system-name>, The blade
in slot
<Slot number> has rebooted successfully with new firmware.
Probable Cause Indicates that the blade in the specified slot has rebooted with new firmware. This is a normal step
in the firmwareDownload process.
Recommended
Action
Run the firmwareDownloadStatus command to monitor the firmwareDownload progress.
Severity WARNING
SULB-1023
Message <timestamp>, [SULB-1023], AUDIT, WARNING, <system-name>, The blade in slot <Slot
number>
has rebooted during firmwaredownload.
Probable Cause The error may be caused by an unexpected disruption of the firmwareDownload command, for
example, by powering off and on of the indicated BP blade in the middle of a firmwareDownload.
The error may also be caused by persistent storage hardware failure or by a software error.
Recommended
Action
firmwareCommit will be started automatically after the blade boots up to repair the secondary
partition. If at the end of firmwareCommit, the blade firmware version is still inconsistent with the
active CP firmware, firmwareDownload will automatically be restarted on the blade. Run the
firmwareDownloadStatus command to monitor the progress. If the problem persists, contact your
switch service provider.
Severity WARNING
SULB-1024
Message <timestamp>, [SULB-1024], AUDIT, WARNING, <system-name>, Firmware commit has
completed on the blade in slot
<Slot number>.
Probable Cause Indicates that the firmwareCommit operation has completed on the specified blade.
Recommended
Action
Run the firmwareShow command to verify the firmware versions. If the blade firmware is the same
as the active CP firmware, firmwareDownload has completed successfully on the blade. However, if
the firmwareCommit operation has been started to repair the secondary partition, at the end of
firmwareCommit, the blade firmware version may still be inconsistent with the active CP firmware.
In that case, firmwareDownload will automatically be restarted on the blade. Run the
firmwareDownloadStatus command to monitor the progress.