Error Code Range; Node Errors; Message Classification Number Range - IBM Storwize V7000 Troubleshooting And Maintenance Manual

500 • 501
Cluster recovery codes
You must perform software problem analysis before you can perform further cluster operations to avoid
the possibility of corrupting your cluster configuration.

Error code range

This topic shows the number range for each message classification.
Table 20 lists the number range for each message classification.
Table 20. Message classification number range
Message classification

Node errors

Cluster recovery
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.
Possible Cause-FRUs or other:
v None
501 Incorrect slot
76
Storwize V7000 Version 6.1.0: Troubleshooting, Recovery, and Maintenance Guide
Range
Critical node errors
Noncritical node errors
920, 990
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.
1. Review the saved location information of the node
2. If the canisters have been swapped, use the
3. If the partner canister is in candidate state, use the
4. If the partner canister is in active state, it is running
5. If the partner canister is in service state, review its
Possible Cause-FRUs or other:
v None
500-699
800-899
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.
hardware remove and replace canister procedure to
swap the canisters. The system should start.
hardware remove and replace canister procedure to
swap the canisters. The system should start.
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.
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.