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. Follow Procedure: Reseating a node canister to reseat any node canister in this state. If the condition
persists, follow Replacing a node canister if just one canister is affected,
or Replacing a control enclosure midplane if both canisters are affected.
|
Blinking slowly |
Power is available, but the canister is powered
off. The main CPU is not running.
To restart the node canister,
follow Procedure: Reseating a node canister.
|
Blinking fast |
The node canister is performing self test
during startup.
Wait for the canister to complete its startup
sequence.
|
On |
Off |
Off |
The node canister is in standby mode. Thesystem software is not running.
It is safe to remove or reseat the canister.
To restart the node canister, follow Procedure: Reseating a node canister.
|
Blinking |
The node canister is in candidate state.
The node is not performing I/O in the system.
Unless indicated
by the battery status LED (see Table 4), it is safe to remove or reseat the canister.
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 need to recover the system or create a new system.
|
Blinking fast |
A code update is in progress.
The canister must not be removed. No user action is required.
|
On |
Thesystem software is running, and the node canister is participating in the system.
The LED state indicates normal system operation.
The canister
must not be removed.
|
Off |
Blinking |
The node canister is in standby mode. Thesystem software is not running.
It is safe to remove or reseat the canister.
|
Blinking |
The Identify function for this canister was
activated. To determine whether 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. |
Blinking fast |
The Identify function for this canister was
activated. A code update is in progress.
The canister must not be removed.
|
On |
The Identify function for this canister was
activated.
To determine whether 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.
|
Off |
On |
Thesystem software is not running. The BIOS might have detected a fault.
It is
safe to remove or reseat the canister.
Try reseating the canister
by following Procedure: Reseating a node canister. If the canister still shows this
fault, follow Replacing a node canister.
|
Blinking |
The node is in service state. It is safe
to remove or reseat the canister.
Refer to Table 4 to determine whether the battery charge is insufficient.
Use the service assistant to identify any node errors or refer
to Procedure: Fixing node errors to determine what to do.
If
the node is able to communicate with the configuration node, there
might also be an error alert in the system event log. In this case,
you should run the associated fix procedure.
|
Blinking fast |
The node is in service state.
A code update is in progress.
The canister must not be removed.
No action is required until
the code update completes.
|
On |
Thesystem software is running. However, the event log might contain an alert, 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. Otherwise,
refer to the service actions for node error 550.
|