Fabric OS Message Reference v6.4.0 (53-1001767-01, June 2010)

Fabric OS Message Reference 747
53-1001767-01
SULB-1020
128
Recommended
Action
Run the slotShow command. If the blade is in a 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 AUDIT, <timestamp>, [SULB-1020], ERROR, FIRMWARE, <event-initiator-details>,
<event-location>, , New firmware failed to boot in slot
<Slot number>.
Probable Cause Indicates the BP blade should restart 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 AUDIT, <timestamp>, [SULB-1021], WARNING, FIRMWARE, <event-initiator-details>,
<event-location>, , Firmware is being downloaded to the blade in slot
<Slot
number>.
Probable Cause Indicates the firmware is being loaded to the specified 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-1023
Message AUDIT, <timestamp>, [SULB-1023], WARNING, FIRMWARE, <event-initiator-details>,
<event-location>, , The blade in slot
<Slot number> has rebooted during
firmwaredownload.
Probable Cause Indicates there may be an error 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.