Brocade Fabric OS Message Reference - Supporting Fabric OS v7.0.1 (53-1002448-01, March 2012)

860 Fabric OS Message Reference
53-1002448-01
SULB-1010
137
In a director-class switch, when firmwareDownload fails, the two CPs may end up with different
versions of firmware and they may not gain high-availability (HA) sync. In that case, run
firmwareDownload single mode (-s) to upgrade the firmware on the standby CP to the same version
as the active CP. Then retry firmwareDownload to download the desired version of firmware onto
the CPs.
Refer to the Fabric OS Administrator’s Guide for troubleshooting information.
Severity INFO
SULB-1010
Message <Sequence Number> AUDIT, <timestamp>, [SULB-1010], INFO, FIRMWARE,
<event-initiator-details>, <event-location>, , Firmwarecommit failed (status=0x
<error code>).
Probable Cause Indicates the firmwareCommit command has failed. The error code provides debugging
information. See Table 12 for more information.
Recommended
Action
If the failure is caused by an inconsistent filesystem, contact your switch service provider.
Severity INFO
SULB-1017
Message <Sequence Number> AUDIT, <timestamp>, [SULB-1017], ERROR, FIRMWARE,
<event-initiator-details>, <event-location>, , Firmwaredownload failed in slot
<Slot number>.
Probable Cause Indicates the firmwareDownload command has failed in the specified blade. The error may be
caused by an inconsistent AP blade firmware stored on the active CP. It may also be caused by an
internal Ethernet issue or by a persistent storage hardware failure.
Recommended
Action
Run the slotShow command. If the blade is in 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-1018
Message <Sequence Number> AUDIT, <timestamp>, [SULB-1018], ERROR, FIRMWARE,
<event-initiator-details>, <event-location>, , Firmwaredownload timed out in slot
<Slot number>.
Probable Cause Indicates there may be an error 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.