IBM Storwize V7000 Troubleshooting And Maintenance Manual page 164

562 • 576
6. If you are unable to find a Storwize V7000 node
canister with the same WWNN as the node canister
showing the error, use the SAN monitoring tools to
determine whether there is another device on the
SAN with the same WWNN. This device should not
be using a WWNN assigned to a Storwize V7000, so
you should follow the service procedures for the
device to change its WWNN. Once the duplicate
has been removed, restart the node canister.
562 The nodes hardware configuration does
not meet the minimum requirements
Explanation: The node hardware is not at the
minimum specification for the node to become active in
a cluster. This may be because of hardware failure, but
is also possible after a service action has used an
incorrect replacement part.
User response: Follow troubleshooting procedures to
fix the hardware:
1. It is not possible to service parts within the node
canister. Reseat the existing node canister to see
whether the problem fixes. If it does not, use the
hardware node canister remove and replace
procedures to change the node canister.
564 Too many machine code crashes have
occurred.
Explanation: The node has been determined to be
unstable because of multiple resets. The cause of the
resets can be that the system encountered an
unexpected state or has executed instructions that were
not valid. The node has entered the service state so that
diagnostic data can be recovered.
The node error does not persist across restarts of the
node machine code.
User response: Follow troubleshooting procedures to
reload the machine code:
1. Get a support package (snap), including dumps,
from the node, using the management GUI or the
service assistant.
2. If more than one node is reporting this error,
contact IBM technical support for assistance. The
support package from each node will be required.
3. Check the support site to see whether the issue is
known and whether a machine code upgrade exists
to resolve the issue. Update the cluster machine
code if a resolution is available. Use the manual
upgrade process on the node that reported the error
first.
4. If the problem remains unresolved, contact IBM
technical support and send them the support
package.
Possible Cause—FRUs or other:
v None
146
Storwize V7000: Troubleshooting, Recovery, and Maintenance Guide
565 The internal drive of the node is failing.
Explanation: The internal drive within the node is
reporting too many errors. It is no longer safe to rely
on the integrity of the drive. Replacement is
recommended.
User response: Follow troubleshooting procedures to
fix the hardware:
1. The drive of the node canister cannot be replaced
individually. Follow the hardware remove and
replace instructions to change the node canister.
Possible Cause—FRUs or other:
v Node canister (100%)
573 The node machine code is inconsistent.
Explanation: Parts of the node machine code package
are receiving unexpected results; there may be an
inconsistent set of subpackages installed, or one
subpackage may be damaged.
User response: Follow troubleshooting procedures to
reload the machine code.
1. Follow the procedure to run a node rescue.
2. If the error occurs again, contact IBM technical
support.
Possible Cause—FRUs or other:
v None
574 The node machine code is damaged.
Explanation: A checksum failure has indicated that
the node machine code is damaged and needs to be
reinstalled.
User response:
1. If the other nodes are operational, run node rescue;
otherwise, install new machine code using the
service assistant. Node rescue failures, as well as the
repeated return of this node error after
reinstallation, are symptomatic of a hardware fault
with the node.
Possible Cause—FRUs or other:
v None
576 The cluster state and configuration data
cannot be read.
Explanation: The node has been unable to read the
saved cluster state and configuration data from its
internal drive because of a read or medium error.
User response: Follow troubleshooting procedures to
fix the hardware:
1. The drive of the node canister cannot be replaced
individually. Follow the hardware remove and
replace instructions to change the node canister.