Sulb-1024; Sulb-1026; Sulb-1030 - Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base Reference Manual

86

SULB-1024

Recommended firmwareCommit will be started automatically after the blade boots up to repair the secondary
Action partition. If at the end of firmwareCommit, the blade firmware version is still inconsistent with the
active CP firmware, firmwareDownload will automatically be restarted on the blade. Run the
firmwareDownloadStatus command to monitor the progress. If the problem persists, contact your
switch service provider.
Severity WARNING
SULB-1024
Message
AUDIT, <timestamp>, [SULB-1024], WARNING, FIRMWARE, <event-initiator-details>,
<event-location>, , Firmware commit has completed on the blade in slot
number>.
Probable Cause Indicates that the firmwareCommit operation has completed on the specified blade.
Recommended Run the firmwareShow command to verify the firmware versions. If the blade firmware is the same
Action as the active CP firmware, firmwareDownload has completed successfully on the blade. However, if
the firmwareCommit operation has been started to repair the secondary partition, at the end of
firmwareCommit, the blade firmware version may still be inconsistent with the active CP firmware.
In that case, firmwareDownload will automatically be restarted on the blade. Run the
firmwareDownloadStatus command to monitor the progress.
Severity WARNING

SULB-1026

Message
AUDIT, <timestamp>, [SULB-1026], WARNING, FIRMWARE, <event-initiator-details>,
<event-location>, , Firmware commit operation started on the blade in slot
number>
Probable Cause firmwareCommit has started on the specified blade. The operation may be a normal part of
firmwareDownload, or it may have started to repair the secondary partition of the blade if the
secondary partition is corrupted.
Recommended Wait for the commit operation to complete.
Action
Severity WARNING

SULB-1030

Message
AUDIT, <timestamp>, [SULB-1030], WARNING, FIRMWARE, <event-initiator-details>,
<event-location>, , The switch has rebooted during relocating the internal
firmware image.
Probable Cause The error may be caused by an unexpected disruption of the firmwareDownload command, for
example, by powering the switch off and on in the middle of a firmwareDownload. The error may
also be caused by persistent storage hardware failure or by a software error.
526
.
<Slot
<Slot
Fabric OS Message Reference
53-1000600-01