IBM Storwize V7000 Maintenance Manual page 153

4. If all nodes have either node error 578 or 550,
follow the cluster recovery procedures.
5. Attempt to determine what caused the nodes to
shut down.
Possible Cause-FRUs or other:
v None
671 The available battery charge is not
enough to allow the node canister to
start. Two batteries are charging.
Explanation: The battery charge within the enclosure
is not sufficient for the node to safely become active in
a cluster. The node will not start until sufficient charge
exists to store the state and configuration data held in
the node canister memory if power were to fail. Two
batteries are within the enclosure, one in each of the
power supplies. Neither of the batteries indicate an
error–both are charging.
The node will start automatically when sufficient
charge is available. The batteries do not have to be
fully charged before the nodes can become active.
Both nodes within the enclosure share the battery
charge, so both node canisters report this error.
The service assistant shows the estimated start time in
the node canister hardware details.
Possible Cause-FRUs or other:
v None
User response: Wait for the node to automatically fix
the error when sufficient charge becomes available.
Possible Cause-FRUs or other:
v None
672 The available battery charge is not
enough to allow the node canister to
start. One battery is charging.
Explanation: The battery charge within the enclosure
is not sufficient for the node to safely become active in
a cluster. The node will not start until sufficient charge
exists to store the state and configuration data held in
the node canister memory if power were to fail. Two
batteries are within the enclosure, one in each of the
power supplies. Only one of the batteries is charging,
so the time to reach sufficient charge will be extended.
The node will start automatically when sufficient
charge is available. The batteries do not have to be
fully charged before the nodes can become active.
Both nodes within the enclosure share the battery
charge, so both node canisters report this error.
The service assistant shows the estimated start time,
and the battery status, in the node canister hardware
details.
Possible Cause-FRUs or other:
v None
User response:
1. Wait for the node to automatically fix the error
when sufficient charge becomes available.
2. If possible, determine why one battery is not
charging. Use the battery status shown in the node
canister hardware details and the indicator LEDs on
the PSUs in the enclosure to diagnose the problem.
If the issue cannot be resolved, wait until the cluster
is operational and use the troubleshooting options
in the management GUI to assist in resolving the
issue.
Possible Cause-FRUs or other:
v Battery (33%)
v Control power supply (33%)
v Power cord (33%)
673 The available battery charge is not
enough to allow the node canister to
start. No batteries are charging.
Explanation: A node cannot be in active state if it
does not have sufficient battery power to store
configuration and cache data from memory to internal
disk after a power failure. The system has determined
that both batteries have failed or are missing. The
problem with the batteries must be resolved to allow
the system to start.
User response: Follow troubleshooting procedures to
fix hardware:
1. Resolve problems in both batteries by following the
procedure to determine status using the LEDs.
2. If the LEDs do not show a fault on the power
supplies or batteries, power off both power supplies
in the enclosure and remove the power cords. Wait
20 seconds, then replace the power cords and
restore power to both power supplies. If both node
canisters continue to report this error replace the
enclosure chassis.
Possible Cause-FRUs or other:
v Battery (33%)
v Power supply (33%)
v Power cord (33%)
v Enclosure chassis (1%)
690 The node is held in the service state.
Explanation: The node is in service state and has been
instructed to remain in service state. While in service
state, the node will not run as part of a cluster. A node
must not be in service state for longer than necessary
while the cluster is online because a loss of redundancy
will result. A node can be set to remain in service state
Chapter 9. Event reporting
671 • 690
137