IBM Storwize V7000 Troubleshooting And Maintenance Manual page 167

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%)
674 The cycling mode of a Metro Mirror
object cannot be changed.
Explanation: The cycling mode may only be set for
Global Mirror objects. Metro Mirror objects cannot have
a cycling mode defined.
User response: The object's type must be set to 'global'
before or when setting the cycling mode.
677 System code upgrade cannot start
because a component firmware update
is in progress.
Explanation: An attempt was made to initiate an
system code upgrade (CCU) while the system was
updating the firmware of various hardware
components. A CCU can not be done while a firmware
download is in progress and so the request to start a
CCU failed.
User response: The firmware download needs to
complete before you can perform a CCU. Due to the
dynamic nature of firmware downloads there is no way
of following the progress of one. Wait approximately 10
minutes and retry the command.
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
either because of a service assistant user action or
because the node was deleted from the cluster.
User response: When it is no longer necessary to hold
the node in the service state, exit the service state to
allow the node to run:
1. Use the service assistant action to release the service
state.
Possible Cause—FRUs or other:
v none
700 The Fibre Channel adapter that was
previously present has not been
detected.
Explanation: A Fibre Channel adapter that was
previously present has not been detected. For Storwize
V7000, the adapter is located on the node canister
system board.
This node error does not, in itself, stop the node
canister from becoming active in the system; however,
the Fibre Channel network might be being used to
communicate between the node canisters in a clustered
system. It is possible that this node error indicates why
the critical node error 550 A cluster cannot be formed
because of a lack of cluster resources is reported
on the node canister.
Data:
v Location—A number indicating the adapter location.
Location 0 indicates the adapter integrated into the
system board is being reported.
User response:
Chapter 9. Event reporting
673 • 700
149