BL-1007
Message
<timestamp>, [BL-1007], <sequence-number>,, WARNING, <system-name>, blade #<blade
number>: blade state is inconsistent with EM. bl_cflags 0x<blade control flags>,
slot_on <slot_on flag>, slot_off <slot_off flag>, faulty <faulty flag>, status
<blade status>.
Probable Cause
Indicates that a failover occurred while a blade was initializing on the previously active control
processor (CP).
Recommended
No action is required. The blade is reinitialized. Because reinitializing a blade is a disruptive
Action
operation and can stop I/O traffic, you might have to stop and restart the traffic during this process.
Severity
WARNING
BL-1008
Message
<timestamp>, [BL-1008], <sequence-number>, FFDC, CRITICAL, <system-name>, Slot
<slot number> control-plane failure. Expected value: 0x<value 1>, Actual: 0x<value
2>.
Probable Cause
Indicates that the blade has experienced a hardware failure or was removed without following the
recommended removal procedure.
Recommended
Make sure that the blade is seated correctly.
Action
If the blade is seated correctly, restart or power cycle the blade.
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.
Severity
CRITICAL
BL-1009
Message
<timestamp>, [BL-1009], <sequence-number>, FFDC, CRITICAL, <system-name>, Blade
in slot <slot number> timed out initializing the chips.
Probable Cause
Indicates that the blade has failed to initialize the application-specific integrated circuit (ASIC)
chips.
Recommended
Make sure that the blade is seated correctly.
Action
If the blade is seated correctly, reboot or power cycle the blade.
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.
Severity
CRITICAL
Fabric OS Message Reference
53-1002448-01
7
BL-1007
73