IBM Storwize V7000 Maintenance Manual page 149

install the second node canister in this enclosure.
Restart the node canister. The two node canister
should show node error 504 and the actions for that
error should be followed.
3. If you are sure this node canister came from the
enclosure that is being replaced, and that the
original partner canister has failed, continue
following the remove and replace procedure for an
enclosure chassis and configure the new enclosure.
Possible Cause-FRUs or other:
v None
507 No enclosure identity and no node state
Explanation: The node canister has been placed in a
replacement enclosure chassis. The node canister is also
a replacement, or has had all cluster state removed
from it.
User response: Follow troubleshooting procedures to
relocate the nodes to the correct location.
1. Check the status of the other node in the enclosure.
It should show node error 506. Unless it also shows
error 507, use these procedures to resolve the errors
on the other node.
2. If the other node in the enclosure is also reporting
507, the enclosure and both node canisters have no
state information. You should contact IBM technical
support. They will assist you in setting the
enclosure vital product data and running cluster
recovery.
Possible Cause-FRUs or other:
v None
508 Cluster identifier is different between
enclosure and node
Explanation: The node canister location information
shows it is in the correct enclosure, however the
enclosure has had a new cluster created on it since the
node was last shut down. Therefore, the cluster state
data stored on the node is not valid.
User response: Follow troubleshooting procedures to
relocate the nodes to the correct location.
1. Check whether a new cluster has been created on
this enclosure while this canister was not operating
or whether the node canister was recently installed
in the enclosure.
2. If this node canister is the one to be used in this
enclosure, you should follow the procedure to
remove cluster data from the node canister. It will
then join the cluster.
3. If this is not the node canister that you intended to
use, follow the hardware remove and replace
canister procedure to replace the node canister with
the intended one.
Note: If both nodes are reporting this node error, the
cause may be a damaged enclosure.
Possible Cause-FRUs or other:
v Service procedure error (90%)
v Enclosure chassis (10%)
509 The enclosure identity cannot be read.
Explanation: The canister was unable to read vital
product data (VPD) from the enclosure. The canister
requires this data to be able to initialize correctly.
User response: Follow troubleshooting procedures to
fix the error:
1. Follow the node canister reseat procedure to reseat
the canister.
2. If the error is still present after the canister has been
reseated, proceed to the hardware troubleshooting
procedures below.
a. Check errors reported on the other node canister
in this enclosure (the partner canister).
b. If it is reporting the same error, follow the
hardware remove and replace procedure to
replace the enclosure chassis.
c. If the partner canister is not reporting this error,
follow the hardware remove and replace
procedure to replace this canister.
Note: If a newly installed system has this error on both
node canister, the data that needs to be written to the
enclosure will not be available on the canisters, you
should contact IBM technical support for the WWNNs
to use.
Possible Cause-FRUs or other:
v Node canister (50%)
v Enclosure chassis (50%)
510 The detected memory size does not
match the expected memory size.
Explanation: The amount of memory detected in the
node canister is less than the expected memory. The
error code date shows the detected memory, in MB,
followed by the expected memory, in MB.
User response: Follow troubleshooting procedures to
fix the hardware:
1. Use the hardware remove and replace node canister
procedure to install a new node canister.
Possible Cause-FRUs or other:
v Node canister (100%)
523 The internal disk file system is
damaged.
Explanation: The node startup procedures have found
problems with the file system on the internal disk of
the node.
Chapter 9. Event reporting
507 • 523
133