Node Errors; Message Classification Number Range - IBM Storwize V7000 Maintenance Manual

Node errors

500 Incorrect enclosure
Explanation: The node canister has saved cluster
information, which indicates that the canister is now
located in a different enclosure chassis from where it
was previously used. Using the node canister in this
state might corrupt the data held on the enclosure
drives.
User response: Follow troubleshooting procedures to
relocate the nodes to the correct location.
1. Review the saved location information of the node
canister and the status of the other node canister in
the enclosure (the partner canister). Determine
whether the enclosure is part of an active system
with volumes that contain required data.
2. If you have unintentionally moved the canister into
this enclosure, move the canister back to its original
location, and put the original canister back in this
enclosure. Follow the hardware remove and replace
canister procedures.
3. If you have intentionally moved the node canister
into this enclosure, check whether it is safe to
continue or whether a loss of data can result. Do
not continue if any of the following conditions
apply, contact IBM technical support instead:
a. You require the volume data on the system from
which the node canister was removed, and that
system is not running with two online nodes.
b. You require the volume data on this system, and
the partner node is not online.
4. If you have determined that the node canister can
be used in this location, follow procedures to
remove cluster data from the node canister.
Possible Cause-FRUs or other:
v None
501 Incorrect slot
Explanation: The node canister has saved cluster
information, which indicates that the canister is now
located in the expected enclosure chassis, but in a
different slot from where it was previously used. Using
the node canister in this state might mean that hosts
are not able to connect correctly.
User response: Follow troubleshooting procedures to
relocate the nodes to the correct location.
Table 27. Message classification number range (continued)
Message classification
Error codes when
recovering a clustered
system
Range
920, 990
1. Review the saved location information of the node
canister and the status of the other node canister in
the enclosure (the partner canister). If the node
canister has been inadvertently swapped, the other
node canister will have the same error.
2. If the canisters have been swapped, use the
hardware remove and replace canister procedure to
swap the canisters. The system should start.
3. If the partner canister is in candidate state, use the
hardware remove and replace canister procedure to
swap the canisters. The system should start.
4. If the partner canister is in active state, it is running
the cluster on this enclosure and has replaced the
original use of this canister. You must follow the
procedure to remove cluster data from this node
canister. The node canister will then become active
in the cluster in its current slot.
5. If the partner canister is in service state, review its
node error to determine the correct action.
Generally, you will fix the errors reported on the
partner node in priority order, and review the
situation again after each change. If you have to
replace the partner canister with a new one you
should move this canister back to the correct
location at the same time.
Possible Cause-FRUs or other:
v None
502 No enclosure identity exists and a status
from the partner node could not be
obtained.
Explanation: The enclosure has been replaced and
communication with the other node canister (partner
node) in the enclosure is not possible. The partner node
could be missing, powered off or unable to boot, or an
internode communication failure may exist.
User response: Follow troubleshooting procedures to
fix the hardware:
1. Follow the service procedures to get the partner
node started. An error will still exist because the
enclosure has no identity. If the error has changed,
follow the service procedure for that error.
2. If the partner has started and is showing a location
error (probably this one), then the PCI link is
probably broken. Since the enclosure chassis was
recently replaced, this is likely the problem. Obtain
500 • 502
Chapter 9. Event reporting
131