IBM Storwize V7000 Troubleshooting And Maintenance Manual page 161

Hide thumbs Also See for Storwize V7000:
Table of Contents

Advertisement

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, check the errors on the other node and
follow the corresponding procedures to resolve the
errors.
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
correctly relocate the nodes.
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. Follow the procedure: Get node canister and system
information using the service assistant, and check
the partner node canister to see if it is also
reporting node error 508; if it is, check that the
saved system information on this and the partner
node match. See "Procedure: Getting node canister
and system information using the service assistant"
on page 53.
3. If this node canister is the one to be used in this
enclosure, follow "Procedure: Removing system
data from a node canister" on page 59 to remove
cluster data from the node canister. It will then join
the cluster.
4. If this is not the node canister that you intended to
use, follow the "Replacing a node canister" on page
85 procedure to replace the node canister with the
one intended for use.
Possible Cause—FRUs or other:
v Service procedure error (90%)
v Enclosure midplane (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 hardware:
1. Check errors reported on the other node canister in
this enclosure (the partner canister).
2. If it is reporting the same error follow the hardware
remove and replace procedure to replace the
enclosure midplane.
3. 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 support for the WWNNs to use.
Possible Cause—FRUs or other:
v Node canister (50%)
v Enclosure midplane (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 amount required for the
canister to operate as an active member of a system.
The error code data shows the detected memory (in
MB) followed by the minimum required memory (in
MB). A series of values indicates the amount of
memory (in GB) detected in each memory slot.
Data:
v Detected memory on MB
v Minimum required memory in MB
v Memory in slot 1 in GB
v Memory in slot 2 in GB
v ... etc.
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%)
522
The system board service processor has
failed.
Explanation: The service processor (PSOC) in the
canister has failed or is not communicating.
User response:
1. Reseat the node canister.
2. If the error persists, use the remove and replace
procedures to replace the node canister.
Possible Cause—FRUs or other:
v Node canister
Chapter 9. Event reporting
508 • 522
143

Advertisement

Table of Contents
loading

Table of Contents