Brocade Fabric OS Message Reference - Supporting Fabric OS v5.3.0 (53-1000437-01, June 2007)

408 Fabric OS Message Reference
53-1000437-01
SULB-1020
66
Probable Cause The error may be caused by a blade initialization issue after the new firmware is downloaded and
the blade is rebooted. The error may also be caused by an internal Ethernet issue or by a persistent
storage failure.
Recommended
Action
Run the slotShow command. If the blade is in FAULTY state, run the slotPowerOff and slotPowerOn
commands to trigger another firmwareDownload. If the blade is stuck in LOADING state, remove
and re-insert the blade to trigger another firmwareDownload. If the problem persists, contact your
switch service provider.
Severity ERROR
SULB-1020
Message <timestamp>, [SULB-1020], AUDIT, ERROR, <system-name>, New firmware failed to boot
in slot
<Slot number>.
Probable Cause The BP blade should reboot with the new image, but is still running the old image. This error may
indicate that the new image has not been loaded correctly to the specified blade.
Recommended
Action
Run the slotShow command. If the blade is in a FAULTY state, run the slotPowerOff and
slotPowerOn commands to trigger another firmwareDownload to the blade. If the blade is stuck in
LOADING state, remove and re-insert the blade to trigger another firmwareDownload. If the
problem persists, contact your switch service provider.
Severity ERROR
SULB-1021
Message <timestamp>, [SULB-1021],<sequence-number>, AUDIT, WARNING, <system-name>,
Firmware is being downloaded to the blade in slot
<Slot number>.
Probable Cause Indicates that the firmware is being loaded to the indicated blade.
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.