Off |
(any) |
(any) |
Power is not being provided by any power supply unit (PSU) in the enclosure,
or power is coming from the battery in the canister. If at least one PSU is powering the
enclosure, the canister or the enclosure midplane might be faulty.
If both node canisters in
an enclosure indicate this state at the same time, it is more likely that the enclosure midplane is
faulty. Reseat any node canister in this state.
|
Blinking slowly |
Power is available, but the canister is powered off. The main CPU is not
running. Restart the node canister.
|
Blinking fast |
The node canister is doing a self test during start-up. Wait for the
canister to complete its start-up sequence.
|
On |
Off |
Off |
The node canister is in standby mode. The system software is not running. Restart the node canister.
|
Blinking |
The node canister is in candidate state. The node is not doing I/O in the
system.Unless indicated by the battery status LED, it is safe to remove or reseat the canister.
See Table 3.
If the node state is candidate and
the system is running on the other node canister, the candidate node is automatically added to the
system.
If both node canisters are in candidate state, determine whether you must recover the
system or create a new system.
|
Blinking fast |
The node is doing an emergency shutdown operation, using the battery for
power, after detecting a loss of power from the power supply units. Wait for the emergency
shutdown operation to complete. If the partner node has also done an emergency shutdown operation,
there was most likely a loss of input power to both enclosure power supply units and the system
restarts when the input power is restored. Otherwise, there might be a fault the node canister,
enclosure midplane, or power supply units.
|
On |
The system software
is running, and the node canister is participating in the system. The canister must not be
removed.
This is the normal operational LED state.
|
On |
Blinking |
Off |
The node canister is in standby mode. The system software is not running. It is safe to
remove or reseat the canister.
|
Blinking |
The Identify function for this canister has been activated. To determine if it
is safe to remove the canister, use the management GUI or service assistant to turn off the
Identify function, then check the node canister status LEDs again. |
On |
Blinking |
Blinking fast |
The Identify function for this canister has been activated. The node is
doing an emergency shutdown operation, using the battery for power, after detecting a loss of power
from the power supply units.
Wait for the emergency shutdown operation to complete. If the
partner node has also done an emergency shutdown operation, there was most likely a loss of input
power to both enclosure power supply units and the system restarts when the input power is restored.
Otherwise, there might be a fault in the power supply units or the node canister.
|
On |
Blinking |
On |
The Identify function for this canister was activated. To determine if it is
safe to remove the canister, use the management GUI or service assistant to turn off the
Identify function, then check the node canister status LEDs, again.
|
On |
On |
Off |
The system software
is not running. The BIOS might have detected a fault. It is safe to remove or reseat the
canister.
Try reseating the canister. If the canister still shows this fault, replace the node
canister.
|
On |
On |
Blinking |
The node is in service state. It is safe to remove or reseat the
canister.See Table 3 to determine whether the
battery charge is insufficient.
Use the service assistant to identify any node errors or to
determine what to do, see Procedure: Fixing node errors.
If the node is able
to communicate with the configuration node, there might also be an error alert in the system event
log, in which case you should run the associated fix procedure.
|
On |
On |
Blinking fast |
The node is in service state. There is a code update in progress.
The canister must not be
removed.
No action is required until the code update completes.
|
On |
On |
On |
The software is
running but there might be an error alert in the event log, such as error code 550. The canister
must not be removed.
If possible, go to the management GUI and run the fix procedure for the
error alerts listed there. If this is not possible, refer to the service actions for node error
550.
|