Brocade Communications Systems 8 Reference page 136

Fabric os message reference

Hide thumbs Also See for 8:

Table of Contents

<timestamp>, [BL-1003], <sequence-number>, FFDC, CRITICAL, <system-name>,

Faulting blade in slot <slot number>

Probable Cause

Indicates a faulty blade in the specified slot number.

Make sure that the blade is seated correctly. If the blade is seated correctly, restart or power cycle

Run the systemVerification command to verify that blade does not have hardware problems. To run

this command root access is required. Run the diagPost command to ensure that Power-On

Self-Test (POST) is enabled. Refer to the Fabric OS Command Reference for more information on

these commands.

If the message persists, replace the blade.

<timestamp>, [BL-1004], <sequence-number>, FFDC, CRITICAL, <system-name>,

Suppressing blade fault in slot <slot number>

Probable Cause

Indicates that the specified blade experienced a failure but was not faulted due to a user setting.

Restart or power cycle the blade, using the slotPowerOff and slotPowerOn commands.

Run the systemVerification command to verify that the blade does not have hardware problems. To

run this command root access is required. Run the diagPost command to ensure that Power-On

Self-Test (POST) is enabled. Refer to the Fabric OS Command Reference for more information on

these commands.

If the message persists, replace the blade.

<timestamp>, [BL-1006], <sequence-number>,, INFO, <system-name>, Blade <slot

number> NOT faulted. Peer blade <slot number> experienced abrupt failure.

Probable Cause

Indicates that the errors (mostly synchronization errors) on this blade are harmless. Probably, the

standby control processor (CP) blade connected to the active CP blade has experienced transitory

Use the haShow command to verify that the standby CP is healthy. If problem persists remove and

reinstall the faulty blade.

Fabric OS Message Reference

53-1001767-01

Chapters

Table of Contents