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

Fabric OS Message Reference 407
53-1000437-01
SULB-1010
66
SULB-1010
Message <timestamp>, [SULB-1010], <sequence-number>, AUDIT, INFO, <system-name>,
Firmwarecommit failed (status=0x
<error code>).
Probable Cause Indicates that the firmwareCommit failed. The error code provides debugging information. See
Table 7for more information.
Recommended
Action
If the failure is caused by an inconsistent filesystem, contact your switch service provider.
Severity INFO
SULB-1011
Message <timestamp>, [SULB-1011], <sequence-number>,, INFO, <system-name>,
Firmwaredownload command failed. state: 0x<state code>, status: 0x<status code>.
Probable Cause Indicates that the firmwareDownload command failed. The additional state code indicates where
in the process it failed. Status code provides debugging information (see the tables in message
1109).
Recommended
Action
Run the firmwareDownloadStatus command for more information.
Refer to the Fabric OS Administrator’s Guide for troubleshooting information.
Severity INFO
SULB-1017
Message <timestamp>, [SULB-1017], <sequence-number>, AUDIT, ERROR, <system-name>,
Firmwaredownload failed in slot
<Slot number>.
Probable Cause Indicates that firmwareDownload failed in the specified blade. The error may be caused by an
inconsistent AP blade firmware stored on the active CP. It may also caused by an internal Ethernet
issue or by a persistent storage hardware failure.
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-1018
Message <timestamp>, [SULB-1018], <sequence-number>, AUDIT, ERROR, <system-name>,
Firmwaredownload timed out in slot
<Slot number>.