Sulb-1010; Sulb-1011; Sulb-1017; Sulb-1018 - Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base Reference

SULB-1010

Message
<timestamp>, [SULB-1010], <sequence-number>, AUDIT, INFO, <system-name>,
Firmwarecommit failed (status=0x
Probable Cause Indicates that the firmwareCommit failed. The error code provides debugging information. See
Table
Recommended If the failure is caused by an inconsistent filesystem, contact your switch service provider.
Action
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 Run the firmwareDownloadStatus command for more information.
Action
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
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 Run the slotShow command. If the blade is in a FAULTY state, run the slotPowerOff and
Action 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
Fabric OS Message Reference
53-1000437-01
7for more information.
<error code>
).
<Slot number> .
<
Slot number>
.
66
SULB-1010
407