500 Incorrect enclosure
Explanation: The node canister has saved cluster
information, which indicates that the canister is now
located in a different enclosure 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
move the nodes to the correct location.
1. Follow the procedure: Getting node canister and
system information and review the node canister's
saved location information and the status of the
other node canister in the enclosure (the partner
canister). Determine if the enclosure is part of an
active system with volumes that contain required
data. See “Procedure: Getting node canister and
system information using the service assistant” on
page 53.
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 “Replacing a node canister”
on page 85 procedure.
3. If you have intentionally moved the node canister
into this enclosure you should check it is safe to
continue or whether you will lose data on the
enclosure you removed it from. Do not continue if
the system the node canister was removed from is
offline, rather return the node canister to that
system.
4. If you have determined it is alright to continue,
follow the procedure to remove cluster data from
node canister. See “Procedure: Removing system
data from a node canister” on page 59.
5. If the partner node in this enclosure is not online, or
is not present, you will have to perform a system
recovery. Do not create a new system, you will lose
all the volume data.
Possible Cause-FRUs or other cause:
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, 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 node canister to the correct location.
1. Follow the procedure: Getting node canister and
system information and 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. See “Procedure: Getting node canister
and system information using the service assistant”
on page 53.
2. If the canisters have been swapped, use the
“Replacing a node canister” on page 85 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. See “Procedure:
Removing system data from a node canister” on
page 59.
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, unable to boot, or an
internode communication failure may exist.
User response: Follow troubleshooting procedures to
configure the enclosure:
1. Follow the procedures to resolve a problem 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 midplane was
recently replaced, this is likely the problem. Obtain
a replacement enclosure midplane, and replace it.
See “Replacing a control enclosure chassis” on page
108.
3. If this action does not resolve the issue, contact IBM
Support Center. They will work with you to ensure
that the system state data is not lost while resolving
the problem. Also see Chapter 6, “Resolving a
problem,” on page 43.
500 • 502
Chapter 9. Event reporting 141
To Next Page
Loading...
Need help?
General
